Lyne opened this issue on Feb 12, 2006 ยท 10 posts
Lyne posted Sun, 12 February 2006 at 3:05 PM
Okay...I am getting ready to fix up my P6 (and get all my runtimes back into one...no, don't say anything on that...long story)... BUT my serious concern is I need RECOMMENDATIONS from you all, that my pz3's will still import with perfection into my vue infinite 5.7 (still working on if I should make vue 5.9 or not, yet) ? I do NOT use dynamic anything...I just want to make sure my vue will still import all the textures and trans maps as well as it does now, with making my P6 SR2. Thanks folks for your input!
Life Requires Assembly and we all know how THAT goes!
sirrick posted Sun, 12 February 2006 at 3:13 PM
I updated to SR2 and am having no problems.
randym77 posted Sun, 12 February 2006 at 3:33 PM
I updated to SR2 long ago, and haven't had any problems.
But I would recommend you hold off on updating to Vue 5.09. I tried it, and ended up reinstalling everything to roll back ot 5.08.
Lyne posted Sun, 12 February 2006 at 3:45 PM
Thanks folks! I think I will go ahead on the SR2...I understand the firefly is better... my new "magic mirror" materials may render without crashing then! :) Yes...am so cautious of the 9 update...at the very least I will copy out my whole vue application folder/files...update manually and then if it does not work, slap my original application stuff back in. Heard a few vue-ers did that safely. Still thinking...
Life Requires Assembly and we all know how THAT goes!
bruno021 posted Sun, 12 February 2006 at 4:29 PM
No rpoblem either, updated a while back.
Irish posted Sun, 12 February 2006 at 7:16 PM
Lyne, I have updated to last Vue Infinite beta and pz3s from my Poser 6 import with no problem at all. :)
Vertecles posted Mon, 13 February 2006 at 3:42 AM
I updated to SP2 to fix the "full body morphs" error...which it didn't. I still have the problem. Other than that, SP2 has not broken anything new. I do however still run 5.08 in VUE though. For me .o8 is more stable than .07 and earlier. I say...If you don't have a "NEED" to update your VUE...then don't!. Don't fix what isn't broken(much). So until I run into a major hurdle with 5.08 that only going to .o9 will fix. I will be staying away from VUE updates. My 2c
It's a shame stupidity isn't painful.
Richmathews posted Mon, 13 February 2006 at 4:50 AM
I had many problems with vue 5.09 and poser5, but now with poser6 I have no problems at all. poser6 is a good upgrade over poser5!! Didn't realise it was that much better!
Lyne posted Mon, 13 February 2006 at 9:35 PM
Well...I am THRILLED with the POSER SR2 for my P6 and even happier with consolidating my runtimes... now P6 is sooo fast in loading it's human morphs, finding maps, I am just loving it! :) I still have a ways to go before all my content is safely nestled in P6's own runtime...but honestly Poser opens FASTER and that firefly...well... just take a look in my gallery! :) I am holding off too on the .9 vue update...as much as I WANT to use my Corucopia store bought items I already have when I did try the update for them...I just can't get myself to do so yet... those store things are the ONLY reason to update...my vue is so happy as is.
Life Requires Assembly and we all know how THAT goes!
randym77 posted Tue, 14 February 2006 at 6:34 AM
I still have a ways to go before all my content is safely
nestled in P6's own runtime...but honestly Poser opens FASTER
Those two may be related. IME, it's the size of the runtime that matters. People who don't have a lot of content don't notice any slowdown when everything's in the main runtime. People who have huge runtimes (I have something like 60Gb of content installed, not including the stuff that comes with Poser) notice a big difference. I moved everything outside of my Poser folder, and Poser sped up immensely. Not just opening, but in general.
I have something like 20 runtimes on their own hard drive. I am careful to copy the !DAZ folder (and any folder for injectable morphs) to the main runtime.
Aside from that, if a product is packaged correctly, there shouldn't be any problem with finding geometries or textures with multiple runtimes. Unfortunately, a lot of stuff isn't packaged correctly. That's what Correct Reference is for, I guess.