Community Forums for OTOY Customers
https://render.otoy.com/forum/
No, I haven't, but I just tried it: Even if I directly apply an Octane Object Tag to these instances and deactivate motion blur, I still get motion blur on these parts.jayroth2020 wrote: Fri Oct 31, 2025 6:42 pm Have you tried using an Octane Object tag on those items?
No, I haven't tried that, because the camera is also moving.bepeg4d wrote: Mon Nov 03, 2025 11:05 am @dasmodular:
Have you tried to disable the Camera motion blur in the Octane camera Tag?
ciao,
Beppe
Tim0042 wrote: Thu Oct 16, 2025 9:40 am The material compatibility mode includes "2025.4" as an option, so the Octane version we just jumped to. What is this used for?
I understand switching to legacy behavior when opening older projects / matching old materials (so the "2022.1" option makes sense), but is choosing "2025.4" just the same as leaving the field blank?
I kiiiinda think it has to, because once I choose something, I cannot return to the blank state - not even with "reset to default". However, the material thumbnail does refresh (if not necessarily change).
The Texture Projection Node also has a compatibility mode, but its default is not a blank field but instead "Latest (2025.1)". Maybe these different behaviors could be aligned?
Yeah blank means basically no compatibility mode or latest.Tim0042 wrote: Tue Nov 04, 2025 3:31 pm When scaling a project, would it be possible to have the Bump Height in materials be scaled automatically as well? For example, if I CTRL+D scale the project from 1 to 10, could we multiply the Bump Height in all Materials by 10? This might prevent them from changing their appearance in that regard.
Maybe the reverse could work for Density within a Medium Node, so if the scene becomes 10 times larger, divide the Density by 10 to compensate?
Also, using this chance to pull up my question from last month again, as it also has to do with materials : )
Tim0042 wrote: Thu Oct 16, 2025 9:40 am The material compatibility mode includes "2025.4" as an option, so the Octane version we just jumped to. What is this used for?
I understand switching to legacy behavior when opening older projects / matching old materials (so the "2022.1" option makes sense), but is choosing "2025.4" just the same as leaving the field blank?
I kiiiinda think it has to, because once I choose something, I cannot return to the blank state - not even with "reset to default". However, the material thumbnail does refresh (if not necessarily change).
The Texture Projection Node also has a compatibility mode, but its default is not a blank field but instead "Latest (2025.1)". Maybe these different behaviors could be aligned?