Patch for Windows 8 & 10 compatibility

[BitRain]

I made this patch that contains all the fixes mentioned on the discussions forum for BA2

Download it here: https://drive.google.com/file/d/1rsFgB79lpCWs9TWIhagjAL4lkOc8f8CS/view

It contains fixes mentioned on these threads, thanks for the help!
https://steamcommunity.com/app/15230/discussions/0/154643720194137521/
https://steamcommunity.com/app/15230/discussions/0/1473095331509307581/
https://steamcommunity.com/app/15230/discussions/0/558748822371950962/

UPDATE: 360 controllers are now working!

Extract the contents of the patch to your game folder (where launcher.exe is located), and run the game from either the launcher or BA2.exe, it won't matter any more.

Here's a video guide: https://www.youtube.com/watch?v=xSC4IIX7cE8

If there are any more fixes you know of I'll add them to this post

Hope it works out for ya!

[natesobol]

funny how you've singlehandedly done a better job at maintaining this game than Ubisoft. Thank you.

[Harry Sachz]

thank you for this.

[dday14]

Thank you so Much! The game guns great now except one thing......... I can't get it to read any of my controllers. When I try to define the controller buttons, a box pops up telling me to "please select game controller". I have looked everwhere and have tried three different controllers now.

Its nice to get this game running but sucks to try and play without a controller or joystick

[BitRain]

Originally posted by dday14:

Thank you so Much! The game guns great now except one thing......... I can't get it to read any of my controllers. When I try to define the controller buttons, a box pops up telling me to "please select game controller". I have looked everwhere and have tried three different controllers now.

Its nice to get this game running but sucks to try and play without a controller or joystick

I've tried using 3 different controllers with different controller software in the game under windows 10, seems to be an OS issue with different versions of Xinput never found a fix, my solution was to just run the game under VMware on Windows 7 in the end, it's still well playable in a virtual machine but it's still a ♥♥♥♥♥♥ fix.

[Maikel]

Originally posted by BitRain:

Originally posted by dday14:

Thank you so Much! The game guns great now except one thing......... I can't get it to read any of my controllers. When I try to define the controller buttons, a box pops up telling me to "please select game controller". I have looked everwhere and have tried three different controllers now.

Its nice to get this game running but sucks to try and play without a controller or joystick

I've tried using 3 different controllers with different controller software in the game under windows 10, seems to be an OS issue with different versions of Xinput never found a fix, my solution was to just run the game under VMware on Windows 7 in the end, it's still well playable in a virtual machine but it's still a ♥♥♥♥♥♥ fix.

The application J2K (An alternative for Joy2Key) allows you to assign your key's again(you can even fake the throttle(Z1) axis to read as keys.. no more analogue control on them then though).. it's a painfull process though. You are very correct that the problem is related to directXinput under windows 10, with problems differencing from build to build.

On current windows 10 builds however, the game gets correct information on your monitor(It'll even report the frequency within the game).

Since HAWX, on pretty much thesame engine is working fine, and allways has.. I'll try to see what happens when I try to place some DLL's from that game into the BIN folder of the game.. I'll report my findings.

The real issue here is that we have no proper successor to this game, and to me, the multiplayer co-op campaign is the best point of this game, fly with your buddy, completing the missions together. Games within that construct however are at this moment limited to BA1, BA2(Partially Broken), HAWX(always worked fine), and Starlancer(Now fixed to run on whatever resolution you want on windows 10)

[BitRain]

Originally posted by Maikel:

The real issue here is that we have no proper successor to this game, and to me, the multiplayer co-op campaign is the best point of this game, fly with your buddy, completing the missions together. Games within that construct however are at this moment limited to BA1, BA2(Partially Broken), HAWX(always worked fine), and Starlancer(Now fixed to run on whatever resolution you want on windows 10)

A guy in the youtube vid I posted found a specific dinput8.dll from 2009 that supports 360 controllers and joysticks properly. I just updated the patch to make it work.

[Maikel]

Yes, but even your ass knows the difference betweeen a controller and a flightstick.

[Renan_Vader]

Thank you sir, i was searching for a fix for a long time

[NIGHTWING74]

WOW! worked like a charm for me on 2560 x 1440 thank you so much

[ГОСПОДИН ХОРОШИЙ]

I really respect you . You help me veeeeeery mach. I was searching a fix for a long time.

[vLucky]

Any idea how to make it run on 1080p, it doesent allow me to go higher than 1280x800.

[BitRain]

Originally posted by Vladimir:

Any idea how to make it run on 1080p, it doesent allow me to go higher than 1280x800.

I was able to get it to run in 1080p via the settings but you can also try configuring dxwnd to run it 1080 by default. if neither work you can try setting the resolution in the registry settings in the same dirs that are listed in the .reg file inside the patch zip.

[Khai - Digital Nomad]

oh thank you!!

I bought this what... a decade ago now? and it never worked right.. but I just flew the first mission with my HOTAS - T-flight and it was great!

please tell me someone put a patch together for BA-1.... off to see...

[Baka Racker]

Thank you and everyone else who worked on this so much! I can finally play this again! :D

[stahlhart]

BitRain: thank you for posting this fix! The game launches here now (Window 10 x64). Was able to create a player profile, now time to see if I can map our flight stick into the controls.