Djeser opened this issue on Sep 25, 2004 ยท 5 posts
Djeser posted Sat, 25 September 2004 at 5:39 AM
I have 2 machines for graphics networked; my old workhorse, running W2K Pro with Vue 4.12 and Vue 4 Pro on it (among a ton of other stuff), and a newer machine running WXPPro. Networked via crossover cable and NICs...working fine. I purchased a second copy of Vue 4 d'Esprit for the second machine since I wanted it available to do work on when the other machine is rendering. The version that shipped is 4.2...I never updated because 4.12 works so well for me. I pointed my new installation of 4.2 to the Poser exe that is on the other machine, and it saw it fine. But when I try to import a pz3, I only get parts of it; like only the hair, but not the body, etc. Pretty mystifying! I really don't want to have to duplicate my entire runtime on the newer machine. Anyone have a fix for this? I don't know if it's a quirk with 4.2, I have to assume yes, since no problems with import with 4.12 or Pro. Any help appreciated!
nhirschberger posted Sat, 25 September 2004 at 7:36 AM
I'm running Vue 4.22+Mover+Poser5 on one and 4.53 Pro on another machine and all works fine for me. Maybe an update from 4.2 to 4.22 can solve the problem, btw. it's very solid. You can also check if your connection to the network drive, where poser is installed, is permanent, which means that you have a drive letter for this connection. I already had problems with some programs pointing to a network drive wich was not mapped to a static drive letter. I'm also not sure which version of Poser you actual use. Hope this helps. Norbert
BigGreenFurryThing posted Sat, 25 September 2004 at 7:33 PM
Does the importing box need some of the Poser runtime libraries installed locally? Just a thought.
Cheers,
Mark
Djeser posted Sun, 26 September 2004 at 12:19 AM
Hi Norbert and BGFT...I don't have drives mapped, but folders shared out. I'll check into mapping the drives, see if that helps. I have Poser 5 installed on the new machine, so no problem there, as Poser 5 is pointed to the runtime on the other machine and sees it fine. I opened a few p4 pz3s in P5 and resaved them and they came into the new Vue ok. Strange, huh? I'll keep playing with it, thanks much for your suggestions!
nhirschberger posted Sun, 26 September 2004 at 7:24 AM
I did some tests in the morning and have reproducable problems while working on non mapped network shares with poser, missing skin, missing hair, things like that. The problem is, that Vue stores the information about the path to Poser.exe in a file called "vue.env". I had to use a trick to connect to Poser.exe on a mapped drive. First I mapped the poser directory on the remote machine to a local drive letter. Then I renamed poser.exe on the remote machine to poser1.exe and tried to open a pz3 on the local machine. Now vue is looking for poser.exe (but doesn't find) and brings up a dialogbox, klick ok (!) and wait for the browser to come up (!!). At this point rename poser1.exe back to poser.exe and navigate, within the browser that vue shows, to the poser.exe on the mapped drive. That's it. Norbert