Forum Moderators: wheatpenny, TheBryster
Vue F.A.Q (Last Updated: 2024 Oct 26 8:50 am)
That's really strange, Guitta. Did it work in the beta version? You really need to get ahold of Steve Bell with this one. If you want to use the .obj import feature instead, a way to make that quicker is to place copies of the textures into one folder, and then export the .obj to that folder. When Poser exports a wavefront .obj, it also creates a .mtl file, which has the relative texture/color information in it, so if your textures are there in the same folder with it, Vue will apply them without complaining. It really is a shame the PZ3 import won't work for you , and I have no idea why, but I hope that E-on Support can figure it out for you. In any event, the "old fashioned" .OBJ import still works as well as it did in Vue 3.1.....with the exception that now, at least, we can "browse" for any missing textures.
Mike, in trying lots of things, I have re-installed Vue 4 and the patch. It works now :-) Thanks for helping me. Now I will write to the other users. This was maybe happen because I installed the Poser 4 upgrade after I had installed Vue 4 and the patch. Not sure, but not anymore important, as it works now. Guitta
After reading Guitta's first post in this thread, I spent about an hour trying to track down what Vue does to the system when it first finds Poser. I figured if we could find out what it's doing--or not doing--we could easily fix it when it happens to others. Anyway, I had no luck. I searched the registry and all relevant ini files and found no links at all. There were a couple of coded entries in the registry but nothing readable. So, unless I missed something (very possible), E-on has either coded their registry links to Poser or they're writing or re-writing to to another file--a dll or something. Maybe if E-on would let us know how they do it, we could ease a lot of people's suffering.
I did look in the Vue directory but didn't see that teeny 2.7 mg file. I guess my eyes were crossed after looking at all those registry entries. The poser.dll file in the Vue directory is compiled and, for the most part, illegible. I did find many references to poser files and settings but none to the poser.exe path. It probably is in this file--Lord knows everything else related to Poser is (including animation settings)--but is illegible and, of course, uneditable. It seems to me, though, that if installing other software makes it stop working and forces a reinstall, there must be an external link somewhere.
After my reformatting two of the first apps I reinstalled were Poser and Vue 4, but since then I've reinstalled many other programs, alot of which are graphics programs. Vue has not yet forgotten where Poser is..... I even made a new partition a little while ago and copied the Vue 4 folder to it, set up a shortcut, and even though it's not a "valid" way of addind a program to a different drive, even that works too. Wouldn't it be more likely to be in a .nfo file or a registry entry? Granted, I have no idea... ;)
Vue says wrong serial number...This happend to a user from Germany who wrote to me, too. But he shut down his computer and after it worked. I also must say that Vue 4 is sometimes capricious (with me) when I try to import a pz3 and Poser is almost open behind. Vue says "cannot read*.pz3". If I close Poser AND Vue, then recall Vue alone, it works. Maybe you could try that. Guitta
The invalid serial number happened to me in the beta. Vue would find Poser okay, but would then tell me I had an invalid serial. When I reinstalled everything, it found Poser okay, didn't give me the invalid serial thing, but it wanted me to locate the poser.exe every time I opened Vue and never would import .pz3. But I didn't know all these little tricks either ;). Laurie
I've found that I had to close Poser before importing a figure to Vue. Annoying, but liveable. After the import, I can open Poser back up without any problems. I think it may be a Windows thing. Vue may be making a call to Poser, and is being blocked by Windows since the program is already in use. It's like trying to open a file with a program that is already in use by another program. Sometimes it works, sometimes it doesn;t.
Hmmm... I have to say I never saw the serial number thing, and there have been a few times when I've had Poser and Vue opened at the same time, while doing experiments, and Vue hasn't whined about anything. you know, it makes me wonder though, particularly the serial number thing. Why would it be concerned about a serial number, unless it had been "told" to look for one? or is it just a really weird error? How does Vue even know Poser uses serial numbers, unless it was told?
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.
Thanks Mike for the idea to rename poser.exe into poser.exe for importing *.Pz3 files into Vue. Unfortunately, this did not work for me. First time I tried to use this feature after renaming poser.exe, Vue 4 brought up a popup saying some thing like "You need Poser to be installed to use this feature, would you like to locate it now ?". I answered YES and located the poser.exe file. But this did nothing, absolutely nothing and the question always came back :-( I never could import Pz3 and I have messages from some other users in my mail box, they have the same problem. In importing *.OBJ from Poser, Vue 4 askes me for each body part "to locate" the texture. This makes loosing a lot time. Does any body know another solution ? I have already tried to re-install the Vue patch. Thanks tou all. Guitta