[Kazan]

well.. the BSP errors have been fixed.. curteousy for the BSP Debug tool (available when you load a POF, or after you save a file to POF)



oh.. and PCS2 can utilize multiple cores (POF Compilation on a Athlon 64 x2 AM2 4200+ using a debug build)

[Flipside]

Hehehe, I'll have the fastest ship editor on the planet

[Kazan]

oh?


the reason why PCS2 can utilize multiple cores is because we use threads - the OS can then assign threads to whichever core they want.. if i wanted to be a masochist i could make it detect core count and concurrently compile multiple SOBJs independantly

[edit]new buil in buidls thread

[Flipside]

Hehe, well, maybe not the fastest in the world but I'm still a little giddy from the Core2Duo

Grabbed the new build, it was actually excellent timing, it saves me having to track down what CD the Descent Manager stuff is on

[Scooby_Doo]

Am I not looking right or is there no  left, right,top,bottom, front,back buttons for the view?

[Kazan]

top hotbar

[Scooby_Doo]

I see the rotates, but not those...

Also a more serious problem.... where are the subobjects X,Y,Z location values at? I need that value when making paths

[Kazan]

to be displayed later

[Scooby_Doo]

Ah ok... good.  I'll have to copy and paste from PCS1 right now, but it's a lot easier to use than pcs1 is 

[Kazan]

the X axis is backwards in PCS1 (not in the resulting file... but in repsect to the standard directions it is)

[Col. Fishguts]

In case you want to play around with ASE, here's a simple example. The standard Max teapot textured and with several smooth groups: Download

[Bobboau]

the file specification would be most helpful.

also a file with a few cubes in a hierarchy would be nice.

[Bobboau]

I just remembered something that should be real easy to add to FSO if we had model support, the basic idea is we merge a submodel with it's parent, but we use a special BSP chunk to point to the geometry, this will allow detail boxes/spheres to work without incuring the multable subobject penalty.

the downside will be that the renderer in FSO will need to be modified considerably and use dynamic index buffers, and index data will need to be held in the poly data. might need to wait untill we define a new BSP spec. which will be much later.

[Kazan]

OBJ3

[Unknown Target]

Sorry if this has been suggested/implemented already, but will there be a direct .3DS or .LWO import? That'd be grand, if possible.

[Kazan]

Sorry if this has been suggested/implemented already, but will there be a direct .3DS or .LWO import? That'd be grand, if possible.

no as those formats are superfluous with ASE support (and .3ds is pretty much undocumented)

[Col. Fishguts]

the file specification would be most helpful.

also a file with a few cubes in a hierarchy would be nice.

See my post on the previous page for a link to the best format reference I could find.

I'll post another example with some hierarchy when I get home today.

EDIT: Ok here we go: A box with some boxes as children, which in turn have some children and so on. Also, some dummy helper points are attached to the smallest box.

Download here

[Nuke]

if you do use .3ds, and i hate that format, keep in mind that there are so many bad implementations of that format used in other progs that a great deal of idiot proofing would need to be done to make it compatable with as many programs as possible.

[Scooby_Doo]

I especially dislike the 8.3 filename format Max uses.

[Kazan]

wee look at all that green!