Controls, GUI, texts

[Cevert]

My guns dont work on this new patch. I cant shoot

[BlitzPig_EL]

Re map your fire buttons.

 

Lots of us have had to do it.

[-DED-Rapidus]

@Raptorattacker, new functions have been added, so the control keys have been updated. We apologize for the inconvenience caused.

[DD_Friar]

Report: - Driver position HUD flashes up when in Commanders position

Evidence: Attached video.

Tank: Panzer III

Scenario: Multiplayer Dogfight Map

 

My HOTAS equipment was not connected when getting this clip (I was testing a mission I am putting together)

 

Edited August 13, 2021 by DD_Friar

[DD_Friar]

Update:

 

Same tank, different mission, different map, did not get the error.

 

I have asked my squad mates to check to see if they can replicate the error, so I guess for the time being its "as you were and crack on delivering more great stuff..."

 

EDIT: This has now been reported by two of my squad mates so I think is a "thing"...

Edited August 13, 2021 by DD_Friar

[DD_Perfesser]

I too noticed that flashing in and out, almost certainly in a Pz IV. I think I was on the Finnish server at the time.

Edited August 13, 2021 by DD_Perfesser

[=IRFC=Gascan]

Brief description: Bristol altimeter does not indicate correctly
Detailed description, conditions: Flying the Bristol F3 in multiplayer, it was noted that the altimeter was indicating lower than actual by comparing to SPAD and later DH-4 when flying together.
Additional assets (videos, screenshots, logs): The following screenshots were taken in a quick battle at 4km altitude. One is with the Bristol F2, the other is the Bristol F3. Notice that the gage indicates a much lower altitude than the GUI.

[LukeFF]

22 hours ago, gascan said:

Brief description: Bristol altimeter does not indicate correctly
Detailed description, conditions: Flying the Bristol F3 in multiplayer, it was noted that the altimeter was indicating lower than actual by comparing to SPAD and later DH-4 when flying together.
Additional assets (videos, screenshots, logs): The following screenshots were taken in a quick battle at 4km altitude. One is with the Bristol F2, the other is the Bristol F3. Notice that the gage indicates a much lower altitude than the GUI.

 

 

Edited August 17, 2021 by LukeFF

[slawson612]

The 4.603 update removed several key mappings for me and oddly it is preventing me from resetting them to their original state. For example the "Pause" mode the game enters as a single player quick mission initiates said press "P" to start the game and it has always been so since I have been playing. The "P" key did not but instead I found RCtrl  + P started the game. When I went into Kep Mapping to reset this I could not just select P,  the key was dead, however Alt + P or Shift + P worked and mapped as expected. This also happened to my Map, (M) key as well. 

[=IRFC=Gascan]

Just to add more detail to my earlier report on the Bristol altimeter, I did some more testing in quick battles. I tried adjusting the altimeter setting using L-alt A, which swaps between standard atmosphere and nearest friendly airfield. I can clearly see the altimeter get adjusted, both on the Bristol and on other FC planes. I also tried the R-shift K and R-ctrl K (contact altimeter target altitude), but didn't see any change. I have no idea what that is, so I don't know what effect (if any) it would have. I tried planes on Moscow winter, Kuban summer, and Arras spring. I tried every single FC plane spawning at 4km altitude. Except for the Bristol, every plane showed 3.9km (12,800ft) while the simple gage indicated 4km (13,126ft). That's close enough that it doesn't significantly affect gameplay. The Bristol, and only the Bristol, showed a significant deviation from this. 4km (13,126ft) gave an indication between 8,000ft and 9,000ft, depending on the map and whether the gage was set for standard atmosphere or nearest friendly airfield. I followed this up by spawning a Bristol then an SE5a on the Arras map at 4km and descending to a landing at Mont St. Eloi (a common airfield for operations on the FlugPark server). The SE5a stayed fairly closely matched to the simple gage the whole descent, while the Bristol grew much closer to the simple gage reading. This means that the higher a player climbs in a Bristol, the larger the difference is.

 

 

[No.23_Gaylion]

Brief description: In P38 Lightning while no engines are selected, pressing the key bind to start engine 1 or start engine 2 starts that particular engine. This should not happen as the engines were unselected.  Pressing "E" does not start the engines when no engines are selected-this is good.
Additional assets (videos, screenshots, logs): None
Your PC config data (OS, drivers, specific software): N/A

[-DED-Rapidus]

3 hours ago, US213_Talbot said:

n P38 Lightning while no engines are selected, pressing the key bind to start engine 1 or start engine 2 starts that particular engine. This should not happen as the engines were unselected.  Pressing "E" does not start the engines when no engines are selected-this is good.

Sorry, but after all, the buttons on the specific motors are for that))) to specifically control the motor to which the button is assigned(sorry for the expression)

[No.23_Gaylion]

4 hours ago, -DED-Rapidus said:

Sorry, but after all, the buttons on the specific motors are for that))) to specifically control the motor to which the button is assigned(sorry for the expression)

No problem! Thought it might have just been an error.

[SShrike]

Flying the La-5 FN tonight. the pilot personal weapon will not fire but uses up ammo. When intercepting Ju-88, fired aircraft guns. Can hear guns firing but no tracers and absolutely zero bullets. I was very close and lined up but when I pull trigger there is the gun sounds but no tracers and no hits from my guns!  

Edited August 20, 2021 by SShrike

[MajorMagee]

On 8/13/2021 at 7:35 AM, DD_Friar said:

Report: - Driver position HUD flashes up when in Commanders position

Evidence: Attached video.

Tank: Panzer III

Scenario: Multiplayer Dogfight Map

 

My HOTAS equipment was not connected when getting this clip (I was testing a mission I am putting together)

 

I've recently seen this happen in the game generated Quick Missions. I suspect it's related to my HOTAS send driving commands (speed / direction changes) when I'm in the commander's position so it briefly throws up the driver's menu.

[MOtt]

Brief Description:

Since the last hotfix (or maybe previous patch) the hs129 weapons groups are different.

firing weapon group 1 = fires the mg17 and mk101 (or mk103)

firing weapon group 2 = fires the mg151/15

 

Before weapon group 1 fired the mg17 and mg151/15, while weapon group 2 fired the mk101

Tried un-mapping and re-mapping the weapons groups and ensuring the buttons I use joy0 and joy1 were only mapped to firing the weapon groups but get the same outcome.

[LukeFF]

1 minute ago, MOtt said:

Brief Description:

Since the last hotfix (or maybe previous patch) the hs129 weapons groups are different.

firing weapon group 1 = fires the mg17 and mk101 (or mk103)

firing weapon group 2 = fires the mg151/15

 

Before weapon group 1 fired the mg17 and mg151/15, while weapon group 2 fired the mk101

Tried un-mapping and re-mapping the weapons groups and ensuring the buttons I use joy0 and joy1 were only mapped to firing the weapon groups but get the same outcome.

 

Sorry, but you are mistaken - the MG 17 and MK 101/103 have always been assigned to Group 1 and the MG 151s on Group 2. 

[MOtt]

Well, I'll take your word for it as I have not played it in a while. Does not make logical sense to me to waste cannon rounds when shooting some truck with the mg17, so maybe fooling myself into believing the opposite.

[-DED-Rapidus]

On 8/20/2021 at 9:31 PM, MajorMagee said:

I've recently seen this happen in the game generated Quick Missions. I suspect it's related to my HOTAS send driving commands (speed / direction changes) when I'm in the commander's position so it briefly throws up the driver's menu.

Yes, we found and reproduced this one, it shouldn't be like this, thank you.

[Q_Walker]

Brief description: Small typo in the Battle of Stalingrad Career with a message for air operations being suspended.
Detailed description, conditions: I am currently flying a Battle of Stalingrad Career with the 3rd GIAP. On 31.12.1942 two missions were flown by the squadron and I proceeded to the next day. I then got the message that air operations were suspended from 13.12.1942 to 01.01.1943, when the message should have read 31.12.1942.
Additional assets (videos, screenshots, logs): 
Your PC config data (OS, drivers, specific software): Window 10, Nvidia Drivers Up to date, i7-10700K CPU, RTX 2060 Super, 32 GB Ram.

[Ghostbasedk]

hello i am asking because i aligned my trim and stabillizer to the same button but when i press it nothing happen can somebody help me?

 

[cardboard_killer]

10 hours ago, Ghostbasedk said:

hello i am asking because i aligned my trim and stabillizer to the same button but when i press it nothing happen can somebody help me?

 

 

Okay, a couple of basic questions first. Sorry if this seems pedantic, but let's start with the basics and go from there:

 

1. What realism settings are you using?
2. What plane are you flying?

The trimming of a plane with elevator trim tabs is controlled by the Elevator trim axis control; the trimming of a plane with elevator stabilizer is controlled by the either the Adjustable stabilizer axis or the pair Adjustable stabilizer switch: pitch up/down (see circled controllers).

 

Since each plane willhave only one set of controls, you can assign the same controller to them as they will never conflict on one plane. So, my key map has joy1_b11 and joy1_b10 for all the elevator/stabilizer controls.

 

I'd guess you already know that based on your question, but I just want to be sure.

[LLv34_Flanker]

Report: Oil and coolant radiator controls

 

Symptoms: On Bf109E-7 neither of these controls work when mapped to throttle or joystick. They work from default keyboard commands. Every other control work as intended. On 110E-2 they do work as an example. I did re-map the controls to different buttons but they still failed to work on the 109E-7.

[LukeFF]

1 hour ago, LLv34_Flanker said:

Report: Oil and coolant radiator controls

 

Symptoms: On Bf109E-7 neither of these controls work when mapped to throttle or joystick. They work from default keyboard commands. Every other control work as intended. On 110E-2 they do work as an example. I did re-map the controls to different buttons but they still failed to work on the 109E-7.

 

The E-7 uses the same radiator controls as the Soviet planes. 

[Ghostbasedk]

On 8/27/2021 at 1:32 AM, cardboard_killer said:

 

Okay, a couple of basic questions first. Sorry if this seems pedantic, but let's start with the basics and go from there:

 

1. What realism settings are you using?
2. What plane are you flying?

The trimming of a plane with elevator trim tabs is controlled by the Elevator trim axis control; the trimming of a plane with elevator stabilizer is controlled by the either the Adjustable stabilizer axis or the pair Adjustable stabilizer switch: pitch up/down (see circled controllers).

 

Since each plane willhave only one set of controls, you can assign the same controller to them as they will never conflict on one plane. So, my key map has joy1_b11 and joy1_b10 for all the elevator/stabilizer controls.

 

I'd guess you already know that based on your question, but I just want to be sure.

im using normal realism and im flying the bf 109 f-4 and i did assign elevator trim axis and adjustable stabillizer axis to Rsht cursor up and down it the complete same yet when i try to adjust it it dosent work and im having a really hard time taking of because of that hope you can help.

[cardboard_killer]

2 hours ago, Ghostbasedk said:

im using normal realism and im flying the bf 109 f-4 and i did assign elevator trim axis and adjustable stabillizer axis to Rsht cursor up and down it the complete same yet when i try to adjust it it dosent work and im having a really hard time taking of because of that hope you can help.

 

The RShift+cursor up/down is the default for the game. Again, I'm sorry if this seems stupid, but to be sure, these are the buttons you're pressing:

 

If so, and if you are sure the keyboard is working correctly, do this:

 

1. Go to the C:\Program Files (x86)\Steam\steamapps\common\IL-2 Sturmovik Battle of Stalingrad\data\input folder (the input folder) and rename these three files
   1. current.actions to current.actions.old
   2. current.map to current.map.old
   3. devices.txt to devices.txt.old
2. Start IL-2
3. Start a quick mission with the Bf-109F4 parked. Use the normal realism.
4. Unpause the game, and try the Rshift+cursor up/down to see if the stabilizer moves.
5. If it does move, you are good to go, but you will have to remap your joystick/rudder/throttle controls.
6. If it does not move, go back to the input folder and delete the three files
   1. current.action
   2. current.map
   3. devices.txt
7. Then rename the
   1. current.action.old to current.action
   2. current.map.old to current.map
   3. devices.txt.old to devices.txt

If the stabilizer did not move, then I'm not sure what the problem is. It may be the steam generic controller setting is on, so turn that off. Also, use the Steam verify integrity command in you steam account (in fact, try this first).

 

I do not fly the Bf109F-4 much, but I thought it strange that you are using the stabilizer to take off. My go to for take off and landing is Requim on youtube. He does not indicate that the stabilizer is used in take off.

 

 

[AKSMOKEY]

Hello there

 

Every time I zoom in, I have to hit the reset view key to go back to my saved view, otherwise I stay zoomed in, if I zoom out, it will zoom out but the moment I let go, the view will go back zoomed in, and I have to hit the reset view key to go back to the view I saved using f10. Very frustrating in dog fighting especially when your at a disadvantage of being useless at them in the first place lol.

 

 

 

Im new to flight sims but love il2 and purchased track IR and everything was working a dream until this zooming issue

 

 

Anyhelp would be greatly appreciated 

 

 

 

Kind regards 

 

 

 

S

 

 

 

Oh specs

 

 

 

Not great but using a T16000m hotas

 

 

I7 10700k Strix z490f

2080ti 11gb

32gb

Installed on SSD

[Ghostbasedk]

On 9/1/2021 at 12:36 AM, cardboard_killer said:

 

The RShift+cursor up/down is the default for the game. Again, I'm sorry if this seems stupid, but to be sure, these are the buttons you're pressing:

 

If so, and if you are sure the keyboard is working correctly, do this:

 

1. Go to the C:\Program Files (x86)\Steam\steamapps\common\IL-2 Sturmovik Battle of Stalingrad\data\input folder (the input folder) and rename these three files
   1. current.actions to current.actions.old
   2. current.map to current.map.old
   3. devices.txt to devices.txt.old
2. Start IL-2
3. Start a quick mission with the Bf-109F4 parked. Use the normal realism.
4. Unpause the game, and try the Rshift+cursor up/down to see if the stabilizer moves.
5. If it does move, you are good to go, but you will have to remap your joystick/rudder/throttle controls.
6. If it does not move, go back to the input folder and delete the three files
   1. current.action
   2. current.map
   3. devices.txt
7. Then rename the
   1. current.action.old to current.action
   2. current.map.old to current.map
   3. devices.txt.old to devices.txt

If the stabilizer did not move, then I'm not sure what the problem is. It may be the steam generic controller setting is on, so turn that off. Also, use the Steam verify integrity command in you steam account (in fact, try this first).

 

I do not fly the Bf109F-4 much, but I thought it strange that you are using the stabilizer to take off. My go to for take off and landing is Requim on youtube. He does not indicate that the stabilizer is used in take off.

 

 

thanks i shall try that but the thing is you need it for take off otherwise it will just lean to the left and crash you when you take off

 

[cardboard_killer]

2 hours ago, Ghostbasedk said:

thanks i shall try that but the thing is you need it for take off otherwise it will just lean to the left and crash you when you take off

 

 

the only trim the Bf-109 has is pitch trim via the elevator stabilizers. Pitch trim affects nose pitch up/down. I'm not sure what you mean by "lean to the left"--an a/c has three axes: pitch (up/down), yaw (left/right), and roll (rotate left/right). The Bf-109 does not have the ability to trim yaw or roll, only pitch.

On 9/5/2021 at 6:13 PM, AKSMOKEY said:

Every time I zoom in, I have to hit the reset view key to go back to my saved view, otherwise I stay zoomed in, if I zoom out, it will zoom out but the moment I let go, the view will go back zoomed in, and I have to hit the reset view key to go back to the view I saved using f10.

 

I will look for a solution in the next couple of hours and get back to you. It might be better if you start a new thread in the Hardware folder

 

Edit: See if this video helps. If not, let us know.

 

 

Edited September 9, 2021 by cardboard_killer

[cardboard_killer]

On 9/9/2021 at 12:53 PM, Ghostbasedk said:

thanks i shall try that but the thing is you need it for take off otherwise it will just lean to the left and crash you when you take off

 

Any luck with this?

[jokerBR]

Brief description: Possible bug involving TrackIR and mouse turret control
Detailed description, conditions: Mouse ceases to control turret (tank or AA truck) if TrackIR isn't loaded. If you start the game without firing up TrackIR, when activating the turret (T) and then entering the nest gunsight position (LSHF+T), mouse enters the "free cam" mode, and doesn't move the gun. If you have TrackIR loaded, then you can use your head to look around and the mouse to control the gun (as intended) when in "nested mode".
Additional assets (videos, screenshots, logs):
Your PC config data (OS, drivers, specific software): Win10, i5 3570k@4.4Ghz, 16Gb RAM, GTX1080 driver 471.96, TrackIR 5 driver 5.4.2.27545, TM WARTHOG HOTAS + TM ELITE rudders.

[Yo-Yo_Kirby]

Brief description: 48fps lock when using zoom gesture on trackpad w/Windows Precision Touchpad support. Also prevents zooming in/out on map.

 

Detailed description: During a flight in career or quick mission (assuming any gameplay mode), on a laptop with a trackpad that supports Windows Precision Touchpad gestures, fps may drop and lock to 48fps down from desired fps while using the zoom gesture (two fingers moving away/towards each other). This can be observed with huge amounts of stuttering when looking around or using camera and head controls. This will continue until you have alt-tabbed out and don't repeat this again.

 

Your PC config data: Lenovo Legion 5 Pro (2021, AMD). Windows 10 21H1, Ryzen 7 5800H, 64GB 3200MHz DDR4 dual-rank memory, RTX 3070 mobile 140W, Nvidia drivers 471.11 and 471.96, VKB Gladiator NXT.
and;
MacBook Pro (16-inch, 2019/2020). Windows 10 21H1 (Boot Camp), Core i9-9980HK, 64GB 2666Mz DDR4 memory, Radeon Pro 5600M, official AMD Boot Camp GPU drivers, VKB Gladiator NXT.

[durruti]

Brief description: Some wrong letters on Sd. Kfz. 10/5, wrong translation of cockpitlight

 

Detailed description: see pictures :

 

 

 

 

 

 

 

 

The manufacturer is called "Demag" not "Damag", also it´s "Bosch" not "Dosch" and in the last picture it should read "Cockpitbeleuchtung" as stated with the symbol.

 

Your PC config data: not necessary

 

 

 

 

 

 

 

[-DED-Rapidus]

@durruti,1) the names demag and bosch, you noticed correctly, but in the game should be the same as in the screenshots 2) it should be exactly the illumination of the dashboard, "Rücklicht".

 

[LukeFF]

5 hours ago, durruti said:

Brief description: Some wrong letters on Sd. Kfz. 10/5, wrong translation of cockpitlight

 

It's done that way likely to avoid copyright issues, since DEMAG and Bosch still exist. The same thing was done on the GAZ truck: the tire manufacturer insignia was cleverly changed from 'Goodyear' to 'Goodbear.'

[durruti]

1 hour ago, LukeFF said:

It's done that way likely to avoid copyright issues, since DEMAG and Bosch still exist

 

Oh, i didn´t know this, quite clever !

 

 

5 hours ago, -DED-Rapidus said:

it should be exactly the illumination of the dashboard, "Rücklicht".

 

Illuminitation of dashboard means translated "Cockpitbeleuchtung" !

"Rücklicht" means translated "Taillight" !

 

Thanks for your answers.

[-DED-Rapidus]

@durruti, thank you, we will double-check the message.

[Leon_Portier]

Brief description: TC, using the "Report the object to platoon" command gives players the range to their target, making range shooting in multiplayer unrealistically easy if the player knows about it, see picture.
Additional assets (videos, screenshots, logs):
Your PC config data (OS, drivers, specific software):

IL-2 version: 4.604b

Edited October 9, 2021 by [N.O.G.F]Leon_Portier

[Levelord]

Brief description:

The game crashes to Windows after 2-3 seconds in the hangar (after logging in) if the joystick is already plugged in (USB).

 

Detailed description, conditions:

I bought Flying Circus #1 from 1C Game Studios store (not Steam).  If I wait to plug the joystick in until after entering the hangar it doesn't crash.  I can see the 'primary fire = joy0_b0', etc assigned in the input control keys, but nothing happens when I try to fly, of course.  I have a DEXP TopGun 1 joystick.  Windows 10 recognizes it (all axis/buttons work) under Devices.  It is the only game controller.  I have successfully played the game using my mouse and keyboard for over 20 hours.  Great game!

 

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

Processor              Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz   2.60 GHz
Installed RAM       16.0 GB
System type         64-bit operating system, x64-based processor
Edition                  Windows 10 Home
Version                 21H1
Installed on          8/17/2020
OS build               19043.1348
Microsoft.NET     4.8.4084.0

Intel HD Graphics 4600, driver version 20.19.15.4624
NVIDIA GeForce GTX 860M, driver version 23.21.13.9135

 

Thank you!

[RNAS10_Oliver]

Brief description: Airco Bombsight Airspeed Adjustment Broken.

Detailed description, conditions: If this would have been better posted into Armament and Equipment then I'm sorry though it's not always obvious which thread an issue should be categorised as. The problem that I am reporting is that since the last update the airspeed adjustment control on the right side of the DH4 bombsight no longer has any gradations shown nor can the knob be rotated about with the mouse. Before the update 160 was the maximum airspeed (not sure what the minimum was) in KMH that could be set on the bombsight. The DH4 is beyond crippled as a level bomber while this bug exists. I've tested this in both MP and SP and see the same things. Also confirmed that it's not just issue with my own installation as @[F.Circus]Gorn_Captain is seeing the same problem. Thanks in advance.

 

Additional assets (videos, screenshots, logs): 

The airspeed control in 4.701b

 

The airspeed control in 4.603

 

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

Intel i5-2500 @3.30GHz

16GB RAM

NVIDIA GeForce GTX 1060 6GB

NVIDIA Driver Version 496.13

Windows 10 Home, 64-Bit

Edited December 22, 2021 by RNAS10_Oliver