I’m using PoseRay with Poser 5. When I export Poser scene as OBJ, dynamic hairs are exported as line elements and this is not a problem since PoseRay can read them. The problem is that Poser export only guide hair and not others hair, even if I check the visibility of all hair before exporting. This seems a limitation of Poser 5: does someone know a workaround?

I don't think there is one.  Dynamic hair is not exportable.

Vue Infinite (or Vue d'Esprit plus the Mover plugin) can import Poser dynamic hair, but it really doesn't look the same. 

Use transmapped hair instead. 

You can access the fully populated hair through Python and through that export it in whatever format you wont.

So does that mean there's a Python script that exists for exporting dynamic hair as an OBJ or it's just possible and nobody's bothered to write it yet?

Attached Link: http://www.stewreo.de/poser/poserman.html

Once I have a RIB export, can you take us through the steps of getting it into a format that could be imported by Bryce / Vue / Carrara?

Something like obj, 3ds, etc...

And do you have a screenshot of the results?

While I'll agree that the default OBJ importers of most 3D apps are rudimentary - there are plenty of solid importers by third-parties.  Riptide is probably the best for Cinema 4D.  And did I mention that, yes, my Wavefront OBJ importer can handle lines properly into C4D splines - it is not all that difficult.  Currently I don't use it since Poser (by default) exports/saves only the guide hairs - I'd need to recreate the populate algorithms of Dynamic Hair to start simulating Poser hair otherwise.

But, if you've got an exporter that handles Dynamic Hair properly (guides and populated), that might be an incentive to reinstate and finalize support. :)

Hm, so I just tried it out in Poser 6: Went to the hair room, created a new hair group on the ground plane. Checked "show populated". Exported as an OBJ. Got a 160MB OBJ file with every single hair strand in it.

....... bingo? (it's a start! lol)
...just that file size....

160mb?

That's almost as big as a Bryce sphere primative... :blink:

It contains > 80,000 hairs with 20 vertices each. Small test scenes are for pussies :)

It'd be better to have the splines than the 160MB mass of polygons... ;)

Those are 160MB worth of splines. Remember, OBJ is an ASCII file format.

Really?  Wow.  Would have never guessed.. :/ (I've written an OBJ importer/exporter once or twice)

So in export of the guide and populated hair splines, it occupies a 160MB file?  Part of that I would think would be the precision to which each vertex is taken (since Poser works in microverse, the floating point values need to remain rather significant (literally here)).

Why is everyone acting so surprised? I was using an abnormally large number of hair strands (about ten times of what the hair cuts that come with Poser 6 have), so it's only normal that I ended up with an abnormally large file. If you export James with his layer cut hair style, you get a 20MB OBJ file. Anyhow, can we finally stop with the "dynamic hair doesn't export" myth? Yes it does export and yes it does export every single populated hair and yes it does export them as splines and not as polygons. If $SOFTWARE_OF_CHOICE doesn't know how to import or to render OBJ splines, don't blame Poser.

I thnk that is the problem.  Most "software of choice" basic Wavefront OBJ importers are very rudimentary - Cinema 4D converts splines into god-awful polygon meshes.  Not sure about Spanki's Riptide - will have to put it to the test.  interPoser Pro's does support lines into splines - but that doesn't help as it uses the Poser file directly - not an export.

Especially in the case of C4D it's sad - they've done a good job on their hair module, and it would be capable of creating hair from imported splines. I haven't had a look at v10 yet though, did they make any changes to the OBJ import there?

Just checked - same situation in R10 - lines to polys. :(

Riptide ignores the lines,  but I can't verify the version (there is a newer version I'll need to dig out and install).

The Poser dynamic hair into C4D Hair would be a good approach.  The biggest problem would be parameter matching between the two different interfaces (basically the same problem as matching materials, lights, and cameras between the two).  Should be possible, but wouldn't know until attempted.

Hex2 will read "l" lines (but would probably not cope with a full head of hair).
It also is the only app that I've seen save splines to OBJ files using the cstype, curv etc. records.