posted 02-06- 12:11 AM            

The introduction of Condor's dm is a sweeping change and I have started to notice a few problems with a few aircraft. A couple of specifics,

1. HE100 - cannon problem as noted previously
2. spit ixe - left wing breaks on takeoff very easily - ai is failing takeoff test 100%. Also SDOE locksup completely when it explodes - 100% repeatable (fly it into the ground).

I have tested the spit1a, spit v, 109e4, 109f and they seem ok, although I've noticed some odd lower level lods with all of them (these are consistent with previous packs - the pit canopy seems to disappear on several of these). I now this is limited yet but it's hard to test them all.

I have only started testing, but I think more testing is needed to uncover these problems. I need assistance - please if you haven't already - download the engine damage files (final, fix1 and fix2) and test them extensively. Don't just fly them - look for lod problems (disappearing flaps and control surfaces), crash them, you know the drill. Please report problems - I don't know if Condor can fix them - let's document the problems and we'll figure out how to fix as many as possible.

We need to be careful with this - I don't want to release all these updates without knowing and eliminating or minimizing the problems.

------------------
Spin

posted 02-06- 05:02 AM               

I have downloaded a number of new aircraft in the last few weeks and noticed that there are some problems with duplication and replacement of existing pilot models. I'm not sure which aircraft download caused the problem but I lost the pilot from the Yak and Zero and was getting a number of CTDs until I removed the new file that was causing the problem. I am still getting a few CTDs in off-line missions (very rare for me) and again I have to test this to ascertain the causes.

I think the conclusion to draw from this is test and document the finding. However my rig is so choked with stuff at the moment that I feel it will only be when we have a PP release candidate on a clean install that we can really isolate any nagging bugs. (I think it may even be sensible to use a self extracting zip for the beta as it will be easier to isolate any issues).

My suggestion would be to lock the features of PP6.1 in the near future and get that release candidate out so we can isolate any outstanding bugs and standardise things like pilot kill mods across all the pilot models.

posted 02-06- 01:25 PM            

WT - I had reported those to you separately as well - Have you had any luck correcting them? I find ops seems to randomly delete wonderful things like lods and dofs when you work with them. It gets a bit frustrating.

Since I went to Directx8 it hasn't worked properly - I can only get OPS(even Bryan's latest version) to work in wireframe mode. When I choose the render option it crashes.

Yardstick, I wasn't aware of the corrupt spitix in pp6, perhaps I could send you the source file that TS gave me. Maybe it's ok. I don't think I opened it but it might help to trace back to a non-corrupt version.

Your suggestion of a feature fixed beta makes sense. I'll pack up what I have for limited distribution this week. This will require extensive testing and feedback.

A note to the Admin on this: Could we add a Planepack Section to the board? - I would be happy to administer it. This will help to document bugs without cluttering Tech Talk.

------------------
Spin

posted 02-06- 01:30 PM               

He has the SM and i'm sure you'll get it soon..

see, i didn't completely leave SDOE.

posted 02-06- 06:33 PM               

Yes, absolutely I have been requesting a high level of testing in order to determine if any problems have been created by me or by OPS 1.3 making unknown and unwanted changes(like the he100d).

The SpitIXe has always had that exploding ctd problem. The version that actually made it into pp6.0 was the same as 5.3 due the the file being corrupted - long story but anyway in my testing of the spitIXe before I put my engine dm into it, the ctd bug was there and happened almost every time the plane was destroyed.

I double checked on the left wing obhits to be sure there is no typo there which could be causing the wing to break to easily. There isn't so this is a mystery to me.

There were problems with the canopies in the 109's, the fw's, the zero's. OPS 1.3 on saving would move the canopy to be below the pilots legs and I appempted to address these in the fix1 file. If you have noticed any others, check to see if it is below the pilots legs, and then please let me know as well.

Others are much more adept at fixing 3d visual model problems or when say a cannon starts firing the wrong way. I am getting better as time goes on, but I still have a ways to go to catch up to the other's skill level. If I can repeat a statement here that goes for me as well:

We need to be careful with this - I don't want to release all these updates without knowing and eliminating or minimizing the problems.

Yardstick,

Just to repeat, the pp5.3 version of the SpitIXe also has the ctd problem when the plane impacts the ground at a high rate of speed.

On the he100d, I received it from Razer, and found a small but new bug created by OPS when he saved his cannon firing fix. I am hoping to get a new file soon, but if we don't the problem is small enough to ignore if necessary.

I will be creating a new single engine dm zip file shortly and I will send it to you spin to be part of the 6.1 testing.

posted 02-06- 11:53 PM            

Tailslide made some big changes in the spitix fm for pp6.0.

Tailslide: Have you had a problem with the file corruption being referred to? I don't want to overwrite TS's work to introduce the new dm unless he thinks it's necessary.

------------------
Spin

posted 02-07- 10:58 AM               

TS

posted 02-07- 01:47 PM               

I also fixed the problem with the U/C leg that caused SDOE to Lockup everytime you lost the wheel or damaged the actual leg. I sent the fixed version to Condor so he could add & test his excellent engine DM code.

The CTD/lockup bug that is mentioned above when it is totally destroyed still needs to be nailed although it seems to happen to me randomly.

I have been working on improving the 3D model (well not me personally as I'm not to hot at drawing!)of both the Spit IX & the V
and in fact have a whole load of Spits in the works.

The plan is to release 3 versions of the MK IX - the FIXc, LFIXc & LFIXe (see above pics).This way you can have missions using correct variants for the correct time period.I'll probably do a same thing with the Mk V.

Cheers

Paul

Bradburgers SDOE Projects

posted 02-07- 03:42 PM               

BTW those textures look familiar

posted 02-07- 08:01 PM               

When did you send those file to me? I haven't gotten anything recently so I wanted to be sure I am not missing them.

Thanks,

posted 02-08- 05:59 PM            

I checked back in the betas you sent out for 6.0 pack -TS4beta11 to TS54beta14 and each seems to have the spitix file that won't open in ops. If you didn't make any changes, I guess it makes sense to go back to the 5.3 spitix (to incorporate Condor's dm changes).

Yardstick, seeing as Tailslide didn't make changes to it, I don't know if it's worth chasing down the problem - unless we can't fix the ctd bug for the 5.3 + dm version.

------------------
Spin

posted 02-08- 06:09 PM               

The SpitIXe in my engine damage pack is the pp5.3 version with the engine damage code in it. I did alot of testing with these planes before I put in my engine damage code and with the SpitIXe from pp5.3, the ctd bug was there before I put my code in place.

Basically, I think this leaves us with having to find someone who can track down the ctd bug.

The he100d is still being looked at.

On another testing note, please fly the "Valleta Field Attack" mission in Africa with all full realism settings on and the enemy slider put to max in the general screen inside of sdoe.

It has the p38j, typhoon, and fw190a4 in it.
Let me know if you get any ctd's with that mission.

I got one last week and haven't recreated it and also have made my own missions with these a/c against eachother and still no more ctd's. I just want to be thorough here.

Thanks,