[Kazan]

ARGH!!!!

I was going to support .max - but i cannot find documentation for the format.

If any of you can provide it

[mikhael]

Originally posted by Kazan
it keeps a depth tracker during the recursion to generate the BSP - if it goes over a certain value it figures "hey we're just going to keep going" - so it stocks and refuses t ocontinue [returning and error]

In that case, you're right. Its a problem with the model.

You might want to consider putting in a stupidity slider to adjust the recursion limit (like a renderers ray recursion limitting). On the far left, your bog standard limit. On the far right, no limit and you were warned, you moron! That way, when the user tries to POF a model that's got coplanar and/or collocated polygons, the user can attempt to up the limit. On the far end of the limit, mind, the windows protection error that pops up will and the user will have to concede that you were right in the first place.

Or you could leave it as is.

[mikhael]

Originally posted by Kazan
ARGH!!!!

I was going to support .max - but i cannot find documentation for the format.

If any of you can provide it

I belive .MAX is considered off limits without a licensing fee. 3ds is probably your only option there. Could I beg and plead you to consider .LWO?

[Kazan]

.3DS doesn't save the hierarchy data as Styxx and I understand it

if you can get me a very good document on the .LWO format i can add it eventually

those ****ers can kiss my ass about .max then... *******s

[WMCoolmon]

Originally posted by mikhael
By hand. In assembly. Of course.

Real men use hex editors

11010111110000111010101011111110
00001101010111100000111000111010
10101010100000011111111000000111
00011111010110101010100101010101
11110000111010000011111000011110
00111110011101110110101101010111
01101001110001110011101000111001

There's your graphics renderer, Kaz.

[DragonClaw]

I'm not entirely sure if this is what you are looking for, since I know absolutely nothing about programming... but it looks complicated and informative, along with containing a bunch of unintelligable jargon.

http://www.wotsit.org/search.asp?s=3d

[NGTM-1R]

If you mean the model hierarchy, .3ds either saves it or Cinema4D magically reproduces it.

[Kazan]

k

[mikhael]

That looks like it DragonClaw. Though I should point out that the LWO format itself changed between LW5 and 6.

[Nuke]

yay!

[Boomer]

http://blender.org/cms/Home.2.0.html

Go to blender.org.  They do of stuff with Python scripts and the such so they might have what you need?

But what do I know?  I build computers, not program them.

[Kazan]

Boomer you must be new - you're not aware of my standing orders related to blender

Don't use that piece of monkey excrement!

it corrupts models - I will not give debugging support for any model that has been touched by blender

[Col. Fishguts]

Nice work

Will the ***->POF geometry conversion routine be rewritten from scratrch or ported from older PCS versions ? Meaning is there a chance that the autofacet problems will be adressed ?

[Kazan]

it was naturally ported - but there is only one *->POF converter in PCS2 - a PMF->POF converter [PMF is PCS Model File, the format it stores it in internally.. and can write to disk] -- this makes it easier to support various model types.

[Vasudan Admiral]

I've only ever used blender to model my stuff - and the only times i've run into problems has been when i screw something like heirarchy up in TS. All meshes i've converted with your post 1.1 versions have worked perfectly in every aspect - nothing corrupted whatsoever in about a hundred conversions so far.

'neways, the new PCS is looking good - i really like the heirarchy idea.
Questions: will it be able to:
1) Read DDS textures?
2) TGA/JPG?
3) Display glowmaps, shinemaps and environment maps?
4) Play/edit model animation scripts set up using Bobs system?
5) Auto-path all the turrets and subsystems automatically?
6) any other intended cool features?

[Kazan]

1) If DevIL does
2) DevIL supporst them
3) Maybe eventually - but not the first release
4) Maybe eventually - but not the first release
5) That's a canonical part of the conversion process - i just ahve to translate the cob->pof code into cob->pmf
6) FOF support

[Getter Robo G]

On teh BSP error...

Sometimes if I convert and end result is 10 times to big, IT still works. knock it down to 2 times (like a 90meter bomber) still works.  but resize down to 45 meter model and it crashes PCS (1000 BSPrecursion error)  what changes in the conversion process that size matters?

Just curious if this meant the model (s) had a geometry error inherirantly or if it is a size/polly isssue.

Been trying to get a fighter/bomber in game for a while now but it won't work unless it's cruiser sized.

[Kazan]

Getter Robo G: the coordinates of the polygons change in the conversion process -- it means your model has geometry errors

[Roanoke]

I may be wrong here, but I seem to recall PCS didn't store a default mesh size for conversion (ie if I changed it, I was unable to return it to the default value).
Only a minor gripe ofcourse though.

[Vasudan Admiral]

Sometimes if I convert and end result is 10 times to big, IT still works. knock it down to 2 times (like a 90meter bomber) still works. but resize down to 45 meter model and it crashes PCS (1000 BSPrecursion error) what changes in the conversion process that size matters?

I'm fairly sure that error is caused by the shrinking of the model. TS's co-ordinate system only has 3 decimal places, and so with really small objects, chances are two or more close polys are going to be merged together, thus screwing the conversion. The simple fix is to scale your ship up to the dimensions you want it to be in-game, meter to meter, and set PCS's conversion scaling factor to 1 rather than 20, basically meaning 1 TS meter equals 1 FS meter.

1) If DevIL does

This? http://openil.sourceforge.net/about.php
(according to that page, it does indeed support DDS, so...sweet. )

5) That's a canonical part of the conversion process - i just ahve to translate the cob->pof code into cob->pmf

An auto-convert feature? Awesomeness. Will it be incorporated as a feature into the path screen as well? (ie, for older models)

6) FOF support

FOF as in Field Of Fire? ie, a conical representation of the firing arcs of turrets. That would be....incredibly handy in preventing the dreaded shoot-through-self syndrome.