Mon, Dec 23, 10:30 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)



Subject: Poser import function


Staby ( ) posted Tue, 28 August 2001 at 4:22 AM · edited Tue, 26 November 2024 at 10:16 PM

Hi, Im a Bryce 4 user but I was thinking to buy Vue 4 instead of upgrading to Bryce 5, mainly because of the Poser import capability. I read that there were some bugs in this particular area and I would like to know if with the last update those problems were solved and if you (Poser/Vue users) were satisfied with this function. Thanks


SAMS3D ( ) posted Tue, 28 August 2001 at 4:29 AM

All I know, is I have Vue 4, when I create a poser file, meaning .pz3 and import it into Vue, I never have a problem, all comes over, with hair and clothing intact. It is great not to have to worry or find a tutorial to correct this. You will love it. Sharen


MikeJ ( ) posted Tue, 28 August 2001 at 4:33 AM

Hi Staby, As for me, I have no problems with it. A few people have had to rename their "poser.exe" file to "poser.exe", to get Vue 4 to "recognize" the file (Strange, yes, but it doesn't harm Poser in any way, and it does something to help Vue "see" it.) I didn't personally have to do it the first time I installed Vue 4, but after a reformatting, I did. shrug In my particular installation, Vue won't read Poser .BUM files. That's not a problem for me, since I don't use them anyway, but it could be for others. Nevertheless, there are many people who do NOT have that problem and have reported perfect Poser PZ3 imports. You'll probably get several more replies through the day, but my best suggestion would be to download the demo of Vue 4, which should become available soon. E-on's website says it's due out in September. Overall, I have to say I am quite pleased with Vue 4's poser PZ3 import. It works quicker and faster than .OBJ import, and Poser people imported into Vue that way, seem to render more smoothly than imports based on .OBJ files.



MikeJ ( ) posted Tue, 28 August 2001 at 4:34 AM

Oh I might add, all your color and transparencies in your Poser PZ3 files will come into Vue just fine, and every element in your Poser scene will load into Vue in the exact same position as it was in Poser.



genny ( ) posted Tue, 28 August 2001 at 4:59 AM

Hi Staby, I agree with Sharen and Mike J, importing Poser to Vue4 works great. I did have a problem when I first installed it, but after installing the Patch, I couldn't be happier with the effects. Like MikeJ, my Vue won't read .bum, but I hardly use them to, so I don't miss that feature at all. For me, the decision to buy Vue4 over Bryce was the capability to import Poser files directly........I haven't regretted my decision yet! (: genny


pvlassov ( ) posted Tue, 28 August 2001 at 8:34 AM

Is there a way to import Poser ready animations into Vue? I considering to buy this product and the demo doesn't seem to provide the answer.


Varian ( ) posted Tue, 28 August 2001 at 11:06 AM

Count me in as another one happy with the PZ3 import. It's never been easier to get Poser items to another app. Just import - PZ3, and boom, there it all is. Sure saves a lot of drive space, not needing to make a gabazillion exports from Poser! Animations, no. Poser models can be animated within Vue itself (well, just about anything can be animated within Vue), but the Poser animation files don't import. And If you've worked with the Walk Designer, etc, don't expect the same kind of motion ability in Vue. Poser models are treated like any other model once in Vue; i.e. no "bones", joint stuff, IK, etc.


pvlassov ( ) posted Tue, 28 August 2001 at 11:24 AM

Ok I see. It appears that none of the software is perfect :) I just have another question, and that is how well Vue exports terrains to Max. This feature is very important for me since I am a heavy max user. I find it unfortunate that many demos are not sufficient enough to fully convince someone to buy the product, unless the user is already famililar with it.


gebe ( ) posted Tue, 28 August 2001 at 1:32 PM

For me, it doesn't work to import pz3 files to Vue. Thanks to Mike for the topics. I had already 4.03 and renamed the poser.exe to poser.exe, but it will not work :-( Guitta


Staby ( ) posted Tue, 28 August 2001 at 2:00 PM

Thank you all for your answers, Im looking forward to try the demo! There is only one thing I dont understand MikeJ , when you say that I would have to rename the "poser.exe" file to "poser.exe", what is different? Another thing that I would like to know is what type of models is provided on the content CD? Thank you again


MikeJ ( ) posted Tue, 28 August 2001 at 5:50 PM

Staby,, I really can't explain why they suggest to rename the poser.exe file with the same name, but I would guess it's a Windows thing--- maybe. In any event, it's a simple workaround, which has worked for so far everyone I'm aware of, but Guitta. Those who had the problem to begin with, that is. Guitta, I'm sorry to hear that-- don't know what to say now. :( As for the animations, true, Vue can't import a Poser animation sequence, but especially since Animatek just did it with World Builder, I wouldn't be at all surprised if Vue 5 did so too. And, for pvlassov, There seems to be a bug in the Vue terrain export. It worked perfectly in Vue 3, and for some, still does in Vue 4, but for some, no. I've read of some Lightwave users who use Vue terrains exported from Vue fine, but am not aware of any Max users. I myself have Rhino, and have imported Vue 4 terrains with no problem in several formats, including the .3DS format (which is actually my favorite), so if I had to guess, I would say that Max would import them fine.



Staby ( ) posted Tue, 28 August 2001 at 6:12 PM

Thanks MikeJ! At least now I know that it was not a typo and if it work it is ok... :)


Cheers ( ) posted Tue, 28 August 2001 at 6:19 PM

Staby wrote: "Another thing that I would like to know is what type of models is provided on the content CD?" Everything from a DAZ Bald Eagle, to a china plate, to a Formula 1 car, to an AK47 rifle, finishingw ith the odd building thrown in :)...ohh and I forgot all the example scene files that are in there as well! Cheers

 

Website: The 3D Scene - Returning Soon!

Twitter: Follow @the3dscene

YouTube Channel

--------------- A life?! Cool!! Where do I download one of those?---------------


genny ( ) posted Tue, 28 August 2001 at 6:58 PM

Guitta, I had the same problem with Vue4 as you when I first got it even after installing the patch. I had to completely uninstall it, and the patch. Then, since I have more then one computer, I made a copy of the cd on the other computer, and used that to reinstall it. It still wouldn't work so I downloaded the patch again, and by some miracle, it did the trick. I know it sounds crazy, but it worked. Although the computer I use is newer and has more gigs, ram, etc. for what-ever reason, it would not read the original CD correctly? I don't know if this was one of the suggestions you got before, but I just thought I would share my experience with you, heck it's worth a try......what do you have to lose? It's always good to have a back up disk anyway. (: I am completely happy with it now, and I hate to see you having the program and not being able to enjoy all the programs capabilities. Take care and I hope this will work for you too. genny PS. I have an HP Pavillion XL761, the other one is an HP Pavillion also.....go figure? (:


Varian ( ) posted Tue, 28 August 2001 at 11:39 PM

The thing about "poser.exe" to "poser.exe" is actually one of type case. It should read: rename Poser.exe to poser.exe. Case shouldn't matter in Windows filenames, but sometimes, to some programs, it does, and this renaming helps Vue import (in certain situations).


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.