Thu, Jan 9, 5:48 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 30 8:14 pm)



Subject: Vicky Changing Fantasy armor and Vue.


arcady ( ) posted Sat, 15 December 2001 at 5:30 PM · edited Thu, 01 August 2024 at 7:10 PM

I'm noticing when I save a pz3 file with vicky's chaning fantasy armor in it and import it into Vue it comes in with different morph settings than those I had in the pz3. Anyone else seen this and know how to get around it?

Truth has no value without backing by unfounded belief.
Renderosity Gallery


MikeJ ( ) posted Sat, 15 December 2001 at 11:38 PM

How can you tell if it has different morph settings, since such is not displayed in Vue? I guess you mean to say that the model is deformed on import, moreso than it ought to be? Does it render correctly? Because my first guess would be that maybe it's an OpenGL problem, which can be disabled in File>Options. If it's actualy causing a permanenet unexpected deformation on import, then something's not right at all. Vue really doesn't have the capacity to deform objects, so it's more likely a problem with the export. However, I would first suggest trying to import as .OBJ, or, better, if you haven't yet done so, upgrading to the 4.03 patch from E-on's website. Vue did, in fact, have problems importing certain objects prior to that patch...



arcady ( ) posted Sun, 16 December 2001 at 6:35 AM

Well on this model the morph dials have a very big effect. For instance setting the arm to 0 will show perhaps a round shield. setting it to 1 a rectangular one. setting it to 2 no shield at all. Another example is a dial that at one number shows a dagger strapped to her leg. at another number a small pouch on her leg. and a third value shows nothing. likewise for a helmet, armbands, belt, and buckle. All of them come into Vue at different settings than they were saved as in Poser.

Truth has no value without backing by unfounded belief.
Renderosity Gallery


LaurieA ( ) posted Sun, 16 December 2001 at 10:13 AM

I haven't tried Vicky's CFS yet, but I have used Mike's and it comes in with what I saved it in in Poser. Very curious...and maddening! I'll have to test it now ;). Laurie



yggdrasil ( ) posted Sun, 16 December 2001 at 1:27 PM

file_244194.jpg

I just tried a quick test and it worked OK for me (see pic) - Mark

Mark


Varian ( ) posted Sun, 16 December 2001 at 3:29 PM

Arcady, try opening the PZ3 in Poser and re-saving it under a new name. Then try bringing in the new PZ3 to Vue. Not sure this will change the results, but it has helped in some situations. Good luck! :)


MikeJ ( ) posted Sun, 16 December 2001 at 7:11 PM

Just curious: is it really a Poser *.PZ3 file, or a Pro Pack compressed *.PZZ file? Vue will import both the same, at least on my setup, but I'm curious. I actually tried to buy the Changing Fantasy Armor today, but DAZ' site was so slow, I couldn't deal with it...



arcady ( ) posted Sun, 16 December 2001 at 11:20 PM

It's a poser .pz3 I'm dealing with. Here's the setting I had her suit on: no helmet. pouch on leg no armbands. necklace with stone (the second such one I think). no loincloth nor bikini (used a seperate item for the 'clothing' from her 'barbarian suit' --- maybe that mixing of two vicky2 clothing items is it?) no boots or shoes no shirt (again used something from another set). belt set to pouches buckle set to round. here's what comes in: helmut that looks like the martian on bugs bunny. squarish shield dagger on leg square belt buckle stoneless necklace grey belt

Truth has no value without backing by unfounded belief.
Renderosity Gallery


MikeJ ( ) posted Mon, 17 December 2001 at 5:43 AM

I couldn't even begin to guess why that's happening, really. How large, file size-wise, is the pz3 file? I did though have something similar happen to me with a cr2 I had made myself out of some models I made. I had royally screwed up the groupings for the materials and objects, and everything collapsed in Vue, but I would doubt that's the problem here. I don't know, I'll have to buy the changing armor and see for myself what happens. All I could say for now, is to let E-on support know about it and see what they have to say. Since the 4.03 patch was released in it's final form, I haven't had any troubles with any kinds of imports, including pz3 and pzz.



thorntoa ( ) posted Mon, 17 December 2001 at 6:53 PM

I've had the same problem though not as extreme. At first I thought that I had not set the poser file up correctly but it turned out to be a VUE problem (either that or the VCFS uses a non-standard method of doing things). Eventually I gave up and used cloths from the VCFS that would import properly. I have not tried this with the latest version of Vue so I don't know if it has gotten better or worse. Oh for the record, I'm using PPP ... and VUE 4 . . .

Allan Thornton


yggdrasil ( ) posted Tue, 18 December 2001 at 6:57 AM

Seems to be a "works for some but not others". I tried various combinations of settings on VCFS and different additional clothing/props, and all imported flawlessly on my system (XP, PPP SP3, Vue 4.03) Mark

Mark


pzrite ( ) posted Thu, 03 January 2002 at 3:38 PM

I've had a similar problem, but also from within Poser itself. When I reopened my PZ3 file, the belt would change to a different setting. It would also export incorrectly into 3DS Max. What worked for me is, change the fantasy armor settings to the correct morphs and then immediately save the file WITHOUT doing any other changes. That will usually allow me to export correctly. (If I make any changes, such as moving an arm or leg, and then save, the incorrect belt setting would be exported into Max) Hope that helps.


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.