I am getting this message on both render nodes occasionally. They had 8GB of RAM and then I upgraded them to 16GB RAM but still I get this message. Is this a memory leak ? Is 16 GB enough for 6GB GPU cards rendering 1080p only final render, no passes ? It surely is, the scene was less then 500 MB. Node is using 14GB so almost 16GB, tha tis why I get this message. Is this a memory leak ? How do I enable logging for the nodes ?
OctaneRender™ Standalone 3.00 alpha 4
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.
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
19 x NVIDIA GTX http://www.borisgoreta.com
Sorry to be a PIA,
What is supposed to happen with Baking cam, is there a setting that is supposed to be applied, or a node that needs to be linked, that I could be missing?
In caveman, "Make car!...RUMMMM RUMMM!"
What is supposed to happen with Baking cam, is there a setting that is supposed to be applied, or a node that needs to be linked, that I could be missing?
In caveman, "Make car!...RUMMMM RUMMM!"
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
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
I think the car has to have a proper UV map, then with baking camera it renders to this UV map.
19 x NVIDIA GTX http://www.borisgoreta.com
Thank you Boris. That I may learn something - is an OBJ file typically exported without said UV map, as in some softs can export with (as part of the OBJ), while others do not?Post by BorisGoreta » Thu Jan 28, 2016 3:09 pm
I think the car has to have a proper UV map, then with baking camera it renders to this UV map.
Or, is there a node in Octane that in some parameter is looking for a separate file, exported along side an OBJ, like a .UVS file?
On the side, the pixelated clutter that the baking camera gives is great for making abstract art. Well done, OTOY!
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
It's possible that there is a memory leak, but I haven't seen it myself yet. If you could send us the scene I could have a look what's going on there.BorisGoreta wrote:I am getting this message on both render nodes occasionally. They had 8GB of RAM and then I upgraded them to 16GB RAM but still I get this message. Is this a memory leak ? Is 16 GB enough for 6GB GPU cards rendering 1080p only final render, no passes ? It surely is, the scene was less then 500 MB. Node is using 14GB so almost 16GB, tha tis why I get this message. Is this a memory leak ? How do I enable logging for the nodes ?
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Here you can find it viewtopic.php?f=33&t=51679Notiusweb wrote:
What is supposed to happen with Baking cam, is there a setting that is supposed to be applied, or a node that needs to be linked, that I could be missing?

Marcus,
I also got a system freeze when using the baking camera on 3 aplha4, I have all 12 GPU PCI 1x speed (6 of the 12 are on an Amfeltec 4-way cluster expansion).
Here is some additional info:
- If I use a lower resolution (ie 300 x 200), it goes right through to end, even 16,000 samples, no freeze
- if I use 1280 x 720, it freezes right at the end at about 15K samples
-if I use 3840 x 2160, it freezes right at beginning
My BSOD (blue screen of death) read this:
"A clock interrupt was not received on a secondary processor within the allocated time interval"
Hope this helps with something.
I also got a system freeze when using the baking camera on 3 aplha4, I have all 12 GPU PCI 1x speed (6 of the 12 are on an Amfeltec 4-way cluster expansion).
Here is some additional info:
- If I use a lower resolution (ie 300 x 200), it goes right through to end, even 16,000 samples, no freeze
- if I use 1280 x 720, it freezes right at the end at about 15K samples
-if I use 3840 x 2160, it freezes right at beginning
My BSOD (blue screen of death) read this:
"A clock interrupt was not received on a secondary processor within the allocated time interval"
Hope this helps with something.
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
Welcome to the "freeze club" Notiusweb !
Seems that you have better USB risers for your Titan. It seems that it is worss with lower VRAM GPU (my 780Ti on USB riser get freeze very often
, not only on the baking cam).
It also depends on resolution, I noticed the same issues.

Seems that you have better USB risers for your Titan. It seems that it is worss with lower VRAM GPU (my 780Ti on USB riser get freeze very often

It also depends on resolution, I noticed the same issues.
I7-3930K 64Go RAM Win8.1pro , main 3 titans + 780Ti
Xeon 2696V3 64Go RAM Win8.1/win10/win7, 2x 1080Ti + 3x 980Ti + 2x Titan Black
Xeon 2696V3 64Go RAM Win8.1/win10/win7, 2x 1080Ti + 3x 980Ti + 2x Titan Black
Yes, I felt very frosty.Welcome to the "freeze club" Notiusweb !![]()
Seems that you have better USB risers for your Titan. It seems that it is worss with lower VRAM GPU (my 780Ti on USB riser get freeze very often, not only on the baking cam).
It also depends on resolution, I noticed the same issues.

It actually reminds me of when I would run Octane Bench at very high overclocks and the Bench process freezes, but my GPUs are all still active and running fine after I close out the frozen Bench process. Although, the Bench script seems to be in somewhat of a sandboxed environment that does not lock up the whole system.
It may be connected to GPU VRam and PCI speed somehow, like there is an underlying capacity for it to happen, but it is dodged when you put less strain on a GPU's VRam, maybe.
Well, as cavemen would say,
MAKE FIX! ARRARRARARRRRRR!!!
I mean, I keep hitting my Titan Z's with a rock and it doesn't seem to help at all...
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
Okay, thanks to you and Boris for the help. Yey! Got it working!Postby mojave » Thu Jan 28, 2016 7:59 pm
Here you can find it [url]viewtopic.php?f=33&t=51679[/url]
What do you do with the texture once baked, is it something that is exported from Octane? (What type of file is it)
Also, (1) can the texture be sampled to any extent as it is being created (ie 1 - 16,000), and (2) can it collect/incorporate any medium (scattering, absorption) elements should they be passing through it geographically when rendered
THANKS
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