Hi Peter, well one of the interesting things about NURBS modeling is that every NURBS surface does already have a UV space associated with it.

These UV coordinates should be already being exported when you save out to a polygon mesh format (except STL format which does not support it).

Right now each surface in an object will all be mapped to the same UV square, so if you apply a texture it will be basically mirrored like copies of the texture on each surface. I do want to add something in v2 to make each surface be associated with a small independent region of the texture instead of the whole texture.

But I don't know if that is the kind of uv mapping that you are talking about. I may need more information from you about what you would like to see for uv mapping inside of MoI.

- Michael

Hi Michael ... yes parts of the whole material ie....
or more then 1 material to one nurbs object.....
Peter

Hi Peter, I do definitely want to support assigning different materials to different surfaces within one NURBS object.

That's an area of "object properties" which will probably be a slightly different area than layers/grouping, like probably there will be an "Object properties" panel for editing things like materials assigned to an object, and the grouping/layering/organizing type list is likely to be a separate UI panel.

I'm not quite sure yet how this will relate to UV mapping specifically yet though.

- Michael

"... UV coordinates are already being exported when you save out to a polygon mesh format"

Is this true when running your SeparateOBJ.exe program ?

Ed

Hi Ed,

> Is this true when running your SeparateOBJ.exe program ?

Yup, it should be - that program doesn't remove any uv information from the OBJ file, it just basically re-arranges some of the grouping labels around different faces, and also adds an additional kind of grouping label called usemtl which some programs seem to want to see in there.

Do you notice any problems with the UV mapping being missing after running SeparateOBJ on an object?

- Michael

I would think that layers would work well if
they can be used for grouping for textures and UV maps.
So for me the layer system should be part of the system too !
ie one material per layer etc.
Peter

Hi Peter, I have been hoping somewhat to avoid having "per-layer" type property assignments, it kind of creates a messy situation where you just want to select one particular object and change its color.

Also I want to have a much more flexible system where you can have objects belong to more than one "tag", instead of a layer system where each object belongs strictly only to one layer.

With the more flexible system it also makes it more difficult to attach properties to the "layer" itself, because if you had an object on more than one layer, and each layer had different display properties, then how should the object be displayed?

There are many problems like this that can be avoided if the properties are attached only to objects instead of being attached to the group/layer instead.


However, I do want to make it easy to select and set the properties for all the objects that are all on one tag though, that should give a lot of the same per-layer editing kind of feeling but without giving up the flexibility.

- Michael

yes I understand that !
Sounds that thats the way to go !
thanks for the reply !
Peter