This happens whether poser 4 or 5 is open or not open. Any ideas. I only just got vue pro to be able to import Pz3s after a lot of problems. I have the latest beta installed. I have a mac computer. Love esther

I am not sure about Macs, but that kind of thing may happen in windows when you set up Poser 5 with a different runtime folder from the priginal setup, or if you are opening your poser figure from a non standard directory, such as 'Desktop'. Anyone with Mac to answer this question ?

Well vue is pointed at poser 4. now when I use poser 5 it points at poser 4 runtime. But the thing is, any pz3 I import now comes in without textures. I've got a feeling it might not be a mac specific problem. I could be wrong. Love esther

Well Esther, i am the Mac person here - or better said one of... Badly enough i don't have that problem, pz3's come in with textures. So i think it needs some more research to find the differences. I am on 10.2.8 and Use d'Esprit and Pro latest updates (beta) and Poser 5 now. Mac G4 with 1 GB RAM and 768 MHz. I really wonder why you don't get an error message - that Vue can't find the textures and wether you can redirect it to them. That's what i normally get when something goes wrong with the textures. First thing is to find out why that isn't the case. I think it is important that Vue points to the right version of Poser. Otherwise it will not find the right Runtime folder with the textures in it. If you look at the error message it looks like that Vue only reads the last bit of the pathname to the textures and ignores the rest - assuming that all textures are in the Vue folder. Or in the Runtime folder of the Poser version it is pointing to. You can do the following to test wether this is a Vue problem or not. Redirect Vue to Poser 5. You can do that by renaming the Poser 4 folder to something else, start Vue and select import object. Then Vue will ask again. Create a new pz3 file in Poser 5. Copy the textures of this object into the bitmaps folder of the Vue version you want to test. Import this object into Vue. Report what happened.

Hi Esther, still into Poser-import-troubles, hu? :( Since I have the same machine like you (G4 MP500, 1.2GB RAM, OSX 10.3.2) I'm wondering what the problem might be. I have the previous version of VuePro (don't have the Build# available right now) and the import works just fine for me. I suggest you re-point VuePro to Poser5 by renaming your Poser4 folder just like wabe suggested. Keep us updated about the results or send me an IM. Phil

estherau; This is a pathing problem, one you can get with Windows, as well. Vue uses the Poser.exe to process the pz3 for import; and if the path to anything is innacurrate, it does a recursive search -through the program tree of the Poser.exe being used-. There are some pathname length issues that Mac's seem to have (i'm a winders fella, meself). If you have the space, one possible solution is to copy your texture files over into the Poser folder that Vue is linked to, and see if that solves it.

Not completely correct i think. Poser can deal with the pathnames so it is no Mac OS problem! And it works fine for TheWingedOne and myself. It is a wrong setup, i am sure. But the idea is ok, try to copy the textures. But to the bitmaps folder in your prefered Vue. Vue always looks there first. Anyway, let us do that structured step by step. First, redirect Vue to Poser 5. Then create a new Poser file and check wether the textures are ok in Poser. Then go to Vue and import that. And tell us!

Hi, well the textures are in the poser 4 folder already, and that is the folder that vue is pointed at, because I did the renaming thing before, otherwise vue doesn't even import at all. But the thing is Vue isn't asking me to tell it where the texture is, it just is importing without textures. When I had this problem a long time ago, funilly enough I fixed it just by having poser 4 open instead of closed. I know others have had it the other way around. But now open or closed makes no difference. Love esther

Hard to say anything without knowing much about your installed structures. It looks like that TheWingedOne knows more. Therefore hopefully he can help. I still think there is a wrong setting, the textures are maybe in the wrong place. Really try to copy them into the bitmaps folder of Vue and try again. Or, if you have VuePro define the textures folder from Poser as additional texture folder in the preferences.

Hi Wabe, that last comment about defining a texture folder - I didn't even know about that option. I'm off to try it now, as it's something easy, and I'll let you know if it works or not. Vue pro always used to import my textures. It was only since I started the beta upgrades. I went back to the original (disk) version of Vue pro, but now it's not working anymore. So weird. Love esther PS I've written to eon too. But I think it was me that discovered the problem with needing poser 4 open the very first time I had this trouble, and that time they couldn't help me, but that was a very long time ago, so maybe they have struck this same problem with other people????

Wabe - you're my hero! And with that last line of your message that looked like just an afterthought! I can't believe it. It's imported a pz3 textures and all - not only that, it didn't even take as long as usual either. I haven't been able to use vue for months with all these problems! Gosh you can just imagine how happy I am!!!!!!!!!! I still need to do a few more tests to make sure my other pz3s will load, but wow, it's looking very good. Thank you so much!!!!!! Lots of love and kisses, a very happy esther!

Should i send you a photo? :-)))) Great that the problem is solved - in a way. I think i said it from the beginning. There is a confusion about Poser 4 and 5. What i did finally - i had a very similar problem - was to copy Poser 4 to another disk and install Poser 5 from scratch again. So that all connections had to be made again. Then it worked fine. The good news about Poser is, that you simply can copy the Runtime folder and have all the models that you had before. So the installation is not too bad. BTW, i ran into a sort of limit with Poser 5 last week. The solution was there to introduce a second Runtime folder. Maybe you should start early to do that as well. Just a little tip.

Hi Wabe, Oooh yes, send photo. I will frame it in a golden frame on my wall! I actually tried reinstalling poser 4 and 5 when I was having trouble importing any PZ3 at all but that didn't help, but what did help was renaming the poser folders and then doing it back again, with vue pointed at poser 4 not 5. And that's when it imported, but without textures. Well anyway, it's importing quicker than it's ever done before since your suggestion about the preferences thing, so I highly recommend everyone try telling vue which texture folders to look in. As for the poser 5 limit, will that apply when I don't have much at all in poser 5 but poser 5 points to poser 4? Is there a limit to how much stuff I can have in my poser 4 runtime when using poser 5? Love esther xxxxxxxxxxxxxx

ok, i will send one - must find the where i lie on the tiger skin! So that it fits! A little confusing your 4 and 5 situation. Are you really sure that you have installed the last Vue update - especially the last beta? I had exactly this fun when the Mac version was not able to read Poser 5 files. I did like you has done. Use Poser 5 and let Vue think it is from 4. The beta solved that problem. An easy way to find out wether you are using the "good" version is, to check wether when you inport a Poser 5 object a second process on your Mac is started and running (as long as VuePro is running). It's called "SimpleAlert". If you plan to install the last beta - maybe you want to backup your environment folder from the Vue folder first. Why? I will tell you later. Ciao, Walther

Hi Walther, yes I've got the very latest beta installed for vue pro! I gotta run. Byee, Love esther

Walther, next time when this questions about textures are asked, you can refer to our faq section where I have put a link to this thread. Thanks a lot, this is a very important explanation. :-)Guitta

I have been following this thread with interest as I now have a problem with my PZ3'S loading into VuePro without textures from Propack since the Beta's have been installed.I don't understand how the problem was finally solved as the thread was not clear to me on this issue! I have been running VuePro since it first came out and have installed all the updates including Mover5. I will admit I haven't used it since I installed the Mover5 and the new Beta.While this thread was happening I was trying to import some Poser figures I worked on last week and imported them into Vue Pro and no textures turned up and nothing was asked by the program on importing.I am running PC with Windows XP Professional 1.5 gigs of ram and dual Athlon 2.6 plus processors. Could someone enighten me with how to solve this issue. Cheers arrow1

Ok, i am the Mac expert, but the idea is platform independant. In the preferences - third tab - you find the option to add folders where Vue looks for textures. Beside the standard ones (Normally the textures folder in Runtime of the Poser version Vue is pointing to and the bitmaps folder inside the Vue one). Add there the folder where your Poser textures are - for example the textures folder in the Runtime one. That helped in Esthers case. Maybe you try that as well. I am not sure why this happens to Esther and you but to be honest, it looks to me like a non-standard Poser installation. That especially the textures are moved to somewhere else. Vue is not reading the full pathname i think, only the last part and expects the standard pathes for the rest. But that is only a guess. Hope that helps - otherwise let us know. Walther

Hi, no I think my poser folder hasn't really been changed as to where the textures are. The funny thing was I was doing a similar thing to arrow1 except I don't own mover. I thought I did because I found it on my vue 4 disk, and I tried to install it. maybe that had something to do with it all going wrong. And at the same time I was installing beta upgrades. Love esther

Thanks for your replies.Could I just clarify something? I go to Options in the file menu and click on Operations and add the runtime folder I want to use.Is this correct? arrow1

Yes arrow1, exactly that. I have added a lot of other folders there as well - i am a structure "freak". Walther

Thanks Again! arrow1

Big problem now. I want to add texture folders inside poser 4 using that vue preferences thing, but now vue pro is not writing the path correctly as it[s not recognizing the superscript tm in my posertm4 folder. If I rename the poser folder to poser 4 then poser can't find all the objects etc when I try to load my figures into poser. I know I could copy the texture folders somewhere else but then I'd have to upgrade them everytime I loaded anymore stuff into poser 4. Love esther

Gosh that's not very clear is it? Sorry! I want vue to be able to search my texture folders that are inside my posertm4 folder but I can't direct vue pro to do this as it can't see the superscript letters. I've got a feeling this is a new problem. Love esther