OTOY Forums

aoktar wrote: How can you be sure that's not working? I see that's working.

Sorry it works. I had to use more objects to see difference.
As for min. samples I will test it more. I use them because they are good to make clear view during changing surface parameters.

SSmolak wrote: Sorry it works. I had to use more objects to see difference.
As for min. samples I will test it more. I use them because they are good to make clear view during changing surface parameters.

Yes that's good for it. But you should make tests with min. disp. samples=1, if you compare the interactivity. What you say is that's a different topic as I say.

Also is there chance to add Perspective Correction feature from Thin Lens Camera to Universal Camera in ThinLens mode ? Keep up-right works totally different.

SSmolak wrote:Also is there chance to add Perspective Correction feature from Thin Lens Camera to Universal Camera in ThinLens mode ? Keep up-right works totally different.

+1 on that one.

When we have full stack of stored images there is need to remove last image before add next - if not it will be not stored correctly. It would be great for menu option like "remove all stored images".

for an experimental version it is remarcably stable and well working! congrats! cinema R26 here with macbook pro M1 max.

aoktar wrote:Hi all,
This is the latest experimental plugin build based on experimental 2022.1-XB3 SDK. Any feedback will be much appreciated. Enjoy it!
This is the SDK matching OctaneRender® 2022.1 XB 3.

seems network rendering is disabled completely in this version?when will we get a version which is including this?

In all Octane versions there is very bad behavior while editing material parameters using text field by moving mouse. When mouse is going to be unpressed it still change value in LV. It works fine when we use slider - unpressing, release mouse button do nothing as it should be.

SSmolak wrote:In all Octane versions there is very bad behavior while editing material parameters using text field by moving mouse. When mouse is going to be unpressed it still change value in LV. It works fine when we use slider - unpressing, release mouse button do nothing as it should be.

Not sure what you mean exactly but it maybe about high GPU usage and delayed reactions because of this. Text fields are not custom, they are native UI elements. And because of it this cannot be something we can do anything for you else of priority settings.
Did you try low priority and multi GPUs? And did you try to check it on every scenes even with lightweight scenes? Are you sure that's not about heavy GPU usage and giving delays to interface?

aoktar wrote:

SSmolak wrote:In all Octane versions there is very bad behavior while editing material parameters using text field by moving mouse. When mouse is going to be unpressed it still change value in LV. It works fine when we use slider - unpressing, release mouse button do nothing as it should be.

Not sure what you mean exactly but it maybe about high GPU usage and delayed reactions because of this.

I mean that if you move slider to for example 23% value Octane Live Viewer shows value 22% until you release mouse button. After that it switch to 23% value. But we never see true value if mouse button is pressed. This is issue even with simple box scene any texture. This is mainly noticeable in Transform node when we want perfectly place or scale texture.

Interesting is that this bad behavior is only while using Octane Node editor with Edit Controls enabled. Using controls in different panel works fine.