Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Thrasher]

BAT 4.2.2

Hi guys, I'm really hoping that somebody can help with this problem.
One of our squad members had his computer fail and he lost everything.

I copied my game onto an external drive.  I then ran the game from the external drive and it worked perfectly - all four modules. I then mailed it to my friend in Buffalo.

He has purchased a brand new computer which came with WINDOWS 11 installed - naturally. LOL

He loaded the game onto his new computer.  He changed the resolution in his config to match his screen 1920x 1080

The game launched to the blue opening panel and then shut down. Same result on all four modules.

This afternoon four of us got onto TeamViewer and went through his setup.  We:
-  Changed the compatibility settings in both the IL2 app and launcher app
-  Added IL2 to the list of exceptions in the Data Execution Prevention settings
- double checked his resolution
- We even tested the old HSFX version which ran perfectly even though we DIDN'T add it to the DEP exception list (strange)
- Out of desperation we tried to disable the DEP through the cmd but got a message saying that it was not allowed.

BUT still the BAT game refuses to launch.  Four heads spent 2.5 hours on this and we are all now utterly befuddled.

Short of voodoo does anybody have any suggestions?

[Thrasher]

BTW I saw something very unusual this afternoon.
A police helicopter chasing a Sesna.

Love to know the story behind that. LOL

[csvousden]

 I have had that problem.  What has worked for me twice was replacing the confi.ini file from my backup game.  Don't know why but it has worked for me when nothing else seemed to do so.

[Wing Walker]

Only 2.5 hours? That would be nice...

... took me like half a day to reinstall all my backups and zips... and I still couldn't get 4.2.3 to install correctly.  So I just stay with 4.2.2 hotfix4 I guess.

I also had problems transferring a backup off an external drive, like random errors where 4.2.2 wouldn't work.

[Vampire_pilot]

... took me like half a day to reinstall all my backups and zips... and I still couldn't get 4.2.3 to install correctly.  So I just stay with 4.2.2 hotfix4 I guess.

I don't know what to say.
The installers are the exact same thing in 4.2.1 up to 4.2.3 , including all fixes in between. If you can install one, you can install the other.
Literally and technically, there is no way to make it any simpler. There is no explanation or reason within the files or the Modpack that explains the troubles you describe. The problem resides on your end with your setup and there is no way to help from the outside since I can't see what these peculiar things may be that you are doing.

[Thrasher]

Hi guys,

Well here is the latest in this saga.
RECAP
Our squad member purchased a brand new gaming computer with Windows 11.  He then loaded a fresh clean copy of the game. We tested the game before hand and it worked perfectly.  Game would not run.  After days of trials and chats with tech support he returned the computer.

He then purchased a second new computer (not as expensive) with Windows 11 - Game would not work.

he then took it to a tech support guru who loaded Windows 10 and the game booted immediately.  He's now up and running. GOOD NEWS if somewhat mystifying.

A second squad member in Wisconsin went through exactly the same crap only he reverted back to Windows 8 I think so he's flying again now.

But there's definitely something odd going on.

[SAS~Storebror]

Strictly a DEP issue. Sorry to say.

-  Changed the compatibility settings in both the IL2 app and launcher app

Argh... messed it up on first step.
Why did you do that again?

-  Added IL2 to the list of exceptions in the Data Execution Prevention settings

Why?
This would indicate that DEP was enabled for all applications which is not the recommended setting for Windows Clients.
Adding IL-2 to that exception list is of little to no help at all, as with the advent of new Selector versions, process yield breaks your exceptions boundary.
Simply do as explained here: https://www.sas1946.com/main/index.php/topic,71235.0.html

- We even tested the old HSFX version which ran perfectly even though we DIDN'T add it to the DEP exception list (strange)

Not strange at all.
HSFX uses the old stock "mod enabled" launcher.

- Out of desperation we tried to disable the DEP through the cmd but got a message saying that it was not allowed.

...which just means that whatever settings you applied to DEP before, will not have come to effect either.
This is your core issue.
You need to find out why your PC doesn't accept DEP settings.
If your account has local admin rights, there's no reason why this shouldn't work.
If it still doesn't, then this is the issue you need to fight.

It's really that simple:
Enable DEP for essential Windows Programs and Services only.
Didn't work? Do it again, you did something wrong.
Still not working?
Do it again.
No go?
Try again.
Still stuck?
Repeat.
Repeat until you finally get that damned DEP setting going.
This, and only this, will solve your issues with recent IL-2 versions on Windows 11.
NOTE: There is no inherent reason for the game not to run on Windows 11. It does, believe it or not. Once you get your DEP settings sorted, it runs.


Mike

[Thrasher]

Thanks Mike  I'll pass this all on.