[Unknown Target]

Almost all of my models have a stack overflow on PCS1, however with PCS2 they actually do get converted, minus collision detection (and in one instance a couple missing triangles). So there is progress, it's the collision detection generation bit needs work.

[Bobboau]

Kaz just supposedly fixed that. I think my sig build has his new code. try it.

[Unknown Target]

Nope, no detection using that build.

[Kazan]

about time this got fixed

try testing the collision detection with this build: http://www.ferrium.org/media/pcs2-alpha-20070627.zip

(make sure to open from the COB not just reopen the POF)

VA reported the collision detection fixed in this build.  If you are having problems still with this build i need you to post the model, post a table entry for it, give me a copy of the .pof so i can import gunpoints etc and a mission to test.

[Vasudan Admiral]

Bobboau, I've gone through the path data for all original destroyers, corvettes and cruisers and have worked out the average trends for subsystem and turret paths.

Subsystems:
- The first vert (the big one further away) should have a radius of 6 x that of the subsystem itself. Your vectoring system seems quite good, and the distance of this vert from the subsystem should be 1.2 x it's own radius.
- The second vert (small one close in) should have a radius of 0.3 x that of the subsystem. Again, the vectoring system is fine, and the distance should be about 0.9 x the subsystem radius.

Turrets:
- The first vert should have a radius of 30 x the radius of the target subobject. The 'down-the-normal' vector is fine, and it should have a distance of 1.2 x it's own radius.
- The second vert should have a radius of 0.7 x the radius of the target subobject. Again, the vector is fine, and here so is the distance.

Docking I've not looked into, but since there should only be one of them anyway people shouldn't rely on an autopath to get it spot on for them.

[Bobboau]

ok so

      path.verts[0].radius = model.radius*30.0f;
      path.verts[1].radius = model.radius*0.7f;

      path.verts[0].pos = model.offset + turret.turret_normal * (model.radius*1.2f);
      path.verts[1].pos = model.offset + turret.turret_normal * (model.radius*0.7f);


and

      path.verts[0].radius = spcl.radius*6.0f;
      path.verts[1].radius = spcl.radius*0.3f;

      vector3d n = MakeUnitVector(spcl.point);

      path.verts[0].pos = spcl.point + n * (spcl.radius*1.2f);
      path.verts[1].pos = spcl.point + n * (spcl.radius*0.9f);


that is what you wanted?
that's what's in my sig.
although I don't think your going to like it...

[Bobboau]

ok, my sig has been updated again, now PCS2 has copy/delete capabilities for subobjects (in addition to the import from file).

and a shield "editor", though it doesn't allow editing, it will let you look at the shield mesh.

[TrashMan]

Just one request - add POF SCALING PLS!!!

Just a simple scale factor that would multiply all points with the modifier?

[Bobboau]

that will be the first thing implemented when I start working on geometry editing.

[TrashMan]

  You made me a very happy man 

[Kazan]

geometry edit is a 2.1 feature

[Bobboau]

n'other update, movement constraints and axis locking.

[Bobboau]

for the love of god people, I only have three days to code before I have to go back to work for another week, work with me!

[Kazan]

we need more testers... lemme see what i can do to scrounge up more!

[Bobboau]

just added selected texture highlighting.

I'm literally jumping in my seat trying to think of things to implement/improve/fix.

[Kazan]

yup, you're the bomb bro

[Bobboau]

ok, untill I get something else I'm going to work on... a geometry filter that will fix convex polygons (and polys over 20 points).

it's non-critical, easy to remove if it doesn't work and has a big payoff if it works.

[Kazan]

there's a function floating around to triangulate convex pcs_polygons .. i think it's in pmf_bsp_funcs.cpp

[Bobboau]

yeah, but triangulating leads to suboptimal colision detection. FS collides on a per poly basis, if you revert geometry down to simple triangles it will not be able to take advantage of polys of a >3 vert size.

[Bobboau]

hold it, I found something better, I'm gona remove the triangulated restriction from shield meshes.
well I'm gona do that first anyway.