Forced New Gen Studio causing issues with current Gen Studio

Hi there,

I recently made a post about a related issue: “Parts randomly changed their size when using a Z-fighting prevention trick”.

While continuing my work in Studio today, I noticed even stranger behavior. Not only are parts randomly changing their size and values as described in my previous post, but now copied models and other objects are starting to completely break apart, as shown below:



Here’s another example where only one fence model is affected:

Since the Roblox Studio Beta “New Gen Studio” is being randomly forced on some of our team members, while others revert to the old version, my only assumption is that New Gen Studio and Old Gen Studio are conflicting somehow within the workspace. (When working in a Team Create)

Only Roblox parts seem to be affected, orientation values become slightly corrupted or misaligned.
This happens exclusively in our development place, not in the main game place, and we don’t run any scripts or commands via the Command Bar.

I’m not entirely sure if this issue is directly caused by the New Gen Studio rollout or something else, but at the scale of our project (Emergency Emden), it’s becoming quite frustrating to fix all these orientation and part issues manually.

Would appreciate if this could be investigated, it seems like a possible New Gen Studio compatibility or replication bug.

2 Likes

We’ve started looking in to this issue. Do you have a placefile or steps to reproduce the issue? Are you still running into the issue today?

I work with my team in a DevPlace, i can try to find some parts that have the “-0” values in them. I dont know if that helps. All i can say it happend one time and then never so far.

Without a repro file / steps, it’s really difficult for us to test and fix bugs like this. If you could get us this repro info, that’d be great. Thank you!

I get that, i can try to give you a part where its “-0”.

Here’s a part of a model that contains the “-0” value. If this doesn’t help, you can go ahead and close the bug report. The issue only occurred once in this place, and I’ve already manually fixed all affected areas.
Repo.rbxm (3.9 KB)

Thank you for reporting this - we weren’t able to reproduce it so we’ll be closing this bug.