BETA PATCH v1.06.17582--Bug thread

[snpshot]

I applied the patch and tried to start the game, ctd every time. The little gunsight comes on my screen but it doesn't go any further. I am not sure what the path is to the crash log file, but I did turn them on in my config.

[von Brühl]

Is anyone else getting text overlaying text in the FMB? Like when you go to Object Browser, the text overwrites itself, making it hard to read?

[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.

[klem]

Originally Posted by GF_Mastiff

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

Its 87 Octane we're using and the SpitIIa figures have the 87 octane boost numbers in brackets. At the time it would have been possible to have either 87 or 100 octane although 100 octane was the fuel used during the BoB. We should get that eventually otherwise its not 'The BoB' but don't restart that discusion here, its been done to death in other threads and its in the Bugtracker now.

[Insuber]

Originally Posted by snpshot

I applied the patch and tried to start the game, ctd every time. The little gunsight comes on my screen but it doesn't go any further. I am not sure what the path is to the crash log file, but I did turn them on in my config.

Hi - did you extract files with WinRar or 7zip? If you use Winzip straight it won't extract all the files.

[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.

[TarJak]

Originally Posted by 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.

You might want to check your conf.ini. In the [Window] section there is a value that needs to read Render=D3D10_0 if it does not the patch will not work and it means you are using DirectX9 NOT DirectX10. The patch is only compatible with Dx10. I had the same problem as you and this fixed it. It caused another problem but at least I can play single player now without crashes.

[Highwayman-Ed]

I have a general decrease in performance with many more stutters than before the patch.

No Anti Aliasing
No clouds
Grass in Hangers
Mirror only displayed a frame in the air but when I land, it works.
Saitek Pedals brake axis was recognized in the setup menu, but didn't work in game (Saitek driver 6.2.2.0)

In the Spitfire on the first familiarization campaing mission in it, the compass heading is 170 degrees out and the artificial horizon was all over the place.

Intel i7 3930K
16GB Quad channel RAM
Gigabyte 7970 Windforce Edition - Catalyst 12.4

[Kwiatek]

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.

I got similar problem with engine broken at + 9lbs in SPit II even during short time of using - 1-2 minutes. I think temperatures was ok - radiator open. I was
surprised by what happened initialy thinking i got hit in engine but it was just engine broken - probably after some dive.

[FS~Phat]

Ive seen messages that the exhaust manifold has failed when running at max boost for too long. I guess thats what they've modelled which the temp gauges dont pick up!