CSG problem alignment


#1

Hello all. I have this simple stairway made where all parts are aligned. When I union it however some parts seem to have extended outwards. As you can see (changed colour to green to see clearly), the size has 0.001 increased. I find this with all of my csg builds which should be perfectly aligned. Any idea why this occurs? I use the Studio Build Suite plugin to move my bricks.

51

54

11


#2

The new CSG system gets rid of the constant solving errors by bumping your parts all around and trying to find a match. It’s great for speed, but if you want a certain part of your build to be completely flush and exact, you’ll need to disable CSGV2 in studio settings and try again.


#3

I believe to reduce the number of errors you got for unsolvable unions, the new CSG system offset parts by a fraction of the amount you can manually in studio. This can cause some visual offsets as you have pointed out, you could try going to File > Settings > Physics and enable DisableCSGv2. You may find that the union is unsolvable with the legacy CSG solver, but this is the only way of fixing it.


#4

I’m not sure if CSG is appropriate for this case. Check Settings -> Physics -> ShowDecompositionGeometry. For a something like a staircase, which is large, somewhat complex, and demands fairly precise collision geometry, I think you’ll find that the collision geometry is not what you expect, and might not be sufficient for stairs. Why do you want to union the stairs in this case?

To answer your question, in general you can often avoid this problem by building your union subtractively from one large part, rather than additively from multiple parts. For a shape like this, it would be easy set up multiple negative parts to cut away stairs.


#5

The real question is. Why does Roblox’s CSG system goof up so much. >.>


#6

It’s purely for visuals. I replace the actual stair with a slope.

Negative parts might be the solution in this case, but that takes time.


#7

Making a union of these stair parts to generate a slope-like collision is a horribly inefficient solution to this problem. This impacts performance so much more than if you were to just make the parts non-cancollide and add an invisible cancollide wedge over it. You really shouldn’t union parts together for that kind of reason (even better: don’t use unions at all if you can).


#8

I hope this helps you :slight_smile:


#9

You’re saying those misalignments are caused by CSGv2?


#10

That’s exactly what I said. Add an invisible slope.


#11

What’s the reason for making a union out of this in that case?


#12

Yes, that’s it.


#13

Then I wouldn’t agree with that at all. CSGv1 also had those issues.
I can say it’s caused only by Floating Point, by the looks of it.


#14

Yeah, ahaha. I’ve had problems with it in the past, now I just ignore them. :weary:


#15

#MeshesForLife CSG is only good for bricks lol.


#16

Yeah dude! I’ve been making lots of new meshes in Blender recently, although not top tier quality. :grin:


#17

Keep going the more you learn the better and faster you’ll become!


#18

Thanks Veov :slight_smile:


#19

V1 has never had an alignment problem for me. Here’s the same operation done with V1 and V2.


#20

No problem!