1.35 CONV Box in Keymapper bugged

[bogol]

First all CONV values are defaulted to zero, independent of 1.34 preferences.

Second: It does NOT save the values one inputs. It actually reads all of them as ZERO. This can be seen from the message that confirms that the change will take effect at respawn. Below it it also mention that the value will be 0m, independent of the value typed in CONV box.

The only way to set CONV now is using the .conv command as before

EDIT: I am on MAC OS. CH47124 has the same problem on Win7

Edited May 20, 2016 by bogol

[sascha]

First all CONV values are defaulted to zero, independent of 1.34 preferences.

Second: It does NOT save the values one inputs. It actually reads all of them as ZERO. This can be seen from the message that confirms that the change will take effect at respawn. Below it it also mention that the value will be 0m, independent of the value typed in CONV box.

The only way to set CONV now is using the .conv command as before

EDIT: I am on MAC OS. CH47124 has the same problem on Win7

I didn't check my conv after the 1.35 switch (silly me) but I'll sure as hell do it now.

This could actually be related to the Stug's/88's new range-setting behavior (only moves in increments of 100m now) and the "coarser" settings for trim and flaps. For some reason these two now produce more % of deflection-change per keypress.

EDIT: Could you actually confirm that the convergence settings work in-game? Like using ridiculously high convergence to see if your shells/bullets fall differently?

S.

Edited May 20, 2016 by sascha

[sascha]

Tried it now on my PC ... conv-settings were all reset to 190 for me. The setting-thing in the keymapper does not accept new values - changed it, clicked on "save changes" exited mapper, re-entered and it was back to 190.

.conv still does work in game however. Spawned a 109 with 100 and then with 800 convergence and the shells did behave like expected. Changing it with .conv also works and the game seems to "remember" your settings.

S.

[t0minator]

I can confirm this, the convergence box in the keymapper does not work

[sajuk]

Same here, it is impossible to play this game in air with convergence zero.

And in 50% off all my mission i join the gamechat wrote to me

"Invalid Building Message"

CRS what can i do?

Ok i have full delete the game and install this again.

Problem is not away.

Edited May 29, 2016 by sajuk

[bogol]

Same here, it is impossible to play this game in air with convergence zero.

And in 50% off all my mission i join the gamechat wrote to me

"Invalid Building Message"

CRS what can i do?

Ok i have full delete the game and install this again.

Problem is not away.

If you do .conv VALUE, where value is whatever you want your convergence to be, while spawned in, does that not store the VALUE in your settings? For me it does. This is actually how convergence used to be set, back in the day, before the box.

[waver25]

If you do .conv VALUE, where value is whatever you want your convergence to be, while spawned in, does that not store the VALUE in your settings? For me it does. This is actually how convergence used to be set, back in the day, before the box.

The above method will work to set your convergence via the chat.

Setting the convergence in keymapp itself is in fact bugged.

[sajuk]

If i change convergence ingame over keymapper the chat say with next join the chance is rdy.

But if i quit and join back the convergence is again 0.

If i change convergence from Main menu the same ****.

Game is unplayable for me.

[bogol]

The above method will work to set your convergence via the chat.

Setting the convergence in keymapp itself is in fact bugged.

LMAO. who reported that bug?

[bogol]

If i change convergence ingame over keymapper the chat say with next join the chance is rdy.

But if i quit and join back the convergence is again 0.

If i change convergence from Main menu the same ****.

Game is unplayable for me.

While spawned in a plane type in chat bar .conv 200 This should save and store convergence for the unit you were spawned in to 200m. IF you want another value replace 200 with whatever your preferred convergence is.

[sajuk]

I know but it helps not.

If i make this i can read this message in chat.

"New convergence will take efffect next time you spwan this vehicel"

But if i rejoin convergence is really 100% at zero.

[sascha]

I know but it helps not.

If i make this i can read this message in chat.

"New convergence will take efffect next time you spwan this vehicel"

But if i rejoin convergence is really 100% at zero.

Weird.

The method Bogol described is what I use, and it works - I never, ever went through the keymapper's convergence-screen.

Doubled checked the F-2 last night which I had set to 250 or so a few days ago and that value was still "stored".

Plus: 0 convergence shouldn't even be possible in-game. I *think* 100m is the minimum, no matter what you try to set? I mean... zero would mean that your bullets converge as they leave your guns' muzzles - which doesn't really work, does it?

S.

[sajuk]

@ Sascha

Da du ja auch deutsch kannst, erspare ich mir das lästige übersetzen.

Ich weiß genau wie man die Konvergenz verstellt, ebenfalls auch was es damit auf sich hat und wie sie sich anschließend auch genau dazu verändern sollte nach dem jeweiligen Umstellen.

In der der letzten Map habe ich u.a. mehre Stunden für mich an der besten Konvergenz für die Stuka gefeilt. Womit ich dann letztendlich auch auf Deutscher Seite die beste K/D Rate erringen konnte und mit einem Orden belohnt wurde. Was ich damit sagen will, es liegt 100% nicht daran dass ich da was falsch mache.

Im Chat steht ja auch, dass die Änderung beim nächsten Neustart übernommen wird. Aber Sie bleibt wie ich es schon mehrfach geschrieben habe "immer" exakt gleich.

Egal was ich nun einstelle, die Explosionen z.b bei der BF-109 E4 und der 2 x 20 mm Cannonen sind bei mir nicht zentral am ende gebündelt, sondern "IMMER" ganz am Bildschirmrand links und recht deutlich zu erkennen.

Der Streuradius liegt somit bei ca über 100 Meter von den Einschlägen von ganz links bis rechts gesehen.

Es sieht bei mir so aus, als ob die Waffen sich bereits nach 1cm vor dem Flugzeug kreuzen und dann immer weiter schräg nach links und nach rechts fliegen und am Ende ca 100m oder evtl. auch 200m weit auseinander liegen.

Kurz gesagt es ist unmöglich so zu spielen.

[sascha]

Let's stick to English, sajuk... not everyone sprechen ze deutsch around here..

I don't doubt that what you describe is happening for you. Just saying that it doesn't seem to be an issue for me. Maybe it's a "selective bug"? Would help to know where the conv-settings are stored. Locally or on the server? If they're stored on the server, that might help to explain why some people have issues with this while others don't have issues.

Hmm.. just started up in offline mode and the E-4 had my (non-standard) convergence in there for me. So that would point to the setting being stored locally.

I just went online and double-checked everything:

meIA1MkM-CU

uploading now.. might take a while until it's available in 1080.

As you can see, convergence is stored for me and it does make a difference in the cockpit. Note how the shells fly way out there and detonate inside my gunsight in my first test-firing with 800m convergence and how they cross over real close and detonate left and right of the sight when I'm using minimum convergence (100m)

S.

Edited May 30, 2016 by sascha

[OLDZEKE]

Let's stick to English, sajuk... not everyone sprechen ze deutsch around here..

I don't doubt that what you describe is happening for you. Just saying that it doesn't seem to be an issue for me. Maybe it's a "selective bug"? Would help to know where the conv-settings are stored. Locally or on the server? If they're stored on the server, that might help to explain why some people have issues with this while others don't have issues.

Hmm.. just started up in offline mode and the E-4 had my (non-standard) convergence in there for me. So that would point to the setting being stored locally.

I just went online and double-checked everything:

meIA1MkM-CU

uploading now.. might take a while until it's available in 1080.

As you can see, convergence is stored for me and it does make a difference in the cockpit. Note how the shells fly way out there and detonate inside my gunsight in my first test-firing with 800m convergence and how they cross over real close and detonate left and right of the sight when I'm using minimum convergence (100m)

S.

Conv settings are saved to documents/battleground Europe/wwiiol.xml

This needs to be a read and write document. It may be possible that Sajuk's is set to read only. If that is the case then no preference changes would hold from 1 login to the next.

[sascha]

It may be possible that Sajuk's is set to read only. If that is the case then no preference changes would hold from 1 login to the next.

Aaahh! Why didn't I think of that?

Might also be a good idea to double-check that the folder where the file is stored isn't set to "write-/read-protect" either. Windows will sometimes do that crap to folders and files for no apparent reason.

S.