F18 Keybinds after 07/18/18 Update

Don't think the TDC-axis has been "released" for F-18 yet. I've been unable to assign it since the module came out.

Well, I use an X-55 and before yesterday I was able to directly bind TDC to the ministick on the throttle (the mouse-like one) in the axis assign page, without using the Saitek software.:huh:

From yesterday update the TDC line in the axis assign page is not selectable anymore.

Strange...

Well, I use an X-55 and before yesterday I was able to directly bind TDC to the ministick on the throttle (the mouse-like one) in the axis assign page, without using the Saitek software.:huh:

From yesterday update the TDC line in the axis assign page is not selectable anymore.

Strange...

Just tested myself, TDC slew worked fine on loading aircraft (though i had updated my binding files as a previous post said to). TDC slew also does look bindable to me (not greyed out), but i didn't actually try for fear of breaking it.

These are "Throttle Designator Controller - Horizontal Axis" and "... - Vertical Axis" that bound.

Custom joystick job though, just an arduino powering it.

Too bad i read this too late, rebinded them, took les than 5 minutes rebinding those missing, fresh save profiles and voilà. Was faster to rebind them that read this entire thread.

Just confirming that a re-bind has no ill effect? I’d rather just remap than dive into file editing. Thanks!

TDC is unbound, but the greyed out column is not the one you wanted, the axis are there for it and it works fine.

TDC is unbound, but the greyed out column is not the one you wanted, the axis are there for it and it works fine.

Thanks Pikey!

Just tested myself, TDC slew worked fine on loading aircraft (though i had updated my binding files as a previous post said to). TDC slew also does look bindable to me (not greyed out), but i didn't actually try for fear of breaking it.

 

These are "Throttle Designator Controller - Horizontal Axis" and "... - Vertical Axis" that bound.

TDC is unbound, but the greyed out column is not the one you wanted, the axis are there for it and it works fine.

Got it! I'll check this evening.

Thanks guys!

Think I found a solution.

...

And to add... it would have made much more sense to just use device 13 for the new NVGs. Then backwards compatibility would have been maintained, there would have been no unused device id, and NVG support would still work.

Thanks for this quick find abelian! I was going to compare .lua files between old and new to find the culprit and fortunately you beat me to it. It would have taken me a while before I looked into "devices.lua"!

I think the fix you propose is safe and will not cause problems going forward.

The developer probably didn't realize what he did to us when he removed the duplicate. He should have left it there with a comment. It wouldn't have done any harm. And the shift of the references after 38 could have caused problems for other developers.

PS: I saw you used the IMGUR site for file comparison, and you are probably happy with that. I use the Compare function in Notepad++ (under Plugins) which is very quick and effective. Does the IMGUR functionality have advantages over Notepad++?

Edit: A word of caution though: the replacement of "cd38" with "cd13" will only fix bindings for buttons that are on the F-18's throttle or stick. I have mapped buttons from other F-18C devices to stick, throttle and button box, and some of these devices have references > 38. For example, the RADAR device was 43 and is now 42. So, rather than trying to find and fix all these references, I have decided to re-create my .diff.lua files by re-doing all bindings.

Any chance they'll hotfix this? Or will it simply be left as is?

Confirming, a lot of keybinds don't work for me. For instance I had to rebind the commands for extending and retracting the speedbrake as well as opening the comm menu, yet flaps, gear and refueling probe bindings were completely unaffected and continued to work.

This is one reason I do like CH manager keybindings when it's playing nice with win 10. Going to miss it when I change to a VKB stick.:cry:

Is there a fix, for this issue ?

Thanks

Is there a fix, for this issue ?

Thanks

to be honest, on my side, took me 5 minutes to redo those that disapeared and 10-15 minutes reading all the threads and post about it trying to find a fix or ever 24 hours the time it takes to wait to see smeone coming up with a fix... i let you guess which is faster. I was just too impatient to wait for it so i had to redo them, and save back all Profiles After as latest 2.5.2 patch, we never know. :)

You're right, actually

Thanks

That's what I eventually did anyway as I realized this will probably happen again. I'm just glad it didn't affect my other modules. Then it would have taken much longer.

That's what I eventually did anyway as I realized this will probably happen again. I'm just glad it didn't affect my other modules. Then it would have taken much longer.

It's less a pain when it's a fresh aircraft, since we mostly flight it a lot now and it's new, all bindinds are mostly fresh in our minds, i wouldn't find it as funny if for exemple it happened to the Harrier which i haven't flown since the Hornet came out, lots of bindings i forgot, so redoing them would had been a bit more tricky.

It's not an issue that should be fixed.

During development stuff changes which affects config files, and this means the existing ones have to be replaced. Attempting to merge a user's custom configs with new ones (either during the update or manually) is prone to errors, which would make identifying actual problems much more difficult.

Best advice is to leave controller default as much as possible, and do the remapping (both keybinding and curves etc.) in the respective profiling software. Takes a bit of effort, but is far more robust.

It's not an issue that should be fixed.

 

During development stuff changes which affects config files, and this means the existing ones have to be replaced. Attempting to merge a user's custom configs with new ones (either during the update or manually) is prone to errors, which would make identifying actual problems much more difficult.

 

Best advice is to leave controller default as much as possible, and do the remapping (both keybinding and curves etc.) in the respective profiling software. Takes a bit of effort, but is far more robust.

It might be, but ever since i bought DCS in 2010, that is the first time i reacall ever loading a Saved Profile doesn't work, so it's not that commun it cause issues. So the few many times it happens, we won'T be yelling at ED for this as you said, it's part of the deal and evolution of a constant updating game, specialy when new features are being implemented requesting new bindings added.

Not wanting to wade through another 12 pages of forum to find an answer to be honest, but same issues here as I read the first 3 pages. Cannot fire cannon, greyed out cannot bind.

Any answers, news or fix info please☺?

Not wanting to wade through another 12 pages of forum to find an answer to be honest, but same issues here as I read the first 3 pages. Cannot fire cannon, greyed out cannot bind.

 

Any answers, news or fix info please☺?

It might be, but ever since i bought DCS in 2010, that is the first time i reacall ever loading a Saved Profile doesn't work

that is correct.

I would just rebind everything. The fix is a lua file change a few posts up if you want to go that route. But if you didn't save your profile from before, you may as well rebind.

Well, if it's something that easy to do, why haven't we heard this from an official?

No clue there is always strange bugs on open beta if you look in the bugs section there is even one related to radar that several people have experienced with no official word either.

Try the fix posted in the thread a few pages back but people report not being able to load profiles into the game since 2010.

It's an alpha release still and as systems get added controls will change, part of running the beta release and I'm sure that this will happen again as systems get added/modified.

Does fix get applied prior to update or after update I'm not disputing the fact that errors will pop up. I would just like to have someone from the ED team tell us that the fix we have works and will not corrupt anything else. Not from one of the members, someone from the Developers Team...because this has to have been affecting them (the testers) as well. It's gotta be annoying for them as well....so if someone says they have the fix...please, ED, acknowledge that this will work or not work either way...would it take that much time to chime in here?

I really don't get why you all go batshit crazy here... early access is not a finished product and subject to change. It's not even close. We all jumped willingly straight into the punjistick called beta. If it was my project, I couldn't care less about this thread or similar one's until my product is finished and tbh I wouldn't care here as well, if it weren't for the fact that this topic pops up 20times a day on my feed.... relax, sit it out, swallow it, whatever floats your boat but don't stress so much about minor, not gamebreaking issues. Please.

Gesendet von meinem SM-G935F mit Tapatalk

Confirmed here as well. Outstanding effort abelian!

Worked for me too. Thank you Abelian.