Bf109E and F2 single missions/career "briefing" screen frozen.

[Voxman]

Brief description:  Briefing map stays in wait state for any single mission/career for the Bf109E and F2 a/c.  All other 109s not affected
Detailed description, conditions: 

Flying in VR, but observed this behaviour in screen mode as well. 

Set up a QMB duel fight.  Picked the 109E against Random allies. 

Tried this on the BoM, BoS and BoK maps. 

 

After picking 109E or F2 arming/fuel, etc settings, and pushing START, the screen will transition to the cockpit, but the Briefing/arming screen does not disappear, even after pressing P key.  Stays up, and disables most keys..except pause ..  Cannot ESC, HOTAS will work, sometimes the throttle is inverted as well.   The only way out of the menu is to auger the plane to the ground...or bailout and wait.

 

Menu screen will show that mission failed, and will exit as it always does, back to the finish mission screen. 

Have replicated across all modules, and specific for these two Axis planes.  Have not tried it with others.

 

 

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

Windows 11;  AMD Adrenalin 23.7.1, latest version of IL2.  Have deleted and reinstalled the whole game.  Kept data settings for input/career and a few other crucial files.

 

Not sure where to find crash log files or specific files to send...please advise.

Thank you.

[LukeFF]

Do you happen to still have the _gen.mission file?

[Voxman]

I do have a file, not sure if it's specific to the fault.  It is attached.   

 

If that doesn't show anything, I certainly can try to generate another one as this bug is repeatable. 

_gen.zip

[Voxman]

Just ran a QMB with the 109E...same issue.

_gen.zip

[LukeFF]

Okay, thanks. I'll pass along the report.

[Regingrave-]

19 часов назад, Voxman сказал:

Not sure where to find crash log files or specific files to send...please advise.

We'll need your /data/input/ and /data/startup.cfg. Also, try recording a log, when the bug occurs press LShift+LCtrl+B and close the game with Alt+F4 and send us /data/_gui.log as well.

[Voxman]

Here are the files requested...

input.zip startup_gui.zip

[Voxman]

Any updates from the bug fix team?

 

 

On 7/21/2023 at 8:09 AM, LukeFF said:

Okay, thanks. I'll pass along the report.

 

On 7/21/2023 at 9:40 AM, Regingrave said:

We'll need your /data/input/ and /data/startup.cfg. Also, try recording a log, when the bug occurs press LShift+LCtrl+B and close the game with Alt+F4 and send us /data/_gui.log as well.

 

Any updates from the bug fix team?

[LukeFF]

17 hours ago, Voxman said:

Any updates from the bug fix team?

 

When you see this again, please send a generated mission where the bug occurs, and write and send the _gui.log from /data/ (when the bug occurs, press LCtrl+LShift+B and then close the game with Alt+F4).

[Voxman]

_gui.zip  file is attached....note, this was done without VR so I could do the key combinations correct.

This file is a QMB with the ME109E.   This also occurs with the 109F2.

1 hour ago, LukeFF said:

 

When you see this again, please send a generated mission where the bug occurs, and write and send the _gui.log from /data/ (when the bug occurs, press LCtrl+LShift+B and then close the game with Alt+F4).

 

[Voxman]

Update:

I think I may have resolved this issue.  I believe the input file is corrupted, or at least one of my profiles is.  Here is my troubleshooting steps.

First I backed up the following:
startup.cfg;  data/inputs ; career; usersave   files

 

I uninstalled and reinstalled the game.

 

I started the game up as a fresh install and the 109E and F2 no longer were hung up in the briefing screen.

I then exited the game, and first installed the startup.cfg file.  Restarted the game, and again the E and F2 planes were fine. Exited the game.

 

Installed the backup input folder, and found that the E and F2 were experiencing the briefing screen bug again. 

I then renamed that input folder to a different name, restored the trashed input folder from the recycle bin, started the game, and the E7 bug and F2 bug disappeared.

Inside the Input folder is a Custom folder.  I copied the specific input profile for the 109s from the renamed folder and pasted into the restored folder and after starting the game, the E and F2 worked perfectly.

 

I believe that old Input folder may have had a corrupted file, which created this briefing screen bug.

Hopefully this helps those that are/have experienced this bug.