Flying the F4E fully manually without the help of the AI optional but possible

[Lau]

Hi HB,

ED made this possible in the AH64D with the option "aircraft Control Priority" that can be set to "Equally Responsible" for both pilots allowing the single player to fly manually in both seats without the AI taking over the flight controls. I have seen the temporary bindings that allow the pilot to action some of the WSO functions without having to jump to the backseat and hope these will remain and become optional since they are not doing any harm but helping the single players enjoy the module and only use AI assistance when convenient, with the possibility to deactivate it at any time. I am of course aware that JESTER contract serves that purpose, I am just hoping that HB will keep working in improving the single player experience also without AI assistance in a fully manual environment, helping singleplayers to use some shortcuts bindings from the front seat to fully operate the jet without a human WSO. 

Thanks,

Lau

[Zabuzard]

Note that you can technically always expose yourself any binds you want to the front seat.

Therefore, go to your DCS Install/Mods/F4E/Inputs/Pilot/keyboard/default.lua and add anything from the corresponding WSO lua file that you want to use. You can do this with any aircraft in DCS, the game doesnt care.

[Lau]

Cool, thanks for the feedback, I will try !

Congrats on your videos, please keep them coming 

 

[LeCuvier]

On 6/17/2024 at 11:17 AM, Zabuzard said:

Note that you can technically always expose yourself any binds you want to the front seat.

Therefore, go to your DCS Install/Mods/F4E/Inputs/Pilot/keyboard/default.lua and add anything from the corresponding WSO lua file that you want to use. You can do this with any aircraft in DCS, the game doesnt care.

But, unless something fundamental has changed,  the next update will restore the "original" default.lua, without these additions. Correct?

[Zabuzard]

Yes. There are tools though to persist changes like that. For example:

https://github.com/Quaggles/dcs-input-command-injector

[Biggus]

DCS also seems to back up my modified inputs, so after an update I just go to my main DCS folder and drag the backed up folders back into the main directory.  It's relatively painless.

[LeCuvier]

1 hour ago, Zabuzard said:

Yes. There are tools though to persist changes like that. For example:

https://github.com/Quaggles/dcs-input-command-injector

I have been using this tool for quite some time now, and I recommend it to everybody who has made additions to the stock "default.lua" or intends to do so.

[LeCuvier]

Just now, Biggus said:

DCS also seems to back up my modified inputs, so after an update I just go to my main DCS folder and drag the backed up folders back into the main directory.  It's relatively painless.

This is ok for "mature" aircraft modules that see very few additions or changes to the stock files. But this thread is about the F4-E which is in Early Access. And modules in EA tend to see additions and changes to the stock files with just about every update. And when you restore your backed-up files you lose these updates. In other words, you freeze functionality. Better use the @Quaggles tool!

[Biggus]

Perfectly valid point of view, that does happen from time to time.  I personally tend to restore the backed up file and if unexpected behavior is observed, I delete the edited lua and repair, and then edit the fresh input lua.  But Quaggles' tool is certainly a great option.  Different strokes, I guess.