[KARMA]

yes, I thought something like that.
BTW, do you have any clue about the flythrough problem?
This was happening sometimes in the past, and usually the way to solve this problem was to change converter (cob2fs2 instead of pcs or viceversa), but now this can't obviously be done anymore.
edit->I'll try to split the turretts/engines/radar from the main object, and convert the model as it will be in the final version, to see if the problem persist, but even the other non optimized version was having this kind of problem, so...

[Bobboau]

might be due to the large number of intersections, they arn't a problem for rendering anymore but the BSP tree is still used for colision ditection and haveing polys that go throught each other is going to confuse the hell out of a BSP interpeter no matter how well the tree was constructed, in fact a better BSP compiler may cause these problems to be actualy worse

[KARMA]

ahrgh!!
ok, well, thanks anyway:)

[Bobboau]

just so you know a BSP tree is a way of organiseing polys based on wich ones are in front of wich, so you can see how a poly that goes through another poly is going to cause problems when you ask wich one is in front

[KARMA]

well, many thanks for the explanation..
btw this is a problem, and I'll have to solve it...in a way or the other...