CSG V3 Shading and Texturing Issues

[Imprezive]

there shouldn’t be ANY way this issue keeps occuring without the Roblox staff noticing this too. im extremely surprised about how this even passes the QA test, this issue been going on for a few days/weeks. no ways to resolve it besides ways to break your texturing. come on, Roblox.

(Image courtesy of user “hurtfuleagle2”)

[DanBuildsTrains (Dan)]

@subcritical could this be a result of the new part shape/size changes? This problem seems to have started around the same time it was released.

Improvements to Part Shape & Size

Hey everyone, We have made a number of quality-of-life fixes to the BasePart.Size and Part.Shape properties over the last few weeks. Let’s dive in! Improvements to Size Before, Size was supposedly locked so that X=Y=Z when Shape was set to Ball. This behavior was broken in a way that could lead to clients and servers disagreeing about the size of the sphere. The Y and Z axes would only snap every other time Size was set to a new value. This restriction has been lifted: Spheres can be given…

[Focia19]

We’ve file a ticket to your internal database, and will start investigating!

Thanks for the report!

[DanBuildsTrains (Dan)]

I tried it and it didnt fix it for me

[Real_BenTheMiner]

Any updates on this bug? It seems major enough to be high priority in my perspective.

Also, why does it say that this topic has been solved? It definitely has not been solved as the bug is not fixed yet.

[BuildIntoTrains (BIT)]

CSG V3 Shading and Texturing Issues

We’ve file a ticket to your internal database, and will start investigating! Thanks for the report!

[Focia19]

@Real_BenTheMiner

Also, why does it say that this topic has been solved? It definitely has not been solved as the bug is not fixed yet.

It’s because the OP marked it as solved and an automatic lock timer has turned on!

Please don’t mark a reply as solved if that’s not the case, as it’s messing our internal process as well!

We don’t have updates yet, but we may have some this week! Thank you for your patience!

[deezychesse (Deezy)]

Here’s another example of this bug where the color on the union is different even with UsePartColor enabled

[WH_10]

After checking to replicate the bug today, it appears that it already has been fixed. Even un-unioning bugged unions appears to fix the issue.

[Real_BenTheMiner]

More views of it seeming to be fixed! Great news!

Only slight issue is that unions are not fixed automatically and you must separate/redo them for the shadow issue to be fixed.

[Real_BenTheMiner]

Either fix is not fully rolled out yet or the issue is still occurring:
https://cdn.discordapp.com/attachments/947255567393632276/1128733935812218950/Random_-_Roblox_Studio_2023-07-12_13-04-23.mp4

[dxpsoul]

I am still having the problems as listed in one of my devforum posts, sadly I cannot post bug-reports, so I will link it here. Please revert this update so developers CAN use CSG v2 without being forced to V3 and having bricked engines.

[TrojanHorseAttack]

I’ve had this exact same issue! Negating parts just makes them dark and there is no real way to fix it.

[Real_BenTheMiner]

I believe this is fixed by now? Can anyone deny this?

[Real_BenTheMiner]

This has been fixed. It can be marked as resolved now.

[dxpsoul]

I can deny this, still having problems with unions.

[Real_BenTheMiner]

Could you send a screenshot of the problem?

[dxpsoul]

I’ll link to a post that I have already made which shows my problems + errors.

Issues with CSG V3

I would like to to negate a union in Roblox-Studio with CSG. The Issue is that with CSG v3 it gives me the error code “-11”, and with Legacy CSG it gives me the error code “-3”. I have tried to change the CSG version, the rendering settings and attempted to do multiple attempts to contact roblox-devs. See post here. THIS POST IS RELATED TO A TICKET WITH ROBLOX SUPPORT, I JUST NEED IT TO ADD A LINK, PROBLEMATIC UNION & NEGATE AND PICTURES WHICH IS NOT ABLE TO DO IN THE TICKET ProblematicUnion…

[Real_BenTheMiner]

This doesn’t have anything to do with the shadow issue that this bug detailed.