OctaneRender™ Standalone 3.08 RC 3
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
- PolderAnimation
- Posts: 375
- Joined: Mon Oct 10, 2011 10:23 am
- Location: Netherlands
- Contact:
I have a problem saving very large renders (15000x6000) with multiple passes in octane. If I try to save an ext with one extra pass it works but with more it crashes. I also can not render greater than 15k even when i have enough memory.
Win 10 64bit | RTX 3090 | i9 7960X | 64GB
Yes, sorry forgot to reply. We have seen all kinds of issues with the 39x drivers. IF you check the log you will probably see that the CUDA initialization has failed. If that occurred, the only thing that helped was going back to 387 or 388. Unfortunately this option is npt available for our Quadro cards and on our OSX machine. We are currently in contact with NVIDIA, but have no solution yet.cfrank78 wrote:Marcus, do you also have found the issue with drivers above 390.xx and sometimes not showing cuda devices?
Searched the forum and especially gtx 7xx cards seem to have that problem!
Have a nice day - Chris!
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Ai ai ai. You really seem to be very busy! I allready posted my log on the first site of this thread, when i asked here the first time.abstrax wrote:Yes, sorry forgot to reply. We have seen all kinds of issues with the 39x drivers. IF you check the log you will probably see that the CUDA initialization has failed. If that occurred, the only thing that helped was going back to 387 or 388. Unfortunately this option is npt available for our Quadro cards and on our OSX machine. We are currently in contact with NVIDIA, but have no solution yet.cfrank78 wrote:Marcus, do you also have found the issue with drivers above 390.xx and sometimes not showing cuda devices?
Searched the forum and especially gtx 7xx cards seem to have that problem!
Have a nice day - Chris!
It says:
CUDA error 999 on device -1: unknown error
-> failed to initialise CUDA driver API
Missing or invalid 'seconds_to_expiration' field from ORC server API response
I have to go to 39x.xx in the future. And i only have 780 cards so far for octane. So.........i hav emy fingers crossed! Btw, i only saw it as i believe in win 8.x. win 7 works well and 10 too as far as i can see. But changing OS is no option here.
Hope you find a solution soon!
Have a nice day. Chris!
I just tried it here and it works, but it uses a lot of memory, because all the passes get tone-mapped first and then passed on to OpenEXR, which requires some additional memory. So if I render with your resolution (15000 x 6000) and 6 additional beauty passes, the saving process requires an additional 10GB of memory.PolderAnimation wrote:I have a problem saving very large renders (15000x6000) with multiple passes in octane. If I try to save an ext with one extra pass it works but with more it crashes. I also can not render greater than 15k even when i have enough memory.
-> My guess is that you run out of memory.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- PolderAnimation
- Posts: 375
- Joined: Mon Oct 10, 2011 10:23 am
- Location: Netherlands
- Contact:
Ok thanks abstrax, we have 11 gig cards so there is a high changes that we did run out.
Win 10 64bit | RTX 3090 | i9 7960X | 64GB
Sorry, I was talking of system memory not of graphics memory, since the render film and tone-mapping results are stored in system memory.PolderAnimation wrote:Ok thanks abstrax, we have 11 gig cards so there is a high changes that we did run out.
I.e. check in the task manager how much memory you have left and then you should be able to add enough RAM to your computer to be able to save those results.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- PolderAnimation
- Posts: 375
- Joined: Mon Oct 10, 2011 10:23 am
- Location: Netherlands
- Contact:
The system has 32gb of memory. We looked at the amount of ram memory it uses when saving.
When saving I see that the gpus fail and after a couple of seconds I get the popup with 'octane render has stopped working'. If I look at my memory I still have 15 gbs of ram left.
When saving I see that the gpus fail and after a couple of seconds I get the popup with 'octane render has stopped working'. If I look at my memory I still have 15 gbs of ram left.
Win 10 64bit | RTX 3090 | i9 7960X | 64GB
Ok, then the problem is something else. Which driver version are you using? There have been a lot of issues reported for the 39x drivers, especially for Kepler GPUs. If you are using one of those recent drivers, maybe it works better with 387 or 388 driver.PolderAnimation wrote:The system has 32gb of memory. We looked at the amount of ram memory it uses when saving.
When saving I see that the gpus fail and after a couple of seconds I get the popup with 'octane render has stopped working'. If I look at my memory I still have 15 gbs of ram left.
Two more questions: Which GPUs are you using? Your signature says 780Ti, is that still true? And do you use post-effects (bloom/glare) in the scene and can you save the result with bloom and glare disabled?
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
When I try and save a material, as an ORBX, it saves to my localDB, but without the textures. So the file will be 1kb or 2kb.
Then, sometimes it will give an error message that it could not save the material, but then it actually does save, and with textures!
I get this material saving weirdness in V4XB1 as well.
Thx!
Edit - Maybe it has to do with image size? ie 4096 x 4096 too large to be saved?
Also, the displayed LiveDB does not get refreshed if I change the actual windows folder structure.
Then, sometimes it will give an error message that it could not save the material, but then it actually does save, and with textures!

I get this material saving weirdness in V4XB1 as well.
Thx!
Edit - Maybe it has to do with image size? ie 4096 x 4096 too large to be saved?
Also, the displayed LiveDB does not get refreshed if I change the actual windows folder structure.
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise