(09-23-2017, 05:45 AM)oort Wrote: No need to worry about your English. I was able to understand without any problems...Thanks for the feedback.
oort Wrote:It looks like you are using the grid intersections to choose your points.It was casual. There is no need for that and the grid is just a reference as the regular grid.
It's all new code (no reuse) and I try to keep it working the most integrated to Wings3D as I can. The view/camera commands are already working and I still want to add support to the Wings3d constraints keys for distance.
oort Wrote:After creating the path, is the plan to assign a shape to the path and then we see the shape extruded along the path?Yes. I'm still not sure about how I'm going to manage that.
When I first started the lost curve plugin (Apr/2013) I started it as a freehand style and the 3D object was created during the curve draw over a surface - that was nice, but I don't know if I can do that with the new structure I'm using this time:
While in curve mode everything is in a parametric form, so the "curve object" will need at some point be converted to a real Wings3D object and it's my intention to have an option to set its UV map at that moment.
"Avonaeon" at YouTube Wrote:If you use orthographic mode and have it viewing along only x, y or z, does it then just use the standard planes as the starting point?We don't see this temporary grid in other apps as I could noticed watching a lot of video tutorials and I believe it can be useful for we better see where we are on the "space". During the time I was working on it I also noticed it cannot be active in those view modes - it's a messy. So, yes, that should happen.