Mon, Jan 6, 10:06 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: Newbie question for Vue......


XENOPHONZ ( ) posted Sun, 09 November 2003 at 7:11 AM · edited Mon, 22 July 2024 at 8:39 AM

file_83280.jpg

No doubt,this topic has already been covered by someone....

I seem to be having a texture problem in Vue 4.2. When I import a Poser 5 scene into Vue, if I have more than one character or object in the .pz3 scene, then Vue "clones" textures onto ALL similar items (See image).

Can anyone enlighten me as to what I am doing wrong here? Is there some way to avoid the "clones"?

Thanks!

Something To Do At 3:00AM 



ishroom ( ) posted Sun, 09 November 2003 at 8:24 AM

you need to get the patch for vue to inport poser 5,e-on sothware has the patch.


XENOPHONZ ( ) posted Sun, 09 November 2003 at 8:27 AM

Do you mean the 4.2 patch? I've already got that one, and updated with it.

Something To Do At 3:00AM 



agiel ( ) posted Sun, 09 November 2003 at 9:20 AM

The only workaround I can think of is to save each character separately and import them into Vue one at a time. The added bonus is that this takes care of cross talk issues between multiple characters in poser.


XENOPHONZ ( ) posted Sun, 09 November 2003 at 1:41 PM

Thanks for the suggestion -- I considered that idea, too. I suppose that I can do it that way if I HAVE to. But it's a pain.

One other thing that I've considered - I have both P4 and P5 installed on my machine. I wonder if Vue might be somehow defaulting to the P4 poser.exe file for Poser imports? That might explain the problem.

I'll remove my P4 poser.exe file. See if that makes a difference.

Something To Do At 3:00AM 



xoconostle ( ) posted Sun, 09 November 2003 at 2:09 PM

I haven't tried this, but it's just an idea...before saving your characters in Poser, give their shared clothing items different names. For example, on the first figure, leave all the default names. Let's say that the shirt is called "Shirt." When you save the second character, select shirt/body and change the name to "Shirt2." Do the same for all clothing items that share the same names. Extra work, but if it works, it's worth it, and would be less drastic than deleting your P4 executable file. I had a HD crash this past week and haven't re-installed Vue4 yet, so I regret that I can't test this for you before making the suggestion. It's just a hunch based on how Vue seems to interpret texture application. Good luck!


XENOPHONZ ( ) posted Sun, 09 November 2003 at 2:17 PM

Thanks, xoconostle, I'll give your suggestion a try. I've already removed my P4 executable. I re-named the file to "poser.exe.old", and moved it to another drive on my PC. It didn't work. Same texture import problem, still. I'll post back here on whether or not re-naming the individual models fixes this.

Something To Do At 3:00AM 



XENOPHONZ ( ) posted Sun, 09 November 2003 at 2:50 PM

No, re-naming the individual items in Poser didn't work. <sigh> Still the same texture "cloning" in Vue. If anyone can think of a solution.....I'd be extremely grateful....... Meanwhile, I'll keep trying things. I hope that this isn't a bug in the 4.2 upgrade.

Something To Do At 3:00AM 



XENOPHONZ ( ) posted Sun, 09 November 2003 at 3:19 PM

Importing the individual models one-at-a-time works. This fixes the texture cloning problem. Unfortunately, Vue imports all of the models in the scene directly on top of one another, forcing you to re-postion each model in the scene. This can be time-consuming. And, as I mentioned earlier, it is a definite pain..... I hope that e-on has some kind of a work-around for this. Or, perhaps, I am just doing it wrong. In either case, it would be nice to know.

Something To Do At 3:00AM 



wabe ( ) posted Sun, 09 November 2003 at 3:46 PM

Isn't it more a Poser problem. Not naming the materials differently, so that Vue does have the problem to identify what belongs to what. Maybe you copy the textures and name them differently - then it could work as well.

One day your ship comes in - but you're at the airport.


XENOPHONZ ( ) posted Sun, 09 November 2003 at 3:59 PM

Well, I suppose that one could say that it's a Poser problem. But, since Poser is the native app here, and Vue is merely importing a foreign file, I would say that it's up to Vue to work around the requirements of Poser. And not the other way around. It's sort of like attempting to get your phone service fixed. The local provider blames the equipment manufacturer for the problem, and the equipment manufacturer blames the local service provider. In the end, your phone just doesn't work. And, here, Vue is doing something that it shouldn't be doing. Whether the difficulty is regarded as a Poser problem, or as a Vue problem. Once again -- Poser is the native app. Importing P5 files is a selling point for Vue. It's why I bought Vue in the first place [[Along with Vue's beautiful rendering capabilties]]. I can work around this, but only with time-consuming difficulty.

Something To Do At 3:00AM 



Polax ( ) posted Mon, 10 November 2003 at 7:14 AM

my two cents here, if vue imports all models on top of one another (in the same place), maybe the option 'center/resize imported objs' is checked in file/options?


XENOPHONZ ( ) posted Mon, 10 November 2003 at 1:51 PM

OK - let's see if I can get this message posted before the forums die again, like they did this morning. Even when the forums ARE working, things around here are SLOW....... Polax - thanks kindly for the pointer. Yes, I checked my options, and, yes, the center/resize option was checked. As I mentioned earlier, I am a Vue neophyte.....and your information is very helpful. This evening, I will check to see if this at least fixes the re-positioning problem in Vue. Unfortunately, this still won't address the fact that one has to save separate Poser models for each similar character in a scene -- and then import the models into Vue, one at a time. I think that the "texture cloning" difficulty is a bug in Vue 4.2's P5 import capability. It makes smooth imports of .pz3's into Vue somewhat problematic. Thanks again for the help.

Something To Do At 3:00AM 



xoconostle ( ) posted Mon, 10 November 2003 at 6:12 PM

I've never had this problem of imported Poser objects piling on top of each other, but it does appear to be due to the settings already mentioned. I usually prefer to import objects individually, since the cameras in Poser and Vue are so different. You can compose a scene beautifully in Vue, then have a very difficult time trying to get your composition to appear the same way in Vue. All things considered I find it easier to simply compose scenes in Vue. This thread reminds me that it takes a long time (in any app) to figure out all the work-arounds and particulars to get things the way you want them. Eventually, this knowledge becomes second nature, easy to take for granted. Anyway, still wishing you luck. :-)


XENOPHONZ ( ) posted Tue, 11 November 2003 at 11:51 AM

Thanks, everyone.

Something To Do At 3:00AM 



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.