of     1   

CodeNil
#156323828Thursday, February 19, 2015 6:54 PM GMT

We need a triangle object, and no, not a wedge, basically a part with no cframe, size or position, just 4 new properties, position1, position2, position3 and normaldirection. Input 3 vector3s into each position and either -1 or 1 into normaldirection and it will render as a completely flat triangle between the 3 points, also only rendering one side based on normaldirection. You could then combine huge number of these in csg for actual mesh type objects with high optimization.
WackoMcGoose
#156325708Thursday, February 19, 2015 7:25 PM GMT

Serious support. One of the biggest nitpicks I have with Solid Modeling is that I keep thinking of cool shapes I want to make, and then realize how incredibly complex it'd be to do in CSG, whereas with the experience I had making render classes for a MC clone, it'd be trivial to make by defining individual vertices. Then again, given how SOLID Modeling works (volumes rather than triangles), it would actually have to be a separate system entirely. Plus, looking at Unity Engine and how its Mesh Colliders work, Roblox would either have to implement that (with serious overhead, notice how Unity explicitly says the render mesh can't be used as a collision mesh due to complexity, and you have to make a simplified mesh for collision), or have the new TriangleModeling objects use rectangular collision, like how CSG used to be. More likely the latter, because decompositional geometry works /because/ CSG is based solely on primitive shapes, whereas it'd be computationally expensive to make convex shapes from an arbitrary mesh... and that's assuming the mesh has no leaks! (Yes, I know about Binary Space Partitioning, which is a possible solution, but again takes a lot of preprocessing - hence why Source maps take a while to compile - and wouldn't work unless the mesh had no leaks.) Still though, being able to make shapes from arbitrary triangles would be awesome, even if we have to do collisions the old-fashioned way. Highly support.
sebe30
#156325945Thursday, February 19, 2015 7:30 PM GMT

+1
CodeNil
#156326148Thursday, February 19, 2015 7:34 PM GMT

Yeah thinking about it more, probably not ideal for csg in its current state, but would still be useful mainly just for rendering, if it was treated as a non "part" type object, aka no collisons or anything, purely just visual. This would also be a extremely simple solution to importing meshes, as we can currently import them into thousands of wedge parts, instead just import them as half the amount of these parts with 1/6 of the faces needed to render and no physics, then just create a couple invisible parts for the collisions and boom.
Valoric
#156329335Thursday, February 19, 2015 8:27 PM GMT

agreed

    of     1