[Col. Fishguts]

So, opening a Max exported POF in PCS2 and resaving as POF recompiles the BSP data without changing any smoothing data of the polies ?

*Goes of testing*

EDIT: Oh yes, it works ! Perfect collision detection with the perfect shading of Max exported models. You just made my day, I can now finally throw Turdspace back down to the lowest pits of hell from where it came.

[IPAndrews]

Kazan. Just a note to say well done for getting PCS2 to RC1. Maybe they'll unmonkey you now as a sign of gratitude?

[skygunner58203]

Well, thought i'd try it out and see what all was different.  only one problem.  Crash to desktop on launch...doesn't even finish loading.  Do i put the error report on the mantis or here as a file?

[Water]

I'm finding it likes crashing when writing to cob.

@ skygunner58203
Did you put the dll pack files in the same dir as the pcs exe file?

[skygunner58203]

yep.  Running XP pro on a 1.2 GHz system with a GeForce 4 MX440 AGP card and 389 megs of ram....yeah...my compy is a piece of work....doesn't even have a proper case.  its using my desk as a case until i get a new one.

[TrashMan]

You just made my day, I can now finally throw Turdspace back down to the lowest pits of hell from where it came.

*Burs Col.Fishguts on a pole for heresy*

[Kazan]

I'm finding it likes crashing when writing to cob.

@ skygunner58203
Did you put the dll pack files in the same dir as the pcs exe file?

send me the offending model pls

Well, thought i'd try it out and see what all was different.  only one problem.  Crash to desktop on launch...doesn't even finish loading.  Do i put the error report on the mantis or here as a file?

most likely bad video drivers

[skygunner58203]

Well i checked my drivers....they are the best i can get for this card.  81.98 nvidia drivers.  If i install any higher my card doesn't work.

[Kazan]

doesn't mean the drivers aren't the problem.  no reason for it to be CTDing other than something wrong with your system's openGL

[Water]

I'm finding it likes crashing when writing to cob.

send me the offending model pls

The ones I noticed were all SteveO pof files
http://www.mediafire.com/?4njyauxjruw (mig343)
They all seem to crash at the last stage -
So I tested some FSport models 3_0_4.vp
The ones that seem to cause the crash are the bigger ones
cruiser01b
karnak
capital01-repulse
capital01-myrmidon (didn't test more)
So then I tried the V original Sath supercap2s-01 - also crashes

[Kazan]

2008-1-13 build posted

please check if inverted bounding boxes still exist - to check this your MUST compile from .cob to .pof and then use that .pof to open/save open/save several times

any pof with the error already present will probably continue to show the error - i need to make sure the error isn't being introduced into good models.

[chief1983]

Just curious, do you know if Bob committed everything in his most recent 1-13 build, and is there anything additional you've added on top of that build's stuff, or should they be pretty much the same?

[Bobboau]

it should have everything I've done untill just before he posted, there is very little I have that isn't in CVS.

[Vasudan Admiral]

I'm afraid this one appears to undo all the speed improvements Bobs latest one has, and takes approximately twice as long to load up pofs. (22 seconds for the loki vs the previous 12)

And how do I tell if the bounding box problem is present or not? Open a suspect model up in debug fred?

[Bobboau]

that's be cause he disabled them because he doesn't "know where this 'dismal render performance complaint' is coming from".
well it seems as if that's going to have to wait untill after we make our official release, as per the loading issue, he probably didn't disable the VBO creation code which is slow as hell due to there not being a good way to approximate the size of the buffer (and no way to precache our vector class). I should probably go turn that off so he isn't tempted t delete everything.

[Kazan]

I should probably go turn that off so he isn't tempted t delete everything.

at most i would #ifdef

[ARSPR]

2008-1-13 build posted

please check if inverted bounding boxes still exist - to check this your MUST compile from .cob to .pof and then use that .pof to open/save open/save several times

any pof with the error already present will probably continue to show the error - i need to make sure the error isn't being introduced into good models.

I still get this very same issue.

But I haven't compiled from cob. As I say in that post:

• I open Comm2S-01.pof from Mediavps 3.6.10 beta.
• I insert an Enter in Special Points > $core > Properties.
• I save the pof again.
• I watch the model in F3 Lab. (Xt1207 debug).

My favourite question  : Do you want me to Mantis it?

Nevertheless OGL warnings are gone and textures and submodels are outlined again. 

[Kazan]

look at the model in the lab or modelview or PCS1 - not them
open it in PCS2 - are they flipped from what they were before

if no, the problem does NOT persist and you MUST recompiled from .cob

[ARSPR]

look at the model in the lab or modelview or PCS1 - not them
open it in PCS2 - are they flipped from what they were before

if no, the problem does NOT persist and you MUST recompiled from .cob

I don't know if I've understood you but I cannot see any difference because:

• There's a damm not-so-invisible invisible texture in the middle.
• Comm2S-01.pof has spherical symmetry from its centre. You can't see any mirroring effect.

I know it seems being a bit lazy but, please check it yourself who are much more expert. It shouldn't take you much time. I feel myself like I'm blind-testing ...

[Kazan]

you don't have to look at the model - it's all values in the header editor.

three coders cannot replicate this error: it's fixed.  any models corrupted by it will have to be recompiled from .cob