Launch without any setup override and VR switch
-
Problem description:
As the alt launcher can’t detect my throttle I have to run it with “Launch without any setup override”, but it seems to disable the VR switch as well.Workaround:
Start the game in VR with “Launch without any setup override” disabled then start it with enabled (it should still start in VR) and rebind axes in game. This is ok if you don’t plan to switch between VR and monitor often.Solution suggestions:
- VR switch should ignore the “Launch without any setup override”
- Extra flag to only ignore axis / keybinding
- Fix alt launcher device detection or add an option to be able to manually select device / axis just like in-game
-
-
@chinpok what is your throttle? can you share what’s in your DeviceSorting.txt file?
-
{62040EB7-0000-0000-0000-504944564944} “FANATEC CSL Elite Pedals LC”
{BEAD1234-0000-0000-0000-504944564944} “vJoy Device”
{00040EB7-0000-0000-0000-504944564944} “FANATEC ClubSport Wheel Base V25”
{00040EB7-0000-0000-0000-504944564944} “FANATEC ClubSport Wheel Base V25”
{BE684098-0000-0000-0000-504944564944} “WINWING Orion Throttle Base II TGRIP-F16”
{BE684098-0000-0000-0000-504944564944} “WINWING Orion Throttle Base II TGRIP-F16”
{BE684098-0000-0000-0000-504944564944} “WINWING Orion Throttle Base II TGRIP-F16”
{200112E0-0000-0000-0000-504944564944} “FSSB R3L MJF SGRH”
{BE684098-0000-0000-0000-504944564944} “WINWING Orion Throttle Base II TGRIP-F16” -
seems you are separating it to 32DX x 4 throttles. I think you have some option to combine them to 1 throttle with 128DX with WINWING driver.
-
All those 4 throttles not on KeyMapping column???
-
@chihirobelmo It is separated because the combined one is not working with BMS, at least not with the in-game setup but then assume neither it will work with the alt launcher.
-
@chihirobelmo I have 4 columns of the throttle
-
Then it is detecting them…what do you mean “alt launcher can’t detect my throttle” ?
-
@chihirobelmo It means I can’t assign it, I move any axis on the throttle nothing is detected. Actually it seems to already have the correct axis set but when I move it nothing happens (progress bar is not changing).
-
Just tried 32x4 DX button mode with SimAppPro and AL detects axis moving no problem…can you confirm axis are moving in simAppPro? (BTW I’m flying BMS with 128x1 DX mode…)
-
@chihirobelmo I’m not using SimAppPro (I set it up once and now it’s “disabled”), working in Windows Game Controllers, in-game BMS, DCS, everywhere it’s just not working in the alt launcher.
-
@chihirobelmo If it works for you it must be some local issue then, thanks for the help.
-
sorry, I could not find the repro but the default BMS UI should still work for you…
-
I’ll make “Launch without any setup override” to only ignore AXIS/KEY in the future update, thx.
-
@chihirobelmo No need to apologize you did what is possible, thanks again!
I’m running win 11 other than that obviously it’s a fresh install so I put it in the weird bugs category -
@chinpok someitmes simappro needs to be started to make the device “work”. I would recommend following chihiro’s advice and using the throttle as 1 device with 128 buttons though, it makes it much easier to bind.
-