Logbook question
-
After resolving my recent CTD in version 4.36, and remapping my joystick. I noticed my Logbook entry for my callsign was empty, showing 0 hours when it should be just over 40 hours. The file is still in the directory, about 1k in size. The default callsign/name of “Viper/JoePilot” is primary, i can see my callsign in the name dropdown field but can’t change to it.
How can i get my callsign reselected?
-
How did you resolve your CTD issue? Did you do a fresh re-install of BMS? If so, did you back up yourCallSign.lbk beforehand? And did you restore your back-up to Falcon BMS 4.36\User\Config?
Delete all of the Viper. files, e.g. Viper.ini, Viper.lbk, etc. When you look again under Logbooks you should see only your log.
-
@Crassus I resolved the CTD by deleting my \Falcon BMS 4.36\User\Config\d3d11.dsp file.
Here is the forum link: [https://forum.falcon-bms.com/topic/23736/bms-no-longer-starts/4?_=1670097834313](link url) -
Well I’m stumped on this one.
-
Is there no one that has encountered this?
The default Joe Pilot is selected in the logbook, I can click the dropdown and see my previous username/callsign, but cannot select it. The 40 hours I had logged there are gone.Any ideas on how this can be fixed?
Are there any details available on the logbook format, maybe I can write a program to edit it.
-
@jcook said in Logbook question:
Is there no one that has encountered this?
The default Joe Pilot is selected in the logbook, I can click the dropdown and see my previous username/callsign, but cannot select it. The 40 hours I had logged there are gone.Any ideas on how this can be fixed?
Are there any details available on the logbook format, maybe I can write a program to edit it.
There is a logbook editor out there floating around, that would allow you to at least read your former logbook (if it is not corrupted). At that point you could create your pilot again and populate it with all your hours/medals/etc… and then use that.
-
@Icer i had read this was a very old editor and required some support libraries and files thst would need to be added.
Is the logbook format detailed anywhere? Maybe i can just write a new editor program.
-
@jcook did you back up your logbook?
-
@JUmpstart5179 Probably just going to have to reinstall.
-
@jcook Back up your .lbk, .plc, .pop, and .rul I do this anytime I have a clean install and it saves everything.
-
@JUmpstart5179
Recreated same name and callsign as new pilot. Then copied in the previously named files overwriting the newer empty files. Made no difference - still cannot select that name/callsign - it defaults to the JoePilot/Viper. -
@jcook said in Logbook question:
@Icer i had read this was a very old editor and required some support libraries and files thst would need to be added.
Is the logbook format detailed anywhere? Maybe i can just write a new editor program.
It is old but works fine, just tested it. It does has 4 support dll’s in it’s folder that came with it. I just run it from it’s download folder and then point it to mu user/xxx.lbk file. If you can’t find it PM me your email and i’ll zip it up and send it to you.
-
If it were me. Id reinstall fresh BMS and try my logbook. If it still doesn’t work then it is corrupt file and Id start a new one or replace it with the backup I always make
-
Do you still have a copy/link? The one on the website is down
-
@toncey sent you a Dropbox link in Chat… let me know if all is good…
-
Works perfectly thank you!