While working on my project, I happened to encounter an issue whenever I change the CollisionFidelity of a MeshPart and try to parent it to an object afterwards. Studio proceeds to crash and not respond indefinitely (I hopped off my PC and left the frozen Studio instance for around 20 minutes, after which I came back to absolutely no changes).
Relevant FFlags enabled: CSG v4 related flags, including Mesh Union support, although no union operations are running, so I doubt this is a concern.
Expected behavior
Studio does not crash while editing the collision properties of a MeshPart and parenting it afterwards.
There’s no crash report because it’s a hang and not a crash, don’t look in there. Look in your normal logs folder instead, and find the most recent.
A memory dump is useful in theory (though yes, never post them publicly), but only if you’re confident it’s actually correlated with the hang–I suspect because it’s “just” a hang, a memory dump isn’t actually being made, and you’re looking at one made earlier.
Ah interesting, I did not know you tweaked your FFlags.
Out of curiosity, if you can figure out an FFlag combination that has the crash, send them over to me. I want to make sure that this isn’t something that will come up when engineers start enabling their features.
Happened more often with CSG v4’s Mesh Unioning thingies. Studio crashes much less tbh with that off. I also had random stuff on like the new Light Attenuation, but it seems like y’all didn’t work that out yet. Gives me weird cubic unshaded voxels, ngl
Out of curiosity, what is it that you’re planning for the Light Attenuation? I wish it could be more like the NumberSequences with the falloff.