Guys, only thing we all BMS players can do is continuously and always say a really BIG THANK YOU!!! for all your hard and marvelous work!
We’ll wait and, as usual, it will be worth it!!!
Guys, only thing we all BMS players can do is continuously and always say a really BIG THANK YOU!!! for all your hard and marvelous work!
We’ll wait and, as usual, it will be worth it!!!
So, here I am!
I double checked the file and it’s already the latest version, so no need to re-upload it (this has been a very tiring period and my memory faults sometimes… welcome Christmas holidays!!!)… so I’ll just provide the description of the mappings and their logic.
=== STICK: 8-WAY POV HAT ===
UNSHIFTED LAYER: move radar cursor up/right/down/left
SHIFTED LAYER: DMS up/right/down/left
=== STICK: BUTTON 1 (TRIGGER / R1) ===
UNSHIFTED LAYER: second trigger detent (i.e. fire gun)
SHIFTED LAYER: switch to MRM override mode (you could change the call to SimSelectSRMOverride if you want to switch to DF override mode instead… your choice)
=== STICK: BUTTON 2 (PICKLE / L1) ===
UNSHIFTED LAYER: weapon release (pickle)
SHIFTED LAYER: emergency stores jettison (hold it)
=== STICK: BUTTON 3 (under your right index finger / R3) ===
UNSHIFTED LAYER: CMS left
SHIFTED LAYER: radar antenna elevation down
=== STICK: BUTTON 4 (to the right of the pickle / L3) ===
UNSHIFTED LAYER: CMS up
SHIFTED LAYER: radar antenna elevation up
=== THROTTLE: BUTTON 5 ===
UNSHIFTED LAYER: TMS up
SHIFTED LAYER: comms switch up (operates UHF radio)
=== THROTTLE: BUTTON 6 ===
UNSHIFTED LAYER: TMS right
SHIFTED LAYER: comms switch down (operates VHF radio)
=== THROTTLE: BUTTON 7 ===
UNSHIFTED LAYER: TMS down
SHIFTED LAYER: CMS down
=== THROTTLE: BUTTON 8 ===
UNSHIFTED LAYER: NWS / aerial refuelling disconnect / missile step switch
SHIFTED LAYER: CMS right
=== THROTTLE: BUTTON 9 (under your left index finger / R2) ===
UNSHIFTED AND SHIFTED LAYER: pinky shift
This is the button you use to switch between the two layers (has to be the same in both), works as pinky switch too
=== THROTTLE: BUTTON 10 (lower under your left index finger / L2) ===
UNSHIFTED LAYER: manual range knob - uncage
SHIFTED LAYER: MRM/DF override modes cancel
=== THROTTLE: BUTTON 11 (on the throttle basement / SE) ===
UNSHIFTED LAYER: cursor enable
SHIFTED LAYER: does nothing
=== THROTTLE: BUTTON 12 (on the throttle basement / ST) ===
UNSHIFTED LAYER: cursor zero
SHIFTED LAYER: does nothing
This is the verbatim code you’ll find inside, just added it at the bottom of the original “BMS - Full.key” from the Docs folder with absolutely no other modifications:
#===============================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "== THRUSTMASTER T.FLIGHT HOTAS X =="
#===============================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "============ UNSHIFTED ============"
SimCursorUp 0 -1 -3 0 0x0 0 "TQS: RDR CURSOR - Up"
SimDoNothing 0 -1 -3 1 0x0 0
SimCursorRight 0 -1 -3 2 0x0 0 "TQS: RDR CURSOR - Right"
SimDoNothing 0 -1 -3 3 0x0 0
SimCursorDown 0 -1 -3 4 0x0 0 "TQS: RDR CURSOR - Down"
SimDoNothing 0 -1 -3 5 0x0 0
SimCursorLeft 0 -1 -3 6 0x0 0 "TQS: RDR CURSOR - Left"
SimDoNothing 0 -1 -3 7 0x0 0
SimTriggerSecondDetent 0 -1 -2 0 0x0 0 "STICK: SECOND TRIGGER DETENT"
SimPickle 1 -1 -2 0 0x0 0 "STICK: WEAPON RELEASE (Pickle)"
SimCMSLeft 2 -1 -2 0 0x0 0 "STICK: CMS Left"
SimCMSUp 3 -1 -2 0 0x0 0 "STICK: CMS Up"
SimTMSUp 4 -1 -2 0 0x0 0 "STICK: TMS Up"
SimTMSRight 5 -1 -2 0 0x0 0 "STICK: TMS Right"
SimTMSDown 6 -1 -2 0 0x0 0 "STICK: TMS Down"
SimMissileStep 7 -1 -2 0 0x0 0 "STICK: NWS A/R DISC MSL STEP SWITCH"
SimHotasPinkyShift 8 -1 -2 0 0x0 0 "STICK: PINKY SWITCH (DX SHIFT)"
SimToggleMissileCage 9 -1 -2 0 0x0 0 "TQS: MAN RANGE Knob - UNCAGE"
SimCursorEnable 10 -1 -2 0 0x0 0 "TQS: RDR CURSOR - Cursor Enable"
SimRadarCursorZero 11 -1 -2 0 0x0 0 "TQS: RDR CURSOR - Cursor Zero"
#===============================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "============= SHIFTED ============="
SimDMSUp 2 -1 -3 0 0x0 0 "STICK: DMS Up"
SimDoNothing 2 -1 -3 1 0x0 0
SimDMSRight 2 -1 -3 2 0x0 0 "STICK: DMS Right"
SimDoNothing 2 -1 -3 3 0x0 0
SimDMSDown 2 -1 -3 4 0x0 0 "STICK: DMS Down"
SimDoNothing 2 -1 -3 5 0x0 0
SimDMSLeft 2 -1 -3 6 0x0 0 "STICK: DMS Left"
SimDoNothing 2 -1 -3 7 0x0 0
SimSelectMRMOverride 256 -1 -2 0 0x0 0 "TQS: DOGFIGHT Switch - MRM Override"
SimEmergencyJettison 257 -1 -2 0 0x0 0 "GEAR: EMER STORES JETTISON Button - Hold"
SimRadarElevationDown 258 -1 -2 0 0x0 0 "TQS: ANT ELEV Knob - Tilt Down"
SimRadarElevationUp 259 -1 -2 0 0x0 0 "TQS: ANT ELEV Knob - Tilt Up"
SimTransmitCom1 260 -1 -2 0 0x0 0 "TQS: COMMS Switch Up - UHF"
SimTransmitCom2 261 -1 -2 0 0x0 0 "TQS: COMMS Switch Down - VHF"
SimCMSDown 262 -1 -2 0 0x0 0 "STICK: CMS Down"
SimCMSRight 263 -1 -2 0 0x0 0 "STICK: CMS Right"
SimHotasPinkyShift 264 -1 -2 0 0x0 0 "STICK: PINKY SWITCH (DX SHIFT)"
SimDeselectOverride 265 -1 -2 0 0x0 0 "TQS: DOGFIGHT Switch - MRM/DF Cancel"
SimDoNothing 266 -1 -2 0 0x0 0
SimDoNothing 267 -1 -2 0 0x0 0
#===============================================================================================
Enjoy and feel free to ask further information shouldn’t it be clear enough.
Hi guys, sorry for necroposting this a bit, but I’m also searching for a workaround for runway lights not working at night in campaign when using a dedicated server.
I tried to follow the suggestion @VIPER-0 gave of placing the server with 3D rendering enabled in cabin at night, but no luck and all the airport remains extremely dark.
@VIPER-0 would you mind to detail what you do on the server step by step?
I see you posted some here, but it’s not clear to me if when you say “we create the package 20 minutes before takeoff” you mean the server flight or your own and also if you create it everytime or only once.
And when you say " the time of the campaign has to be at night" you mean that the campaign clock itself must be advanced until it’s night time or is it enough to set the departure time for the server flight at night (say, at 22:30 LT)?
Moreover, do you use this trick only on KTO or also on other theaters?
Asking because I tried on Balkans, I don’t think this is the issue because lighting should be part of the BMS core (so the behaviour should be consistent in all theaters), but it might be useful to further understand under what circumstances the bug happens.
Thanks in advance, hope for your reply soon!
Really interesting, thanks, just took it!
@VIPER-0 thanks very much mate, will try and let you know how it goes!
@VIPER-0 thanks very much mate, will try and let you know how it goes!
Hi guys, sorry for necroposting this a bit, but I’m also searching for a workaround for runway lights not working at night in campaign when using a dedicated server.
I tried to follow the suggestion @VIPER-0 gave of placing the server with 3D rendering enabled in cabin at night, but no luck and all the airport remains extremely dark.
@VIPER-0 would you mind to detail what you do on the server step by step?
I see you posted some here, but it’s not clear to me if when you say “we create the package 20 minutes before takeoff” you mean the server flight or your own and also if you create it everytime or only once.
And when you say " the time of the campaign has to be at night" you mean that the campaign clock itself must be advanced until it’s night time or is it enough to set the departure time for the server flight at night (say, at 22:30 LT)?
Moreover, do you use this trick only on KTO or also on other theaters?
Asking because I tried on Balkans, I don’t think this is the issue because lighting should be part of the BMS core (so the behaviour should be consistent in all theaters), but it might be useful to further understand under what circumstances the bug happens.
Thanks in advance, hope for your reply soon!
Really interesting, thanks, just took it!
Guys, only thing we all BMS players can do is continuously and always say a really BIG THANK YOU!!! for all your hard and marvelous work!
We’ll wait and, as usual, it will be worth it!!!
Hello, I noticed that in the HARM tab of the DTC there’s a system name reported as -1.
The code is 608, given that the symbol showing in the RWR is listed as 8 I guess it should be SA8 instead.
Not sure if it’s a WDP issue or if it comes from some BMS database.
EDIT: I double checked and, in fact, SA8 is in the list… but if I try to select it, code is listed as 0 and symbol as -1.
Also other systems show the same behaviour (e.g. SA9, SA13, SA19, PATRIOT, NIKE and probably more).
Gosh, completely forgot it was also in the launcher… thanks guys, sorry for bothering!
Version
4.37.2 (x64)
Build
521
Detailed Description
It seems that the pilot model cannot be deactivated by default: if I go into the Setup -> Graphics and uncheck the relevant checkbox, next time I start BMS it’s checked again and the pilot model is visible when I enter the 3D.
Disabling/enabling it with Alt-c + p from the cockpit works, it’s just the checkbox in the setup that doesn’t seem to be honored (and resets itself to being checked everytime you launch the game).
Reproducibility Procedure
Expected Behavior
The ‘Pilot Model’ checkbox should stay unselected if it has been disabled by the user
@airtex2019 To be honest, I don’t know… but I guess there’s a valid reason for it to be there.
Version
4.37.2 (x64)
Build
521
Detailed Description
I don’t even know if it can be considered a bug, but I just realized that in my User\Config I have two Setup.v100.MouseWheel.xml files.
Looking at creation/modification dates it seems to be like this since a while, so maybe it begun in previous versions.
The only difference is that the second one has a space between the second dot and the “MouseWheel” component of the name… and it seems to be intended, because if I try to move both to the Windows Recycle Bin and subsequently launch the game, it gets recreated with this space.
But the other XML peripherals config files all have no spaces between the name components, so I think it’s a typo in the code or something like that.
I didn’t have the opportunity to test if it has some impact or creates issues in game, can do specific tests if needed.
Reproducibility Procedure
Expected Behavior
You should have only one Setup.v100.MouseWheel.xml file in your User\Config dir, with no spaces in the file name.
If you can do something in reality, but not in BMS, then reality isn’t realistic. Expect next version of reality in 3-4 weeks.
ROTFL, you won it all m8!!! :rofl: