Tom Kazansky

Oder umbenennen, z.B. in: DCS [am Ende doch keine] falsche Entscheidung Aber ohne Witz: freut mich zu hören, und zwar für dich.

@Dovivan I'm curious about that too.

Good to read. I assume the overclocking is not really part of the solution, is it? Just to clarify, were there any of those stutters after resetting the bios to default (without overclocking)? And how much did the DCS performance improve after overclocking?

Yepp, and you need to redo your modifiers for every module, in case you use own modifiers. If you use the same set of own modifiers for each module, simply copy the first correct modifiers.lua to each input folder of the other modules. Saves time.

"next update" is my favourite "soon" in DCS.

me: "hi, what are you able to do?" AI: "I'm here to assist you with questions related to the DCS (Digital Combat Simulator) and its various modules, including providing information about aircraft, missions, and gameplay mechanics. If you have specific questions about a product or need help with a particular feature, feel free to ask!" edit: me: "do you know bignewy?" AI: "Bignewy is a member of the DCS community and is recognized for his contributions, particularly in testing and support roles. He is mentioned in the context of the L-39 Albatros flight manual as part of the testing team."

That's exactly the case I am curious about. (Edit:) next time, could you please check whether the modifiers.lua of that module shows any entries (odd or correct ones as I described in my last post above yours)?

Those spam attacks always follow the same pattern. Is there any way for moderators to filter or hold back those posts or users? Maybe by reducing the amount of allowed posts per hour for new users? Where is the AI when you need it? Could those spam posts be identified automatically by comparing their content which is 99% the same but not 100%?

interesting. in the case of lost keybinds with modifiers, is the "modifiers.lua" file still there and does it show some odd entries (i.e. do the ID's in the modifier.lua fit to the ID's of the input devices? (path e.g. C:\Users\{username}\Saved Games\DCS\Config\Input\A-10C\modifiers.lua ["JOY_BTN4"] = { ["device"] = "LEFT VPC Throttle MT-50CM3 {D74506E0-DD2F-11ed-8004-444553540000}", ["key"] = "JOY_BTN4", ["switch"] = false, matches: C:\Users\{username}\Saved Games\DCS\Config\Input\A-10C\joystick\LEFT VPC Throttle MT-50CM3 {D74506E0-DD2F-11ed-8004-444553540000}.diff )

even when the DCS keybinds seem to be gone, sometimes (btw. every time I saw them gone) they are still there as a file with the old ID in its name. Only the USB ID of your input device may have changed. here is a thread with some answers and the solution for those cases:

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.