Logbook issues - completely reset

[Hyperion35]

On Friday, after the last of many frustrating attempts to complete a mission in a campaign, I finally decided to go ahead and just edit the logbook.lua file so that I could pass on to the next mission. When I re-opened DCS, it showed all of my campaigns as inactive. I assume that I must have mistyped something during the editing. But now when I go back to the logbook with the intention of editing it to fix my mistake, the entire logbook has been completely reset. No campaigns, no statistics, nothing, just the basic default values for a new pilot. It shows that the file was last modified on July 10th, which sounds about right.

 

This does not seem like it should be the normal behavior. Instead of an error and being unable to load my campaigns, all of my campaign progress from every single campaign is gone. Windows does not show any restore options, unfortunately, and I suppose it is my fault for not backing up the file before editing it, but I had assumed that if I made a mistake I'd be able to go back and fix it. I have an old backup logbook from 2018 that I had saved a while back. Is there any other way to restore my logbook? Or should I jusr take a break from DCS for a while?

[TOViper]

On Friday, after the last of many frustrating attempts to complete a mission in a campaign, I finally decided to go ahead and just edit the logbook.lua file so that I could pass on to the next mission. When I re-opened DCS, it showed all of my campaigns as inactive. I assume that I must have mistyped something during the editing. But now when I go back to the logbook with the intention of editing it to fix my mistake, the entire logbook has been completely reset. No campaigns, no statistics, nothing, just the basic default values for a new pilot. It shows that the file was last modified on July 10th, which sounds about right.

 

This does not seem like it should be the normal behavior. Instead of an error and being unable to load my campaigns, all of my campaign progress from every single campaign is gone. Windows does not show any restore options, unfortunately, and I suppose it is my fault for not backing up the file before editing it, but I had assumed that if I made a mistake I'd be able to go back and fix it. I have an old backup logbook from 2018 that I had saved a while back. Is there any other way to restore my logbook? Or should I jusr take a break from DCS for a while?

 

Did you change the code-page of the file?

I remember I had problems with that when creating a autoexec.cfg once upon a time.

 

You should of course NOT take a break from DCS, you might wanna re-fill your logbook again :joystick:

[Rudel_chw]

Unfortunately, the best way to face these type of accidents, is to have backup copies. That’s why I have all my important files on a Cloud, including DCS data .. I use a Cloud that support versions, so I can go back to any change, useful if one doesn't detect the loss right away:

 

[Hyperion35]

Did you change the code-page of the file?

I remember I had problems with that when creating a autoexec.cfg once upon a time.

 

You should of course NOT take a break from DCS, you might wanna re-fill your logbook again :joystick:

 

I'm not sure what you mean about the code-page. I didn't do anything that should have changed the file or filetype, and I was able to confirm that this is the original logbook file based on the creation date of the file itself, so DCS didn't go and create a new logbook.lua file.

 

Dunno about taking a break or not. It was nice to fly a different simulator last night where I didn't have to go in and mess with a bunch of files, I could just load it up and fly. I still don't understand how this could happen.

[Hyperion35]

Unfortunately, the best way to face these type of accidents, is to have backup copies. That’s why I have all my important files on a Cloud, including DCS data .. I use a Cloud that support versions, so I can go back to any change, useful if one doesn't detect the loss right away:

 

The problem is that the logbook file changes constantly. I had an old logbook file backed up from 2018, probably a situation where I must have made some sort of logbook change then as well. And yeah, I should have backed up the file before editing it this time too. But I also wasn't expecting something like this to happen, I figured either the changes to the logbook would work or they wouldn't, not that it would erase the entire contents and overwrite it with a new and empty default logbook. But to properly back up a logbook you'd pretty much have to do it each time you fly.

[Rudel_chw]

... But to properly back up a logbook you'd pretty much have to do it each time you fly.

 

Correct, that's why I placed the MissionEditor folder on a Cloud drive, leaving a Folder link on its place. That way it is constantly being backed up, each time it changes.

[TOViper]

I'm not sure what you mean about the code-page. I didn't do anything that should have changed the file or filetype, and I was able to confirm that this is the original logbook file based on the creation date of the file itself, so DCS didn't go and create a new logbook.lua file.

 

 

This I meant:

 

 

From one to another day my autoexec.cfg in the userprofiles config foder got another coding, and from this moment on DCS began to behave strange.

Took quite a while until I found out, also using help of other guys around here.