Fri, Nov 8, 5:58 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Oct 26 8:50 am)



Subject: Poser5, multiple runtimes and Vue4.2


Tintifax ( ) posted Wed, 26 November 2003 at 6:06 AM · edited Fri, 08 November 2024 at 5:56 AM

OK my system is running and it is running very well (Only Open GL is not working on my GeForce 4, have to look for a different NVidia driver?). Learned a bit about P5 import to Vue4.2 and would like to share it here. Just made several runtime folders to get my Poser5 better organized. Imported the *.pz3 to Vue 4.2 and experienced slight problems. The rules I found until yet is the following. You can keep your libraries in different Runtime folders. The Geometry folder MUST be in the main Runtime folder in order for Vue to find it. So copy the whole Geometry folder to the main Runtime folder after installing the product in a personal Runtime folder. The Texture folder can stay in your personal runtime folder. I had no problem with that. Didn't try MAT and MOR files until yet. Installed some props, V2 and Koz hair without external geometry. This all works smooth. Next will be V3 with her injections and morphs. I'll keep you posted how this works for me. Hope this helps some of you.


shante ( ) posted Wed, 26 November 2003 at 5:43 PM

I have been trying to decide whether to get Vue4 or Vue Pro mostly for the ability of Vue Pro to use and track and save Runtime a texture paths for imported Pz3s. You are trying to say if set up properly it (Vue 4) should be able to track them across several Runtime Folders on different drives? If so, is there any other reason to get VuePro except getting more sophisticated animation perks and more plants? Basically I just want to import character complex PZ3 files and have Vue remember where all the textures are from from the imported Pz3 at import without going through the extreme hassle to find and reapply all textures to all items and character parts one at a time! Been asking around and have gotten different responses. Yours is the first I was directed to by someone at DAZ Forums trying to help me out that actually addresses my issues. IF Vue4 works as you say this way I should lay my money down before the offer expires. BTW are you on a Windoz machine or running on a Mac?


Sentinal ( ) posted Thu, 27 November 2003 at 6:03 AM

"If so, is there any other reason to get VuePro except getting more sophisticated animation perks and more plants?" I've found, having used Pro for a short time now, that one of the real time-savers is Pros ability to notice when a pz3 that you have in a vue scene has been altered by poser and ask if you wish to reload the new pz3 into your scene. Way cool.


Tintifax ( ) posted Thu, 27 November 2003 at 8:38 AM

I work on a PC. It seems that in *.pz3 the whole path for the texture is stored. Unfortunately not for the *.obj. I use Poser5 SR3 German and Vue4.2 German. Don't know about the injection system and other things yet. Will do further tests tonight. I'll install new items and will have a look how the system behaves then. Keep you posted...


shante ( ) posted Thu, 27 November 2003 at 12:13 PM

To Tinifax: Do you mean that if there are objects in a Poser Pz3 import such as a building in background or jewelry, etc. the textures are not remembered? I am not sure I understand by it not remembering the whole path for the .obj? To Sentinal: With the price difference between the two I hope there are other valuable perks going with Pro besides that. Though a prime incentive I need a bigger kick in the heinie to part with that extra change! LOL


Tintifax ( ) posted Thu, 27 November 2003 at 4:17 PM

No, I refer to the geometry data. E.g., if you look at a prop file (*.pp2), you may find all the data for vertices, mapping and maybe normals inside (v, vt and f lines) the file. It also happens that there is just a reference to an external *.obj file in the runtimegeometry folder. This reference of the *.pp2 is copied to the *.pz3, if you use such a prop. But instead of using the full pathname in this reference it is just a relative pathname beginning with the runtime directory. Thus during import Vue doesn't find this *.obj file, because it just searches in the default runtime folder. Textures seem to work fine with full path reference.


Sentinal ( ) posted Thu, 27 November 2003 at 5:05 PM

Shante: There are plenty of 'perks' both mentioned here and on e-on's site. The 'perk' I mentioned is one that's usually overlooked and saves me countless time in opening and closing the applications when you just want to reposition a figures feet to match uneven terrian for example. Also, Pro is reviewed in this months Digit magazine. Usually the reviews part of the Digit site are for subscribers and those who pay, however I believe that it is open to all for a short while, so it may be an idea to pop alone there. Http://www.digitmag.co.uk


Sentinal ( ) posted Thu, 27 November 2003 at 5:15 PM

Here is the full address for the review. http://www.digitmag.co.uk/reviews/article/display_review.cfm?ReviewID=372 Hope this is of some use. BTW it's open 'till 16th Dec


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.