Xsi munge model problem

Redline · Post by **Redline** » Fri Jan 19, 2007 4:32 pm

Hello everyone, i have a problem with the munge from my export deathstar model.
My Deathstar will be not munge and the munge output stops at the middle

Everyone can help me ?
pls

PS:(i hope you will be understand my english)

RC-1290 · Post by **RC-1290** » Sat Jan 20, 2007 9:24 am

I think it's a good idea to try and explain how you put the deathstar in Zero Editor. Give us some more information please.

RC-1290'Dreadnought'

Redline · Post by **Redline** » Sat Jan 20, 2007 9:56 am

Okay, first i put the export msh model in the "msh addon " and then i open the zero editor and put the model in to the world.

Next --> I save world
Next --> i munge the World
Next --> The Modtools VisualMunge.exe will be stop by the middle munge
Next --> You can wait all the time and nothing munge

Ps: Is my mistake by the export ??? from my Model ???

Pls all help me !

RC-1290 · Post by **RC-1290** » Sat Jan 20, 2007 10:03 am

You have to make a odf file and load that in zero editor, not the msh file itself. Search gametoast, there should be some tutorials on this.(and it's quite easy, it's just that I haven't been modding for a half a year and I'm not the right person to explain it right now XD)

Redline · Post by **Redline** » Sat Jan 20, 2007 12:03 pm

Ok , I say thx to you , i hope the best model maker will help me

Pls Help me

RC-1290 · Post by **RC-1290** » Sat Jan 20, 2007 2:28 pm

but, DID you make a .odf file? and DID you load that in stead of the .msh file? If you didn't, that's why it doesn't work...

RC-1290'Dreadnought'

Redline · Post by **Redline** » Sat Jan 20, 2007 3:32 pm

Yes, i make a odf ,but the munge stop in the middle of-.- munge

Post by **Qdin** » Sun Jan 21, 2007 10:24 am

well, Majin says that some of his maps takes more than an hour to munge where it just stands still for ALOT of time - more than half an hour - if he's got something really big or something.

So I'd suggest waiting... and yes - wait 2 hours if that's what you gotta do.

RC-1290 · Post by **RC-1290** » Sun Jan 21, 2007 11:45 am

Well that sounds quite logical if you've made a full scale deathstar

.

Post by **Qdin** » Sun Jan 21, 2007 4:35 pm

Eeeeeeeeeeeexactly

Depending on the size of your model...

Post by **Qdin** » Thu Jan 25, 2007 9:10 am

Oh yeah!

Like Bandu's huuuge ship in 'real scale'? took him 15 minutes or something to fly from the beginning to the other end of the ship... and it only showed the model a few hundred meters away...

So considering it was like 9 km or something then... o.o

Fred is right: it's important to have smaller pieces than one big one. it don't spend energy on the 20 small pieces if it sohuld only show 7, but if you have 1 huge 20-piece-in-one model it'll spend energy on it as a whole.

Vyse · Post by **Vyse** » Thu Jan 25, 2007 12:52 pm

I had this problem just a couple of days ago. Once you have exported the mesh from XSI what is the files size of the .msh, Mine was 13mb and I waited 3 hours and it still wouldn't munge. I believe it was that there was way too many polygons in a single .msh, so I made several meshes out of it.

minilogoguy18 · Post by **minilogoguy18** » Thu Jan 25, 2007 4:03 pm

i think fred was telling me though that there really is no limit like some games where the compiler will reject the model, it just depends on whether your PC can handle it or not, maybe while munging you ate up all your physical memory, whats your PC specs?

t551 · Post by **t551** » Thu Jan 25, 2007 5:17 pm

A 13 mb msh file? That's insane! Even complex models usually only occupy a few hundred kiloBytes in msh format...

Post by **Qdin** » Fri Jan 26, 2007 4:54 am

Yeah - isn't that what he's saying?

Mini' when you say Physical Memory, are you thinking of CPU or RAM? or..?

RC-1290 · Post by **RC-1290** » Fri Jan 26, 2007 7:08 am

I THINK he means RAM, since that is short for Random(I love random

) Acces Memory. And CPU is short for Central PROCESSING Unit. So RAM actually stores information for a short amount of time until it can be written on the hard drive, and the CPU just calculates everything. So when all your memory is used, the virtual memory(using the relative slow hard drive; relative to the speed of Physical memory) must be used, wich makes everything MUCH slower, while when your CPU is overoccupied, everything just has to wait a few seconds.

---
I'm no expert tough and I might be horribly wrong(just correct me if I'm wrong

)

RC-1290'Dreadnought'