You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complex scenes are slow partly because neoscore renders every object on every frame, regardless of whether the objects are visible inside the frame. Qt automatically culls objects on the graphical rendering side, but neoscore still instantiates the Qt objects every frame, which is a pretty slow process. If we had broader bounding rect support we could implement some kind of culling. There are complications with flowable contexts, but my gut says they aren't so bad.
The text was updated successfully, but these errors were encountered:
Complex scenes are slow partly because neoscore renders every object on every frame, regardless of whether the objects are visible inside the frame. Qt automatically culls objects on the graphical rendering side, but neoscore still instantiates the Qt objects every frame, which is a pretty slow process. If we had broader bounding rect support we could implement some kind of culling. There are complications with flowable contexts, but my gut says they aren't so bad.
The text was updated successfully, but these errors were encountered: