Malo

By changing the Obj format created by AM, it is possible to have a good model in Blender. The changes are as follows. - rewrite the triangles (eliminate duplicate vertice in the faces). - eliminate unnecessary edge in the face five sides - Eliminate the two edges formed on single hooks to create 5gones. The benefit is that it is possible to keep the Uvs and operate with MDDS. If you want to see the result in Blender (and the trick to recreate volum lost in subdivision with low-poly): Thom walked. http://treser.net/AnimationMaster/2015/export/Thom.blend I deepened my reflections on the conversion hooks, and here's a better solution to the one I presented above: the trick is to convert hooks in 5gones. (the 5gones in subdivision create better topology than triangles.) The explanation of patches is interesting (thank Rodney), it allows to better understand the problems of rendering normals, bumps, displacement, patches with 5 sides, compared to polygons that are attached to each other without being able to break away and create holes in them. But the advantage of the patches is that they can be dynamic and not be dependent on the topology for the density of polygons. Nice to see the evolution of your plugin, rasikrodri.

yes, indeed ... but more poles with 5 or 3 edges, and there I don't know what is best 3 pole with 5 or 3 edges or one pole with 7edges. I think Furchur want to make reference to the technicque you use in your script for Blender "Animation: Master Middleman". If that is indeed this could work, but I was not thinking about that, because if it is for export to the outside of AM and reimport in AM, there is an easier way, which is to use the UVs as references to reconstruct the topology of the starting AM model.

that's right nemyax, the Catmull Clark Subdivision works like this ... And I thought to do this at the start. But from what I understand, a good topology includes 3.4 or 5 edges by vertices, hence the choice of topology of a hook in the first level of subdivision, after the rules of subdivisions will be classic.

In my opinion, the export of information to the AM to a classic polygonal program is possible. There are just two problems to solve. The first problem is the triangle: AM uses to the triangle, the patches 4 sides, and overwrites one of its sides, which creates a bad topology: Is it possible to do otherwise ?, yes! The solution and the code is in Jpatch, the code is visible (in Java) (http://www.jpatch.com/) The second problem are the hooks (3 types). the topology of AM or Jpatch gives no perfect solution. they create triangles. (with bugs in AM?) One solution would be to get to create a topology like this: Once solved this, I do not see what could block the export. For import is more complicated ... There are different manner to do it for the purposes and different results. Props, it could improve its ability for example by giving a subdivision level option and importing Mdd for animation. patches, nemyax's plugin works well, it requires creating a retopology the model to fit the topology of the patches before the import. Use AM to animate polygonal model, rasikrodri's plugin is promising for that. The import/export of information of UV, bones, weigts, cameras, lights, scenes should not be a problem. What is missing for AM is time, mathematicians and programmers.

Thanks!

That helps, David! Thank again!

Thank you all for your answers ! I'll study it all tonight.

Good evening everyone, I am looking for a way to give the same size of a bone to another bone by the constraints or expressions. Anyone know how we do it?

good news!

Nice work! I have not 3DCoat , so I could not do testing, but have you found a way to not break the topology hooks and patches to 5 sides in futur? Again congratulations.

thanks you!

Happy holidays to all! Congratulations Nancy, your image and colors are very beautiful. Congratulations Robcat! Your work on procedural material gives an impressive result! Thank you for voting for me, it'll allow me to restart my subscription for another year! Thank you all very much!

It's a great tool! Look at this picture: Keep the purple topology and you get a topology compatible with AM: I explain the method in this topic: http://www.hash.com/forums/index.php?showt...mp;#entry390604 Don't need to remodel or to retopology the model in AM. (there is some correction to do, You can find some patches made with more than 5side, but it is very easy to repair, before import in AM)

Thank for your reponse. That is a good news!

If it helps, I had this little flash animation for a fish (modeled in Sculptris to create the rotoscope) modeled in AM ... we see the steps by steps : flash animation

Hello, Is it a way that the bones which the attribute "Assigning Prevent PC's" are "on" are not visible in "Edit CPs weights"?

Thank you very much again David!

Thank you very much David!

Hello, I am trying to use models using the rig "steave headgizmo V2" on the V17 or V16 version on win.64bit. but "CEyebrowsCentre, CEyelids, CMouth and CCheeks" no longer work. Do you know what is wrong with this rig in V.17? What needs to change to make it work again?

Hi, Thank William for the link. I have done a new test. Using Xnormal to bake a Sculptris sculpt on AM model. The two solutions have goods and bads renders. But I think, with a high export (4096 subdivs), unwrapp in AM will give a better solution. I will do new test then when V18 will be done.

A hight subdivision in V18 will help to have a good result. Do you know, when V18 will be finish? Here's a little experiment I do today: I create a model. I just peak the model in modeling window before to apply UV. To try to have à peak UV (try, because it seem that it don't peak it completely) I export the model x1 with its uv. I repair the 5 sides polygons in wings3d. The UV is the same, except that we have lost the coordinates of bias. I use Troer to convert this new obj, Troer recreates the coordinates of the bias. I import the models in AM16, and render : A : the original model, B : the model converted by Troer. If you want to compare Uvs, here are the two mdl files and the map in this zip file

From what I understand, and so I thought Troer. The uV a patch is subdivided into nine areas defined by the bias. The picture of the UV polygon is divided into 9 part to be distributed to each area of ​​the patches. If the bias is not located in tier length, there will be deformation. And I think, the bias coordinate of the wizard plugin is calculate on the 1/3 of the % magnitude and not on the length of the side. But I ma not sure. What I am sure, the bias coordinate of the wiazrd is not on the 1/3 on the lenght, and it is why there is bad result.

Sorry, It is not easy for me to explain this in english. In the UV window, a patch have bias, but you can't see them. A polygon have not bias. To write an UV for a polygon, you need to write the X Y and Z coordinate for each vertices. For a patche you need to write the coordinate for each CPs and for each bias (8) (in blue on the graphic) The problem when you import the UV of a polygon, you have no coordinates for this bias. So you must create them. (The CPs have the same coordinate as the vertices) For Troer, I use the 1/3 of the side for each bias. What I understand about the wizard plugin, is : it use the 1/3 of the magnitude of the CP, so the the map in the patch is deformed.

Benoit is the programmer of Troer. This is a friend who knew very little in 3D, and nothing in AM. It was kind of program Troer in his free time. Troer is not the solution to long therm. It would be better to improve the import AM plugin (and also export with more options). To return to the issue of the wizard import. I think it would not be difficult to fix it. It seems to me that the calculation error come from there is a confusion between the tier of the side and the tier of the magnitude. I'm sorry if I'm not very clear in my English. A picture to help to understand:

Hi Robcat! No, because it's not a bug from AM. I did not understand all the way to encode the Mdl format. Troer written an incorrect file. Luckily before version 17, AM rectified the code, now it no longer does as expected. But it is not a bug. Nothing to do, I read quickly in a topic, the closure of 5-sided patches will be automatically ... Is this true? If this is the case, it will be great.