Thank's for veryfing this "problem".

And if it's reported to E-On then even better.

This might be something skipped for performance resons but i have to admit that it did surprise me.

I can also add that it does not work in Vue 6 either.

I used the mirror material in the Vue Basic material folder.

I tried changing some settings but nothing I tried did help.

But I can of course have tried the wrong things.
 

Sorry, missed the Yes and the meaning of the happy face.
Thank's Bob :)

Quote - > Quote - Say a model has 10 verices witch is refered to from 0 to 9 in the face data.

Say that the vertices from 3 to 6 belongs to group A and the rest to group B.
Now if I want to export the verticese for group B they should be
0-2 followed by 7-9(jumping over the vertices belonging to groupA).

As far as I remeber thats also the only data that is needed for a morph.

Is this correct?

Yes. Actually vertices are numbered starting from 1, but you have the general idea right. You can use an OBJ file containing only vertices as a morph target, but most modellers will want facet definitions before you'll be able to see the mesh and edit it.

The morph files my program will create is just for import as morphs into poser.
The actuall geometry (the faces) will be keept in a file with the fully morphed model (welded and with no groups).

Any suggestions on how to order the verices that belongs to a bodypart.
 Should it be in the order they appear in the face description (in witch case also the order of the faces would be important ) or should they be ordered by sorting the vertice references in the faces.

Or are they supposed to be sorted some other way?

Unless someone can help I will have to do it  the hard way by building a 10-20 vertice model with a freaky vertice  order and then analyse the generated poser files,exported Morphtargets etc. in order to find out how poser orders the bodypart vertice data.

Yeah but if I want morph the area around the lips (and now I consider them to be different groups/bodyparts) then that would be a problem if I only could export the head or the lips.

As it is I could actually export the head and the lips.
Get them into Silo2 and edit the model.
Export the lips and then export the head.
Import respective as a morph.

This way of doing it even seems to work for a full model.

So if Silo can get this right so should I.
The needed information seems to be in the file.
By witch faces that belongs to a certain bodypart i can find witch vertices that has to be included. Question is how i find the  correct order.
Say some faces in a bodypart references the following 7 vertices.
7 2 1
1 3 4
9 6 3

Should the vertices be ordered  in the order they are used
7
2
1
3
4
9
6

Or the following way, just skipping those that not is used by the bodypart.
1
2
3
4
6
7
9
Or maybe in a compleatly different way?

What I more or less want to do is to export the full model out of Silo and the have my program to automatically write out all the morphs so I dont have to do it one by one.

Also Im not sure how the materialzones gets into this as long as we talk about exporting the geometry from poser as a morph target and importing the modified data.

Nice to see that people still remember my old models ;)

If I just got $5 for for each download of those file and I could had quit my jobb and done Poser stuff full time ;)

Well.
Applications won't help me as I want to do this from an application of my own.

So if I get you right.

Say a model has 10 verices witch is refered to from 0 to 9 in the face data.
Say that the vertices from 3 to 6 belongs to group A and the rest to group B.
Now if I want to export the verticese for group B they should be
0-2 followed by 7-9(jumping over the vertices belonging to groupA).

As far as I remeber thats also the only data that is needed for a morph.

Is this correct?

I suppose that this also means that if I for some reason want to write the face data aswell then I have to change the references in the face data as vertice 7 now is vertice 4.
 

Look at it from the bright side, the new TOS could give you some ideas for renders that demonstrates how absurde it is!

I allready have ideas for at least five images...opps now they are six... EDIT: ..and up pops another one..now i got seven...

Message edited on: 03/23/2005 05:43

Message edited on: 03/23/2005 05:45

Ehhh, but it was not quite that fast... Hhhrmmm, hate to admit it but I got 3 days to be 36 hours. Strange I can have a job and even get paid for it. It should of course be 72 hours witch of course still is god for a Standard delivery. Not much idea to pay extra for 2-day delivery. Sorry about that...;)

Got mine right now (I'm in Sweden). First I would like to thank UPS for the speed of delivery, only around 36 hours for a standard delivery, that's nice. But most of all I would like to say thank's, to e-on for sending a compleate box and not just the CD:s and the manual even though it was an upgrade from VUE4PRO. It does add to the value...

Yeah, I find it pathetic that E-On not give you the final version for free. If you have tested throughly you must have put weeks of work into it...

??? I don't understand the problem at all, who cares if the same kind of solution exist and even have existed in other application 10 years ago. I can se what it can do, so I want it, and now I will get it in my favorite Landscape render;)

The camera might be in the same place but it has for sure not the same focal setting. The placement of the camera and the focal setting do however hardly have anything to do with the problem. To even guess, a real closeup and more high ress render is needed so that one can see what it is that goes on in the hair.

The problem have been fixed in the current Beta version.

Triangulating in my model app was my first fix to this problem. However, in order to save on the geometry in the modelling app I did rather locate the problem areas and rebuild them manually. So, now I know that the problem is created by polygons with 5 or more vertices, something that can create problems for some applications. But, as import worked in Vue4Pro I do expect that it's supposed to work in Vue5 as well so I will report the problem.