Sorry to repost, but not sure if this is a bug or just the way V3 works now?
My scene seems to take over two and half time the VRAM than it did in V1, and now crashes my PC. If this is a bug/leak which can be fixed then great, but if this is just the way Octane is now programmed to work, I need to know....
viewtopic.php?f=27&t=55563
Octane 3 memory leak?
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Hi,
V3 does have a lot more to process than previous versions. The consequences of this, is that simpler scenes may take longer. The performance payoff can be seen in more intensive scenes, especially scenes that take advantage of the latest V3 features. This is in direct comparison to 2.24, so the difference would be even more so between v1 and v3.
How complex are your scenes? Are you applying any of the new v3 features to your scene?
V3 does have a lot more to process than previous versions. The consequences of this, is that simpler scenes may take longer. The performance payoff can be seen in more intensive scenes, especially scenes that take advantage of the latest V3 features. This is in direct comparison to 2.24, so the difference would be even more so between v1 and v3.
How complex are your scenes? Are you applying any of the new v3 features to your scene?
I posted directly to your thread. To recap, in order for Octane to support important features added after 1.0 - e.g. motion blur, multiple UV coordinate sets, fur, displacement etc, the core mesh/scene memory footprint has had to increase somewhat over time.
That span of time is not small - Octane 1.0 was released almost 4 years ago. Today, GPU memory is generally higher, and with V3, we fully support CPU memory for textures, film buffers and render passes without much of a speed hit. CPU offloading of data does provide significant savings in GPU memory for many scenes in V3.
If you could share your scene with us, i think we should still run a quick test on our end.
I'd like to at least confirm that what you are seeing is not the result of some bug or optimization pass we may have missed. It could also give some better insight into optimizations we might consider in the future for these kinds of scenes. User feedback on this topic is always welcome.
That span of time is not small - Octane 1.0 was released almost 4 years ago. Today, GPU memory is generally higher, and with V3, we fully support CPU memory for textures, film buffers and render passes without much of a speed hit. CPU offloading of data does provide significant savings in GPU memory for many scenes in V3.
If you could share your scene with us, i think we should still run a quick test on our end.
I'd like to at least confirm that what you are seeing is not the result of some bug or optimization pass we may have missed. It could also give some better insight into optimizations we might consider in the future for these kinds of scenes. User feedback on this topic is always welcome.
Thank you for the responses
The scene doesn't take advantage of any of those features as I'm opening the exact same max file which I made with V1 of octane. The scene is actually very simple. It's a single teddy bear but covered in fur which has been converted into a mesh in 3DSmax using the standard hair and fur tools. So the poly count of the hairs brings it up to around 24 million polys. The fur is meshed and linked to the underlying object (so octane doesn't have to re process the fur every frame).
When V2 came out it didn't support this amount of polys, so I reduced the fur by over 50% and instead supplemented it with displacement maps. It looked ok, but not as good as the bear I had working with V1. But I was able to get motion blur and use render passes which was needed. So I was waiting for the limit to be removed in v3 so I could go back to rendering my original full fur bear but with the motion blur and render passes too.
I understand there are new features, but to me it's a marked different to go from 2.5GB to over 6GB VRAM (and no longer fit into memory) for an object that uses none of these features. My system has 32GB ram and yet I've noticed I get warnings to close 3DSMax as it's running low on memory when I use V3 with a lot of my V2 scenes - something I never experienced before. As a rule of thumb, what should I be expecting to see? Do most scenes now take up 2.5x the VRAM as before? Some kind of ballpark would be helpful.
I have uninstalled V3 and gone back to V2. I was also experiencing a lot of hangs/viewport freezes in V3 (seems to take longer for the viewport to even open). One scene that did open with V2 now just stays on the 'evaluating scene' screen so I've no choice but to go back to the older version. I would normally spend days testing this kind of thing, finding out exactly where it breaks and under what circumstances but unfortunately I just don't have the time to do that right now, I need to get on with the work so I have to stick with V2.
I'm afraid Ive never used ORBX I do not even have standalone installed on my system, sorry. But I am happy to send the max scene (with the meshed fur it's over 1GB) if that would help you.
The scene doesn't take advantage of any of those features as I'm opening the exact same max file which I made with V1 of octane. The scene is actually very simple. It's a single teddy bear but covered in fur which has been converted into a mesh in 3DSmax using the standard hair and fur tools. So the poly count of the hairs brings it up to around 24 million polys. The fur is meshed and linked to the underlying object (so octane doesn't have to re process the fur every frame).
When V2 came out it didn't support this amount of polys, so I reduced the fur by over 50% and instead supplemented it with displacement maps. It looked ok, but not as good as the bear I had working with V1. But I was able to get motion blur and use render passes which was needed. So I was waiting for the limit to be removed in v3 so I could go back to rendering my original full fur bear but with the motion blur and render passes too.
I understand there are new features, but to me it's a marked different to go from 2.5GB to over 6GB VRAM (and no longer fit into memory) for an object that uses none of these features. My system has 32GB ram and yet I've noticed I get warnings to close 3DSMax as it's running low on memory when I use V3 with a lot of my V2 scenes - something I never experienced before. As a rule of thumb, what should I be expecting to see? Do most scenes now take up 2.5x the VRAM as before? Some kind of ballpark would be helpful.
I have uninstalled V3 and gone back to V2. I was also experiencing a lot of hangs/viewport freezes in V3 (seems to take longer for the viewport to even open). One scene that did open with V2 now just stays on the 'evaluating scene' screen so I've no choice but to go back to the older version. I would normally spend days testing this kind of thing, finding out exactly where it breaks and under what circumstances but unfortunately I just don't have the time to do that right now, I need to get on with the work so I have to stick with V2.
I'm afraid Ive never used ORBX I do not even have standalone installed on my system, sorry. But I am happy to send the max scene (with the meshed fur it's over 1GB) if that would help you.
Windows 7 64bit/ Intel 3930K/ ASUS Rampage IV/ GTX980ti x 2/ 64GB system RAM
Please send the Max scene via a PM to myself, Jim and Azen. Exporting to ORBX should work in all versions of the Max plug-in, it's a one click button in the Octane UX.
darkline wrote:Thank you for the responses
The scene doesn't take advantage of any of those features as I'm opening the exact same max file which I made with V1 of octane. The scene is actually very simple. It's a single teddy bear but covered in fur which has been converted into a mesh in 3DSmax using the standard hair and fur tools. So the poly count of the hairs brings it up to around 24 million polys. The fur is meshed and linked to the underlying object (so octane doesn't have to re process the fur every frame).
When V2 came out it didn't support this amount of polys, so I reduced the fur by over 50% and instead supplemented it with displacement maps. It looked ok, but not as good as the bear I had working with V1. But I was able to get motion blur and use render passes which was needed. So I was waiting for the limit to be removed in v3 so I could go back to rendering my original full fur bear but with the motion blur and render passes too.
I understand there are new features, but to me it's a marked different to go from 2.5GB to over 6GB VRAM (and no longer fit into memory) for an object that uses none of these features. My system has 32GB ram and yet I've noticed I get warnings to close 3DSMax as it's running low on memory when I use V3 with a lot of my V2 scenes - something I never experienced before. As a rule of thumb, what should I be expecting to see? Do most scenes now take up 2.5x the VRAM as before? Some kind of ballpark would be helpful.
I have uninstalled V3 and gone back to V2. I was also experiencing a lot of hangs/viewport freezes in V3 (seems to take longer for the viewport to even open). One scene that did open with V2 now just stays on the 'evaluating scene' screen so I've no choice but to go back to the older version. I would normally spend days testing this kind of thing, finding out exactly where it breaks and under what circumstances but unfortunately I just don't have the time to do that right now, I need to get on with the work so I have to stick with V2.
I'm afraid Ive never used ORBX I do not even have standalone installed on my system, sorry. But I am happy to send the max scene (with the meshed fur it's over 1GB) if that would help you.
Very well, send me the scene via PM at your earliest convenience. It is understandable that the jump from V1 to V3 would be quite an adjustment. I will be happy to help you along with that as much as possible.
Thankyou for offering to take a look.
Ive tried to attach the file via PM twice but I get an 'entity too large' error. Can you PM me an e-mail address and I can send the file via wetransfer?
Ive tried to attach the file via PM twice but I get an 'entity too large' error. Can you PM me an e-mail address and I can send the file via wetransfer?
Windows 7 64bit/ Intel 3930K/ ASUS Rampage IV/ GTX980ti x 2/ 64GB system RAM
Any way to PM a Dropbox or gdrive link?darkline wrote:Can anyone send me an email address and I can send you the file please?