Hi mbetke,
I don’t think this is actually an issue. When you create a new material, the default setting is applied correctly.
The issue occurs when you open older materials. In that case, the material keeps its original color space settings, which can conflict with the new color space set for the scene. That actually makes sense, so the material’s color space needs to be changed manually to match the scene’s color space.
Regards
Paride
OctaneRender® 2026.4 for 3ds max® v26.11
Forum rules
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
-
paride4331
- Posts: 3998
- Joined: Fri Sep 18, 2015 7:19 am
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
-
paride4331
- Posts: 3998
- Joined: Fri Sep 18, 2015 7:19 am
Hi coilbook,
Could you please run a few tests so we can narrow down where the slowdown is coming from?
enable Load and Render Performance Report under Octane Preferences > Troubleshooting and run the same empty scene
First, disable both RTX 3080 Ti cards in Octane's Devices settings and leave only the RTX 5090 enabled. Start the Octane Live Viewer and let it run until the initial startup/initialization period is finished. Please report how long it takes from starting the Live Viewer until rendering actually begins, and then the stable Msamples/s after the initial startup period.
Then enable the RTX 5090 and only one RTX 3080 Ti, leaving the second 3080 Ti disabled. Run the same test and report the startup time and stable Msamples/s.
Finally, enable all three GPUs and repeat the same test, again reporting the startup time and stable Msamples/s.
Please post the complete report log.
Regards
Paride
Could you please run a few tests so we can narrow down where the slowdown is coming from?
enable Load and Render Performance Report under Octane Preferences > Troubleshooting and run the same empty scene
First, disable both RTX 3080 Ti cards in Octane's Devices settings and leave only the RTX 5090 enabled. Start the Octane Live Viewer and let it run until the initial startup/initialization period is finished. Please report how long it takes from starting the Live Viewer until rendering actually begins, and then the stable Msamples/s after the initial startup period.
Then enable the RTX 5090 and only one RTX 3080 Ti, leaving the second 3080 Ti disabled. Run the same test and report the startup time and stable Msamples/s.
Finally, enable all three GPUs and repeat the same test, again reporting the startup time and stable Msamples/s.
Please post the complete report log.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
Hi Paride,
I am following up on slaves not using out of core ram. Even 32 gb did nothing. So the scene is borderline what gpu can hold in vram. I attached the image. master has 5090 and 2 x 3080 ti with 12 gb of vram. But the slaves have some 2080ti with 11 gb of vram. It seems that octane tries to use vram only therefore slaves fail. How can I tell octane after 10Gb of vram usage start using out of core?
Does all mesh must fit vram or textures?
UPDATE:
After hiding some hi poly meshes, slaves render fine as long as vram is bellow 11 gb due to 2080ti. So out of core is not working.
Thank you
"16 GB o-o-c limit could be the bottleneck. If the scene exceeds the available VRAM by more than those 16 GB, Octane may still run out of memory and crash instead of using more system RAM. Also, some data may still need to fit in VRAM, so large or complex meshes, displacement, subdivision, volumes, hair, etc. could be the actual cause. Since most textures are procedural, I’d look at the geometry and check the VRAM/o-o-c usage in the Octane log right before the crash.
Regards
Paride"
I am following up on slaves not using out of core ram. Even 32 gb did nothing. So the scene is borderline what gpu can hold in vram. I attached the image. master has 5090 and 2 x 3080 ti with 12 gb of vram. But the slaves have some 2080ti with 11 gb of vram. It seems that octane tries to use vram only therefore slaves fail. How can I tell octane after 10Gb of vram usage start using out of core?
Does all mesh must fit vram or textures?
UPDATE:
After hiding some hi poly meshes, slaves render fine as long as vram is bellow 11 gb due to 2080ti. So out of core is not working.
Thank you
"16 GB o-o-c limit could be the bottleneck. If the scene exceeds the available VRAM by more than those 16 GB, Octane may still run out of memory and crash instead of using more system RAM. Also, some data may still need to fit in VRAM, so large or complex meshes, displacement, subdivision, volumes, hair, etc. could be the actual cause. Since most textures are procedural, I’d look at the geometry and check the VRAM/o-o-c usage in the Octane log right before the crash.
Regards
Paride"
- Attachments
-