In general, I must say - the release is very stable. As soon as I figured out the problematic instances, Octane in a huge scene (12 million pure geometry and about 100 million instances) works flawlessly.
The Selected Objects feature in the IPR is especially helpful - I haven't used it before, but now I've found it very useful.
OctaneRender 2020.2 LightWave Production build 2020.2.4.0
Moderator: juanjgon
- scooternva
- Posts: 88
- Joined: Thu Jul 04, 2019 6:13 pm
- Location: Suburban Washington DC
- Contact:
C4D and other plugins have had a spotlight for years now. It's feature parity issues like this--not to mention the ridiculous years-long documentation problem--that aggravate me enough to make me wander over to the Redshift site when I'm waiting for an Octane job to finish.promity wrote:Thank you, Juanjgon! It is a pity, however, that spotlight is not available yet. It would be very useful to me now )
Octane 2020.2.3.1 | LightWave 2019.1.5 (3134) | Win10 Pro 19041.1052 | 2 x Gigabyte AORUS RTX 2080 Ti Xtreme w/NVLink | Gigabyte AORUS Xtreme X399 | AMD Ryzen 2950X | 64 GB RAM | SSDs: Samsung 970 PRO 512 GB + Seagate FireCuda 510 2 TB | blog.gammans.zone
Thanks Juan,
Does this build solve FiberFX crash with 30X0 GPUs ?
Does this build solve FiberFX crash with 30X0 GPUs ?
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Hi Juan, ok i checked now on my RenderSlave (i don't have 30X0 either in my main workstaiton
) and it seems to be working/FIXED.
That is good, strange but good (since you've not done any fixes there ?) but maybe some of octane CORE bugs caused crash and now fixed so good side-effect ?
Thanks

That is good, strange but good (since you've not done any fixes there ?) but maybe some of octane CORE bugs caused crash and now fixed so good side-effect ?
Thanks
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
- pixelsmack
- Posts: 112
- Joined: Wed Jun 11, 2014 6:31 pm
I am seeing objects dropping more with this build. I can resubmit the scene 5-times. Each time it's a different object that is dropped. But once the object that is dropping happens, its that same object each time for that render. I have two Octane render nodes. Both with a 3090. Both up to date for drivers, Windows, etc. I turned off the Octane instancing of nulls and clones. I've been doing this to fix the issue where this can cause object drops. It's always been a 100% failsafe. Now with this build, objects are dropping out nearly every render. No errors in the log. Rolling back....
Can you please attach a scene as simple as possible to reproduce this problem here?pixelsmack wrote:I am seeing objects dropping more with this build. I can resubmit the scene 5-times. Each time it's a different object that is dropped. But once the object that is dropping happens, its that same object each time for that render. I have two Octane render nodes. Both with a 3090. Both up to date for drivers, Windows, etc. I turned off the Octane instancing of nulls and clones. I've been doing this to fix the issue where this can cause object drops. It's always been a 100% failsafe. Now with this build, objects are dropping out nearly every render. No errors in the log. Rolling back....
Thanks,
-Juanjo