Worksession and clipping planes - problem

Enabled clipping planes in attached files in Worksession cannot be deactivated. If a file is attached and it contains an enabled clipping plane that clipping plane will affect all geometry. The only way to disable the clipping plane is to switch the active file, wait for all the attached files to reload, find the enabled clipping plane and disable it. If the enabled clipping plane is in another file then the you have to switch the active file again, wait again for all the attached files to reload, find the enabled clipping plane and disable it. Repeat until the enabled clipping plane is found and disabled. Then switch the active file back to the file being worked and wait again for all the active files to reload.

A method to disable clipping planes in attached but not active files is needed.

Example files:
File 1.3dm (2.8 MB)
File 2.3dm (3.3 MB)
WS Example A.rws (656 Bytes)

Open the worksession file.
Note that File 2 is the active file and does not contain a clipping plane.
File 1 is attached and contains a clipping plane which is clipping geometry in the perspective window.
Try to disable the clipping plane.

Rhino 7 SR7 2021-5-31 (Rhino 7, 7.7.21151.13001, Git hash:master @ 24d76fc798fa6ffd33733e5f18b034d547b87840)
License type: Commercial, build 2021-05-31
License details: Cloud Zoo

Windows 10.0.19042 SR0.0 or greater (Physical RAM: 64Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 5-6-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 462.59
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0

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: 5-6-2021
Driver Version: 27.21.14.6259
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB

Rhino plugins that do not ship with Rhino
C:\Program Files\Orca3D V2\Orca3D.rhp “Orca3D” 2.0.21.0
C:\Users\dcock\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\IntelDenoiser\0.6.2\IntelDenoiser.Windows.rhp “IntelDenoiser.Windows” 0.6.2.0
C:\Users\dcock\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.0\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.0.0

Rhino plugins that ship with Rhino
D:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.7.21151.13001
D:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
D:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.7.21151.13001
D:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.7.21151.13001
D:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
D:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
D:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.7.21151.13001
D:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.7.21151.13001
D:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
D:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Users\dcock\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\PanelingTools\2021.3.2.446\PanelingTools.rhp “PanelingTools”
C:\Users\dcock\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SectionTools\2021.4.21.831\SectionTools.rhp “SectionTools”

Hi, bumping this up.
Could it be possible to disable worksession clipping planes in future versions of Rhino?

It is rather inconvenient when several people are working on the project through worksession files.

Checking it, thanks.
RH-67861 Worksessions: Dispable attached clipping planes

-Pascal

Hi @pascal
any news about this?
I am experiencing this problem too with
Version 7 SR28
(7.28.23058.3001, 2023-02-27)

I checked your link and look like we will have to wait for v8 to have this solved?
Do you confirm this?
Thanks!

this is still a problem