[Kazan]

i put back in the optimization for sortnorm regions that contain exactly two polygons.. though in a probably-slightly-safer way - pls tell me if future builds break geometry again.

[Tempest]

I'm getting a bounding box of 0,0,0, for three seperate models I've tried to convert. It's only resetting the bounding box in the latest builds. The geometry and heirarchy for one of those models converted properly with PCS1. Is there a simple thing I'm forgetting or should I mantis it?

In PCS2, the models all show the proper bounding box in the editing window, but the model crashes FRED and shows up as 0,0,0, in modelview.

I'd like to add that the missing triangle problem HAS been resolved as far as I can tell, and no more flipped X dimension.

Great stuff, though. PCS2 is progressing quickly! I have a suggestion as well: Put the name of the model in the top bar, so you can see the modelname easily if you have multiple instances of PCS2 going. Because of the icon, we know it's PCS2, so we don't need it to repeat it again. It'd be more useful for it to say "fighter01.pof - PCS2" in the taskbar instead of "POF Constructor Suite 2".

[Bobboau]

ok, just updated the sig, fixed a few bugs, modified the auto-path (those values seem to work much better) and added an orthographic projection option.

though I'm still working out some bugs with the ortho.

[Bobboau]

ok, I think I got the ortho problem mostly solved.

[Bobboau]

updated, now with wireframe color options.

[Bobboau]

Thought about it and realized that different icons may solve my problem - Would you mind if I did some icons for the constrain and lock buttons? And if so what size?

didn't notice this till just now, if you can make icons better than the ones I have for anything includeing the executable icon, tree icons, or tool bar icons I'll use them. the tool bar seems to like 24x24, {212,208,200} is the transparent color for them

[TrashMan]

Grr...I tried converting hte hybrid with the latest version..it converts it allright, but chrashes during saving!!!

[Bobboau]

Exelent! a reproduceable bug!

be sure to include a copy of the COB!

[Kazan]

i'm pretty sure i had it remembering the open file... but that got kobashed somehow ... making it remember the open file name should be trivial... updating the file name on title bar marginally more difficult

[Tempest]

Where is the collision mesh thingy made? during COB import or when exporting to POF?

[Bobboau]

exporting to cob pof for the first time.

[Kazan]

when exporting to POF for the first time[ after geometry is modified], not cob [and on any POFs opened that were generated by versions of compilers i don't trust - IE any POF not built with PCS1 compiler 1.3.4, V's compiler, or right now PCS2.. though that really shouldn't be trusted]

[Bobboau]

I meant to say pof...

[Scooby_Doo]

Kazan or Bobboau, you might want to bring the forward clipping in the viewport closer to the viewer.  When I tried zooming in on a model it started clipping. (I bet it was because i forgot about the new conversation ratio).

Also when I switched to Thrusters (I'm converting a model right now) the background switches to white (then  another time to light blue) are you remember to restset the background to black?

[Bobboau]

it probably was, that's what it usualy is when that happens to me. (it'll only happen after I reset the config. obviusly) try setting your conversion scale ratio to 20 and see if it's more acceptable to you.

you mean the... the screen in the back gets set to something other than black?
are you sure you don't just have a bizarrely huge thruster glow?

[Bobboau]

had a thought while hunting down why saveing to POF hangs some times, actualy two, the first is you should add a handeler for the stack overflow exeption, something that terminates the thread and *set's the external flag to false* i.e. IsRunning.

also, within GenerateTreeRecursion, were it recurses you can catch infinite recursions, if either fmax/min or bmax/min are the same as Max/Min, or if the difference of any dimension in any bbox is or very close to 0.0, you also have the general coordanants of the polygons that are causing the infinite recursion, so you can communicate this information back to the user via a message box.

also you can handle this case by making a poly group with more than one polygon in it, most V pofs a bbox encompasses several polys, not always one like PCS pofs tend to.

[Tempest]

I had to reload the COB and then global data import everything. I'm finally able to get POFS converted in PCS2 to show up ingame, with no problems. Hooray! It'd be nice to be able to drag the model, instead of rotating it. Textures also don't show up; I've tried JPG and PCX, both of which did not render, and I did set the folder they're all located in.

By the way, the list-copy feature is by FAR the most useful thing. Ever. I can turret a model in about 1/10 the time it used to take. Thanks!

If I may, why is there a conversion ratio issue? It seems silly to do anything but 1:1, I'm just curious as to why it started?

[Bobboau]

because the first guy to write a pof converter did it that way, it became standard, all pof editors worked like that and all COBs were made with it in mind.

and you can drag the model, both in terms of actually moving it (hold down ctrl) and in terms of moveing the camera position (hold down shift).

[Bobboau]

anyway, I've been saying for years now that the whole infinite recursion on identical centroids issue can be solved by simply placeing more than one poly in a leaf node, Kazan has always maintained that the POF structure does not suport this, but I know it does from many years of dealing primaraly with V pofs that do just that.

in the pof's bsp structure you have a block of memory and various offsets in this block point to different nodes, typically you have a swarm of sortnorm nodes, each having five offsets in them, each of these offsets points to a diferent node, in practice, the nodes a sortnorm points to will be either a bbox or another sortnorm. bboxes have no offsets, they are simply followed by one OR MORE polygons which are ended by a EOF marker. sort norms exist in this same fashion, theoretically you could have mutable sortnorms as children of another node, and you could put sortnorms inside bboxes. but the V pofs don't do this, and I'm not 100% sure FS would interpret them correctly (I'm at about 95%). but I do see that the polys of the V pofs in these lists are not cocentric, they typicaly have very similar normals, that's about it, but I think this method would be very useful for forever fixing the dredded infinite recursion error.

[Bobboau]

ok, I put my theory to the test, I really really, really really really REALLY _REALLY_ ***REALLY*** would like it if _you_ who ever you are would test this build here as soon as posable with what ever COBs any verson of PCS has not liked, note I have BSP caching disabled so everytime you save a model it's going to recompile it. also note that is not my sig build and it lacks the dlls that comes with my sig build.