Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
That is amazing chihirobelmo, thank you!!
-
Hey guys, hope you’re doing well.
I’ve ran across a problem with the Alt Launcher where it forces the game to think I have 2 POV hats when I actually only have one (I got a T.Flight Hotas X so the only POV hat it has is the one on the stick).
From what I saw fiddling around, the launcher basically forces the values of “set g_nNumOfPOVs”, “set g_nPOV1DeviceID”, and “set g_nPOV2DeviceID” in falconbms.cfg to be 2, efectively telling the game there are 2 POV hats, with the same ID, which is POV2 (if I’m not mistaken).
The thing is that, while binding the POV in the launcher’s keymapping tab, it recognizes it as POV1 (which is correct, since there is only one POV hat) and lets you bind keys to it normally but the game sees it as POV2 when pressing the POV hat in the controller tab (and since POV2 doesn’t really exist in this case, it cannot be bound to any key, so it defaults to panning the view). The in-game result is that the POV hat behaves as two POV hats at the same time, doing both what I bound it to do in the launcher and panning the view (again, at the same time).
Let me explain myself better with an example: I have the POV hat bound to slew the radar cursor in the launcher so let’s say I press POV UP to slew the radar up, well then the game slews the radar cursor UP and pans the view UP both at the same time.
I tried changing the values of “set g_nNumOfPOVs” and “set g_nPOV1DeviceID” to 1 (and the rest to 0) and launching BMS via the original hub.exe and it works fine, so I figured I would try modifying the .cfg and then launching via the launcher with the “launch w/o any setup override” option active but it still overwrites those values back to 2. So right now the only solution I found is to momentarily launch the game through the normal hub.exe after having modified the .cfg, which is a pity seeing that the Alt Launcher is way better.
Sorry for the long post but I thought I’d write everything I had found while trying to solve this myself in the hopes that it helps to find a solution quicker.
-
Sorry and thank you for your detailed issue report.
I just fixed it.https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases/tag/v1.51
-
Thanks man, you’re awesome!
-
Hi, I’m very new to Falcon BMS. Long time DCS player and I was intrigued by the dynamic campaign so I decided to jump into Falcon. Anyway, I’ve been trying to map hotas bindings for the last few days. I finally had to download Joy Gremlin to get the throttle POV to work for me. I happen to come across Alternate Launcher and seen that now “Supports Throttle POV.”. I bound the POV to trim and launched Falcon and it seems not to register in the controller setup menu and when in the cockpit it doesn’t seem to work either. I’m in the please help stage haha, as I felt like I’ve tried everything…
Sorry if I’m not understanding something.
-
Hi, I’m very new to Falcon BMS. Long time DCS player and I was intrigued by the dynamic campaign so I decided to jump into Falcon. Anyway, I’ve been trying to map hotas bindings for the last few days. I finally had to download Joy Gremlin to get the throttle POV to work for me. I happen to come across Alternate Launcher and seen that now “Supports Throttle POV.”. I bound the POV to trim and launched Falcon and it seems not to register in the controller setup menu and when in the cockpit it doesn’t seem to work either. I’m in the please help stage haha, as I felt like I’ve tried everything…
Sorry if I’m not understanding something.
I’m new to this stuff as well - but I’d try binding the trim switch to other functions. That might help you diagnose…
-
I’m new to this stuff as well - but I’d try binding the trim switch to other functions. That might help you diagnose…
I’ve bound it to multiple different functions. I don’t know what is meant exactly by “Supports Throttle POV” but I’m assuming that I can now map my POV button to a function regardless that it’s on the throttle axis. It’s showing up in the Alternate Launcher key mappings that it’s mapped, but in game it simply does not work for me. Is there something else I’m suppose to do other than map it and launch the game from Alternate Launcher??
EDIT: Fixed I hadn’t realized I needed to download the U1 and U2 patches for everything to work.
-
I’ve bound it to multiple different functions. I don’t know what is meant exactly by “Supports Throttle POV” but I’m assuming that I can now map my POV button to a function regardless that it’s on the throttle axis. It’s showing up in the Alternate Launcher key mappings that it’s mapped, but in game it simply does not work for me. Is there something else I’m suppose to do other than map it and launch the game from Alternate Launcher??
EDIT: Fixed I hadn’t realized I needed to download the U1 and U2 patches for everything to work.
Have you downloaded the latest AL (1.51), it was just released on Feb. 1st.
-
Hi all,
After installing the latest version of the Alternative Launcher (v1.51) I found out that my POV hats weren’t working anymore to orbit around the plane. And also I had a pilot model active which wasn’t the case prior to installation. I had a look in the Alternative Launcher and saw that for some reason the External MouseLook and Pilot Model options were enabled so I decided to untag these options. Problems solved! However, I now have a new problem which at first sight doesn’t seem to be related with the modifications I made. Now, the 3D world stays in a windowed mode and doesn’t switch to fullscreen anymore. It uses only a quarter of the screen or so (like in 2D). I’ve made a screenshot to explain what I mean. Does anybody have any clue how this might have happened and moreover: how to fix this problem? I’m running on Windows 10 64-bit with the latest upgrade (Nov 2019) and start Falcon BMS in windowed mode. I have two monitors attached but am using only one of them to play the game.
-
Have you downloaded the latest AL (1.51), it was just released on Feb. 1st.
Icer yes I did, everything is peachy on my end now. Thank you!
Well I could still use an instructor to teach me Falcon BMS, because this learning curve is MAAAAAASSSIVE!!
-
Did you try deselecting the “Window” command line in the launcher screen?
-
Yes, I did. Both the 2D and 3D world are fullscreen then. However, that’s not what I want because I use a second monitor to show the training manual alongside as a guide. If I don’t use windowed mode, switching from the game to the manual and then returning back to the game is more tedious. Sometimes Falcon BMS even gets hung. In windowed mode you don’t have these issues and switching between game and another application (in my case the manual) is much easier.
-
Now, the 3D world stays in a windowed mode and doesn’t switch to fullscreen anymore. It uses only a quarter of the screen or so (like in 2D).
in BMS UI, go to SETUP -> GRAPHICS -> RESOLUTION and set your resolution properly. Also, don’t forget to set DPI override to Application.
-
Excellent utility, thanks for still supporting it.
-
Unfortunately, no luck yet :(. I also tried maximized window and some settings of the graphical card. Previously, when the mission was loading it would show a screen like I have now but it would switch to maximized window within a second.
-
Unfortunately, no luck yet :(. I also tried maximized window and some settings of the graphical card. Previously, when the mission was loading it would show a screen like I have now but it would switch to maximized window within a second.
Can you show me screenshots of both
“a screen like I have now when the mission was loading”
and
“maximized window switched within a second”
?
-
Can you show me screenshots of both
“a screen like I have now when the mission was loading”
and
“maximized window switched within a second”
?
I’m not sure how this would help you but here are the requested screenshots. The first one is when I’m still in 2D. The second one is during mission load. Like I said, within a second the game would normally switch to fullscreen now. This doesn’t happen anymore. I just tried the Cockpit Display Extraction but to no luck.
Just curious: could the dx9display.dsp file in the config directory have anything to do with it since it changes during the game?
Thanks!
-
I’m not sure how this would help you but here are the requested screenshots. The first one is when I’m still in 2D. The second one is during mission load. Like I said, within a second the game would normally switch to fullscreen now. This doesn’t happen anymore. I just tried the Cockpit Display Extraction but to no luck.
Just curious: could the dx9display.dsp file in the config directory have anything to do with it since it changes during the game?
Thanks!
Invalid Attachment specified.
In General, BMS launches in 1024*768 resolution in 2D and launches 3D with the resolution you set at GRAPHICS page.
For eg:
Let’s say you enabled the window mode of BMS.
BMS will have “border” and title as below if launched in window mode and with 2D/3D border enabled in Cockpit Display Extraction.
Now, if you disabled “border” from Cockpit Display Extraction than BMS launches without a border, but it is still window mode. A window without border and title.
AL v1.5 automatically overrides the Cockpit Display Extraction 2D/3D border option to be disabled.
2D UI launches and fills the entire screen if you launch BMS without window mode enabled, or it just fills 1024*768 size of your left top corner of the monitor if you enabled window mode.
Then you select INSTANT ACTION and TAKEOFF, BMS will switch to 3D and now it fills the screen again if window mode disabled, or may fill XY resolution of your top left corner of the monitor if you launch BMS in window mode. XY value depends on the resolution you set at GRAPHICS page.
Now if you set the resolution at GRAPHICS page to exactly same to your monitor resolution, let’s say you have 32802160 monitor and you also set them to 32802160, 3D fills 3280*2160 size of your top left part of the monitor but it is just as same as filling your entire monitor screen. So it just looks as if launched without window mode. But is still a window, without border.
Note that if you set the Windows10 DPI option to 150% and without setting DPI override property of BMS to Application, BMS 3D fills 1.5x*1.5y of your screen. So you may have to set global DPI to 100%, or set DPI override property of BMS to “Application” so that BMS launches in 100% DPI.
-
Invalid Attachment specified.
In General, BMS launches in 1024*768 resolution in 2D and launches 3D with the resolution you set at GRAPHICS page.
For eg:
Let’s say you enabled the window mode of BMS.
BMS will have “border” and title as below if launched in window mode and with 2D/3D border enabled in Cockpit Display Extraction.
Now, if you disabled “border” from Cockpit Display Extraction than BMS launches without a border, but it is still window mode. A window without border and title.
AL v1.5 automatically overrides the Cockpit Display Extraction 2D/3D border option to be disabled.
2D UI launches and fills the entire screen if you launch BMS without window mode enabled, or it just fills 1024*768 size of your left top corner of the monitor if you enabled window mode.
Then you select INSTANT ACTION and TAKEOFF, BMS will switch to 3D and now it fills the screen again if window mode disabled, or may fill XY resolution of your top left corner of the monitor if you launch BMS in window mode. XY value depends on the resolution you set at GRAPHICS page.
Now if you set the resolution at GRAPHICS page to exactly same to your monitor resolution, let’s say you have 32802160 monitor and you also set them to 32802160, 3D fills 3280*2160 size of your top left part of the monitor but it is just as same as filling your entire monitor screen. So it just looks as if launched without window mode. But is still a window, without border.
Note that if you set the Windows10 DPI option to 150% and without setting DPI override property of BMS to Application, BMS 3D fills 1.5x*1.5y of your screen. So you may have to set global DPI to 100%, or set DPI override property of BMS to “Application” so that BMS launches in 100% DPI.
OK, I’ll have another look at it tonight. The strange thing is that I haven’t changed my resolution at all. Is the resolution that will be used in 3D perhaps saved in this dx9display.dsp file in the user\config directory?
Thanks for your elaborated answer!
Marcel
-
I think I found the problem. Hopefully my attachments are valid :). My graphical card is shown twice in the setup menu (1st screenshot). The first card is currently selected and the maximum resolution (and my current setting) here is 1920x1080 (2nd screenshot). This explains why I don’t get fullscreen. If I select the second card I get a maximum resolution of 3840x2160 (3rd screenshot) which is the same resolution as my monitor. So I tried to select the second card and use this last resolution but when I save it, leave the menu and go back again, the first card is selected again with the mentioned resolution of 1920x1080. So for some reason I can’t save it hence still no fullscreen. I’m thinking about installing the game again but perhaps anybody has a quicker solution? Thanks!