GMan's Mods & Stuff — .X poly limit?

Re: .X poly limit?

null@example.com (kimgar) — Fri, 13 Apr 2007 17:22:49 +0000

ahhh, for some reason that bugger suddenly loaded, and i could see the debug ouput:

Could not draw triangles, too many primitives(302470), maxium is 65535

...so yes, a limit is confirmed

Re: .X poly limit?

null@example.com (kimgar) — Fri, 13 Apr 2007 14:02:53 +0000

yep, that's what i've been doing so far - it just seems 'cleaner' to work with a single object rather that 100.000 small ones

anyways, thanks for the input - i will continue my search for a smooth export/import workflow...

Re: .X poly limit?

null@example.com (gman) — Fri, 13 Apr 2007 13:51:02 +0000

not sure about .X specifically but i would say yes its still a limit. until they decide to support integer data instead of short data for their vertex info Irrlicht pretty much has this limitation all around. now, i think you can do some creative things in breaking your single mesh into smaller portions.

.X poly limit?

null@example.com (kimgar) — Fri, 13 Apr 2007 13:32:44 +0000

unfortunately i am bound to work with enourmous amounts of data, but i've managed to export and import to irrlicht a 1.3 million poly .X using
pandasoft exporter for max (could not get the polytrans .X format to work...).

BUT, when collapsed to a single object, this object causes bmax to stall forever, and i read something on the irrlicht forums about a 65,000 limit regarding the .X format in 2005, and that a fix could be expected for later versions.

nvidia FX composer loads my .X file amazingly fast and painless, so i am wondering if there is still a limit in irrlicht? if so, does anyone know exactly what is the limit?

...and lastly, this is just a static object, would .X still be a preferred file format?

wow, finding a good export workflow is a science in itself