I frequently work by going very near or even inside the control point “cloud” (not an actual point cloud object) of a mesh/subD.
The camera seems to fail if one/some points are behind the camera plane (just a guess), and even the target and rotation center fails, making the edit very difficult.
(Here it triggers by selecting a point, but it happens just by navigating in space…) generic subd.3dm (1023.6 KB)
Turning Parallel view let me avoid the problem, but the target/rotation center is even worse… (and parallel is just bad, I can’t go inside shapes to visually isolate the portion of points i need…)
I think this problem is very old.
I always hoped for a fix to come…
Please fix it!
Edit:
If control points are off > no problem.
Maybe camera bounding box calculation, depth (and all the other camera stuff) should just completely ignore all control points…
And manually re-setting the camera center every 3 seconds is not an acceptable workflow.
Anyway, I must have the camera inside the object (who works on complex subd/meshes understand why). Parallel view doesn’t let the concept of “inside”.
You see all the points.
For ex: you can edit the finger nail by putting the camera inside the finger tip, so avoiding visualizing all the other points of the hand-arm-body.
You can’t do so with parallel.
(Just a dumb example ^)
… not feasible for 4 hours of edit at time… I need to freely navigate space and not waste time readjusting target center or clipping planes all the time.
This is a bug.
I meant a workaround to avoid the bug, but i still need perpective.
Just gave it a go and can confirm weird behavior if using the mouse. I normally use a SpaceMouse and it’s not causing any weird behavior if editing control points “from the inside”. Just another reason to get one. I am so used to it by now and I think its super intuitive, especially in Rhino (works better in Rhino than any other 3d software).
I’m trying to reproduce to no avail, i was thinking it was a possible camera clipping issue but everything seems fine with showcamera. Can you post your system info? Thanks.
I’ve recordered a video, 3d mouse not connected.
Most of the time i’m just rotating the camera with right click or zooming in/out with the wheel.
Visible camera on top viewport.
The problem occur much more likely when selecting a control point.
I think control points should just be ignored by camera resizing/relocation math…
Windows 10.0.19044 SR0.0 or greater (Physical RAM: 16Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: Radeon RX 580 Series (AMD) Memory: 8GB, Driver date: 10-18-2021 (M-D-Y). OpenGL Ver: 4.6.14761 Compatibility Profile Context 21.30.23.01 30.0.13023.1012
> Accelerated graphics device with 7 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
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)
Vendor Name: ATI Technologies Inc.
Render version: 4.6
Shading Language: 4.60
Driver Date: 10-18-2021
Driver Version: 30.0.13023.1012
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Users\maje\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\AMDDenoiser\0.4.1\AMDDenoiser.Windows.rhp “AMDDenoiser.Windows” 0.4.1.0
On thing i’m seeing is that your camera gets tiny quickly, i have a hard time duplicating that, which is why i was asking about the wheel mouse sensitivity. But at no point is geometry disappearing regardless.
Windows 10.0.19043 SR0.0 or greater (Physical RAM: 16Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce GTX 770 (NVidia) Memory: 2GB, Driver date: 9-30-2020 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 456.71
> 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: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 9-30-2020
Driver Version: 27.21.14.5671
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 2 GB
Anyway, with 3dconn driver ON and 3Dmouse plugged, the problem occurs much more often.
The camera target randomly get very close to camera, and sometime camera location “back off” because of that.
I’ve tried the downloadable 3dconn driver but no change… (i’ll stick with the one shipped with rhino as it is better).
A similar issue with disappearing objects often occurs with my Rhino 7 when I set the camera close to the control points while Wireframe viewport mode is being used. However, if I use Shaded or any other viewport mode with visible geometry, then Rhino performs nicely. Looks like the 3d connexion’s automatic center of rotation gets confused due to the lack of actual rendered geometry while in Wireframe mode.
I think i pinpointed it.
Likeliest scenario to trigger the bug:
wireframe mode
some other far geometries
3dconnexion driver active + 3dmouse connected (without ever touching it)
be inside a control point “cloud” (from a mesh/subd/surface)
selecting 1/many control points
Target going really near camera… frustum cutting-out far objects. That’s the problem.
To replicate this ^ :
3dconnexion driver Enabled, 3dmouse unplugged:
Open this camera target control points bug.3dm (1.7 MB)
don’t move camera
try to select the control point marked by circle, it does nothing
plug the 3dmouse
selecting the same cp trigger the bug.
Can someone replicate this?
(maybe on different machine it triggers on a different camera position/angle …and with a different point…)
… not feasible for 4 hours of edit at time… I need to freely navigate space and not waste time readjusting target center or clipping planes all the time.
