wilbur81 Posted July 24, 2018 Posted July 24, 2018 (edited) It would be great to have a controls' 'cycle' option for every single mutli-position switch, knob, etc. in the Hornet. I would much rather push a physical button or key multiple times to get the switch position I want rather than have to reach for my mouse, pause head tracking, click, reach back for stick, etc. Fully clickable cockpits are great. But reaching for and operating a mouse cursor is not realistic... or combat-practical. Edited July 24, 2018 by wilbur81 i7 8700K @ Stock - Win11 64 - 64gb RAM - RTX 3080 12gb OC
Kev2go Posted July 25, 2018 Posted July 25, 2018 (edited) It would be great to have a controls' 'cycle' option for every single mutli-position switch, knob, etc. in the Hornet. I would much rather push a physical button or key multiple times to get the switch position I want rather than have to reach for my mouse, pause head tracking, click, reach back for stick, etc. Fully clickable cockpits are great. But reaching for and operating a mouse cursor is not realistic... or combat-practical. you just have to deal with. it. It would be impractical on the other hand to cycle through countless MFD pages and countless sub pages for changing Settings inputing data etc. ( even impossible) with a single button. When it comes to A2A weaponry and A2A operation modes. most of the work can be done without the mouse, mapping the controls to HOTAS setup. ( like it is IRL) A/G modes requires more MFD clicking due to selection of weapons, INputing paramaters with UFC ( which should be in some respects offest in the future via loading data cartridge) , and in the future operation of Targeting pod and selections or switching in between other sensors. IN the A10C you can have somewhat less MFD clicking because like in the real plane you can cycle through the various MFD pages, but at the same time A10 MFD fuctions arent as wide as the Hornets,( IE didnt have a seperate TAC and Suppport Menus, and countless other features) but even in the A10 you couldnt get around data input for some of the weapons profile setups for A/G, or for wapoint creation etc. Any Modern plane with a glass pit is going to requite a degree Interaction ( in the form of clicking) on the various MFD pages. Even so the A10's Diigtal maangement via MFD's was still deeemed far easier to use by RL Hawg pilots than the Analog Weeapons selection and management of the A10A ( its easy to see why it would be more work than working with MFD's) The only feature tI can think offsets this and replicates actual button pressing would be VR Gloves if your willing to spend the money for that simulated physical interception Edited July 25, 2018 by Kev2go Build: Windows 10 64 bit Pro Case/Tower: Corsair Graphite 760tm ,Asus Strix Z790 Motherboard, Intel Core i7 12700k ,Corsair Vengeance LPX DDR4 64gb ram (3600 mhz) , (Asus strix oc edition) Nvidia RTX 3080 12gb , Evga g2 850 watt psu, Hardrives ; Samsung 970 EVo, , Samsung evo 860 pro 1 TB SSD, Samsung evo 850 pro 1TB SSD, WD 1TB HDD
Frederf Posted July 25, 2018 Posted July 25, 2018 Unhelpful murmurs aside the reason why developers don't make key bindings for inc/dec; explicit positions; cycle; hold-else-x for every single switch is the clutter in the controls interface plus I guess dev workload and opportunity for error. Really the 2-layer (category, command) structure of the GUI is too shallow to consistently provide these control options practically. What would be needed is for each logical switch to have a setup screen a 3rd layer deep. So you'd have some 8-position knob as a single entry and you'd double click on it to enter an editing dialog where you could pick keys to increase, decrease, cycle, explicitly enact various positions, and even choose if it's pressing or releasing a key that does it. And if that wasn't enough it would be nice to have native ability to control axes via buttons and buttons via axes. It would mean a big change and a rewrite of a lot of control systems. Failing that you have to do what every sufficiently-motivated person does when faced with wanting a control that isn't in the list... you write it yourself by editing the lua s.
David OC Posted July 25, 2018 Posted July 25, 2018 I'm waiting for VR gloves or hand tracking to be a thing. The only real way around this is to build a button box and buy some MFD's, not real good for VR tho and I don't mind using the mouse with VR , for now anyway. i7-7700K OC @ 5Ghz | ASUS IX Hero MB | ASUS GTX 1080 Ti STRIX | 32GB Corsair 3000Mhz | Corsair H100i V2 Radiator | Samsung 960 EVO M.2 NVMe 500G SSD | Samsung 850 EVO 500G SSD | Corsair HX850i Platinum 850W | Oculus Rift | ASUS PG278Q 27-inch, 2560 x 1440, G-SYNC, 144Hz, 1ms | VKB Gunfighter Pro Chuck's DCS Tutorial Library Download PDF Tutorial guides to help get up to speed with aircraft quickly and also great for taking a good look at the aircraft available for DCS before purchasing. Link
Trubshaw Posted July 25, 2018 Posted July 25, 2018 Yes I agree. It is difficult to find, in the heat of battle, the clickable sweet spot with no tactile feed back no matter how good you are. (sorry I am) Track IR movement and taking my hand off the HOTAS to find and move the mouse is sometimes difficult. In my experience the best modules allow for a key bindings to be exported to a physical switch. eg: a rotating switch could be exported to rotate left and rotate right. Also in my experience the best developers get round to responding to such requests for key binding as the module matures. [sIGPIC][/sIGPIC] TrubshawRN -=SHREK 94=-
wilbur81 Posted July 25, 2018 Author Posted July 25, 2018 (edited) These 'cycle' controls already exist for many functions (CW, CWW for knobs, UP and DOWN for switches and applying to controls such as flaps switch, INS and Radar knobs etc...) so some arguments against my suggestion above don't make sense. I'm just suggesting that they offer for all (for example: Some of the HUD control panel switches). Also, many of the "Special for joystick" options are momentary only and don't stay in position once pushed when assigned to one of my cougars. Also, I own 4 cougar MFD's and use modifiers. The problem isn't the number of buttons available to me. The problem is that some functions, for whatever reason, aren't available for cycling while others are. By the way: I can guarantee that I (and probably anybody else) am faster with physical button pushing than anybody out there who's using a mouse around their pit. :-) Edited July 25, 2018 by wilbur81 i7 8700K @ Stock - Win11 64 - 64gb RAM - RTX 3080 12gb OC
wilbur81 Posted July 25, 2018 Author Posted July 25, 2018 (edited) Unhelpful murmurs aside the reason why developers don't make key bindings for inc/dec; explicit positions; cycle; hold-else-x for every single switch is the clutter in the controls interface plus I guess dev workload and opportunity for error. It would mean a big change and a rewrite of a lot of control systems. This already exists for most functions in the Hornet in the form of 'clockwise' CW and 'counterclockwise' CCW options for knobs and "up" and "down" options for switches. Doesn't seem that earth-shattering of an idea to add a few more. This is a "wish list" thread. Edited July 25, 2018 by wilbur81 i7 8700K @ Stock - Win11 64 - 64gb RAM - RTX 3080 12gb OC
Svend_Dellepude Posted July 25, 2018 Posted July 25, 2018 FC4 is coming. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
wilbur81 Posted July 25, 2018 Author Posted July 25, 2018 FC4 is coming. This is a Hornet thread.... i7 8700K @ Stock - Win11 64 - 64gb RAM - RTX 3080 12gb OC
wilbur81 Posted July 25, 2018 Author Posted July 25, 2018 Yes I agree. It is difficult to find, in the heat of battle, the clickable sweet spot with no tactile feed back no matter how good you are. (sorry I am) Track IR movement and taking my hand off the HOTAS to find and move the mouse is sometimes difficult. In my experience the best modules allow for a key bindings to be exported to a physical switch. eg: a rotating switch could be exported to rotate left and rotate right. Also in my experience the best developers get round to responding to such requests for key binding as the module matures. +1 :thumbup: i7 8700K @ Stock - Win11 64 - 64gb RAM - RTX 3080 12gb OC
Recommended Posts