Zoom Extents bug?

Grasshopper
,
1

I’m trying to add a logic to some of my scripts where the user could “zoom extent” on selected objects. However, it seems that adding Content Cache as the final step makes Rhino very laggy and sluggish to rotate and pan.

image
image1920×689 71 KB

Here is the script to reproduce the issue.

To me it seems the Content Cache is buggy in this case. It shouldn’t slow Rhino down but should instead only update the Views when pressed or given a button that Pushes the changes.

Wombat has a nice component, Zoom Bounding Box, but I would like to achieve the same using native components as well:

image
image443×287 17.5 KB

I am running Service Release 8.16,
8.16.25042.13001, 2025-02-11
ZoomExtentsProblem.gh (12.8 KB)

2

Here’s a GhPython solution that might work/could be edited to:

1 Like
3

Hi @tuomas.lehtonen,

The lag comes from the ‘Query Viewports’ component.

In this case you don’t need to query on any viewport change, so you can turn of ‘Synchronise’ option.

image
image1780×494 77.3 KB

4

Thanks, but that can’t be it. I tried switching the Synchronize on and off on both Query components, disabling the components, shutting the Grasshopper file down and so on.

I could send a test model with ~790 curves, but the file size is too big (it is a map with lots of control points). Is direct message ok? If I just open this Rhino file and pan and rotate around, the FPS is around 150. Then, if I open the ZoomSelected script, it gets really slow. Like 8 FPS. And after that, no matter what I do (disable components, synchronize on/off, shut Grasshopper), Rhino persists this laggy behaviour.

To me it seems there is something else happening in the background outside the Synchronize issue.

Please see if you can reproduce it.

5

Thanks, works like a charm!

1 Like
6

@kike where can I send a test model that lags on my computer so you may try to reproduce?

7

Please go upload support and use kike @ mcneel.com as a receiver.

Many thanks!!

1 Like
8

Should be sent now.