I just installed Poser 8, when I try to export any lores or hires  figure mesh to Obj, lwo, 3ds.. P8 crashe right aways. It only successfully export to Dxf formay..

I wonder if this is a nasty bug or what.

TIA.

 Hm that's odd. I have had some problems IMporting bojs (with the Weld Identical Vertices, my Poser crashes. Without it, it's fine)

But I've exported several objs with no ill effects. Gonna try the other ones now...

Yup, only dxf format on my side, and it crashes if it is exported to dxf from a frame of pose of any BVH motion capture data. Weird.

I try to export to 3ds, obj, lwo, now it can do so, weird. Just couldn't do that last night. When I export, I click from frame 1 to frame 1 at the Multi-export of Export Range panel,

Now I am trying to export one frame from Walk Designer motion pose, and it does exp too.

Happy. :)

I was able to export to obj, lwo, dxf, 3ds - but I couldn't re-import the .3DS.

My test subject: Ryan with his genitals and Alicia hair (rather high rez hair)

The dxf import took ages and ages, but eventually he was there. with all facets showing...

 Sometimes, a restart of Poser, and/or a reboot of the computer solves the problems. I think sometimes Poser doesn't quite release ALL of its memory on shutdown and some bits and pieces keeps hanging around. 

I wonder if a reboot will allow me to import my 3DS.. hmm...

I just fail to exp to any 3d format using "Single Frame" export, I have to choose from ..to frame range function, otherwise P8 crashes. But I am happy now with the result.

I never encountered any export problem in P5/6, and i did not run P7 cos my computer just couldn't handle it as fast as now I do in P8.

I wil try import 3d function later.

I can export one frame from mocap pose, but it crashes somethimes. Walk Designer is save to export for me.

I can successfully import 3ds, lwo, obj into P8, but I test with lo-res model. I also try to import obj exported from ZB and SketchUp, all are fine, P8 never crash.

I will rty to import hi-res models tomorrow.

OK, I do a quick test by export Andy and re-importing it into P8, P8 hangs and I force to shut it down,

OMG, P8 takes 210,000K to run this program, it is a monster now :(

Importing 3D mesh is an issue with P8, it takes so long to import Andy in 3ds, and obj that I test, it just hangs and not crashes. Performance needs to be enhanced at this aspect.

Well ... My poser 8 imports LWO instantly, OBJ fairly fast (takes a moment to locate the texture, then it loads too) and DXF takes a while.

But it's not a general Poser issue you're decribing.

Better send in a bug report tio SM though. They may be aware of it and it may be solved in SR1, but if that's not the case.. they won't know there's a problem before someone tells them. 

I would write off even thinking about 3ds or lwo format if I were you.

For one thing, the 3ds format is limited to 65,000 polygons, so anything more than that will fail, which would include the Daz people, and I think the latest S-M creations would be pretty close to that limit too. More importantly, perhaps, is that the 3ds format supports only triangles, and most (if not all) Poser figures are mostly quads, which deform better than triangles. Meshes exceeding the limit will be broken apart into groups, and probably not the groups you want.
There are other limitations of the ancient .3ds format too that don't bode well with Poser.

Secondly, in spite of the fact that Poser claims it uses the LWO2 format for lwo import/export (as an option), it is wrong, because whatever bizarro broken version of it they implemented doesn't support UV maps either on import or export. So any models you have that have UV maps - which of course means all Poser figures - will import or export and lose the UV map along the way.

Best bet for Poser is and has always been OBJ. Really, that's about the best for all programs until the day when Collada or FBX become more standardized.

Poserpro - The geometry import/export functions were rewritten in Poser 8 SR1 to address the issue you've seen.

Steve Cooper

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2763580&page=1

(as in the link)

Assuming that question was directed to me.

Thanks for the link to that thread. I'll take a look and share it with engineering, but this wasn't addressed in our work. The new code deals with an instability that  was getting introduced when using geometry import or export features.

Quote - did you fix the artifacting we've seen on importing meshes?

(as in the link)

Lightwave objects can be confusing. Lightwave 8 by default does NOT export uv info unless it is attached in surface editor to every material that uses it. So import an obj , export it, no uv map. Import, set materials to use uv map , export and all is good . Poser was using LW 5 format, not the later LWO2 specification.

Quote - Lightwave objects can be confusing. Lightwave 8 by default does NOT export uv info unless it is attached in surface editor to every material that uses it. So import an obj , export it, no uv map. Import, set materials to use uv map , export and all is good . Poser was using LW 5 format, not the later LWO2 specification.

Lightwave saves UV data in the LWO format, regardless of whether or not it is attached in the surface editor. It is part of the LWO format.
What you meant to say is that if you export OBJ from LW, you have to physically attach the UV map to the surfaces before exporting.
But since I was talking about LWO import and not OBJ...

Poser does in fact appear to be using the earlier 5.0-5.6 format for LWO.
However, LWO2 was the first LWO format to include the ability for UV data, and Poser does, in fact call it LWO2 in its import/export options.
So they either outright lied or somebody made a monumental typo.
The thing is though, LWO was already there, so they consciously added LWO2 with (I think ) Poser 6... but apparently nobody read the LWO 2 spec sheet.

Nope...
Just ran another test.
Exported V4 (with textures even) from S-M Poser Pro using LWO2 export and opened the LWO in Lightwave Modeler. No UV map present at all.

Then I Exported a fully textured V4 from LW, which needless to say had UV maps applied in all surfaces and imported that into Poser using the LWO2 option. Tried to add a texture to it and only ended up with the surface color, no texture. Because Poser can't apply a texture map to an object using UV coordinates if there are no UV coordinates.

Well, my lightwave 8 does not recognise Poser lwo files as current version. And I loose uv data in the lwo if the maps are not attached. And yes that lwo not obj . I suspect I have some corrupt files but thats what I have .

Quote - Well, my lightwave 8 does not recognise Poser lwo files as current version. And I loose uv data in the lwo if the maps are not attached. And yes that lwo not obj . I suspect I have some corrupt files but thats what I have .

Well it should. The LWO2 geometry format hasn't changed since version 6. (it's been updated since LW v9 to include surface node data, but that doesn't affect the geometry)
Are you telling me you can export a file from LW 8 as LWO and load it into Poser and apply a texture map to it?
I'm using LW 9.6 and don't have LW 8 installed any more, but I was at one point using LW 8 with Poser 6 and then still with Poser 7 even and never have I been able to texture a LWO export in Poser, with or without UV maps applied on export.

In any event the LWO2 specs call for the inclusion of the UV vertex map, and regardless of whether or not a UV map is physically applied to a surface, if it's in the LWO file, it should be able to be read by Poser.
home.comcast.net/~erniew/lwsdk/docs/filefmts/lwo2.html

Bottom line is, they did it wrong, and apparently nobody ever bothered to test it either.

Hi, Steve Cooper
Very long time no talk, glad you are here.