OTOY Forums

Hi, yesterday I changed my password to new one. Now Rhino is not started. It's freeze on Octane plugin loading. How to remove and/or reinstall render (V3) for Rhino to see prompt window again and reenter credential? Thanks.

Hi - I think when you get this window, there is another window open under the Rhino window, asking you to log into the plugin. If you mouse-over the Rhino application icon on the Windows toolbar, it should show up, and you should be able to select that hidden window.

Paul

You will be surprised. I do not see this window (I mean on this screenshot) after Rhino starts. I see only freeze Rhino welcome window. And when I do like you said (pointing to taskbar by mouse), I can see this window of awaiting for plugin. Suddenly I see no way to see login Octane screen. What to do?

First image

Second, when I pointing to Rhino in taskbar

Hi - as a test, I just changed my Otoy password, and Rhino started OK and asked me to authenticate.

Can you tell me what the old version of the plugin's release number was?
What is the release number of the version you have just installed?
It looks like you are using the /nosplash startup parameter for Rhino - is this correct? If so, can you try without this parameter pls?

Thanks

Paul

Actually, there is no parameters at all when Rhino starts. Pure path to .exe file.
My previous version was OctaneRenderForRhino_3_4_4_74. It was replaced by OctaneRenderForRhino_3_5_3_78.

Is there any chance to untick somewhere octane loading? When I start Rhino in Safe-mode everything is ok. I mean it can start. But in the render menu is no Octane, only standard render and another-one.

Oh my! Solved!

In Safe-mode I dropped new version of Octane and it installed again. After restart in regular mode it's really stuck for a while with authentication but passed by. Which is wearied... Why it didn't ask for new password?..

Hi - glad you have resolved the problem. The first time loading a new version of Octane takes a long time (sometimes a minute) - and you went from 3.04.4 to 3.05.3, so that explains the long load time. Unsure why it glitched the first time you installed the plugin though.

Paul