BETA PATCH v1.06.17582--Bug thread

[MadMacGunner]

Well.......

What can i say....
I can´t tell you how the game runs on my PC....
What I can say is that I don´t have CTD anymore.
Of course, this might be cause the game does not launch at all. If i don´t enter the game, i can´t be sent to the desktop as i never left it.
Really, a good solution to the problem. How didn´t I realiced before?

Keep up the good work.

Perhaps in a few years we can play a red baron like game on our flamant new PC.

[furbs]

Just had my first ever offline crash in a quick battle.

Log sent.

Just checked through my ccpcrash folder and i have 2000 files, 537mb!

You think Luthier wants the whole lot?

Maybe i should zip them up and mail the lot.

[Sammi79]

I just had a strange bug in Spit2a on ATAG patch server, took off Manston flew south and climbed to 12,000 feet, everything good, watched temps & rpm all the way, then the engine failure effect kicked in - but with no damage as I have my engine info window display damage. rpms and temps were still good, gear/flaps were up, (unless my cockpit indicators were faulty as there is no external view) but the screen is shaking madly and horrible grinding metal noise. Tried cycling mixture, no effect - slightly lower rpms on lean. I recorded a short track to review, but guess what? in the track there was no shaking, no grinding metal, and steady(ish) needles for rpm/temps. mind you the track record is still not getting the engine right so I don't know.

Anyone else had this one? I think that's twice for me, the first time I thought I'd cooked the engine but now I'm pretty sure this is a bug.

Regards, Sam.

[epoch]

Originally Posted by Sammi79

Anyone else had this one?

Yes!

I experienced this a couple of days ago on ATAG. Spit IIa, departed Ramsgate, headed south up to 12,000 just like you (to rendezvous with some Blenheims). Engine conked out for no apparent reason and I had to divert to Hawkinge (whereupon I borked the landing).

I was sure I'd done nothing wrong in terms of engine management, so your report kind of supports that.

[klem]

Originally Posted by Sammi79

I just had a strange bug in Spit2a on ATAG patch server, took off Manston flew south and climbed to 12,000 feet, everything good, watched temps & rpm all the way, then the engine failure effect kicked in - but with no damage as I have my engine info window display damage. rpms and temps were still good, gear/flaps were up, (unless my cockpit indicators were faulty as there is no external view) but the screen is shaking madly and horrible grinding metal noise. Tried cycling mixture, no effect - slightly lower rpms on lean. I recorded a short track to review, but guess what? in the track there was no shaking, no grinding metal, and steady(ish) needles for rpm/temps. mind you the track record is still not getting the engine right so I don't know.

Anyone else had this one? I think that's twice for me, the first time I thought I'd cooked the engine but now I'm pretty sure this is a bug.

Regards, Sam.

The Merlin engine does fail in CoD if you maintain max boost and max revs for long enough and probably also if they are higher than recommended. I think its the Constant Speed unit that fails and that doesn't involve excessive engine temps. I don't know that its accurately modelled but its happened to me several time when I've been pushing too hard for too long.

[Sammi79]

Originally Posted by klem

The Merlin engine does fail in CoD if you maintain max boost and max revs for long enough and probably also if they are higher than recommended. I think its the Constant Speed unit that fails and that doesn't involve excessive engine temps. I don't know that its accurately modelled but its happened to me several time when I've been pushing too hard for too long.

OK, thank you. does this not register in the damage window though? governor failure or something? I held 3000 rpm for climb, and found that after I could still fly effectively, no loss of power, rpm control etc working fine just with the screen+needles shaking it was unplayable. I don't use the boost, as the throttle in spit 2a maxes out the manifold pressure at about 40% throttle currently, and the push lever stays where it starts locking max throttle at 100%

Also, no failure in the replay - but then replays are not working properly.

Is it just me being a newb then? what is the correct protocol for quick climb and boost control on the Spit2a? I've heard folks talking about the boost, but for me there is no difference between 40%-110% throttle other than manifold pressure going through the roof as far as I can tell, no extra rpms, no extra speed etc...

Regards, Sam.

[klem]

Originally Posted by Sammi79

OK, thank you. does this not register in the damage window though? governor failure or something? I held 3000 rpm for climb, and found that after I could still fly effectively, no loss of power, rpm control etc working fine just with the screen+needles shaking it was unplayable. I don't use the boost, as the throttle in spit 2a maxes out the manifold pressure at about 40% throttle currently, and the push lever stays where it starts locking max throttle at 100%

Also, no failure in the replay - but then replays are not working properly.

Is it just me being a newb then? what is the correct protocol for quick climb and boost control on the Spit2a? I've heard folks talking about the boost, but for me there is no difference between 40%-110% throttle other than manifold pressure going through the roof as far as I can tell, no extra rpms, no extra speed etc...

Regards, Sam.

I don't use the damage window but I just had a failure of a SpitII engine, it simply failed. I was down to 5 gallons and running low rpm/boost to stretch it out. After a while it begamn to misfire under low fuel pressure, causing intermittent vibration and eventually it stopped and wouldn't restart.

I don't know if this is what heppened to you? Failed fuel pressure?

The throttle currently controls boost levels over about 0-40% ov its range which is obviously a bug. I can get boost pressures between -4 and +6 but its hard to get exactly what I want and have to settle for about +/- 1lb.

Here are the boost figures from SpitIIa pilots notes for the Merlin XII and the Hurricane Merlin III (Spitfire will be the same). You'll find these splattered all over the forums.

[GF_Mastiff]

Originally Posted by klem

I don't use the damage window but I just had a failure of a SpitII engine, it simply failed. I was down to 5 gallons and running low rpm/boost to stretch it out. After a while it begamn to misfire under low fuel pressure, causing intermittent vibration and eventually it stopped and wouldn't restart.

I don't know if this is what heppened to you? Failed fuel pressure?

The throttle currently controls boost levels over about 0-40% ov its range which is obviously a bug. I can get boost pressures between -4 and +6 but its hard to get exactly what I want and have to settle for about +/- 1lb.

Here are the boost figures from SpitIIa pilots notes for the Merlin XII and the Hurricane Merlin III (Spitfire will be the same). You'll find these splattered all over the forums.

but that's a report with 100 Octane there not using that in this version. 97oct is what I was told there using.

[von Brühl]

Originally Posted by Sammi79

OK, thank you. does this not register in the damage window though? governor failure or something? I held 3000 rpm for climb, and found that after I could still fly effectively, no loss of power, rpm control etc working fine just with the screen+needles shaking it was unplayable. I don't use the boost, as the throttle in spit 2a maxes out the manifold pressure at about 40% throttle currently, and the push lever stays where it starts locking max throttle at 100%

Also, no failure in the replay - but then replays are not working properly.

Is it just me being a newb then? what is the correct protocol for quick climb and boost control on the Spit2a? I've heard folks talking about the boost, but for me there is no difference between 40%-110% throttle other than manifold pressure going through the roof as far as I can tell, no extra rpms, no extra speed etc...

Regards, Sam.

I can confirm the same thing in the 109, I let the RPM get too high for too long, and no damage messages, but definitely ruined my engine.

[Sammi79]

Originally Posted by von Brühl

I can confirm the same thing in the 109, I let the RPM get too high for too long, and no damage messages, but definitely ruined my engine.

OK, I guess the bug is - damage occurring but not registering on the damage output window.

Regards, Sam.