—“Really awesome job on prefab V2. It looks fabulous and absolutely amazing.”
Thank you! Glad you like it.
—“Now about a bug (hopefully minor):”
Just tried your model in v2. It is not just a uv issue. There is something “wrong” with your file.
If I load it into AC3D, it even crashes the app!
So I took a closer look at your file:
f 25/1/1 26/2/2 28/3/3 27/4/4 1/5/5 2/6/6 3/7/7 4/8/8 5/9/9 6/10/10 7/11/11 8/12/12 9/13/13 10/14/14 11/15/15 12/16/16 13/17/17 14/18/18 15/19/19 16/20/20 17/21/21 18/22/22 19/23/23 20/24/24 21/25/25 22/26/26 23/27/27 24/28/28
Here you go: you have multipolygonal faces. You need to triangulate your model prior to export it.
A typical face looks like this:
f 272/272/272 271/271/271 273/273/273
That a face definition of your model exported as obj by Prefab.
What you look at is a face with indices reference per vertex 0,1 and 2 to uv and normals.
If you would export while using quads, it would be valid as well.
It would look like this:
f 272/272/272 271/271/271 273/273/273 274/274/274
The Away ObjParser ignores some parts of the face info while validates partly others, as a result, the indices are out of sync. Prefab internal checks prevent the app to crash and it does it’s best to display something. While ac3d crashes, probably because it doesn’t have a validation into the face contruct routine.
That Prefab 1 obj parser displays it, is surprising. Especially without a warning. There is some kind of a “doctor” inside (way too expensive for heavy models).
Prefab 2 has one more generic, not extended enough for now (but faster). Basically it doesn’t attempt to fix, it tries to survive and display all what is possible to be displayed. I’m adding on the todo a notice for such case. Your model will be a perfect test case file.
Finally, your mtl is holding a colormaterial definition.
In Prefab 1 / Away 3.x, the parser would ignore your mtl definition.
However, you can see in Prefab 2 and in Away 4 that it does construct this ColorMaterial. If you plan to reexport from Prefab to load in Away3D, then its not a problem, as you will get the propper mtl with the right material. But if you go directly from your editor, then i suggest you do load without mtl. either by commenting out the “usemtl” tag into your obj file or ask the loader to ignore dependencies.
That having said, it is of course possible that some bugs are in parsers here and there. So keep reporting!
Hope it helps