Tom Kazansky

Thanks, but that didn't help with those kind of stutters in those days. (Haven't been flying/testing too much recently.)

Yeah, waiting for announced modules in DCS is like staring at a ticking clock. Time goes by faster by doing something interesting like @Rudel_chw suggested. There is no piece of software that thought me more patience than DCS. On the other hand, if I was a creator of DCS modules I would be concerned about my priduct if a community patiently waits for it without asking for news. So I think you did the right thing, @RodentMaster, fwiw.

+1

still there. I see it is reported, so I just want to add the following just for info: DCS 2.9.8.1214 my CH-47F Chinook flight time is not tracked in the CH-47F section of the logbook. the flight time is tracked in the general (total) flight time, so are the landings and deaths, but the CH-47F section of the logbook shows "0" on any value. others like F-16C do work. There is/was no entry in my logbook.lua file named "CH-47F" or "CH-..." or "CH...". It simply was not there. But the ingame Logbook shows the CH-47F (with all values at "0") So I tried and inserted this one manually into the module list of my Pilot at the end of the list*: ["CH-47F"] = { ["flightHours"] = 0, ["deaths"] = 0, ["agKills"] = 0, ["static"] = 0, ["aaKills"] = 0, ["ejections"] = 0, ["landings"] = 0, ["refuelings"] = 0, ["nighttime"] = 0, ["totalScore"] = 0, ["naval"] = 0, ["daytime"] = 0, }, -- end of ["CH-47F"] This did not change the fact that there is anything tracked there. I see my total deaths, landings and flighttime do(es) count upwards , while all values in the inserted CH-47F section still stay 0. *Interesting fact: after inserting the above at the end of the list and starting DCS, doing 1 free fliight and exiting DCS, the ["CH-47F"] =...end of ["CH-47F"] text moved in the logbook.lua from the end of the list to a spot between my L-39C and my A-10A. Don't know what this is all about.

@Warez27 DCS 2.9.8.1214 - 02.10.2024 my CH-47F Chinook flight time is not tracked in the logbook.lua edit: correction: the flight time is tracked in the general (total) flight time, so are the landings and deaths, but the CH-47F section of the logbook shows "0" on any value. others like F-16C do work. There is/was no entry in my logbook.lua file named "CH-47F" or "CH-..." or "CH...". It simply was not there. So I tried and inserted this one manually into the module list of my Pilot at the end of the list*: ["CH-47F"] = { ["flightHours"] = 0, ["deaths"] = 0, ["agKills"] = 0, ["static"] = 0, ["aaKills"] = 0, ["ejections"] = 0, ["landings"] = 0, ["refuelings"] = 0, ["nighttime"] = 0, ["totalScore"] = 0, ["naval"] = 0, ["daytime"] = 0, }, -- end of ["CH-47F"] This did not change the fact that there is anything tracked there. But I see my total deaths do count upwards when I cash my CH-47F fatally though, while the ["deaths"] = 0 in the inserted CH-47F section still stay 0. *Interesting fact: after inserting the above at the end of the list and starting DCS, doing 1 free fliight and exiting DCS, the ["CH-47F"] =...end of ["CH-47F"] text moved in the logbook.lua from the end of the list to a spot between my L-39C and my A-10A. Don't know what this is all about. already reported:

Any news about those stutters after yesterday's DCS 2.9.8.1107 ?

well, sure? (edit:) well, maybe without the door (you can remove it, can't you? I don't own the Gazelle) edit 2: you can:

By the 2nd picture of OP, I would exclude the BO-105. There is no such canopy strut junction on the BO: And I have a hard time finding this junction on a AH-1W picture so far.

edit: here is an explanation of the background of that intended behaviour:

+1

No worries. Guess you've been driven by hope. I appreciate that attitude these days.

well : "Edited June 18, 2022 by myHelljumper"

Vielleicht ist das Manching im Nebel auf der neuen Germany Map

That's a perfect tutorial of what to do and what I did and very helpful to understand what's going on when keybinds seem "gone". Every new player should read this, but I suspect it might be as helpful as it might be scary for them.

That"s right. But that's not the only cause for a change of USB controller ID's. If so, I wouldn't have had this issue for the last 6 years but I had it twice since then. The last time it happend, I updated the firmware of my controllers before. Not every update caused an ID change though. Is it really that hard, to let DCS ask for something like: "DCS detected new controller ID's. If you did not change your controllers, please 1.) move your stick 2.) move your throttle 3.) move your rudder pedals ... or skip." Is this too naive?

A simple copy and paste does not work without the renaming of the files with the new USB ID and adjusting the modifiers lua's, as explained above. (Never used any tools for that, but they could be very useful I assume)

100% agreed. I just wanted to deliver an explanation in case somebody restores only the keybindings and is confused by the fact that all buttons that use a modifier don't appear in the bindings and don't work.

This is correct but does not take care of the modifiers in case you created modifiers. If you don't want to fiddle with the modifier lua's, you can always simply create the same modifiers again in the game in case you have to restore lost bindings or ID's.

not too long ago, I had a change of USB ID after a simple firmware update of my controlers. Not every firmware update did this though.

Hi, there is no cloud saving for config or settings in DCS. I prefer to save the INPUT directory, but this thread might give more clues:

Moin, ich möchte noch anmerken: Selbst wenn durch einen solchen oder anderen Wechsel der USB ID deiner Eingabegeräte deine Belegung in DCS mal "weg" sein sollte, sind noch alle Belegungen im Input Verzeichnis von DCS als Datei da. Um sie wieder nutzen zu können, muss man den Dateinamen mit der alten ID einfach umbenennen in einen mit der neuen ID. (Die neue ID und den Dateinamen bekommt man indem man einfach eine beliebige Belegung des betreffenden Eingabegerätes abspeichert. Dadurch entsteht zusätzlich zur alten Belegungsdatei eine Neue.) edit: ich erinner mich dunkel, dass es auch ne Datei für die Modifier für jedes Modul gibt bei der man entweder die ID's von Hand ändern muss, oder man erstellt die Modifier einfach schnell neu, wie gewohnt, in den DCS Control settings im Spiel. Die dunkle Erinnerung bezieht sich auf die erstgenannte Methode.

Yeah most probably. But if this should be an excuse for those long time floating numbers it does not strengthen my trust in the 3rd party system for niche modules. I leave it to others to decide whose problem this could be in the future.

ED shop states the only jet done by ED which still is in EA is the Viper. A-10C II and Hornet aren't EA anymore.

No worries. Thanks for the answer and the video.