Controls, GUI, texts

[SqwkHappy]

Brief description:

joystick disconnects then reconnects mid-game

Detailed description, conditions:

my joystick will sometimes disconnect and reconnect mid-game, when it does I have to quit the server, then quit the game. Then restart the game, re-join the server, setup my flight again and hope my joystick does not disconnect, wasting what little time I have to fly. This whole process eats up so much of my time that most of my time in the game will sometimes be spent  loading, re-joining and setting up instead of flying. Please Help!!

 

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

Windows 10

Microsoft FFB joystick

i7-4770k CPU

8GB memory

TrackIR

[RedKestrel]

Brief description:  

After spawning into multiplayer dogfight servers, some engine controls use only half of available control axis travel on Logitech Throttle Quadrant.
Detailed description, conditions: 

This happens randomly, but most often in the Pe-2 and Yak-7B, occasionally in A20. Most common errors occur with mixture but also happens with RPM bound to axis. My controller has three axes, one for RPM, one for mixture, and one for Turbocharger. After spawning in and starting engines, with all axes of the quadrant in the fully forward position, the lever must be moved more than 50% of travel before any adjustment to the bound control happens. E.g. if I go to adjust the mixture, I have to move the lever to the 50% position before the mixture starts adjusting below 100%. Same with RPM when this occurs. Bound buttons adjust engine settings as normal. Never encountered in single player mode. After respawning, issue usually corrects itself.
Additional assets (videos, screenshots, logs): N/A.
Your PC config data (OS, drivers, specific software):
Windows 10, Intel i5 3.4 ghz processor, Nvidia GTX 1060 w/latest drivers. (Controllers are CH Combat Stick, CH pro rudder pedals, CH Pro throttle, and Logitech throttle quadrant (this one has the issue, no issues with other axes on other controllers). 

[silvergun]

Brief description:

Skins that do not match the image of the GUI, Skins that do not load and errors on the specs page.

 

Version 3.101 

 

*Click to enlarge!

 

BF 109 F-4 (Skins that do not load, Skins that do not match the image of the GUI).

 

 

 

 

FW 190 A-8 (Spinner and skins that do not match the image of the GUI).

 

 

 

 

FW 190 D-9 (Error on the specs page, should be 250 per gun).

 

 

 

 

SPITFIRE MK IXe  (Skins and spinner that do not match the image of the GUI).

 

Edited June 10, 2019 by silverguun
Files, text.

[Roger_Meatball]

Brief description:

Microsoft FFB2 joystick connection lost
Detailed description, conditions:

While playing, I hear the windows sound to indicate a device has disconnected, then reconnected. My FFB2 seems to be the device. Despite reconnecting and windows recognizing it again, IL-2 will not pick the joystick back up until the game is restarted. When in-flight, this is a major problem

I only see my joystick disconnect when I am using it to play IL-2. Otherwise it sits connected, idle, to my PC at all times. Windows seems not to lose connection when I'm outside of IL-2.
Additional assets (videos, screenshots, logs):

I am new to bug reports and do not know which log to look for.
Your PC config data (OS, drivers, specific software):

Laptop

Windows 10 Home

i7-8750

32 GB ram

RTX 2070

Sidewinder FFB 2 joystick 

CH Pro pedals

Both inputs run through 4-port USB 3.0 hub 

Edited June 12, 2019 by Roger_Meatball

[SAS_Storebror]

Brief description: Launcher Crashes on DServer
Detailed description, conditions: Stopped DServer.exe, then ran Launcher, then got the following crash message:

 

Additional assets (videos, screenshots, logs): Funny that you're asking. I'd love to show logs if only we had any of the launcher.
Your PC config data (OS, drivers, specific software): Windows Server 2016, Intel Core i7-4770 @3.8GHz, 32 GB RAM, 2x2TB HDD (Raid 1), 1GBit/s non-clocked.

[silvergun]

Brief description:

Skins that do not match the image of the GUI.

 

Version 3.101b

 

*Click to enlarge!

 

BF 109 F-4 (Skins that do not match the image of the GUI).

[ITAF_LG965]

Brief description: Launcher Crashes, and I get the following message

Detailed description, conditions:  after the 3.101 update

 

 

What can I do?

I have already tried the most obvious thing, reinstalling the game.

[[FAC]Ghost129er]

Brief description: Unable to change UI Scale
Detailed description, conditions:

Unable to change UI Scale in settings or anything, always gives choice of only being able to choose auto, but currently at 100%. Using auto on 1024*768 makes the UI microscopic.

Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software): Intel Core i5-2500K @3.3GHz, 8 GB RAM, Zotac GTS 450

P.S. I have learnt that when using a Splashscreens Mod the UI scaling seems to be working well on the versions of gamesplash.gfx, interface.gfx and preloader.gfx, dated March 2018, however, the game doesn't run when using these old version files anymore... Perhaps a look at what changed may help to get the UI scaling back..? I'm apparently the only one with this issue it seems.

Edited July 1, 2019 by [FAC]Ghost129er
date typo

[Jade_Monkey]

On 6/4/2019 at 11:24 AM, RedKestrel said:

Brief description:  

After spawning into multiplayer dogfight servers, some engine controls use only half of available control axis travel on Logitech Throttle Quadrant.
Detailed description, conditions: 

This happens randomly, but most often in the Pe-2 and Yak-7B, occasionally in A20. Most common errors occur with mixture but also happens with RPM bound to axis. My controller has three axes, one for RPM, one for mixture, and one for Turbocharger. After spawning in and starting engines, with all axes of the quadrant in the fully forward position, the lever must be moved more than 50% of travel before any adjustment to the bound control happens. E.g. if I go to adjust the mixture, I have to move the lever to the 50% position before the mixture starts adjusting below 100%. Same with RPM when this occurs. Bound buttons adjust engine settings as normal. Never encountered in single player mode. After respawning, issue usually corrects itself.
Additional assets (videos, screenshots, logs): N/A.
Your PC config data (OS, drivers, specific software):
Windows 10, Intel i5 3.4 ghz processor, Nvidia GTX 1060 w/latest drivers. (Controllers are CH Combat Stick, CH pro rudder pedals, CH Pro throttle, and Logitech throttle quadrant (this one has the issue, no issues with other axes on other controllers). 

 

Im so happy i read this. I thought it was related to my throttle.

 

I get the same issue with the Virpil Throttle.

 

Some axes are set in a way where the midpoint is the 100%. It is hard to replicate because it's not always there. In the same SP mission it might always not happen.

[RedKestrel]

6 hours ago, Jade_Monkey said:

 

Im so happy i read this. I thought it was related to my throttle.

 

I get the same issue with the Virpil Throttle.

 

Some axes are set in a way where the midpoint is the 100%. It is hard to replicate because it's not always there. In the same SP mission it might always not happen.

I haven't encountered this bug in some time and never as far as I recall in a single player mission. I had thought it may be an online only issue but if you are getting it in SP then obviously its not. Its also obviously not simply a hardware issue. I still have no idea what may trigger it.

Edited July 17, 2019 by RedKestrel

[Jade_Monkey]

38 minutes ago, RedKestrel said:

I haven't encountered this bug in some time and never as far as I recall in a single player mission. I had thought it may be an online only issue but if you are getting it in SP then obviously its not. Its also obviously not simply a hardware issue. I still have no idea what may trigger it.

I haven't seen a pattern. I thought ot was related tu spawning on parked, bit then i couldn't reproduce it.

[RedKestrel]

1 hour ago, Jade_Monkey said:

I haven't seen a pattern. I thought ot was related tu spawning on parked, bit then i couldn't reproduce it.

For what its worth, I have only encountered it when spawning in a parked position with the engine off, never with the engine running on the runway or from an air start that I can remember.

[LuftManu]

Brief description: Incorrect text in 109 F4 skin description, Spanish
Detailed description, conditions:

The text in the ingame description of "Shultz" skin of Bf 109 F4 has an incorrect letter in caps.Second line: "COnsiguió" should be "Consiguió"

Additional assets (videos, screenshots, logs):

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

[Redglyph]

Brief description: mapping of trim (aileron, elevator, rudder) don't work on P-51 when mapped to controller
Detailed description, conditions:

The aileron, elevator and rudder trim work with the pre-defined keyboard mapping, but if they are also mapped to a controller (joystick hat for ex), using the controller doesn't do anything. Using the keyboard mapping still works.

Additional assets (videos, screenshots, logs):

Version 3.201

 

EDIT: same problem with P-38

Edited September 30, 2019 by Redglyph

[Semor76]

Brief description: Bug in the Tempest Snap views.
Detailed description, conditions: The function " Pilot head snap- position right" is broken! Same function for the left side works.

 

 

Edit: Same bug appears for the SpitfireMkIXe_B.

 

Pls. fix this.

 

Edited September 30, 2019 by Semor76

[Akatsuki]

5 hours ago, Redglyph said:

Brief description: mapping of trim (aileron, elevator, rudder) don't work on P-51 when mapped to controller
Detailed description, conditions:

The aileron, elevator and rudder trim work with the pre-defined keyboard mapping, but if they are also mapped to a controller (joystick hat for ex), using the controller doesn't do anything. Using the keyboard mapping still works.

Additional assets (videos, screenshots, logs):

Version 3.201

 

EDIT: same problem with P-38

 

Same here, it seems that all aircraft have this issue.

 

Edited October 1, 2019 by Akatsuki

[56RAF_Stickz]

5 hours ago, Redglyph said:

Brief description: mapping of trim (aileron, elevator, rudder) don't work on P-51 when mapped to controller
Detailed description, conditions:

The aileron, elevator and rudder trim work with the pre-defined keyboard mapping, but if they are also mapped to a controller (joystick hat for ex), using the controller doesn't do anything. Using the keyboard mapping still works.

Additional assets (videos, screenshots, logs):

Version 3.201

 

EDIT: same problem with P-38

There is an extra trim control in settings for all trims.

Are you mapping joystick hat to the axis trim command as well as the trim up and down? All planes with a trim wheel now use the axis trim ie all american, British and most Russian- so use the trim up/down axis with hat same as individual trims.

[69th_Panp]

Same here, no trim settings work, remap the default buttons and the trim will not work, same issue with the radiator set up on flight stick.

[THERION]

5 hours ago, Akatsuki said:

 

Same here, it seems that all aircraft have this issue.

 

 

3 hours ago, Panp said:

Same here, no trim settings work, remap the default buttons and the trim will not work, same issue with the radiator set up on flight stick.

 

10 hours ago, Redglyph said:

Brief description: mapping of trim (aileron, elevator, rudder) don't work on P-51 when mapped to controller
Detailed description, conditions:

The aileron, elevator and rudder trim work with the pre-defined keyboard mapping, but if they are also mapped to a controller (joystick hat for ex), using the controller doesn't do anything. Using the keyboard mapping still works.

Additional assets (videos, screenshots, logs):

Version 3.201

 

EDIT: same problem with P-38

 

That is not an issue nor a bug! It hasn't been documented yet, but you simply have to assign/bind your buttons/switches you used until now to the new trim axis.

I had the same problem like all of you, but after assigning those buttons of my joystick accordingly to the new trim axis, everything works fine.

Edited October 1, 2019 by -=-THERION

[=gRiJ=Alado]

13 minutes ago, -=-THERION said:

 

 

 

That is not an issue nor a bug! It hasn't been documented yet, but you simply have to assign/bind your buttons/switches you used until now to the new trim axis.

I had the same problem like all of you, but after assigning those buttons of my joystick accordingly to the new trim axis, everything works fine.

 

i dont see that option, can you show us a photo??

[THERION]

1 hour ago, =gRiJ=Alado said:

 

i dont see that option, can you show us a photo??

 

Sure - here you are:

 

 

As you can see, I just bound my two existing, separate buttons for each trim movement to the new trim axis function.

Hope the sketchy drawing helps.

 

Edited October 1, 2019 by -=-THERION

[=gRiJ=Alado]

Oh, im blindm many thanks

[Jansgi]

Brief description: In MP when GUI is enabled I get constant microstutter.
Detailed description, conditions: Regardless of NVIDIA or game settings GUI is causing constant microstutter in multiplayer. Single player is not affected. When disabled everything runs smooth.
Additional assets (videos, screenshots, logs):
Your PC config data (OS, drivers, specific software): 

ASUS Z170-DELUXE
Intel® Core™ i7-6700K @ 4,6 GHz
ASUS ROG Strix GeForce® GTX 1080 Ti
G.Skill Trident Z 32GB DDR4 3200MHz

Newest NVIDIA drivers

TrackIR software running

 

 

[Redglyph]

10 hours ago, -=-THERION said:

 

 

 

That is not an issue nor a bug! It hasn't been documented yet, but you simply have to assign/bind your buttons/switches you used until now to the new trim axis.

I had the same problem like all of you, but after assigning those buttons of my joystick accordingly to the new trim axis, everything works fine.

 

Thanks for the tip and screenshot, Therion and 56RAF_Stickz!

 

That's very misleading though, it's not an axis but a button and we have to guess we can configure two buttons in one entry. I suggest to at least have a more suggestive label?

Edited October 1, 2019 by Redglyph

[THERION]

1 hour ago, Redglyph said:

 

Thanks for the tip and screenshot, Therion and 56RAF_Stickz!

 

That's very misleading though, it's not an axis but a button and we have to guess we can configure two buttons in one entry. I suggest to at least have a more suggestive label?

 

You're welcome and yes, this thing is a little bit confusing, although we had this already before this update. There are other functions built-in where you exactly

do the same, except it's not label as axis...

[JG4_Sputnik]

Hi

in short: All two engine planes like He111, A20 and P38 don't respond to rpm control if they are started from parking position.

No matter if I put it on buttons or on a lever, the animation is there but the technochat doesn't show anything, also the rpm gauge doesn't increase or decrease rpms.

EDIT: the Pe2 does work though, I think because it has a different rpm input (not a lever but a switch).

 

Why is it a bug: Because when I start the very same plane midair or when engines are already running, rpm control works as it should, technochat included. (no options changed). 

 

I have uploaded a track :

https://we.tl/t-xWnkevDW7r

 

More info in this thread:

 

My system:

 

i7 4770k

Gfx 2060

16gb Ram

win 8.1

Edited October 2, 2019 by JG4_Sputnik

[RedKestrel]

When you add throttle, do the RPMs catch up to where they should be? or do they stay super low?

[JG4_Sputnik]

Hi,

nope, they stay low... so there's no input at all.

It seems that it effects only two engined planes, since I have the same issue with the Heinkel, the Ju88, the A20 and the P38. 

[unlikely_spider]

Brief description:

Messages don't disappear
Detailed description, conditions:

Messages on the left side, such as NPC chatter, kill notifications, etc do not go away if any are on the screen and I pause the game. After unpausing, any messages that exist will stay there until mission end. Normally they would gradually time out after a short period of time.
Additional assets (videos, screenshots, logs):
Your PC config data (OS, drivers, specific software):

Windows 10, RTX 2070, AMD 2700, 16 GB ram; all drivers up to date

[Ghost666]

Just tried theHe111 in SP Parked. Worked with both engines selected and with 1 only and 2 only.

Have not tried the rest.

[JG4_Sputnik]

I know that it doesn't affect all players by now, but there's something fishy going on with twin prop planes and parked position. Other players have also experienced strange behavior in that situation. It could have something to do with having both engines rpm on one lever. 

We are testing further...

[Matt]

Please just upload one trackfile that works (include the folders) or make a video. Until you do that, we can only guess what's wrong and this bug report is not gonna help. 

[JG4_Sputnik]

Hi! Thanks for helping, I've uploaded the whole track file now but I could kind of figuring out myself; here^s my post from the OT:

 

 

PLOT TWIST!

 

Ok here is a strange thing that happened:

I was fiddling in my control settings when suddenly all those tiny orange boxes that signal that you have double bound a key, disappear. A few secs later my PC shut down.

After a restart and back to IL2, all my keybindings are gone and there were the default ones! 

I spent a hour remapping all my buttons an levers and lo and behold, everything works as it should!

 

That was really strange (ok I've overclocked my CPU lately but it was stable until, well it wasn't stable anymore). But I had rebound my RPM levers before and it didn't work, just now after a complete reset it works now.

 

Thanks for all your tips guys, I guess it really had to do something with the keybindings but I couldn't figure it out without the compete meltdown of my system. And strangely enough it happened only to a few planes in the game.

 

Anyways, happy flying and have a good one,

cheers,

Sputnik

[Grobby]

Using SAITEK X52 under 3.201 b and then c. Have the problem with POV2:

Joystick tested under windows 10 and reacting as should do.

With IL2 key settings, 

the software acknowledges the  button e.g. j0 b19 but does not execute the associated command (trim action)  in play.

All other buttons and axes seem to work.

 

[ESA_Overlord]

Brief description: mapping of trim
Detailed description, conditions:

The aileron, elevator and rudder trim  dont work in any plane.

 

Same problem than Grobby, but I have a Thrusmaster Hotas Warthog.

I configure my joy in IL2 Keymapping

I asignate buttons to trims but they not work, only work with keyboard...

After the last update I have a problem with the  trim, they have stopped working, I have tried to configure it again in my Hotas Warthog and there is no way it will work.

If I activate the trimming with the keyboard I have no problem but with the assignment of my hotas in the usual mushroom it has stopped working.

I've even tried to assign an axis of my saitek quadrant and it doesn't work either

If someone can help me I would appreciate it, because I have no idea what the problem may be.
 

Some on my squadp ilots are experiencing this same problem...

 

Thank you all.

Edited October 16, 2019 by ESA_Overlord

[KaC_Furias]

On 10/16/2019 at 9:52 AM, ESA_Overlord said:

Brief description: mapping of trim
Detailed description, conditions:

The aileron, elevator and rudder trim  dont work in any plane.

 

Same problem than Grobby, but I have a Thrusmaster Hotas Warthog.

I configure my joy in IL2 Keymapping

I asignate buttons to trims but they not work, only work with keyboard...

After the last update I have a problem with the  trim, they have stopped working, I have tried to configure it again in my Hotas Warthog and there is no way it will work.

If I activate the trimming with the keyboard I have no problem but with the assignment of my hotas in the usual mushroom it has stopped working.

I've even tried to assign an axis of my saitek quadrant and it doesn't work either

If someone can help me I would appreciate it, because I have no idea what the problem may be.
 

Some on my squadp ilots are experiencing this same problem...

 

Thank you all.

 

Same problem here. everything was ok until  i did a clean install of my win 10. 

[=gRiJ=Alado]

look eight post above

Edited October 22, 2019 by =gRiJ=Alado

[JimTM]

Brief description:  A-20 inlet shutters do not work in multiplayer missions after flying a few sorties

Detailed description, conditions:  The A-20 cooling inlet shutters do not work in multiplayer missions after flying a few sorties but they do work in quick missions. I was in a Combat Box mission and I tried closing the inlet shutters before takeoff and after takeoff but they would not respond. I tried the same thing in a quick mission and the inlet shutters responded on the ground and in the air. I tried flying an A-20 first thing in Combat Box and the inlet shutters worked. It appears like something corrupts the inlet shutter control if you fly a few sorties.

 

UPDATE (2019-01-14): I ran some tests and I think you can mark this solved for now.

 

Additional assets (videos, screenshots, logs):  None
 

Your PC config data (OS, drivers, specific software):  Win 7 Home SP 1, also, see signature.

Edited January 15, 2020 by JimTM

[Letka_13/Arrow_]

Brief description: I am not sure it is a bug/problem, but after every mission too many pilots of my squadron in career are getting the Order of  Lenin and Hero of the Soviet Union
Detailed description, conditions: Each pilot in my ground attack Il-2 career squadron has attained Order of Lenin and Hero of the soviet union award. Seems like award logic is somehow problematic. Please see the screenshot below (Volkov, Kulagin, Voronov all got Order of Lenin and HSU, the others already have it). I've generated a new career and even after an unsuccessful (aborted) mission pilots get HSU and OL awards. This has started happening only after the newest patch.
Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software): Intel I7 i2700K, Nvidia 1070, 16GB RAM, Windows 10, TracIR, G-940 flight system

[LukeFF]

On 11/27/2019 at 11:51 AM, Rudolph said:

Brief description: I am not sure it is a bug/problem, but after every mission too many pilots of my squadron in career are getting the Order of  Lenin and Hero of the Soviet Union
Detailed description, conditions: Each pilot in my ground attack Il-2 career squadron has attained Order of Lenin and Hero of the soviet union award. Seems like award logic is somehow problematic. Please see the screenshot below (Volkov, Kulagin, Voronov all got Order of Lenin and HSU, the others already have it). I've generated a new career and even after an unsuccessful (aborted) mission pilots get HSU and OL awards. This has started happening only after the newest patch.
Additional assets (videos, screenshots, logs):

Your PC config data (OS, drivers, specific software): Intel I7 i2700K, Nvidia 1070, 16GB RAM, Windows 10, TracIR, G-940 flight system

 

Yes, it's correct. The award parameters were re-worked for this update. Before, the requirements to earn just about every Soviet award were way above and beyond what the real pilots had to accomplish.

 

EDIT: if you start a new Sturmovik career, you'll see that most of your most accomplished pilots will have an Order of the Red Star as their most prestigious medal. What you are seeing with your current career is pilots being retroactively awarded the HSU and Order of Lenin*, so to say.

 

In general, the order of precedence for Soviet medals more of less now follows what was in place up to late 1943 (before the Order of Glory was instituted):

 

Medal for Battle Merit

Medal for Courage

Order of the Patriotic War 2nd Class** (after May 1942) (plus multiple awardings)

Order of the Patriotic War 1st Class** (after May 1942) (plus multiple awardings)

Order of the Red Star (plus multiple awardings)

Hero of the Soviet Union / Order of Lenin (plus multiple awardings)

Order of the Red Banner (plus multiple awardings)

Order of Suvorov

Order of Alexander Nevsky

 

*The Order of Lenin was typically awarded at the same time a person earned the title of HSU.

**There is currently an issue where AI pilots can be awarded the Order of the Patriotic War before May 1942, but that should be fixed in the next update.

Edited November 28, 2019 by LukeFF