OTOY Forums

It looks like Modo is checking the "enabled" status of all the buttons in the Setup window when you change navigation modes. When the Setup window is closed, the "enabled" status on those button do not need to be checked. And some of the "enabled" states are complex to determine - for example the "Convert to Diffuse" button need to check if an Octane Override is selected, and if it is it needs to track down the octane nodes to pick up the material type. So all this takes time - so you are seeing a small delay (on my PC it's about 1/4 of a second).

The fix for this would be to remove all those material buttons and put them in a popup submenu (so the enabled state only gets determined when you press the popup button). People may see this as a step backwards - but it's easy to do, so let me know...

Paul

Looks like it is exactly what's happening Paul.

I just pressed "0" to maximize the Setup Windows, hiding the buttons and the lag was gone. I don't know about the other users, but to me it is enough to solve the issue.

Thank you for you time and congrats for the incredible work with the plugin!

Hi Paul
Why would there be no delay if you move, rotate and zoom around the scene with the on screen icons?
Now that I know what is causing the delay I can close the setup window down when I need to, not ideal but it does work.
I don't know if changing that would be worth it, I think other users should chime in to see what the consensus is.

Hey Paul I noticed this too and it may be because all your icons are in separate files. You can avoid this by putting all your icons into a single image file (in a grid).

This method was introduced in 701 to prevent kits with lots of icons/buttons from causing stutters in modo. See the SDK wiki: http://sdk.luxology.com/wiki/Icon_Resources

Hey Paul I noticed this too and it may be because all your icons are in separate files. You can avoid this by putting all your icons into a single image file (in a grid).

I don't think it's the icons (since they will all be cached in memory) - it's the calls to the plugin to determine if each button is enabled or not (which for some buttons requires walking the shader tree or analysing the Octane node setup). So having fewer buttons visible is the solutions (but obviously has a workflow impact).

Paul

face_off wrote:I don't think it's the icons (since they will all be cached in memory)

Apparently modo doesnt cache the icons.

The ACS Kit had exactly the same problem and it was fixed by putting all icon resources in a single file.