I am running an M1 apple chip with 16 gb memory, on a 24-inch retina display
This bug occurs whenever I am typing in the script editor. I notice the letters displayed to noticably lag behind what I am typing. To reproduce this bug, open roblox studio on a mac and try to type quickly
Expected Behavior
I expect coding in studio to be fast, and for the code I type to appear as I type it
Actual Behavior
The displayed code noticably lags behind what I am typing, taking an annoying amount of time to catch up. This problem gets worse when less memory is available on the system, although it still occurs with a large amount of free memory.
This is making it much harder to code quickly
Workaround
No
Issue Area: Engine Issue Type: Performance Impact: High Frequency: Constantly Date Last Experienced: 2022-10-11 00:10:00 (-04:00)
All macs have this ussue. For some its worse than others. Like for me whenever I interact with any server scripts roblox crashes. When I type it rubberbands. When I open the animation editor roblox gets glitchty.Where has the mac support gone??? this is too much, the animation editor now makes studio go boomStreamable
After the update today, it seems that the problem has been solved!! But, this is different thing, login error at multi-client simulation still happens.
Is the Script Editor issue still happening? We have been looking at addressing it recently. If so, can you either DM us your place or at least describe it roughly (number of scripts, largest script size, average script size, number of parts, instances etc in your place.)
Is the Script Editor issue still happening? We have improved Script Editor performance and this looks OK on our side?
If you are seeing it, can you either DM us your place or at least describe it roughly (number of scripts, largest script size, average script size, number of parts, instances etc in your place.)
Closing for now, let’s reopen when this happens again. Note that we also are tracking slow typing on large / complex places. That issue is unrelated to this one given this one was caused by a refresh, the one I mentioned is caused by Studio internal architectural issues and resource starved scenarios.