Logbook not tracking flights

[Vettefan]

Small thing to most, I guess: I flew 3 sorties but none was being logged in the DCS Logbook on my end. The OH-58D(R) section remains empty (I like having flights logged there for some statistical analyses I perform on my flights).

 

Thanks for looking into this.

 

Edit #1: A full repair of my DCS installation did not change the situation, yet.

Edit #2: Logbook not tracking on any map.

Edit #3: Other modules are currently being tracked in logbook.

Edited June 6, 2024 by Vettefan

[DimSim]

I just noticed this, flew a few Instant Action flights and later checked log book to find zero time logged.

[Mud]

Same issue here.

[firefox121]

+ one here too

 

[Mud]

A little update: The time does count for your general, overall logbook time. I also has a look in the logbook.lua and could not find a reference for OH-58.

[Mud]

I see on Discord that Dan from Polychop said that his has been fixed internally.
So hopefully it'll be sorted in the next DCS update.

[One Eyed Ross]

OK, so two weeks, then.

[Sobiratel]

Still broken, worse now. Doesn't even log time in the General Tab of Logbook after recent update.

[The_GhostRider]

It's more likely a DCS problem, my logbook time is randomly updating depending on the A/C since the update.

[ac5]

Same, even worse here... After last update,

no time is added to the logbook, at least not from the f-16 and F-18.

Just single player missions started from the ME.

[Warez27]

You can fix this bug by yourself.

1. Backup you logbook file. Copy C:\Users\<Your profile name>\Saved Games\DCS.openbeta\MissionEditor\logbook.lua file to somewhere else.

2. Add to logbook.lua section:

["OH58D"] = 
{
    ["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 ["OH58D"]

near other planes/helicoptes to look similar and pay atention to commas.

[ac5]

8 hours ago, Warez27 said:

You can fix this bug by yourself.

1. Backup you logbook file. Copy C:\Users\<Your profile name>\Saved Games\DCS.openbeta\MissionEditor\logbook.lua file to somewhere else.

2. Add to logbook.lua section:

["OH58D"] = 
{
    ["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 ["OH58D"]

near other planes/helicoptes to look similar and pay atention to commas.

Well fine, thanks... But firstly after that, the Logbook will start recording the hours etc, AS IT SHOULD, and as it is has been doing before ED broke it? Secondly, it is not our job to fix the Logbook.....

[ac5]

Update today DCS 2.9.7.58923.

In a RANDOM fashion, the logbook records hours and all else,

sometimes it does, sometimes it does not..... All single player missions.

Go figure....

[Warez27]

On which modules logbook records are broken?

[Tom Kazansky]

@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:

 

Edited October 4, 2024 by Tom Kazansky

[Warez27]

I have same bug. ED reported on this error what CH-47 is in early access.

So I think this bug have low priority and will be fixed when CH-47 get more mature.

This bug was not fixed by the last patch. 

Edited October 4, 2024 by Warez27

[Warez27]

Bug with logbook for CH-47F fixed in 2.9.9.2280