Controls, GUI, texts

[Hoss]

Well, if the command is a Pulse, on/off, it will work great on incremental flaps, (109, 110, P-51) i.e. down 10%, 20%, up 10%, but if the button needs to be held down, during the travel up/down of the flaps the button needs to be a HOLD instead of a Pulse.  TMWH lets you do that for switches, buttons.  Not sure what you are using to program your HOTAS. And the hold press will still deploy your incremental flaps, you just hit once for each increment.

TARGET is so simple, I don't know why people have a hard time with it, its all right there in front of you and so intuitive to use. Believe it or not its easier than joy2key. Now SCRIPT is another matter. Your other HOLD functions are fire guns, Radiators, Cowls, Gunsight adjustments, Zooms, RPM, Mixture....

 

let us know if you figure it out or not.

 

Spoiler

 

Edited July 9, 2022 by Hoss

[-DED-Rapidus]

On 7/10/2022 at 6:21 AM, KookyBlimp said:

Brief description: Wonky  Propeller pitch controls

I tried it myself, setting the screw pitch works if I enter the manual control mode, I had no problems. Can you record a video explaining what exactly is going wrong in your opinion?

[KookyBlimp]

lets wait for sunday, will do.

asked people on server its not  100% reproducible ?

[JG4_Moltke1871]

Another thing about the Arado:

It’s about the formation lights. When I play in career mode on the ground it’s possible turn em on. Later in the air it’s impossible. I can see the button try to move but he didn’t switch. What can be the reason for this? I think switch a light on and off should be possible in any case.

[JG4_Moltke1871]

Arado without end….. ?

The handles for the chute are mixed up:

öffnen should open chute

Abwurf should drop chute 

 

In case I chose three bombs:

If I change the Bomb selection already on the ground later the booster drop will also drop my bombs☹️
 

the booster jettison should have no impact on bombs in any case 

[Thales]

Brief description: There's a typo in the labeling of the Me 410's bomb bay switch.

 

Detailed description, conditions: Currently the label next to the bomb bay switch in the Me 410 reads "Nur mit Notzug ausschahren". "Ausschahren" is not a proper word and seems to be a mix of "ausfahren" and "ausschalten". I can provide a blurry picture that appears to confirm that it should read "ausschalten" instead of "ausschahren".

 

Additional assets (videos, screenshots, logs):

 

[FTC_Davies]

Brief description:
P-51 Manual radiators - binding them is confusing and could be improved.

Detailed description, conditions:
In the keybindings, if you want to bind manual oil/water radiators for the P-51 it can be quite hard to understand how to do this since the label in the menu is not saying anything about P-51s. Rather it is specifying only German and British aircraft.
Manual P51 Water/oil radiator control binding (opening or closing them) is described as "He-111, BF-110 oil radiators: open/close one step" and "BF-109/110 and British aircraft water radiator: open/close".

Additional assets (videos, screenshots, logs):
See attached JPG

Your PC config data (OS, drivers, specific software):
Game version: 4.707c

[JG4_Deciman]

On 8/19/2022 at 12:21 PM, FS_DavviZ said:

Brief description:
P-51 Manual radiators - binding them is confusing and could be improved.

Detailed description, conditions:
In the keybindings, if you want to bind manual oil/water radiators for the P-51 it can be quite hard to understand how to do this since the label in the menu is not saying anything about P-51s. Rather it is specifying only German and British aircraft.
Manual P51 Water/oil radiator control binding (opening or closing them) is described as "He-111, BF-110 oil radiators: open/close one step" and "BF-109/110 and British aircraft water radiator: open/close".

Additional assets (videos, screenshots, logs):
See attached JPG

Your PC config data (OS, drivers, specific software):
Game version: 4.707c

 

It's not only a 'confusing' thing...

It's simply a bug if you consider other problems beeing related to this

 

There is absolutely NO way to set coolers for ANY plane using these keysetting options for a specific engine directly.

 

Simply take a Bf110

and try to set one of the following 'basic' functions by simply pressing ONE key (or use an axis)

- oil coolers engine 1 (or 2)

- water coolers engine 1 (or 2)

Even when assuming that the 'open/close only stepwise' function is realistic (and I really do not think it is)

and even when assuming that the 'lever / rotating knob' inside the cockpit of that plane strictly allowed only 5 (or 9) fixed positions

(and I also have serious doubts about that)

there must be at least a way to set these independant levers/knobs inside the cockpit directly.

 

But all we can do is

- Select the desired engine (and make sure that it is the only selected engine)

- Use the 'global' available key setting to modify ALL SELECTED engines

- Restore either a 'basic' selection of your engines or risk a mess up when pressing the next button

 

Same for other settings like 'prop feathering', that are reacting to a 'global' setting ONLY, affecting all selected engines

(and this was mentioned first at leas 8 years ago)

 

And I'm sorry to tell you, but it's the truth:

- I've spent weeks on trying to find a work around

 (even using external software to generate keypresses on axis positions)

 but there was (and is) NO way.

- I've checked reporting of those issues and reported myself

- I've not seen (or received) AND confirmation

- I've not seen ANY posting that gives me at least any hope there things will be fixed in the later future

- I know that a very old game (Cliffs of Dover) offers ALL the missing direct settings

- I know that I spent a lot of time in trying to fix any 'user made' error and to find a solution

- I know I spent a lot of money, too (owning the complete package)

- And finally I know that I'm really frustrated about being not able to use my hardware

  even if it should be supported after at least mapping axis positions to keypresses (and that is what I tried in my final attempt)

  and knowing that the 'wanted' action by 'present axis position' would be performed (virtual button pressed)

 

So please let me know what you want to do on fixing these things (or ignore me and other uses reporting parts of the issues before)

- Your decision

 

Deci

 

 

 

 

[RedeyeStorm]

It isn’t a ‘bug’ but a design decision. You may not agree with it and I would support such a change but it is working as intended.  It is probably one of many design decisions that the developers would wish that were different but they got to work what they have.

[firdimigdi]

Brief description:
The GUI option for tactical markings on planes/tanks is missing.

Detailed description, conditions:

The GUI option for tactical markings on planes/tanks seems to be missing. I tried several that support such but the UI option is not there.

Your PC config data (OS, drivers, specific software):

v5.001

 

Was looking at plane config UI before selecting mission - after selecting mission the plane config UI displays the relevant options. Perhaps these should be the same UI instead?

 

Edited September 15, 2022 by Firdimigdi
resolution

[FTC_Davies]

Brief description:
The pitch response menu acts weird and keeps settings for old profiles

Detailed description, conditions:

When deleting a old pitch profile, the settings will be overwritten on preexisting profiles (watch video)

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):
Patch 5.001

[LF_Mark_Krieger]

Brief description:
Just a little typo mistake in career description

Detailed description, conditions:
In the Dust Bowl Survivor USAAF career description, it should says acres instead of aces.

Additional assets (videos, screenshots, logs):


Your PC config data (OS, drivers, specific software):
Game version: 5.001

[No.10_Ace_Ivo]

Brief description:

Nieuport 28 official skins do not show up in the hangar screen.

Detailed description, conditions:

The official skins of the Nieuport 28 do not show up in the hangar screen, only the default one, quick mission builder. (Don't know if it happens in other game modes too).

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):

Windows 10, game version 5.001

[Deicide]

my bug with controls is when setting joystick (Saitek x56) controls from a fresh install I've ran into issues with my rudder pedals being bound as my pitch (right foot) and roll (left foot). This is after I had set my controls and with my feet off my pedals. To fix it, i had to unbind both pitch/roll and foot brakes (left/right) then go back and first bind pitch and roll to my joystick, then go to that option on the far right (with the graph) and move the stick. I had to do it twice for pitch and click invert twice, then go to roll once and invert it twice. No idea why just the way it finally worked, it wouldn't read my bindings at first, but they showed my personal bindings on screen like I had set them but it wasn't really set until i did that, then it read my bindings correctly. then go to feet brakes and put them back in. no problems on that part. just setting the actual joystick. It showed that I put my joystick at the binding but it didn't read it. Even after I left control area. I still had to go back and do it my way I mentioned. I am using a Saitek X56 stick/throttle and Logitech Rudder pedals.

Also please... PLEASE... PLEASE... can we get a clear all controls. Not for the whole thing just something that can clear all for each control area. Clear all weapon controls, clear all pilot controls, clear all pilot view controls. and so on.

I ask this because I don't always have IL-2 installed (i have teenagers who want to install their games when they are here, so i end up uninstalling my games often) and having to go back and click that little x for each individual control is mind numbing.

Edited September 28, 2022 by Deicide

[JG4_Deciman]

Bug on resetting Visor...

 

Plane Me 410

 

Adjusting 'Wind Speed' using assigned keys sets them as intended (100km/h <-> -99 km/h), even when not 100 / -100

Adjusting 'Target Height' also works as intendend

Possible from both 'stations' (pilot seat AND gunner)

 

Resetting Visor is completely different...

 

Pilot Seat:

- Target Height -> 0

- Wind Speed -> 0

 

Gunner:

- Target Height -> 5000 m

- Wind Speed -> -100

 

Tested in a quick mission, Me410, loadout 8 small bombs

 

Deci

 

gs_reset,                                         ,                                                 0| // Visier zurücksetzen

 

 

 

 

Edited October 10, 2022 by JG4_Deciman

[JTF-skypickle]

Brief description:

Elevator and Stabilizer trim controls only respond to keyboard inputs JU87

Detailed description, conditions:

The elevator/stabilizer trim are assigned to the same keyboard commands. They work fine. Assigning them to a Virpil alpha constellation joystick seems to be ok, the buttons are recognized and assigned to these actions in the key mapping section. However, in the aircraft these buttons do not work. I tested this with some buttons on the CM3 throttle as well, and the actions are not responsive even though the buttons are assignable. These controls (throttle and joystick) however work fine otherwise-plane controls, weapon controls all work.

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):

Windows 10, game version latest

[LukeFF]

7 minutes ago, sausagesskypickle said:

Brief description:

Elevator and Stabilizer trim controls only respond to keyboard inputs JU87

Detailed description, conditions:

The elevator/stabilizer trim are assigned to the same keyboard commands. They work fine. Assigning them to a Virpil alpha constellation joystick seems to be ok, the buttons are recognized and assigned to these actions in the key mapping section. However, in the aircraft these buttons do not work. I tested this with some buttons on the CM3 throttle as well, and the actions are not responsive even though the buttons are assignable. These controls (throttle and joystick) however work fine otherwise-plane controls, weapon controls all work.

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):

Windows 10, game version latest

 

You have to use the Elevator Trim Axis command with the Ju 87.

[kendo]

Brief Description: Bug with the new custom numbers/markings in QMB on some maps.

 

Detailed description: On Stalingrad summer map in QMB using the multi-plane (3 v 3 plane icon) option there is no screen option to select/deselect the custom markings (or the other aircraft setting options - cockpit photo etc) that usually appears just before flight. The option tab for this does not appear for any nationality I tested. So game seems to default to using custom markings with no option to disable.

 

Using the AQMB feature on Stalingrad summer map, the custom markings option is shown and works as expected.

 

I also tried Veliki Luki Winter map and QMB missions on it had the custom markings selection screen appear and it worked as expected.

 

So it seems that on some maps (Stalingrad summer at least) there is a bug with displaying the custom markings option and the other aircraft settings options (cockpit photo, etc)

 

Edit: Also seems to be affecting Normandy Summer map

 

Edited October 12, 2022 by kendo

[Hopper64]

Thanks for adding that Kendo.

[Yankee_One]

Brief Description: Main Menue bug with the new custom numbers/markings when selecting custom skins.

 

Detailed description: New markings can be removed before QMB begins on custom skins. Custom skins are displayed normal when new markings are removed and mission is played on Normandy map. After ending mission and closing QMB, MAIN MENUE shows new markings on aircraft.

 

See files

Edited October 12, 2022 by Yankee_One

[Regingrave-]

7 часов назад, kendo сказал:

Brief Description: Bug with the new custom numbers/markings in QMB on some maps.

 

Detailed description: On Stalingrad summer map in QMB using the multi-plane (3 v 3 plane icon) option there is no screen option to select/deselect the custom markings (or the other aircraft setting options - cockpit photo etc) that usually appears just before flight. The option tab for this does not appear for any nationality I tested. So game seems to default to using custom markings with no option to disable.

 

Using the AQMB feature on Stalingrad summer map, the custom markings option is shown and works as expected.

 

I also tried Veliki Luki Winter map and QMB missions on it had the custom markings selection screen appear and it worked as expected.

 

So it seems that on some maps (Stalingrad summer at least) there is a bug with displaying the custom markings option and the other aircraft settings options (cockpit photo, etc)

 

Edit: Also seems to be affecting Normandy Summer map

That's strange, that shouldn't depend on the map. I'll check it, thanks for the report. ?

 

55 минут назад, Yankee_One сказал:

Brief Description: Main Menue bug with the new custom numbers/markings when selecting custom skins.

Will be fixed, probably there will be an update in the next couple of days.

 

28.09.2022 в 21:56, No.10_Ace_Ivo сказал:

Brief description:

Nieuport 28 official skins do not show up in the hangar screen.

Should be fixed in 5.002.

[Hopper64]

11 hours ago, Regingrave said:

That's strange, that shouldn't depend on the map. I'll check it, thanks for the report. ?

 

Will be fixed, probably there will be an update in the next couple of days.

 

Should be fixed in 5.002.

I still have the same issue as yesterday with version 5.002b with my custom skins. No change here. Yankee_One has it illustrated well. That's my problem too. Thanks!!

Edited October 12, 2022 by Hopper64

[JTF-skypickle]

Brief description: 

Throttle not recognized if more than 8 controllers

Detailed description, conditions:

I have 11 controllers:Virpil throttle, stick, collective

                                          MFG pedals, Total Controls button box, 2 cougar mfd panels

                                          4 homemade controllers from arduinos, and a teensy

(Why so many? I enjoy flying different aircraft)

They are all properly recognized in the joystick control panel (joy.cpl) I just couldnt get a screenshot showing them all.  In DCS they all work fine and are assignable. 

The usual response is to delete the input and the updates folders and let the launcher recreate them, which I did.

If I have more than 8 controllers connected, the throttle is not recognized. If I can at least get IL2 to recognize the throttle, I wouldnt mind not having some of the other controls. I dont want to keep plugging and unplugging controllers. 

 

Additional assets (videos, screenshots, logs):

The devices.txt with the minimal amount of controllers connected is this :

 

configId,guid,model|

0,%22c0cc41d0-1710-11ec-0000545345440180%22,Total%20Controls%20MFBB|

1,%225df1f470-873f-11ec-0000545345440580%22,VPC%20Stick%20Alpha|

2,%228d02c000-67d7-11ec-0000545345440580%22,MFG%20Crosswind%20V2|

3,%2279e7fe30-873b-11ec-0000545345440480%22,VPC%20Throttle%20MT-50CM3|

4,%227a9e5c50-d49f-11ec-0000545345440480%22,Serial%2FKeyboard%2FMouse%2FJoystick|

5,%227a9eaa70-d49f-11ec-0000545345440680%22,Arduino%20Leonardo|

6,%22fe8aa030-873f-11ec-0000545345440780%22,LEFT%20VPC%20Rotor%20TCS|

 

Everything works in this config. If I plug everything else in and restart IL2 it says it found a new controller (one of the cougar panels) and asks me if I want to bring the settings from the throttle over to it. I dont know why it only found 1 new controller since i plugged in a whole bunch. Anyway in this config, the throttle does not work. and the devices.txt file has two new lines at the bottom:

 

7,%22305c72c0-359f-11ec-0000545345440180%22,F16%20MFD%202|

8,%22305c72c0-359f-11ec-0000545345440280%22,F16%20MFD%201

 

These are the cougar panels.

 

Why does IL2 ignore the throttle?

 

Your PC config data (OS, drivers, specific software):

win10 pro updated,nvidia drivers,lots of usb devices

Edited October 15, 2022 by JTF-skypickle

[moustache]

Brief description:

HUD/"game reality" difference

Detailed description, conditions:

in game, with the churchill, the HUD and the "in game" counter indicates a difference in speed ... in view of the tests, it would rather be the "in game" counter which does not work

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):

up-to-date driver, windows 10, no mod

[Hartigan]

Brief description: BF109 F-2 manual radiator

Detailed description, conditions: Radiator control were only full open when manual mode were selected .  Now it seems that radiator flaps can be controlled like later 109 models?? But controller itself doesnt move when adjusting open/close

[JG4_Deciman]

On 10/10/2022 at 3:21 PM, JG4_Deciman said:

Bug on resetting Visor...

 

Plane Me 410

 

Adjusting 'Wind Speed' using assigned keys sets them as intended (100km/h <-> -99 km/h), even when not 100 / -100

Adjusting 'Target Height' also works as intendend

Possible from both 'stations' (pilot seat AND gunner)

 

Resetting Visor is completely different...

 

Pilot Seat:

- Target Height -> 0

- Wind Speed -> 0

 

Gunner:

- Target Height -> 5000 m

- Wind Speed -> -100

 

Tested in a quick mission, Me410, loadout 8 small bombs

 

Deci

 

gs_reset,                                         ,                                                 0| // Visier zurücksetzen

 

 

 

 

 

In addition another bug on 'resetting' the visor...

 

In the 'global.actions' there are 2 different possibilities to 'reset' a visor

 

gs_reset,                                         ,                                                 0| // Visier zurücksetzen
gs_reset,                                         joy6_b52,                                         0|
tc_visor_reset,                                   ,                                                 0| // Visier zurücksetzen
tc_visor_reset,                                   joy6_b52,                                         0|

 

And it's getting even stranger now!

Using 'gs_reset' only does NOT reset the 'target altitude' in the Me 410.

Neither in Cockpit nor in Gunner

After binding 'tc_visor_reset' with the same key

the result is as reported before.

 

And the 'tc_visor_reset' is located in the 'Tank keybindings'...

 

I would recomment that the devs try to check the key binding system themselves completely

instead of waiting for further bug reports.

They know what they wanted to (or were asked to) implement.

I can only tell what looks very strange for me and makes absolutely no sense for me, too...

And I did not check all bindings. 

 

 

Deci

 

 

[-DED-Rapidus]

On 10/19/2022 at 11:24 PM, Hartigan said:

Brief description: BF109 F-2 manual radiator

Detailed description, conditions: Radiator control were only full open when manual mode were selected .  Now it seems that radiator flaps can be controlled like later 109 models?? But controller itself doesnt move when adjusting open/close

I didn't understand.  Is it possible to show the problem in the screenshots with the display of radiator control devices?

[-DED-Rapidus]

@JG4_Deciman, I will ask you to record a short video, because we are conducting visor tests, but the nuances that you refer to need to be reproduced according to the situation.

[JG4_Deciman]

7 hours ago, -DED-Rapidus said:

@JG4_Deciman, I will ask you to record a short video, because we are conducting visor tests, but the nuances that you refer to need to be reproduced according to the situation.

 

Recording a video of what I can see on my screen will make no sense right now.

But if really needed I'll try to setup a recording of both,  'screen' and 'keys pressed'

 

Here are the 'basic' facts for you to recreate what I figured out

 

Fact 1:

What I did was 'editing' the 'global.actions' manually

and simply delete the 'keyboard action' for 'tc_visor_reset' (located in the 3rd row, so it is the binding in the very right col of the settings)

I did this because I noticed that whenever I changed the setting for 'gs_reset', the 'tc_visor_reset' was given the same value (in the same row / screen column)

and whenever I had the 'global.actions' open and restarted the game

my editor told me 'file changed' and asked me to 'reload' it.

And reloading the file to compare the changes clearly showed: THAT entry was modified...

So changing key settings for ANY of these 2 values (located in Weapons AND Tanks) will change BOTH values!

 

Fact 2:

Without letting the game modify the 'global.actions' after boot (so we are talking about TANK setting is unset)

whenever pressing the key for 'gs_reset' (which would be the same key for 'tc_visor_reset' as I figured out before)

ONLY 'wind speed' values are affected

If you let the game modify (and use after restart) both commands BOTH values are affected...

So 'wind speed' and 'target height'

 

Fact 3:

Using the 'gs_reset && tc_visor_reset' (which are the same if you let the game do what it wants)

has different results basing on the 'station' from where you press these keys....

 

Pressing from the 'pilot seat'

sets both parameters to 0 (or only 'wind speed' parameter as figured out in Fact 2)

 

Pressing from the 'Gunner'

sets both parameters to strange values (wind speed -100 / height 5000) or only wind speed (as figured our in Fact 2)

 

 

 

Taken from my 'global.actions'

gs_distance,                                      ,                                                 0| // Visier Weitenregulierung / Bombenvisier: Windgeschwindigkeit
gs_distance,                                      joy6_b47/joy6_b48,                                0|
gs_distance,                                      key_rcontrol+key_numpad4/key_rcontrol+key_numpad1,0|
gs_yaw,                                           ,                                                 0| // Visier Horizontalverstellung
gs_yaw,                                           joy6_b50/joy6_b51,                                0|
gs_reset,                                         ,                                                 0| // Visier zurücksetzen
gs_reset,                                         joy6_b52,                                         0|
gs_reset,                                         key_rcontrol+key_numpad2,                         0|
bs_wind_direction_left,                           key_left,                                         0| // Bombenvisier: Windrichtung - links
bs_wind_direction_left,                           joy6_b54,                                         0|
bs_wind_direction_left,                           key_rcontrol+key_numpad7,                         0|
bs_wind_direction_right,                          key_right,                                        0| // Bombenvisier: Windrichtung - rechts
bs_wind_direction_right,                          joy6_b55,                                         0|
bs_wind_direction_right,                          key_rcontrol+key_numpad9,                         0|
tc_visor_pitch,                                   ,                                                 0| // Visier neigen / Bombenvisier: Zielhöhe
tc_visor_pitch,                                   joy6_b50/joy6_b51,                                0|
tc_visor_pitch,                                   key_rcontrol+key_numpad6/key_rcontrol+key_numpad3,0|
tc_visor_yaw,                                     ,                                                 0| // Visier schwenken / Bombenvisier: wahre Fluggeschwindigkeit des Flugzeugs
tc_visor_yaw,                                     joy6_b59/joy6_b60,                                0|
tc_visor_reset,                                   ,                                                 0| // Visier zurücksetzen
tc_visor_reset,                                   joy6_b52,                                         0|
tc_switchgun,                                     ,                                                 0| // Munition wählen
tc_switchgun,                                     joy6_b31,                                         0|

 

 

As the settings for 'buttons' are not available (you don't have that joystick present) ignore those row(s)

but the keyboard settings will do the same job.

 

BTW: The 'tc_visor_reset' as a keyboard entry is NOT set / last col in the ingame settings)

after implementing the settings to your own 'global.actions'

this setting will be implemented with the same value as 'gs_reset' (See Fact 1)

 

 

Deci

 

PS:

And if you still need further information (or a video) let me know.

But it will take a while...

 

 

[JG4_Deciman]

On 10/22/2022 at 4:15 PM, JG4_Deciman said:

 

Recording a video of what I can see on my screen will make no sense right now.

But if really needed I'll try to setup a recording of both,  'screen' and 'keys pressed'

 

Here are the 'basic' facts for you to recreate what I figured out

 

Fact 1:

What I did was 'editing' the 'global.actions' manually

and simply delete the 'keyboard action' for 'tc_visor_reset' (located in the 3rd row, so it is the binding in the very right col of the settings)

I did this because I noticed that whenever I changed the setting for 'gs_reset', the 'tc_visor_reset' was given the same value (in the same row / screen column)

and whenever I had the 'global.actions' open and restarted the game

my editor told me 'file changed' and asked me to 'reload' it.

And reloading the file to compare the changes clearly showed: THAT entry was modified...

So changing key settings for ANY of these 2 values (located in Weapons AND Tanks) will change BOTH values!

 

Fact 2:

Without letting the game modify the 'global.actions' after boot (so we are talking about TANK setting is unset)

whenever pressing the key for 'gs_reset' (which would be the same key for 'tc_visor_reset' as I figured out before)

ONLY 'wind speed' values are affected

If you let the game modify (and use after restart) both commands BOTH values are affected...

So 'wind speed' and 'target height'

 

Fact 3:

Using the 'gs_reset && tc_visor_reset' (which are the same if you let the game do what it wants)

has different results basing on the 'station' from where you press these keys....

 

Pressing from the 'pilot seat'

sets both parameters to 0 (or only 'wind speed' parameter as figured out in Fact 2)

 

Pressing from the 'Gunner'

sets both parameters to strange values (wind speed -100 / height 5000) or only wind speed (as figured our in Fact 2)

 

 

 

Taken from my 'global.actions'

gs_distance,                                      ,                                                 0| // Visier Weitenregulierung / Bombenvisier: Windgeschwindigkeit
gs_distance,                                      joy6_b47/joy6_b48,                                0|
gs_distance,                                      key_rcontrol+key_numpad4/key_rcontrol+key_numpad1,0|
gs_yaw,                                           ,                                                 0| // Visier Horizontalverstellung
gs_yaw,                                           joy6_b50/joy6_b51,                                0|
gs_reset,                                         ,                                                 0| // Visier zurücksetzen
gs_reset,                                         joy6_b52,                                         0|
gs_reset,                                         key_rcontrol+key_numpad2,                         0|
bs_wind_direction_left,                           key_left,                                         0| // Bombenvisier: Windrichtung - links
bs_wind_direction_left,                           joy6_b54,                                         0|
bs_wind_direction_left,                           key_rcontrol+key_numpad7,                         0|
bs_wind_direction_right,                          key_right,                                        0| // Bombenvisier: Windrichtung - rechts
bs_wind_direction_right,                          joy6_b55,                                         0|
bs_wind_direction_right,                          key_rcontrol+key_numpad9,                         0|
tc_visor_pitch,                                   ,                                                 0| // Visier neigen / Bombenvisier: Zielhöhe
tc_visor_pitch,                                   joy6_b50/joy6_b51,                                0|
tc_visor_pitch,                                   key_rcontrol+key_numpad6/key_rcontrol+key_numpad3,0|
tc_visor_yaw,                                     ,                                                 0| // Visier schwenken / Bombenvisier: wahre Fluggeschwindigkeit des Flugzeugs
tc_visor_yaw,                                     joy6_b59/joy6_b60,                                0|
tc_visor_reset,                                   ,                                                 0| // Visier zurücksetzen
tc_visor_reset,                                   joy6_b52,                                         0|
tc_switchgun,                                     ,                                                 0| // Munition wählen
tc_switchgun,                                     joy6_b31,                                         0|

 

 

As the settings for 'buttons' are not available (you don't have that joystick present) ignore those row(s)

but the keyboard settings will do the same job.

 

BTW: The 'tc_visor_reset' as a keyboard entry is NOT set / last col in the ingame settings)

after implementing the settings to your own 'global.actions'

this setting will be implemented with the same value as 'gs_reset' (See Fact 1)

 

 

Deci

 

PS:

And if you still need further information (or a video) let me know.

But it will take a while...

 

 

 

 

And just a simple quess (ignoring the more complex situation when having BOTH or ONLY 1 'resetting button' activated)

 

For me it really looks like the wrong 'default' values are used on 'reset' for the 'gunner' station...

Wind Speed: -100 <-> 100

Target Height: 0 <-> 10.000 (just a guess)

 

Resetting should set 'wind speed' value to 'center'

and 'target height' to 'lowest value'

 

From the pilot seat that works (ignoring the discrepancies between -100/100 and -99/100

From the gunner it looks like:

Resetting sets 'Target Altitude' to the 'center' value (5000m)

and Wind Speed to the 'lowest value' (-99)

 

So they are simply toggled exactly the opposite way...

 

Deci

 

[Hartigan]

On 10/22/2022 at 7:44 AM, -DED-Rapidus said:

I didn't understand.  Is it possible to show the problem in the screenshots with the display of radiator control devices?

 

Sorry, it was written hastily and quickly. In the F-2 model, the radiator switch should only work in two ways. Automatic or manual fully open. So fine adjustment cannot be done with the switch. In newer BF109 models, this same switch can be used to open the radiator flaps as much as desired. Automatic/manual + open / close. The problem is that due to a bug, the F-2 model now works like the newer models, but the switch animation cannot be seen.

 

[Skoop]

Can't get curves for different aircraft to save to the profile for each different aircraft.  The game really only has a global curve right now.  Even though you can set different curves, none of them save to the specific aircraft.  It's sad really, as setting curves for different aircraft is the most important point in this whole control profile feature.  The more I explore this, the more I'm seeing this as really a poor execution feature by the devs and still needs alot of work.

 

Also, do they even read this section of the forum ?  

Edited October 30, 2022 by Skoop

[JG4_Moltke1871]

I hope it’s the right place here…

For all WW1 Bombsights: 

If I chose salvo „All” in the bombsight use my keybind or button for release only single drop is possible.

 It should be possible release all Bombs with button/keybinds instead the release button in the bombsight, like in the WW2 bombsights. 

[Leftenant_Soap]

Dear 1CGS,

 

A small issue with controls - key binding.

The tank control for "Fuel meter: tank selector" is always bound to the same key for plane controls "Flaps up", no matter which key is assigned.

Similarly for tank controls, "Fuel meter: pump pressure (KV-1, Pz.III) / Fuel meter: init indication (Churchill)" is always bound to plane controls "Flaps down".

 

Meh, there are a few dozen more just like this. Easier to just take Moltke's advice and use a second profile for tanks.

Edited November 21, 2022 by DD_Soapy

[JG4_Moltke1871]

19 minutes ago, DD_Soapy said:

Dear 1CGS,

 

A small issue with controls - key binding.

The tank control for "Fuel meter: tank selector" is always bound to the same key for plane controls "Flaps up", no matter which key is assigned.

Similarly for tank controls, "Fuel meter: pump pressure (KV-1, Pz.III) / Fuel meter: init indication (Churchill)" is always bound to plane controls "Flaps down".

Can this problem solved with create different profiles?

[Leftenant_Soap]

@JG4_Moltke1871

 

The problem may be circumvented with different profiles. However, the key binding behavior does not change.

[moustache]

Brief description:

HUD bug + head sway

Detailed description, conditions:

1)sometimes, the hud bug from the start of the game: indicates an infinite reload, no ammunition count... but it is possible to shoot, reload... etc... seems quite random: sometimes at the beginning, sometimes it solves alone, sometimes in the middle of the game..

2)when we center the head of the tank commander, regularly, during "sudden" movement, we see the model of the tank commander's head appear

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):

no mods, driver ok

[GenMarkof007]

Brief description:  

GUI (compass) disappear and key controls stop responding in IL2 MP online?
 

Detailed description, conditions:  

While playing Multi Player online and switching between tanks and planes in the same mission (on Finnish server). I sometimes loose my GUI and also, some of the keys don't work... so I need to do a CTRL + ALT + DEL to bring the keys to work. For the GUI, I try using the (H) and (I) keys... and nothing happens? Today, I didn't get the GUI to show, but the right text on screen did show after a few minutes of flying when reducing rads, or any other engine controls. It's seems to be repetitive when I switch between tanks and planes.

I've got the latest Steam version of the game.
And I do at least once a week a verification of the files integrity.

Your PC config data (OS, drivers, specific software):

Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz

Memory 32 GB DDR4 RAM

Motherboard ASUSTeK Computer - ROG STRIX Z370-E Gaming
Video Card NVIDIA Geforce GTX 1080 Ti
Hard Disk Samsung SSD 850 EVO 500GB x 2 and more SDD drives

Keyboard Corsair Short Keyboard

Microsoft Windows 10 Pro (64 bit)
 

Hope you can help about this... it started to happen with the last 2 big updates!
Thanks

[JG4_Moltke1871]

Keybinds for P51B cooling shutters water/oil for a separate profile:

 I tried to change the keybinds for these shutters in „hand“ mode to some buttons on my equipment. The new binds not work. It was also impossible re-enter the old ones.

The only way to solve this problem was to reinstall my saved settings.

Edited February 4, 2023 by JG4_Moltke1871

[Grey-Knight]

Brief description: 

Flying Circus factions do not have identifying colors for in-flight tags.
Detailed description, conditions:

When flying in a Central Powers or Entente plane while the interface color is set to "Red USSR" for friendlies and enemies, aircraft only get a grey name label.
Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software):

Game version 5.101