Yeah well the new system is just way beyond broken… hopefully it gets fixed soon…
2 Likes
I’ve noticed a bug with this beta. This union I made can no longer be separated, and any negations I add to it ruin the union entirely. Shown below is the error and the before and after of a negation.
2 Likes
Unfortunately not, there’s a post on how to get them back though if I remember correctly. Look it up on Google.
1 Like
Will there be a fix at some point so our CSG V2 unions can work, as they crash studio whenever you try to use them.
1 Like
The engine needs some improvements as shown on the picture.
Last picture explained:
- Didn’t merge the left top parts into the normal part
- Created some weird lines on the bottom left and top right side.
I assume this is a bug?
7 Likes
I’ve also tested the bugs reported above. It seems that all of these bugs are caused by rendering problems in the new CSG engine.
From what @DevJanick mentioned, Studio Beta: CSG Has a New Engine - Vroom, Vroom, Vroom! - #102 by DevJanick didn’t have the negated parts merged onto the normal part.
Thank You!
Now I won’t have to search through the autosaves that studio creates to find an uncorrupted version of the union. 
Hi, would you mind sending us the models for which CSG V3 did not succeed? We are more than interested in fixing these issues. 
1 Like
Any chance you could extract the parts that cause problems for CSG operations and send them to us? Thanks a lot for the feedback. 
Sure, here’s a place with some of the models I had most issues with… UnionPlace.rbxl (219.4 KB)
(BTW In folder number 4 there’s unions that were made with the older engine…)
Does that only happen with CSG v3? If so, could you provide a place we can use to investigate? Thanks!
1 Like
Hi yes - one of the major goals of V3 is speed improvement over V2 for the purpose of having a much faster in-game CSG. CSG V3 will eventually be enabled in-game, once we work out all the issues. Studio V3 beta is sort of testing ground for that.
1 Like
Supporting meshes in CSG is one of our future goals.
3 Likes
In terms of robustness/accuracy, V3 should be as good or better than V2, but the major drive of the project is to make it way faster than V2. Some of the perceived V2 accuracy issues are UI related - V2 engine is actually waaay more accurate than V1.
1 Like
UI related? I’m confused, when I separate v1 unions in v2 it can not only offset parts, but rotate them wrong. I have cylinders on a model I made, and separating with V2 caused it to rotate the cylinders into a different position.
1 Like
Hi! Not sure if this is a CSG issue. It looks like the multi-colored picture at the bottom shows convex decomposition (collision geometry) for this object (Default setting, I think). Can you please confirm and/or, if possible send me the place or model file in a DM.
Hi - would you be able to share the place or model file in a DM, so we can take a look at the issue. Thanks!
1 Like
I should have been more specific! By UI, I meant how the frames (position/orientation) of the objects are handled on the level above the CSG engine. When you work down on the low level a lot, you tend to think of everything higher up as “UI”
2 Likes
Oh, noted. Thank you for clarifying.