Fri, Jan 10, 2:19 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: Poser importing problem with Vue 4 under Mac OSX still exists...


TheWingedOne ( ) posted Sun, 25 August 2002 at 8:05 AM ยท edited Fri, 10 January 2025 at 2:18 PM

file_21481.jpg

Dear Mac users of Vue4, did anyone of you encountered the same problem? I don't get the Poser import of Vue 4.1 working. =:o( Okay the import of the dork worked once, but who needs the dork?!? I attached a project whichI'm currently working on. It's not that complex, but when I try to import it into Vue the following happens: - Locate file to import - locate Poser (but reside on the same drive/partiton like Vue does) - Vue starts to import -after the progress bar reaches about 70% Vue crashes If the Poser import works for you - especially with the Millenium figures and some other props that don't come with Poser- how is your Mac set up? Where did you install both apps? Any help it greatly appreciated, since e-on couldn't help so far. Best regards, Phil


scotttucker3d ( ) posted Sun, 25 August 2002 at 4:52 PM

Wow - I haven't had it crash on me like that. Usually it just loops trying to find the poser app when the patch isn't applied. There is a known bug that Vue won't find pz3s for the poser app if poser wasn't installed under classic. Steve posted a fix for this awhile back in this forum about a month ago and that worked for me. Search this forum a couple of months back and your should find it. There is also an existing bug with the .bum bump maps from poser - Vue does not recognize them and needs to be forced quit when this happens. In poser just be sure to get rid of the bump maps before you create the pz3 file. Then you'll need to manually add the bump maps back in Vue. If these don't help Vue might be running out memory during the import. If so - try making the imports into smaller chunks instead of one big scene and that might work. Scott


wabe ( ) posted Mon, 26 August 2002 at 6:13 AM

Hi Phil, still problems - i am sorry to hear that. My first idea as well was that something is wrong with the textures in the Poser originals. I as well do have problems that Vue likes to crash when i try to load a file and Vue can't find a texture file. By the way, that seems to be a problem in the Mac and in the windows version. Have you tried out smaller Poser files as well? Because Scott's second idea that it simply could be a memory problem makes sense as well. I think you should try out to import small poser files (a horse or something like this) first to find out wether your Vue will import any Poser file or wether your problem is a general one. If you are interested i can send you my system profile (in screenshots??) so that you can compare it with yours. By the way, i never needed the e-on fix from Steve, the import worked on my system from the very first moment on. AND I DEFINETLY INSTALLED POSER UNDER OS X!!! If you need more help, let me know. Walther

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


TheWingedOne ( ) posted Mon, 26 August 2002 at 8:36 AM

Thanks for the hints folks! I'll give them a try as soon as I return home :) Walther, I'd be really thankful if you could send me the screenshots. Looks like I'll need tot do a hellufa testing to get this thing to work :( I can't imagine that it's a out of memory thing since I have more than 1.2 GB of memory... One thing I'll do is to get rid of the bump maps and re-apply them in Vue if this works. Keeping my fingers (and toes) crossed... :) I'll keep you guys informed about the progress. Thanks, Phil


scotttucker3d ( ) posted Mon, 26 August 2002 at 9:54 AM

I figured you would have a lot of RAM Phil - what I am thinking is maybe Vue itself has smaller buffer sizes for importing objects and the memory gets full in Vue. I wish you success. Scott


wabe ( ) posted Mon, 26 August 2002 at 12:08 PM

Phil, no problem to send you these screenshots - maybe you give me your e-mail address via a direct message. The only problem is, that i am out of office minimum tomorrow. And i have my Mac at the office, so you have to wait a little. Anyway, i am shure that we can find a solution - if there is one. By the way, how big is that poser file you try to import? That would be interesting to know. Walther

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


TheWingedOne ( ) posted Tue, 27 August 2002 at 3:12 AM

Scott and Walther, Just had a little time to test the Poser import problem. I removed every bump map within the file, but that didn't help. Vue still crashes at about 70%... What I'll do next is to do a new install of Poser and add only a few models just to test some things out. Hopefully Steve Bell from e-on reads this thread so he might help, too. Phil


TheWingedOne ( ) posted Wed, 28 August 2002 at 7:07 AM

Scott, Walther and all other Mac Vuers, who managed to get the Poser import to work, yesterday evening I had the time to do further testing. I seems like Vue has problems to recongnize the texture paths within the Poser file. I imported the female from the image above only with the texture applied (no clothes, no hair, no car...). Vue finished the import but didn't import the textures - female was only grey just like an ordinary OBJ file. If I applied transmaps like used with a hair prop Vue crashed again at about 70%. I tried this with several other models (clothing, vickie 2 with texture etc.) The result was always the same. So it must have something to do with the textures/texture paths. Since I checked several textures this is not a problem related to certain texture. Any ideas what to do? How does the texture path look like within your Poser files? Any help is highly appreciated since I'm getting really crazy... =8OP Thanks, Phil


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.