[Droid803]

See title.
The bar just goes to exporting detail0, and stops.
For an hour. Before I decided to stop it.

Might be an issue with the mesh, but it can't be because its hitting a poly/vertex limit or anything because I've exported higher poly models... :/

It exports to DAE and PMF fine, but it just refuses to write the POF.

Happens on 2.0.3 stable, 2.1 Alpha, and 2.1 Alpha with insignia editor.

Attached is the file in both DAE and PMF.

Am I just...doing something wrong (but I've exported like fifty models the same way no problem), or is this a bug?

[attachment deleted by admin]

[Spicious]

You've got 4 identical polygons with
centroid at x = -55.8005333, y = -30.1753311, z = -201.328995
vertices:
x = -55.764801, y = -34.9662018, z = -201.328995
x = -55.2229004, y = -28.4267998, z = -201.328995
x = -56.4138985, y = -27.1329994, z = -201.328995
norm is in the positive z direction.

[Droid803]

So uh...
Mesh error?

I don't quite understand

[Spicious]

Yes, mesh error. There are four copies of the same polygon at the same place; that's bad.

[Droid803]

Thanks, go it working now...
I ran it through optimize with 0.1 threshold and it got rid of three faces, which I presume were the duplicate ones

[FUBAR-BDHR]

You've got 4 identical polygons with
centroid at x = -55.8005333, y = -30.1753311, z = -201.328995
vertices:
x = -55.764801, y = -34.9662018, z = -201.328995
x = -55.2229004, y = -28.4267998, z = -201.328995
x = -56.4138985, y = -27.1329994, z = -201.328995
norm is in the positive z direction.

How did you determine that was the issue.  It would be nice for these errors to show up instead of causing an infinite loop. 

[Spicious]

I used a debugger. This probably could be avoided by filtering out duplicate polygons or putting an upper bound on loop iterations.

[FUBAR-BDHR]

It would be great to get some kind of error message.  Not everyone that does conversions is a modeler.  Sometimes a quick low threshold weld will fix these things and sometimes it wont.  I've had pieces that I've looked at and fiddled with for hours and seemingly no reason they shouldn't convert but wont.  

Is there any kind of higher debugging or log generation like debug builds in FS2_Open? 

[Spicious]

I don't see how an error message here could really help a non-modeler fix the problem. More important might be whether the converter is a coder.

This does seem like the most likely place for it to get stuck though.

[headdie]

I don't see how an error message here could really help a non-modeler fix the problem. More important might be whether the converter is a coder.

This does seem like the most likely place for it to get stuck though.

an error message would help because the user will know things have gone bad the moment it happens and not when they get frustrated with the waiting and decide to ctrl+alt+del in this case an hour later.  I have also hit a similar issue lately and because i didnt know it was a mesh problem i tried to convert the dae again so ran into the problem twice so knowing that there is a mesh issue means the user knows they have to go back to the source model to look for a problem

[Spicious]

Error message added. Let me know whether it helps.