A obtenu à une surprise gentille hier par l'intermédiaire de Fedex toute la voie de Paris, France. Toutes les environ 3 heures. Fixateur, vous êtes modeste quand vous avez énoncé que combien de meilleur rend soyez alors Colle.

(translation)
Got a nice surprise yesterday via Fedex all the way from Paris, France. All of about 3 hours playing with Vue so far.  Fixer, you are being modest when you stated how much better the renders would be then Poser. YIKES!

Being a complete Noob, and following the threads on importing poser content (P6 vs P7) and the issues of using prop hair, I did a little experiment.. Loaded V3 nude with just the Juni prop hair in P7 and and saved the file. Then reopend the same file in P6 and saved that off again. Then took Text Wrangler (I am on a Intel Mac) and opened both files and did a comparison. There are 132 lines that are different between the two files. Most are either file reference paths or in P6 material refs as file "" vs P7 file "NO_MAP" Or just changes to how P7 adds filtering to the bottom of the material pallet reference.

However there is major difference in how lights are saved between the two files. Being completely stupid before I learned about Vue, and don't hold it against me...when Daz released C6 I bought it because it would import poser scenes, so they claimed. I won't go into all the details of what a mess it was (I got a refund after about a week) but one of the work arounds to import poser scenes saved in P7 was to delete all the lights and then save the file. So I just did that to the same file a second time. Deleted all the lights  in P7 and saved it off and then tired to import into Vue 6 inf. Wham the prop hair made it into the scene in Vue 6 inf from the file saved without lights.

Somebody else that has a file with prop hair using p7 want to verify that deleting the lights before you save a file  might help (not sure if it solves it completely) as I have only tried this 3 times, yet they all worked so far.

I happen to like P7 over P6 because I have a bunch of runtimes by character and then probably 15 more where I break props off by type (vehicles, bedoom, kitchen, garden, etc). Way easier to navigate runtimes in P7 over P6. However all my object and texture files are all in the P7 base runtime. Cr2's, pz2's, Hr2's, mc6's etc are what I have in separate runtimes. Plus P7 runs (loads characters etc) a ton faster on an intel Mac then P6.

I could not find any reference to trying this by doing a Vue only fourm search. Not exactly an easy issue to come up with the right search terms either. If it has been tried before and discounted and I somehow got lucky with these 3 tests, then sorry for the waste of bandwidth.

You shouldmn't need to delete your Poser lights because Vue doesn't see them anyway, I've never had to do this!
What I do is set up the scene in Poser [6 or 7] with just the default 3 lights showing, then import straight into Vue!

As for problems with imports, the only ones I've had problems with have been sorted by running the "uncompress" python script inside Poser before saving the pz3 but evenn then I only do that after installing new stuff!
I do know of others that have different issues that they have their work arounds for!!

 Nope I don't delte the lights either;

I have seen the problem though - seems to happen to me when I use hair that has very big trans maps attached. I now use down rezzer to make low rez versions - use them in poser and then run in Vue... Really cuts down on the memory issues...

My guess is that large textures use up memory (like on the dress)  and trans maps may cause a memory leak, but it is that - a guess. Not even an educated one...

Anyone tell you importing Poser models into anything is straightforward - they tell fibs.
Oh by the way turn off the posing and pose in Poser - that will save you a whole heap of hassle.

I use C6 Pro too - different issues and advantages. I use that sometimes so I can crash things differently ;-)

*I use that sometimes so I can crash things differently ;-)

 * That really cracked me up!!!!