Camera movement is not fluent in the very begining

[Bogdan_Chipara]

I noticed this a while back, but now since I use WIP more and more it gets annoying.

When rotating and panning at the very beginning, like half a second, the movement is not at all fluent, sometimes it first jumps into a new position and than it starts to run fluently. So if I make small camera movements all the time it jumps all the time. I notice the difference clearly between Rhino 5 in which thins work well, and the WIP.

[menno (Menno Deij - van Rijswijk)]

Do you have a 3Dconnexxion mouse? If so, this behavior is due to the calculation of render meshes (even when you’re in wireframe view) because these meshes are used to calculate the position of rotation. You can disable “rotation center” and I think the problem then goes away.

[Bogdan_Chipara]

No, I have a very banal mouse which is not a space mouse.

[Bogdan_Chipara]

Strange, I just saved the file and things seemed to improve. Still, I copy-pasted the model in Rhino 5, and there is a difference, Rhino 5 is more fluent.

When the model is complex WIP behaves better than 5 but overall on a regular model Rhino 5 is more fluent.

[Bogdan_Chipara]

Actually, I can confirm this! When the model is not saved the camera movements are not fluent.
To replicate, i open a file move the camera and things are OK. I take all the model and i copy-paste it in another WIP instance and the camera movements are slow.

[menno (Menno Deij - van Rijswijk)]

It does sound like there are render meshes being created in the background.

[Bogdan_Chipara]

Yeah, if I save small, it still happens.

[DavidEranen (David Eränen)]

Does this happens in any mode? Or only in Shaded, or Rendered?

-David

[menno (Menno Deij - van Rijswijk)]

It seemed related to the linked topic, that’s why I suggested render meshes and the role of the 3dConnexxion mouse.

[C++/WIP] Creating render meshes when viewport is not shaded

I just want to report that I see strange behavior when our custom BRep object is asked to generate render meshes. If no viewport is shaded, we don’t generate these meshes, and exit CreateMeshes with a count of zero. Now, every time the user changes the camera on a viewport (by e.g. panning, rotating), the DestroyMeshes and CreateMeshes functions are called in quick succession. Nothing much happens, because there are no meshes to destroy and when no viewport is shaded, no meshes to create. Then…

[Bogdan_Chipara]

I can still see this problem on Version 7 SR21, NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2.
Camera hangs before it becomes fluent.

(5 years later…)

[wim (Wim Dekeyser)]

Hi -
Can you provide all necessary steps and models to reproduce this issue?
Also post your SystemInfo data.
-wim

[Bogdan_Chipara]

@wim

Can you provide all necessary steps and models to reproduce this issue?
Also post your SystemInfo data.

I provided so far so many models and SysInfos… not the right approach. Much better would be to have screen sharing sessions.

[wim (Wim Dekeyser)]

@Bogdan_Chipara

Much better would be to have screen sharing sessions.

To reach someone that’s set-up to do that, eMail tech@mcneel.com.
-wim

[Bogdan_Chipara]

Yes, thanks, good suggestion … otherwise it is very difficult to explain.