Anyway to add an info how many total cuda cores engaged. How many RT cores are engaged. Percentage of cuda contribution vs rt cores towards rendering speed.
Sometimes we turn on RTX acceleration and see no results like it's not working. Would be nice to show all this data
OctaneRender™ 2021.1 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.
There isn't really a good way to measure this. If you enable RTX Octane tries to use RTX as much as possible, but at the moment this applies only for static triangles and instances. So if your scene uses a lot of texture displacement, vertex motion blur, hair etc. it won't help much.coilbook wrote:Anyway to add an info how many total cuda cores engaged. How many RT cores are engaged. Percentage of cuda contribution vs rt cores towards rendering speed.
Sometimes we turn on RTX acceleration and see no results like it's not working. Would be nice to show all this data
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Is there a way to calculate used Vram better? In a scene when I turn on or off RTX no changes show in Vram in Octane but GPU-Z shows 1.3GB Vram difference.abstrax wrote:There isn't really a good way to measure this. If you enable RTX Octane tries to use RTX as much as possible, but at the moment this applies only for static triangles and instances. So if your scene uses a lot of texture displacement, vertex motion blur, hair etc. it won't help much.
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
-
rleuchovius
- Posts: 51
- Joined: Sun May 03, 2015 1:47 pm
Great work!
Do you have any estimate on the Polarized Lighting? Would be a very useful feature for car renders.
Do you have any estimate on the Polarized Lighting? Would be a very useful feature for car renders.
Hi, could it be possible to have "Round edges" applied with "clipping material" ? Because it make hard edges.
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
Thank you wallace. Hope it'll be possible 
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
hi there,
i am not able to start the OctaneRender_Enterprise_2021_1_RC_3_node on my renderslave-machine. during the login-process the node just quits and kill itself.
the Octane 2020.2.5 Daemon works fine.
is that a known issue?
thanks in advance
i am not able to start the OctaneRender_Enterprise_2021_1_RC_3_node on my renderslave-machine. during the login-process the node just quits and kill itself.
the Octane 2020.2.5 Daemon works fine.
is that a known issue?
thanks in advance
Workstation: Win 10 PRO 64 bit, 3,4 GHZ ,6-cores, 64 GB RAM , 4x RTX 2080 Ti
1. RenderSlave: Win 10 Pro 64 bit , 3x GTX 980Ti
2. RenderSlave: Win 10 Pro 64 bit 2x GTX 980 Ti
1. RenderSlave: Win 10 Pro 64 bit , 3x GTX 980Ti
2. RenderSlave: Win 10 Pro 64 bit 2x GTX 980 Ti
OctaneRender 2021.1 was released: viewtopic.php?f=24&t=78621useruser wrote:hi there,
i am not able to start the OctaneRender_Enterprise_2021_1_RC_3_node on my renderslave-machine. during the login-process the node just quits and kill itself.
the Octane 2020.2.5 Daemon works fine.
is that a known issue?
thanks in advance
Please try with the latest build and reply in that thread if you have any issues.
Hi OTOY Team,
I did not share my gratitude towards this stunning release (considered now, at the time of this reply, "deprecated"). In particular the important fixes.
However, I am facing an obnoxious behavior since this release and any versions higher: on some scenes containing USD assets, my materials (nodes) are no longer applied to the USD geometry node. The imported USD assets is using default materials and my custom materials do seem to be lost.
My current workaround is to have two Standalone instances opened, both different versions and copying/pasting my nodes to plug them back again (using the speed-efficient and useful CTRL + HOLD shortcut as I am assigning materials to a custom assets/shading group nomenclature).
I also have back up files and I am aware that these builds are non-production-safe.
I suspect this fix is the cause behind it:
I did not share my gratitude towards this stunning release (considered now, at the time of this reply, "deprecated"). In particular the important fixes.
However, I am facing an obnoxious behavior since this release and any versions higher: on some scenes containing USD assets, my materials (nodes) are no longer applied to the USD geometry node. The imported USD assets is using default materials and my custom materials do seem to be lost.
My current workaround is to have two Standalone instances opened, both different versions and copying/pasting my nodes to plug them back again (using the speed-efficient and useful CTRL + HOLD shortcut as I am assigning materials to a custom assets/shading group nomenclature).
I also have back up files and I am aware that these builds are non-production-safe.
I suspect this fix is the cause behind it:
I can handle the extra manual work, however, I would be curious if I could get a confirmation of my suspicion.abstrax wrote: [*] Updated USD library to version 21.08.