v1.05.15950 PATCH BUG THREAD

[Troll2k]

GRAthos check your config.ini.You have to set log file on from 0 to 1.

[CWMV]

Just had a runtime error, and consequential crash to desktop?
First time for that...

[mungee]

Originally Posted by CWMV

Just had a runtime error, and consequential crash to desktop?
First time for that...

Me too ... and for the first time!! Obviously something "new" with the new patch.

It happend to me when I "escape" from the "Black Death" track after checking frame rates.

Each time I need to reboot machine & reload CoD.

[zwiebacksaege]

thanks you for the patch.

good:
- overall performance seems to be better now and VSYNC is working (at least with new NVIDIA drivers)... thats really nice because now I can hear the engine instead of my graphic card

- the additional damage sounds

- prop pitch in E4 seems to work for me.. not that slow and automatic mode is near to manual performance.

not that good:

- I get frequent CTD.. every 40 min approx. I had none before.

- can confirm ghost dots in online gaming.

- entering cockpit too fast after refly will result in outside engine sounds inside cockpit.

- still the insane AI

- weired force feedback.. effects are always present but the centering force appears and disappears without any understandable rule

- damage model especially for mid air collisions seems very inaccurate for me. at least it feels very unrealistic to me.

[335th_GRAthos]

Originally Posted by Troll2k

GRAthos check your config.ini.You have to set log file on from 0 to 1.

Thanks, I will try, I hope this will solve the problem!

[1.JaVA_Sharp]

no launcher exe crashes yet and I do love the new sounds, BUUUUTTTTT

now there's this

[Trooper117]

Check your conf ini, make sure your anti epilepsy filter is set to '0'..
Some people are finding that it had gone to '1' and was giving them similar problems.

[Jaws2002]

Originally Posted by 1.JaVA_Sharp

no launcher exe crashes yet and I do love the new sounds, BUUUUTTTTT

now there's this

I had this isue too. Looks like changing this line, in conf.ini, from 0 to 1 did the trick for me:

Render=D3D10_0

[klem]

Originally Posted by Jaws2002

I had this isue too. Looks like changing this line, in conf.ini, from 0 to 1 did the trick for me:

Render=D3D10_0

A friend of mine has his problem too.

Did you mean
Render=D3D10_1 ??

[Jaws2002]

Originally Posted by klem

A friend of mine has his problem too.

Did you mean
Render=D3D10_1 ??

I mean, that line had the value 0 and I changed it to 1 to fix the bug.

So yes, if he has dx10 or dx11 card, this should be the correct look:

Render=D3D10_1