The new editor window projection on Grasshopper canvas is a little off…
I see F5 doesn’t do anything and CTRL+R is used instead? Unfortunately it freezes the editor.
I don’t see that here. The projection looks correct here and Ctrl+R runs fine. Does this repeat after a restart of Rhino?
After being able to run the test script which is in the editor by clicking on the green arrow, it crashed again after pressing CTRL+R.
Not sure if this is of any use for you:
RhinoDotNetCrash.txt (1.2 KB)
Can you send me _SystemInfo. I have no clue right now, so will ask around what could be causing this.
System Info
Rhino 8 SR0 2023-3-21 (Rhino WIP, 8.0.23080.12305, Git hash:master @ e59b3ec7f9362de0c9590ae663f7e4b9756bf6e0)
License type: Kommerziell, build 2023-03-21
License details: Cloud Zoo
Expires on: 2023-05-05
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 1.3e+02Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA RTX A5000 (NVidia) Memory: 22GB, Driver date: 2-2-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 528.49
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
Secondary graphics devices.
NVIDIA Quadro K2200 (NVidia) Memory: 4GB, Driver date: 2-2-2023 (M-D-Y).
> Accelerated 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: 2-2-2023
Driver Version: 31.0.15.2849
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 23028 MB
Rhino plugins that do not ship with Rhino
C:\Users\martinsiegrist\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\EleFront\4.2.2\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
C:\Users\martinsiegrist\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\KeyShot9RhinoPlugin (ecfe8d1f-876a-460f-aa5e-3dd816936811)\1.4.0.0\KeyShot9RhinoPlugin\Rhino 7\KeyShot9RhinoPlugin.rhp “KeyShot9RhinoPlugin” 1.4.0.0
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8 WIP\Plug-ins\Commands.rhp “Commands” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 8 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoRoslyn.rhp “RhinoRoslyn” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\SectionTools.rhp “SectionTools”
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoCPython.rhp “RhinoCPython” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.0.23080.12305
C:\Program Files\Rhino 8 WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8 WIP\Plug-ins\ConstraintsUI.rhp “Constraints UI” 8.0.23080.12305
I wonder if the problem persists if you only use one monitor. Have you tried that?
Sorry it makes no difference
I was able to repeat this at first (Cntl+R) but i remembered i hadn’t rebooted since my last WIP install. I installed fresh and rebooted this time and Cnrl+R is working as expected.
I’ve also tried multiple monitors and confusing the window projection to no success.
this build.
Latest wip
Thanks. I switch off my PC every evening and I guess I’m using the latest build. The regular python editor and its projection looks as usual. And now I just got this display error:
The dreaded bloody component error.
Thanks, I put in a youtrack based on what we know.
youTrack
Yeah, I prefer not to post direct links to builds, so either send privately or do it in a pulldown. The youtrack one was due to not enough coffee.
1 Like
@martinsiegrist this is logged as RH-75781 Script editor ↔ Component cone wrong.
I added this thread. As mentioned in the YT, I thought this issue was logged already but it seemed not.
1 Like
This is still a problem and more recently the script editor opens somewhere far off my screen. The only workaround I found was to maximize the script editor window by right clicking in the the task bar.