Rhino 7 for Windows -
I have a very long list of layers and whenever I change the visibility of a layer it shoots me back up to the top of the panel. To be more specific, it actually only scrolls up to the point where the layer I just changed is now visible at the bottom of the panel.
Just to be clear, it isn’t moving layers around. If you can imagine, if there are a few consecutive layers running down my list that I intend on hiding/showing and I start with hiding the top layer, it would shoot me up and I would have to scroll down until the next layer is visible so I can then hide that one - then repeat and repeat.
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-22-2020
Driver Version: 27.21.14.5751
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 6 GB
Rhino plugins that do not ship with Rhino
C:\Users\devin\AppData\Local\Programs\Enscape\Bin64\Enscape.Rhino7.Plugin.dll “Enscape.Rhino7.Plugin” 0.0.20335.757
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Twinmotion Direct Link 2020.2 (e24ee14a-9514-47da-8fe6-f6e61b20160e)\Twinmotion Direct Link 2020.rhp “Twinmotion Direct Link 2020” 1.0.6.0
1.) You launch Rhino 7 for Windows.
2.) You go to the Layers panel and make a bunch of layers - so many that the vertical scroll bar appears.
3.) You grab the scroll bar and drag it to the bottom of the layer list.
4.) You change the visibility of the bottom-most layer by clicking the lightbulb icon.
5.) The layer list scrolls to the top so the layer you just clicked on is no longer visible, unless you re-grab the vertical scroll bar and drag.
Is this what you are seeing?
If so, then I cannot repeat this. It sounds like @pascal isn’t able to repeat this either.
Thanks for checking in. Thanks @pascal for chasing up.
Steps 1-3 are correct. If I click the lightbulb icon of the bottom-most layer then the layer list doesn’t go anywhere - it stays put. If I click the second bottom-most layer, then the scroll bar will scroll up so the bottom-most layer is no longer visible.
It scrolls up to the point where the clicked layer now becomes the bottom-most. Hope that makes sense!
P.S. When I disabled the Twinmotion & Enscape plugins and restarted Rhino7 it temporarily fixed it, but it was only a matter of time until it randomly started happening again. I’m trying to repeat it with another file now and it’s not happening, but maybe it’ll begin out of the blue in a matter of time if I keep the file open…
And, when it happens, can you verify that the two plug-ins are indeed not loaded? I want to make sure about that cause a plug-in can do exactly this sort of thing.
Yep. I see… I cannot make this happen… so it is just the one file? I did not understand that. That would seem to be important but… I can’t think what it might be. Can you please take a screen grab (Alt-PrintScreen) to the clipboard of the entire Rhino window and paste it?
Thanks - nothing astonishing in that screen shot, but I’ll try with a similar docking layout - not that would expect that to have any effect.
(And still the one file, is that correct?)
Yup, still the one file. I might try some other files over the weekend. It seems like it starts off fine when first opened, so I’ll have to trial it over some space of time. I also just tried saving this file as Rhino6 and no troubles there in V6.
I haven’t taken the time to try recreate a file with this issue, because I have no idea what it would take and how long it could take.
Anyway - just shared the file with a co-worker and they opened it on their computer only to find the same glitch. So, it isn’t a problem with my hardware. I suppose the file is corrupted.
Any suggestions on starting a new file but transferring all the information across including annotation styles, my layout pages, all settings etc. ?? This file is very information heavy nowadays and I can’t go on dealing with this glitch, it is infuriating.
@3dsynergy - do you have a file that shows the problem that you can share with us privately? I gather from @devingrayart that, for him at least, the problem is specific to one file.
