fitness88 Posted November 28, 2019 Posted November 28, 2019 Why can't all HOTAS mapping be done directly under the aircraft type where you have most of the commands? There is a separate set of VR and UI mapping commands... Thank you.
MacEwan Posted November 28, 2019 Posted November 28, 2019 I think it's done this way because HOTAS controls are aircraft specific while the VR and UI controls are global to all aircraft.
fitness88 Posted November 28, 2019 Author Posted November 28, 2019 I think it's done this way because HOTAS controls are aircraft specific while the VR and UI controls are global to all aircraft. Yes I see that but you can't map to a keyboard with VR only direct to the HOTAS which is functionally limiting because you can't use your mapping software. Thanks for the response.
Snacko Posted November 29, 2019 Posted November 29, 2019 Are you saying that you can't assign a keyboard key to those commands? I think also since they are not aircraft specific, if you map the same button that is used in an aircraft, the aircraft command overrides the VR and UI commands.. Sent from my Moto Z Play using Tapatalk Snack Officer Intel I9-10850K (OC @ 5.0ghz) │ 64GB (4x16GB) DDR4 3200 │Gigabyte RTX 4090 Gaming OC 24gb - ҉ - Blackshark Cockpit Trainer - ҉ - ♣ Thread | ♥ Download
fitness88 Posted November 29, 2019 Author Posted November 29, 2019 Are you saying that you can't assign a keyboard key to those commands? I think also since they are not aircraft specific, if you map the same button that is used in an aircraft, the aircraft command overrides the VR and UI commands.. Sent from my Moto Z Play using Tapatalk It certainly did that in earlier versions even using modifiers but I tested that this evening and the modifiers were working ok. VR mapping has to be done directly in the control page and not through HOTAS software, UI can be done both ways.
Recommended Posts