Frozen Viewports?

So if I leave Rhino sitting with a detail active (double clicked into and in edit mode) and get into the frozen viewport state, initially everything is frozen and RecreatePipelines will fix everything except the layout which had the active detail. Both the layout that the detail exists on and the detail remains frozen, nothing on that sheet will redraw. If I look at properties, I can see that I can double click in and out of the detail, but the layout and detail are still frozen, regardless if the detail is active or not. All other layouts, and their details will be OK. Double clicking in or out of the frozen detail will dump me out of Monitor state changed command. I can get that frozen sheet back if I double click out of the detail (I have to look at properties to see if Iā€™m out), let the screen saver kick on again, then when I get the Monitor state changed command I can use RecreatePipelines, and that will fix that layout and detail (because the detail is no longer active).

Hope that is clear,
Sam

I looks like the problem is solved in the last WIP @jeff

It seems better on my end as well, but I do get the following Rhino error on returning:

OpenGL Error Occurred

Error:
display_ogl\RhEngine_GL33.cpp (3041 | GL45): invalid operation

ā€“Editā€“
Well, better in that it isnā€™t frozen, but curves stop displaying if GPU tessellation is on.

Sam

@SamPage Sorry for the delayā€¦

Hmmm, that was supposed to have been fixedā€¦and Iā€™m pretty sure it made this weekā€™s WIP. Iā€™m still trying to figure out why the curves fail to come back (theyā€™re there, just canā€™t see them. You can select them and they will displayā€¦jogging them and an undo should bring them back)ā€¦ Hopefully Iā€™ll have a better handle on this before next WIP.

Thanks,
-J

@SamPage Do you get that error every time, for every model? Or just a specific model? Display mode independent?

If possible, Iā€™d like to get a 3dm file that exhibits this GL errorā€¦Iā€™m not seeing it hereā€¦ Iā€™m assuming youā€™ve enabled the GL warnings using ā€œTestGLWarningsā€ ? Or are you seeing these errors somewhere else?

Also, can you post the version info you see on Rhinoā€™s ā€œAboutā€ screen.

Thanks,
-Jeff

Iā€™ll have to investigate this for you. I am currently between two models, so I have two instances of Rhino open, and I thought it was on both of them, but Iā€™ll pay more attention to where and when I see it.

6.0.17234.9201, 08/22/2017

Jeff, I donā€™t see the bug anymore.

Hi Jeff

Frozen viewport no moreā€¦thanks!

ā€œDelete holeā€ in the
solid tools tab donā€™t work, thatā€™s probably a smaller problem!

Thank
you
/Christian

jeff [1] McNeel
July 31

@Christian2 [2]
Thanksā€¦However the distance in time between those two versions is
hugeā€¦so unfortunately trying to find the differences between them
would yield months of changes.

@Christian2,

Please create a new topic for the Delete hole issue. I think you might get better help then.

-David

Use the ToolbarReset commandā€¦

DeleteHole was removed as a command and replaced by UntrimHoles. There should be an upcoming internal alias for DeleteHole to UntrimHoles, but itā€™s not there yet.

Here is the YouTrack issue.

ā€“Mitch

3 posts were split to a new topic: Frozen Viewport - Rhino 5