Interesting, We’re looking into some client local CSG features, send me a DM if you’re interested.
3 Likes
Hey, I’m having a problem with in-game CSG color transfer (SubtracyAsync).
My game relies on the fact that CSG SubtractAsync did not had any sort of color transfer related to
the NegativePart used.
In my game a part is replaced with the result of two CSG SubtracyAsync operations, with the purpose of creating a cutting effect.
In order to address this issue in this update, I changed the color of the operation’s NegativePart to match the BasePart that was the target, but this had an odd, unexpected side effect.
Even with UsePartColor enabled, the resulting face may or may not be darker than the BasePart color. However, this color change is not permanent and will be undone if you perform another CSG operation on the part that results.
The resulting face may or not be darker than the BasePart color, even when enabling UsePartColor, this color change is not persistent, it is going to be reverted if you apply another CSG operation on the
resulting part.
I wish there was a way to completely turn off this color transfer. Given that my game depended on the prior behavior, it is a game-breaker for me.
Public area where this problem also occurs:
(14) Smooth Slicing (Beta Testing Place) V 0.1 - Roblox
2 Likes
Interesting, I’ll take a look at this
For anyone interested. We’re going to do a beta for client side CSG soon. If anyone is interested in joining, please let me know
7 Likes
I am very interested in client side CSG. Please let me know if there are any more details about participating!
I’m interested in joining. So is @tobiO0310.
Please DM the both of us when we get added to this beta.
Count me in for client side CSG too! Let me know when the beta releases.
I’d also like to join in the beta for client-side CSG. I have a few ideas I’ve been itching to try.
I’m interested in joining the client side CSG beta!
Any ETA when this will be enabled globally in-game?
Did a little digging, discovered this function under the name subtractAsync2_INTERNAL. Calling it from both the client and the server returns an error message that reads:
Internal Dev only. CSG3 New API is not ready to be used externally
According to API dumps, two new functions were added on January 3 of this year, the aforementioned SubtractAsync2 and UnionAsync2.
Since we haven’t exactly gotten any updates since December now, I can only speculate and say that they’re working on a brand new system or working on client-performing CSG operations, which is very exciting. All of this is taking place after the staff created the client-side CSG beta list (which I have been waiting on the list since December 22).
4 Likes
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.