(11-14-2013, 02:23 PM)Jake Wrote: Hi,
besides the new main feature "Make it solid and working with custom Meshes" I'm open for requests. So don't hesitate to bring in your ideas.
More ideas so far:
* Callbacks to allow the user to manipulate mesh data while being generated (e.g. to change UVs)
* More UV mapping modes (especially a mode to bend across curvation, e.g. to map a road without distortions)
Jake
These first ones aren't really mesh builder features, so much as spline features.
Are you still planning on constructing the surface snapping features? For me this would be a huge help.
Along the lines of surface snapping, having a way to snap a control point to an arbitrary f on a spline would be helpful, using the same kind of sync options available for ControlPoint to ControlPoint connections.
Then also being able to do a Relative position sync pos/rot would be helpful for building more complex shapes.
As for the mesh builder script I could probably list features I'd like to have indefinitely, so these are just a few that really come to mind for me.
Another thing that'd be nice is adding onto the way hollow works.
Right now you're using a percentage which works, however It would be nice to be able to specify either the interior diameter or width/height, or the thickness of the mesh.
Also allowing all the shape data that is on the SplinePathMeshBuilder to be handled per control point. That way instead of having a base width/height and then scaling it, you could directly specify width/height values.
Another useful thing that could be done is setting up a mesh builder so that you can take 1 spline, and extrude it along another spline.
a rotational Lathe tool, this one I think might actually be fairly simple to do.
I'll probably work on a lot of these myself, and would be willing to collaborate and test/debug them.
I've attached the last functioning version of my TwoSplineMeshBuilder, it's not commented, and its feature incomplete.
The script needs the ability to specify start and end points, per spline, for the mesh generation.
This present a potential problem with either very dense vertices on one spline, or needing to figure out how to determine if vertices need to be condensed, then how to update the triangle list generation.
The script also needs the ability to figure out the correct winding order. Currently if the splines are not in the right positions in the component, then the mesh will be inverted until the splines are moved so that they have opposite positions.
I haven't invested time into figuring out the winding order issue yet, I've been focusing on trying to implement the start and end points (the code I've done for that hasn't been attached)
The callbacks might be a big help in solving a few of these issues for me, such as building my own surface snapping system with mesh deformation (to prevent mesh intersection and visual artifacts)
I could really go on and on, if you ever want more ideas, just let me know.
