Not a clue in the technical section of Roblox Studio but I have some general questions because Studio keeps crashing
A: Is 120k parts and 180k instances a lot?
B: Is it normal or at least not unusual for Studio to crash either just running or running a bigger process? (ex: duplicating large number of parts or autosaving)
C: Is it possible that this is partly due to computer specs?
D: If the answer to C is no, is there a way to optimize 120k parts without losing detail and without the usage of 3rd party apps?
forgot to say that the published version of the game on Roblox itself is butter smooth, as well as Roblox Studio itself (apart from loading all the parts in Explorer) and has no signs that the app may crash
also there are basically no scripts so im pretty sure that its all just parts
It’s definitely a lot of instances to have 180k, especially if they’re in workspace at all times or being looped through by scripts and what not. You should also make sure that you’re not using unnecessary instances such as BaseValues, most of them can be replaced with attributes. Make sure you’re using attachments efficiently. Using unions where it’s possible and disabling collision for parts that aren’t accessible.
PC specs 100% affect performance in studio. When you’re playing in studio you’re essentially running your own server, but when playing through the website it’s being hosted on one of robloxs servers and all your computer needs to do is render everything and run the local scripts.
ill skim through the instances, but there are practically no attatchments. usually the only child to parts are lights, which are only like 40 so far. the build is basically parts and parts only, no extra bits
Then mainly it’s just to use unions where possible, use correct collision and rendering fidelity based on how accessible the areas are and disabling CastShadows on parts that don’t need to cast shadows. Other than that there isn’t much I can think of. Good luck!