Forum Moderators: wheatpenny, TheBryster
Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)
Well, I have imported OBJs sizes from 95-110 MB. So, if you are importing your Poser models as OBJ, you can stretch the limit. Plus, bigger file size of Vue scene itself has it's toll, I'm sure you already know that. Meanwhile, Vue gets a little unstable after importing several PZ3 files, despite their sizes. So, rather then size, the question may be better said as how many PZ3s YOUR Vue can handle?
The file is 253 mb and it's one PZ3. Poser 5 chokes on render, Vue Chokes on import and then says it can't read the file. Funny thing is DAZ Studio Alpha imports it, but not everything is as it should be. MightyPete - I will search out that thread. Although, I mark things read so I hope I can find it. :-)
Well just look in the archive. You know a button with that name click it and all messages show up. Well you could try to simplify it or save it as a obj or some other file format. Simplify meaning if it has a lot of extra stuff attached to it like swords for instance. try to import it first without all that extra fluff and save it as a Vue object. Next import in a new scene the fluff, import the big vob file and arrange it all group it and again save it as a new named vob object. new scene again import the big vob object. Get the idea? Do it in steps. You may find rebooting if things get sluggish between steps helps. Look at my lego church. I could not import that mesh into vue properly don't matter what I tried. So I did it in pieces and it worked. That's a extreme case but if I can do it you can do it.
MPete is very fast with answering. :-) I absolutely agree with him though, import everything separately that can be separated and place them back in Vue. And changing them into VOB, I think is a splendid idea; I never thought of that before! Memorize these four words, "group objects, hide layers!" Makes Vue much faster. Well, I guess I didn't add anything new to the discussion, rather agreeing with MP! :-) No wonder they call him "MightyPete"! :-)
Hmmm somebody just said that a while ago. Where I got that label is much more benign but it's impossible to change now so pick well it has a way of sticking. That was the exact same error I got when I tried to import the church all at once. As I said many times before; Repeat after me "Grouping is my friend " Hidden layers is a must also when working on huge stuff. The only thing that I can see that could possibly goof you up is that max you set on the swap file. If it goofs up the error will be you have run out of memory. I don't know if XP can handle a swap bigger than 4 gigs and with the memory that's already on your motherboard you have exceeded that number although xp will not realize that till it starts using it all up. Linux machines use a 128 meg swap file max. It uses it much more effecently. Not the winders spew and puke method we have become so accustomed too.
Yes I can relate. Like something like a church made out of lego blocks it's critical that all things be resized exactly the same every time. How do I do it? I don't drag a resize, it's too error prone. I use the numerics tab and type in new numbers after I've written down the original numbers on a pad of paper just incase something goes wrong. That last tab on the left in numerics can also goof you up. The world links. The steel nut looking icon. Sometimes you have to reset that depending on what your trying to do. Vue files are bigger than most original meshes but Vue can handle them the best. Don't worry to much about it cause the textures and other things are saved with the mesh, Thumbnails and other info. That church is a good example the mesh is actually small around 20 megs or somthing but in Vue it explodes to 250 meg. Thing is as a Vue object Vue seemed to be able to handle it.
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.
Is there a limit as to what it can handle?