Enable the explorer window while it is docked. The explorer must be the currently selected window if it is part of a tab group
Use the viewport. Significant frame drops will occur.
Navigate from or close the explorer window to recover the frame rate
Expected Behavior
60 FPS framerate while using the viewport as the norm from before the latest modal update
Actual Behavior
While the explorer window is docked and the currently selected tab in a tab group/visible on screen, significant frame drops will occur in the viewport.
Closing the explorer window or switching to another tab in a tab group will restore frame rate, but time consuming
Issue Area: Studio Issue Type: Performance Impact: Moderate Frequency: Constantly Date First Experienced: 2022-09-28 00:09:00 (+01:00) Date Last Experienced: 2022-10-02 00:10:00 (+01:00)
This issue hasnt been adressed. I face unsubstantial amounts of lag whenever I script after these recent updates. Even if the baseplate is empty, I have not installed any new plugins or have malicious content. Its just been crazy lag scripting has become a nightmare.
I’ve been getting this lately too, on a Mac Studio with the latest version of macOS. When testing the explorer panel is impressively slow and some other widgets like the property panel also seem to have worsened, so same thing as previous posts. This is a pretty big slowdown of my workflow right now.
are your scripts rubberbanding?? I tend to type at 93wpm and every letter takes a second to be visible. This issue has never happened before and is making me complete work in such a slow tedious matter
Looks like viewport frame drops have been resolved in the latest update, although hover animations in the explorer window itself seem to be choppy and delayed which I didn’t address in the first post. Remaining issue is very minor.