Why do Viewport settings change when I use this keyboard shortcut?

I have CTRL+ALT+E set up as '_Zoom _All _Extents

After using it one of my viewports will have changed from Shaded view to Wireframe view.
It doesn’t happen always. And I cant seem to pin down what triggers it.

Also, (but this might be the intended behaviour) using the shortcut also changes all Viewports back to their default view.
For example if I am viewing a model from the left:
TOP | PERSPECTIVE
FRONT | LEFT

CTRL+ALT+E changes this back to the default:
TOP | PERSPECTIVE
FRONT | RIGHT

If this happens,this always triggers the Wireframe viewmode as well ! But I don’t think it is the only trigger!

I could make a video if needed to clarify

Can you run SystemInfo in Rhino and copy/paste the results here?

Rhino 7 SR30 2023-6-12 (Rhino 7, 7.30.23163.13001, Git hash:master @ f695e494df78377a81b2b95edb99c6067e324b33)
License type: Commercial, build 2023-06-12
License details: Cloud Zoo

Windows 11 (10.0.22621 SR0.0) or greater (Physical RAM: 32Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3070 (NVidia) Memory: 8GB, Driver date: 12-5-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 527.56
> Accelerated graphics device with 4 adapter port(s)
- Secondary monitor attached to adapter port #0
- Windows Main Display attached to adapter port #1

Secondary graphics devices.
Intel(R) UHD Graphics 770 (Intel) Memory: 1GB, Driver date: 12-9-2022 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- There are no monitors attached to this device!

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 12-5-2022
Driver Version: 31.0.15.2756
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7\Plug-ins\export_ACAD.rhp “AutoCAD file export : export_ACAD”
C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\MeshCommands.rhp “MeshCommands” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\MeshTools.rhp “MeshTools”
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”

Hey Simon -
I can’t seem to reproduce the behavior that you are seeing. Neither the changing of the display mode nor the changing of the view.

That’s a factory-default keyboard shortcut.

That’s a bad sign : )
Your SystemInfo looks fine so, if possible, try to narrow down when this behavior occurs. I see that you have 2 monitors attached. Are you always running Rhino on the same one?
-wim

Oops sorry talking about the wrong shortcut… Sorry, that was stupid of me

I actually meant CTRL+ALT+D : '_4View _Zoom _All _Extents

It isn’t a factory-default.

(can’t seem to edit the first post anymore)

I use both monitors for Rhino. But mostly the primary.

Hi Simon - Is it possible that there are objects outside the current shaded view that are not meshed for shaded display yet, and these are beingmeshed when they come into view (standard behavior)? It should just mesh and display correctly of course but if for some reason meshing fails on some objects it might cause a problem - somewhat shooting in the dark here…

-Pascal

Mmmm you mean Meshes which are offscreen and unrendered to save processing power?

I tried that and I don’t think this is what is triggering it.

I will try to figure out when it happens and come back here to report!