Controls doesn't work before entering to Settings and pressing them.

[Fri13]

I have odd problem, where normal bindings like a TDC depress, Throttle Lift (Both) or TDC itself doesn't work until I press ESC and go to Settings and then press each controller button once. Then when I return back to cockpit everything is registered.

If I need to respawn or I restart the mission, those bindings stops working again and I need to revisit settings panel to get them working. (I don't need to bind them or anything, just press controller buttons and hats etc to get DCS to acknowledge that they exist).

 

 

 

Edit: In video it is hot start on airfield, I press weapons release or NWS/Undesignate but nothing happens, then I open settings and press those two buttons in HOTAS and they register correctly in bindings, then after returning to game the bindings work and you can see them animated as well properly.

no_input_registered.trk

[Fri13]

I did some further testing and it seems that the problem registers only limited number of functions, or changes at middle of flight. Example I can use NWS button to manage TGP for zeroing or slaving to VV. But once I land, it doesn't register to enable NWS and I must go to settings and press NWS button and back to game to get NWS working. Middle of the flight the FOV button can stop working, just after some target bombing using TGP to zoom in/out and then on third/fourth/fifth target the button doesn't anymore work and I need to press OBS button to change FOV if I don't go to settings press it again.

 

 

[LeCuvier]

That's odd. If it happens only in the Hornet I would suspect that something got messed up during the install or update process. Did you try a Repair?

Note: I have some issues in the Hornet where commands/functions simply don't work. Like, I cannot change the laser code for the Mavericks while other people can, and the FOV command doesn't work for the TGP, and the handling of the TGP in conjunction with Mavericks seems weird. The latter point might be my lack of knowldge though.

[Fri13]

I tried repair, removing VJoy and even deleted configs. But it exists only in Hornet.

the bindings (I only have real bindings in HOTAS, nothing else is ever bonded to HOTAS than real functions and rest is done using hands in cockpit) just stop working middle of flight or start of the entering cockpit and requires to go settings to click HOTAS buttons to get them registered in game.

 

it took time from me to notice this as it explains why sometimes things didn't work but sometimes did and when some functions changed anyways between updates it required new ways to do things like TGP caging was removed and target point functionality was changed so it was more difficult to spot as procedures were new.

It feels that there is like a button limitation in memory how many can exist in Hornet before it forgets them and you need to activate them visiting settings.

[Ziptie]

I tried repair, removing VJoy and even deleted configs. But it exists only in Hornet.

the bindings (I only have real bindings in HOTAS, nothing else is ever bonded to HOTAS than real functions and rest is done using hands in cockpit) just stop working middle of flight or start of the entering cockpit and requires to go settings to click HOTAS buttons to get them registered in game.

 

it took time from me to notice this as it explains why sometimes things didn't work but sometimes did and when some functions changed anyways between updates it required new ways to do things like TGP caging was removed and target point functionality was changed so it was more difficult to spot as procedures were new.

It feels that there is like a button limitation in memory how many can exist in Hornet before it forgets them and you need to activate them visiting settings.

 

Very very strange. As you've stated in seems to only be an issue for the Hornet, and not for other airframes that you own (assuming you own more than just the Hornet) - I'd recommend backing up your key binds for the Hornet and uninstalling the Hornet module - then reinstalling it. Seems like something has been correlated incorrectly during an update or something....

 

In terms of the 'feels like a button limitation' - could certainly see how it seems that way, but certainly isn't anything like that on my side. From the A10C I/II, to the Hornet, even to the Viper (very low flight hours in the Viper as of now) - there are hundreds of different combinations across the modules and they all function as intended. Especially in the A10C.

 

 

 

Cheers,

 

 

Ziptie

[LeCuvier]

I have some issues similar to this. For example, I could not change the laser codes of the MAV-E. Now that's a very simple procedure and I'm sure I did nothing wrong. Yet, yesterday I did it several times without a problem. And according to Chuck's guide (version 25-SEP-2020) you can change the TGP field of view between NARROW and WIDE using the "RAID/FLIR FOV Select Button! (China hat aft on the TM WH throttle), and that never worked for me. In fact, although the TGP is SOI, this command toggles the FOV in the Maverick display. Also China Hat Aft Long should toggle the TGO view beteen CCD and FLIR, and that command does nothing at all.

Is Chuck's guide wrong, or is it a bug, or WIP? This points to the issue that after all this time we still don't have a flight manual. And I have found that HOTAS commands which are default bindings for the TM WH throttle suddenly disappeared. So yes, I perceive some instability in the Hornet. So I will probably spend less time with the Hornet and focus on the A-10C II.

[rob10]

And according to Chuck's guide (version 25-SEP-2020) you can change the TGP field of view between NARROW and WIDE using the "RAID/FLIR FOV Select Button! (China hat aft on the TM WH throttle), and that never worked for me. In fact, although the TGP is SOI, this command toggles the FOV in the Maverick display.

Chuck's guide isn't really wrong, it's just not telling the whole story. If you have a MAV "active" (i.e. boxed, even if you don't have it displayed on a DDI) the MAV gets priority for RAID/FLIR FOV even if it's NOT TDC priority. So if you box the MAV to start cooldown, then change that DDI to something else and set priority to the TPOD DDI, the RAID button will still control MAV FOV. That is correct to RL according to ED.

Not sure why the China Aft Long isn't working for you though (don't think MAV overrides priority on that) :huh:

 

[LeCuvier]

Thanks for this info!

... Not sure why the China Aft Long isn't working for you though (don't think MAV overrides priority on that) :huh:

Is it working for you?

 

[rob10]

Thanks for this info!

 

Is it working for you?

 

Now that I try it, China Aft Long is also being blocked when MAV is active so no CCD/FLIR change on TPOD.

EDIT: searching the forum, I see that's been the way for CCD/FLIR (along with FOV) for a long time. Guess I haven't tried that with MAV in a while. You can still change them both with the appropriate OSB on the TPOD DDI (not as handy no doubt).

[LeCuvier]

 

Now that I try it, China Aft Long is also being blocked when MAV is active so no CCD/FLIR change on TPOD.

EDIT: searching the forum, I see that's been the way for CCD/FLIR (along with FOV) for a long time. Guess I haven't tried that with MAV in a while. You can still change them both with the appropriate OSB on the TPOD DDI (not as handy no doubt).

 

Thanks Rob! If that's the way the real thing works then there is no point bitching about it, even though it seems weird.

[Fri13]

Repaired DCS in full method. No fix.

Re-installed Hornet. No fix.

Cleared Hornet settings (my games). No fix.

Plugged another HOTAS and binded it. No Fix.

Updated DCS on another computer, with other HOTAS. Same problem.

 

Only on Hornet, not on any other module.

And found as well another new problem that L-39 instrument textures got wanky. So now need to hope that tomorrow patch does something there as well.

[Frederf]

I would delete (make backups if you want) the .diff.lua and control .lua s in your saved games DCS directory and the DCS World module directory for the hornet. Then run a repair, those tiny text files should download in a microsecond.

 

My guess is that you using the "load" button on the control screen and finding some file to load in a weird spot might be an issue. Normally your controls are saved in a certain place in saved games folder. If you're loading something from the DCS World program folder that could explain things. Overall I'm guessing there are disk write access issues. That would explain changes being effective while the program is running but not saved between EXE sessions. Windows heavily restricts write permissions especially to program files folders and especially for non-administrator users. Attempting to store input preferences not in the normal folder or having user permission issues (e.g. DCS is installed for User1 and you're User2) could prevent normal use.

 

My first step to diagnosing this is to make a change and try to save as a new file and see if writing this file is successful. After making two such files I would test loading one and the other to see they both load properly (say configure file1 and file2 differently from default so you can see the change).

[Ziptie]

If you are still having issues changing the FLIR display between CCD and thermal image - you have to depress and hold the RAID/FLIR button for approximately 0.5 seconds (I apologize that I don't know the specific amount of ms required of depression). Could it be that you aren't holding the command long enough? That command, will cycle between CCD and one of the thermal imaging modes - to cycle between the two different thermal imaging modes, you have to use the OSB on the FLIR display.

 

I just tried it today, a pair of IR Maverick's on board - worked as described above, as expected. Maverick was cooled down and selected while in A/G master mode and Maverick display active on LDDI, FLIR on RDDI, FLIR SOI.

 

 

Cheers,

 

Ziptie