Bring real world creation to your experience with Constructive Solid Geometry (CSG) improvements [Beta]

[BelgianBikeGuy]

Deserialization of parts created in studio on client is something that we’re still validating. There are some wrinkles that might need to be ironed out

[BelgianBikeGuy]

Please do give an example of what you’re doing. That being said, If you’re doing an operation with the new API and then trying to use the buttons in studio or the old API on the part, it not going to work currently. They are only unidirectionally compatible with each other.

[KUW_Alt1 (Kuw)]

Ohhhh that’s why. Sooo I guess the studio buttons will update when it comes out of beta?

[lambarini]

It just does not work at all I printed the spatial query api and it is printing every part correctly

[BelgianBikeGuy]

Hey @lambarini, would you mind sharing the rbxl?

[KiyoshiYamamato (CaptainMajorKiyo)]

This is incredible, is there a chance for us to see a similar feature be applied to imported FBX meshes?

[DeathLilian (Alyssa)]

When csg live is implemented in experience games? I just tried to test it in experience game but it doesn’t show it…

[BelgianBikeGuy]

Soon ™. In all seriousness, we are making sure everything is setup properly once it’s in open beta. We want to make sure all the raised issues are handled properly

[Blast4300]

@Blast4300

Even with these improvements to CSG, the lighting bug when using GeometryService:SubtractAsync() still exists. Below is another example of it in action.
bug_report.rbxl (47.9 KB)

@bjarkibjarki

Is the lighting glitch fixed? I remember previously the lighting on a CSG’d part would ‘freeze’ so, if you used SubstractAsync on a part that was in the shade, the created CSG part would have the lighting baked in so even when moved out of the shade the color/surface wouldn’t change.

Will these lighting bugs be fixed before it’s in open beta? It’s been almost a year since I reported my issue, and it’s still not fixed, even though multiple admins have “invesigated” the bug.

@BelgianBikeGuy

@Blast4300 Thanks for providing an example place. We have a fix that’s waiting to be deployed for this issue but i’ll make sure to test this place too

A fix for the bug was waiting to be deployed.

@meshadapt

@Blast4300 We are currently investigating this matter, and once we have a solution, we will communicate it to you.

An investigation was started (But a fix was previously waiting to be deployed?).

[zagusan]

Hello, I’ve been developing a game for this beta feature and found a bug where the output of a PartOperation can become a ball. Said ball has its material only visible from the inside. I’ve also found that the balls that get created often have a very small piece of debris attached as the same PartOperation. My theory is that the vertices of the PartOperation are becoming negative because the input part is too small and gets handled incorrectly. I also managed to get Roblox Studio to crash twice while trying to record the bug, which I hadn’t managed to do before. I don’t feel comfortable sharing the RBXL file publicly, so if you need it, you can DM me. Here are two videos of the bug occurring (in both it happens roughly after 3/4ths of the video):

2023 12 02 17 26 08

2023 12 02 17 31 09

EDIT: I forgot to mention that this only happens while using GeometryService:SubtractAsync() and not when using BasePart:SubtractAsync()

[baukeblox12]

Hi there, I keep getting the following issue when working with GeometryService:
Internal Dev only. CSG3 New API is not ready to be used externally

At line: local success, newParts = pcall(function() return GeometryService:SubtractAsync(mainPart, otherParts, options) end)

Why is this? I have enabled the Beta Feature. What is the reason for disabling this API?

[BelgianBikeGuy]

Interesting. The API is not currently disabled. That being said, we have noticed some issues with the beta feature system in general. Try toggling it off, restarting studio then back on again.

[BelgianBikeGuy]

Hey Zagusan,
Sorry for the long response delay. We’ve been looking at this issue (or a similar one). Feel free to DM me an example or just to discuss your particular case if needed. Thanks

[baukeblox12]

Yes, after restarting it a few times I got it work and have a bit of fun tearing apart this BasePart. When are you guys adding support for other objects like MeshParts?

[BubasGaming]

Support for objects like MeshParts is already on the roadmap here.

[BuilderBob2562O]

@meshadapt

Technically, it is now possible to add it as a built-in type.

Sorry for the late reply. Anyways, are there any future plans to add a built-in cone type at all?

I’m not much of a modeler to begin with, but when I do I usually try to avoid using cones since, as I mentioned before, they can be annoying to implement into a build. This is further hindered by the fact that the smoothing angle property for unions doesn’t seem to work on cones created with the CSG system, meaning that no matter how many faces you have (unless it’s an obscene amount that is), each face always appear distinct from it’s neighboring faces rather than a smooth curve. A built-in part type could solve these issues and make implementing cones into a build a lot easier.

[zagusan]

Hello BelgianBikeGuy,
Don’t worry about the response delay. On that topic, I also apologize for not replying, I haven’t checked the devforum in a while. I’ve DM’ed you all relevant information. Thanks for checking out my bug report.

[CheezBoy27 (NoComment)]

First thing I thought of

[BelgianBikeGuy]

Thanks zagusan,
I’ll take a look at it

[BelgianBikeGuy]

Maybe. Cone actually causes some interesting issues at the tip where a lot of triangles merge together. Basically it can be done but the performance penalty is severe. We are trying to find a way around it cleanly