[Scooby_Doo]

One small question/problem... Did you alter the way it saves files between the alpha and the 2.0? besides fixing the inverse bound error?  I've got a model that was converted with the alpha and has the inverse error, but if I try to save it in 2.0 it just gets stuck. 

[Hades]

Kazan do you have the latest version without the installer? Because the installed PCS2 is the one thats trouble and the non-installed versions didn't.

[Water]

Bug in Sub-object rotation.

Both X and Y axis rotation do nothing for subobjects. Z axis does work.

Confirmed with Truespace and two different models.
VA during testing also provided a model with x, y and z rotating subobjects. In the mission AXIS-ROTATION-Test the model on the left went through PCS1, the faulty one one the right by PCS2.
http://files.filefront.com/rotation1vp/;9833677;/fileinfo.html

[Akalabeth Angel]

Hey I got your program to crash consistently. See post in Mantis

Though problem is probably my model not your program . . but who knows.

[Snaga]

I also got a crash problem with PCS2 2.0.1 . Already mantised it. Also, (I dont know if it was already posted or if it is a problem with PCS) I´m having collision detection errors with every model I convert with PCS2, and when I convert them with pcs1 I don´t have any. At first I thought I was doing something wrong with my modelling, (bumps, bad geometry, etc), but then I begun testing stable models and they had the same collision detection problems.

[blowfish]

Just purge BSP cache and resave.  Collision detection should be fine.

[Snaga]

Just purge BSP cache and resave.  Collision detection should be fine.

What is the BSP cache and where is it?  Are you saying that by purging this, the collision detection will be fixed? or that it isn´t supposed to be havving problems at all?

[blowfish]

Its under that data menu.  By purging it, you force PCS2 to recompile collision detection data etc.

[Backslash]

Mostly a feature request, somewhat a bug:  may I request that Weapon Points be made more visible/obvious?  Particularly in cases where multiple missile banks share the same points.

I know, the answer might be "don't make the missile banks share the same points" , but picture this.  I have a model with secondary bank 1 that has 20 points, for example.  I wish to split this into secondary banks 1 and 2 with 10 points each.  After I push the copy button on secondary bank 1, bank 1's points look 'faded' when I reselect the bank, and it's a lot harder to tell which is selected, no matter which color I try in the options so far.