Community Forums for OTOY Customers
https://render.otoy.com/forum/
I don't really understand what you're saying. It works like a charm in 2019 and the 2020 test version.aoktar wrote: To get it working it should be implemented to transfer data and adapt it to octane. Nothing appears magically without coding.
Could you send me a scene so?Gregor.Zimmermann wrote:I don't really understand what you're saying. It works like a charm in 2019 and the 2020 test version.aoktar wrote: To get it working it should be implemented to transfer data and adapt it to octane. Nothing appears magically without coding.
The same workflow just crashes Octane V4. So the bug has to be in the V4 right?
Sure - here's a scene and three example pictures. First and second are rendered with V4, third with 2020 trial. It's not crashing all the time, but it's definitely not looking how it's supposed to.aoktar wrote: Could you send me a scene so?
It will be correct if you resend the scene. Problem here that geometry and material is not getting updated on next frame. Because there's a hacked way to obtain vertex map simulation in 4.05. It's working very well for 2018/2019/2020, because they have real support for vertex attributes. And it happen on just geometry data level, no need to refresh material with fake way. Unfortunately I stopped to work on V4 because I cannot keep working on many different versions together. It's not forcing the users to update new versions, it's technical problem on me.Gregor.Zimmermann wrote:Sure - here's a scene and three example pictures. First and second are rendered with V4, third with 2020 trial. It's not crashing all the time, but it's definitely not looking how it's supposed to.aoktar wrote: Could you send me a scene so?
Thanks for your help, ahmed!
Thanks for explaining. So, in order to get it working the right way, I need to upgrade to 2020, right? Or is there any chance that this issue will be resolved in a future version of V4?aoktar wrote:It will be correct if you resend the scene. Problem here that geometry and material is not getting updated on next frame. Because there's a hacked way to obtain vertex map simulation in 4.05. It's working very well for 2018/2019/2020, because they have real support for vertex attributes. And it happen on just geometry data level, no need to refresh material with fake way. Unfortunately I stopped to work on V4 because I cannot keep working on many different versions together. It's not forcing the users to update new versions, it's technical problem on me.
Probably I couldn't explain it well, answered this topic in past also. I stopped to work on V4. Restart and render on next frame it will be correct.Gregor.Zimmermann wrote: Thanks for explaining. So, in order to get it working the right way, I need to upgrade to 2020, right? Or is there any chance that this issue will be resolved in a future version of V4?
Did you deleted other version files after extract all? I stopped to make builds for old versions. It's very hard to do while go ahead for new versionsmNMGN wrote:In this version, when I quit c4d(R20.059), c4d is still running in the task manager. This is because I terminated it with the Octane node editor window active. If I close c4d after terminating the Octane node editor window, this will not happen. But this must be very cumbersome. This happens in 4.05 but 4.04 is not.