Thanks, privateer,

i'll test it this WE. The "bird" you can d/l is still made with your older version - didn't se your post. Sorry.:oops:

I'll have a look at the "Emden".

Greetings :salute:
rowi58

privateer, why not simply write to DAT-file? Much easier (memcpy arrays), no conversion issues (binary to binary is much easier/safer and no headaches for multi uv as data structures of game and GR2 are similar), conversion is done to a single DAT-file, matrices/bones can be converted too, and you can let S3D handle imports/exports to OBJ. I think it will save you from some problems to come.

:yeah:

Hey Privateer

You're on a roll :yep:

Keep up the good work:up:

MLF

Everyone goes by own way :haha:
*********************
You speak about *.dat & S3D?
Look example...
File - Room_CR.GR2
Using Privateer's GR2_Exporter.exe - 55 objects (*.obj) have been exported/created... during 3 minutes (on my not fast machine ).
Two objects have very big size of obj-file...
...

CR_BSide.obj - file size = 407 223 KB

http://a.imageshack.us/img819/3293/crbsideobj.jpg

CR_FSide_Stairs.obj - file size = 657 264 KB

http://a.imageshack.us/img819/465/crfsidestairsobj.jpg

May be, these objects can be divided into smaller with (on) corresponding single-materials...?
...
For those who has not understood...
For comparison: SH4, file NSS_Porpoise_CR.dat, exported object Tzevi01_03_LM2.obj - file-size 2 658 KB...
Whether S3D can process such big file... 657 264 KB...? simple experiment has shown cannot...

http://a.imageshack.us/img842/9614/s3dmsg.jpg

... and pressing of "Continue" button leads to S3D hanging.

...
and Look forward - multi-materials...

I'll work on breaking the larger objs down to seperate files
after I finish a few other things.

Getting the routine finished for multi-textures will help in breaking those
larger meshes down into seperate files.

Yes, being able to break down those larger .objs would be incredible privateer. Many of the things that I would like to add more of or manipulate happen to be included in some of those huge room encompassing .obj files. It seems like that would be very difficult to include into the exporter though.

not necessarily so. He says he is able to read multi-textures...therefore he has the 'breakdown' of the 3D model. In the .dat files you have numbers to represent each piece of a 3D model. Each piece is assigned a texture and texture coordinates. So if there are multiple textures for an object then that means they are subsets of the main object. In DirectX terms it would be DrawSubset(x)

Good point, and good to hear.:yep:

Throw away the .bat file people.
:DL

Here's the basic UI version!
http://www.mediafire.com/?e48vl5q77fz8l6k

Just browse to the file you want and go!
:yeah:

Nice:up:

Thanks, Jeff. :up:
we look forward multi-materials.

P.S. tested... only... visual control of program's work is necessary (for big files).

I'm working on it and several other things now.
;)

And i thought "Good Old DOS Is Back" :haha:. OMG - i remeber those times with DR DOS 6.0 (not Microsoft), got 627 KB free RAM out of 640 KB.

It was realy good to see a BATCH file again - feeling 15 years younger :).

EOJ
(End Of Jokes): privateer - you made and you are making a wonderful job :yeah:.

Greetings
rowi58

:up: I Agree :yeah: , Well done :up: Privateer :up: