Release [Explorer's Application] Captain's Log
- Thread starter Genar-Hofoen
- Start date
One thing I found with the very latest version 2.1.3 (as I've already pm'd Genar-Hofoen about) is that it still doesn't auto upgrade my existing DB's. However, starting from scratch and letting it generate all the necessary files in the C:\..\..\AppData\Local\CaptainsLog2 folder (after removing the old files first), then importing journals in to a new DB works without issue.
GooberTech, there are usually message boxes that appear when the application has issues or doesn't load. If you could post or link the error messages it would help the developer identify the exact problem area
GooberTech, there are usually message boxes that appear when the application has issues or doesn't load. If you could post or link the error messages it would help the developer identify the exact problem area
"All kinds of errors" simply isn't enough info to go on.
My apologies. I get a system memory read error. I also get a "your user doesn't have permission to run this" error message (I am the system admin and only user on my PC. I even tried running the launcher in admin mode). It also flags windows 10 and my avast anti virus. I tell windows to run it anyways and I tell avast that I trust this program. I get one of the previous error messages or nothing happens at all. I will post screen shots when I am off work later tonight if that isn't enough info.
Edit, running windows 10 64 bit and yes I uninstalled and deleted the local file of the previous version as instructed.
My apologies. I get a system memory read error. I also get a "your user doesn't have permission to run this" error message (I am the system admin and only user on my PC. I even tried running the launcher in admin mode). It also flags windows 10 and my avast anti virus. I tell windows to run it anyways and I tell avast that I trust this program. I get one of the previous error messages or nothing happens at all. I will post screen shots when I am off work later tonight if that isn't enough info.
Edit, running windows 10 64 bit and yes I uninstalled and deleted the local file of the previous version as instructed.
I build and develop this on Windows 10. There are no viruses infecting it and it is not malware.
I lost the password to my Class II code signing certificate about 2 weeks ago so I can no longer sign the binaries like I have been doing for previous releases - which is why Windows 10 whines when starting the installer. Obtaining a new class II code signing certificate is going to take time and money, and I hardly receive any donations at all so it basically has to come out of my own pocket - so that's on a very low priority at the moment.
As well as uninstalling CL2, try renaming any CaptainsLog2 folder residing in %localappdata%.
Oh and uninstall Avast - I wouldn't trust that or any other of the big antivirus products - they're not needed these days and I know saying this is going to be contentious, but they're nothing more than bloated pieces of software made by companies for whom it's in their self-interest to display scary big red alert windows at anything that runs code. And I used to run Avast, Eset, Norton... you name it I've ahd them running on my PC's in the past.
Windows Defender is more than adequate at keeping nasties away - as long as you're not in the habit of browsing dodgy websites with equally dodgy malware-serving javascript.
I also scan every single CL2 installer package before uploading them to my server and my alternate Dropbox download location. It would be remiss of me to spread viruses in my programs.
Anyway like I mentioned - try removing or renaming your CaptainsLog2 folder in %localappdata% then running CL2.
Try also downloading the installer from the alternate download link if you haven't already.
I reverted the application toolset to Python 3.4 32-bit, and also using the older method of turning the code into an executable, because those both work and are proven over the many Captain's Log releases to be reliable.
So I think in your case, your errors are occurring due to something bad happening with the CaptainsLog2 folder.
Regards o7
I build and develop this on Windows 10. There are no viruses infecting it and it is not malware.
I lost the password to my Class II code signing certificate about 2 weeks ago so I can no longer sign the binaries like I have been doing for previous releases - which is why Windows 10 whines when starting the installer. Obtaining a new class II code signing certificate is going to take time and money, and I hardly receive any donations at all so it basically has to come out of my own pocket - so that's on a very low priority at the moment.
As well as uninstalling CL2, try renaming any CaptainsLog2 folder residing in %localappdata%.
Oh and uninstall Avast - I wouldn't trust that or any other of the big antivirus products - they're not needed these days and I know saying this is going to be contentious, but they're nothing more than bloated pieces of software made by companies for whom it's in their self-interest to display scary big red alert windows at anything that runs code. And I used to run Avast, Eset, Norton... you name it I've ahd them running on my PC's in the past.
Windows Defender is more than adequate at keeping nasties away - as long as you're not in the habit of browsing dodgy websites with equally dodgy malware-serving javascript.
I also scan every single CL2 installer package before uploading them to my server and my alternate Dropbox download location. It would be remiss of me to spread viruses in my programs.
Anyway like I mentioned - try removing or renaming your CaptainsLog2 folder in %localappdata% then running CL2.
Try also downloading the installer from the alternate download link if you haven't already.
I reverted the application toolset to Python 3.4 32-bit, and also using the older method of turning the code into an executable, because those both work and are proven over the many Captain's Log releases to be reliable.
So I think in your case, your errors are occurring due to something bad happening with the CaptainsLog2 folder.
Regards o7
If I implied I didn't trust you or your software, I sincerely apologize. I was trying to give any info I thought would help.
I will disable my anti-virus and rename/re-delete the local folder as instructed and try again. If it doesn't work I will post screen shots of the error messages. Thank you so much!
I will look for a link for donations as I would happily support the continued development of such amazing 3rd party apps that greatly enhance the enjoyment of Elite Dangerous.
Nah I wasn't taking offence - I take pride in what I do and take pride in getting it right - the 2.1.x release has been a particularly problematic one for me - I've been taking lots of valuable feedback not only here but especially on my Captain's Log Discord server over the last 4 days and have been pulling all-nighters to get 2.1.x straightened out - I event went as far as repairing a guy's GALAXY.db last night over Discord (I can't do that for everyone though, that'd be like a full time job
)A lot of the bother was due to trying to update my toolset to Python 3.5 64-bit - combined with trying to use a new method of building the code into an executable, which interacted in unwelcome ways with Windows 10. That's why I reverted back to the tried-and-working 32-bit Python 3.4 for the 2.1.2 and 2.1.3 releases.
I wanted to get 2.1.x properly running for when ED 2.4 goes live, which is tomorrow.
And of course, forum text never ever comes out right - you can't properly have a conversation on forums
Anywhoo - hope you get 2.1.3 up and running!
Regards
Values are looking better, but still some discrepencies unfortunately.
CL WW TFC 459098 EDD 715026
CL WW TFC 397682 EDD 619374
CL WW TFC 441552 EDD 687699
CL HMC TFC 406122 EDD 445064
CL R TFC 304816 EDD 305795
CL ELW 231152 EDD 645800
CL WW TFC 459098 EDD 715026
CL WW TFC 397682 EDD 619374
CL WW TFC 441552 EDD 687699
CL HMC TFC 406122 EDD 445064
CL R TFC 304816 EDD 305795
CL ELW 231152 EDD 645800
An estimate is an estimate after all
But yeah it depends on the implementation of the formula, and if there are still bugs in it or not - further revision and refinement to the calculation will happen in new releases.
Just to reinforce the point that nowadays running third-party tools like Avast is just as likely to increase your attack surface as reduce it, look at what happened with CCleaner: https://arstechnica.com/information...millions-delivered-mystery-payload-to-40-pcs/
I've long since dumped all third-party tools in favour of Windows Defender.
I've long since dumped all third-party tools in favour of Windows Defender.
It works!
Speaking of 2.4, do you know if 1.4.4 can read the log files after the update? I know 2.1.x is the bees knees, but I'm on a year-long, 7500+ jump voyage and so can't use 2.1.x until I get back
Thanks for keeping CL1 working all this time! [up]
UPDATE: It works fine with 2.4 - Yay!
Speaking of 2.4, do you know if 1.4.4 can read the log files after the update? I know 2.1.x is the bees knees, but I'm on a year-long, 7500+ jump voyage and so can't use 2.1.x until I get back
Thanks for keeping CL1 working all this time! [up]
UPDATE: It works fine with 2.4 - Yay!
Last edited:
Speaking of 2.4, do you know if 1.4.4 can read the log files after the update? I know 2.1.x is the bees knees, but I'm on a year-long, 7500+ jump voyage and so can't use 2.1.x until I get back
Thanks for keeping CL1 working all this time! [up]
UPDATE: It works fine with 2.4 - Yay!
As long as Frontier keep that one valuable little line in the old netlogs, CL 1.4.4 will keep working as it has always done.
If you are having problems with 2.1.3
It's come to my attention that there's a specific problem with 2.1.3 not loading the GALAXY.db - the error windows being posted in the discussion here is the symptom.
There is a way to fix this. The problem is being caused by the database version number marked within the GALAXY.db being incorrect. For some reason the database migration tool Captain's Log uses, is correctly altering the DB structure, but is not marking the database revision number afterwards.
Here is how to fix that:
1) You will need to download and install SQLite Admin, get it from here :http://sqliteadmin.orbmu2k.de/
2) Once installed, run SQLite Admin, and load the GALAXY.db into it
3) Click on the Edit Data tab
4) On the left-hand list of tables, click on the alembic_version table. You should now see the data for that table, which is basically a version_num - it's a hexadecimal number.
5) The correct version number should be 200a2dde7f3b - if the number is different, then overwrite the different number with this one.
6) Click on the tick icon above
7) Exit Sqlite Admin, and then try running Captain's Log 2.1.3 - you should now be back up and running.
Apologies for the inconvenience and I hope this solves your problem.
It's come to my attention that there's a specific problem with 2.1.3 not loading the GALAXY.db - the error windows being posted in the discussion here is the symptom.
There is a way to fix this. The problem is being caused by the database version number marked within the GALAXY.db being incorrect. For some reason the database migration tool Captain's Log uses, is correctly altering the DB structure, but is not marking the database revision number afterwards.
Here is how to fix that:
1) You will need to download and install SQLite Admin, get it from here :http://sqliteadmin.orbmu2k.de/
2) Once installed, run SQLite Admin, and load the GALAXY.db into it
3) Click on the Edit Data tab
4) On the left-hand list of tables, click on the alembic_version table. You should now see the data for that table, which is basically a version_num - it's a hexadecimal number.
5) The correct version number should be 200a2dde7f3b - if the number is different, then overwrite the different number with this one.
6) Click on the tick icon above
7) Exit Sqlite Admin, and then try running Captain's Log 2.1.3 - you should now be back up and running.
Apologies for the inconvenience and I hope this solves your problem.
Last edited:
You can see where the location is by going into the ConfigurationManager and clicking on the Directory Locations tab.
GALAXY.db will be in whatever location is set under the Captain's Log Database File Locations section.
Note: Do take a backup of all files there before editing GALAXY.db
Last edited:
Version number is still incorrect - DB schema system is still trying to add an existing column to a table - make sure you get the revision number correct. Follow the procedure above.
Regards
Root Cause Analysis on recent CL2 Database shenanigans...
Okay so, a lot of the crashes in Captain's Log is because it's a Python program built as a Windows application.
When it's built as a Windows GUI application, standard output messages, and standard error messages, which would normally get sent to a text console, have nowhere to go.
So in Captain's Log's case, whenever something gets sent to stdout or stderr, and because it's been turned into a Windows GUI EXE, you'll get those horrible cx_Freeze dialogue windows with the error messages that were meant to go to the console, and the program just basically crashes out.
The solution - and something I should have put in place a long time ago - is to divert stdout and stderr to some kind of GUI text widget.
I've done this now.
In addition, I've started using Python's Logging functionality (again, something I should have used a long time ago), which will also send logging messages to this text widget I've added.
The result, is this...
The above is what happens whilst checking and migrating the GALAXY.db from the CL2 2.0.0 schema, to the 2.1.3 schema.
Notice the
That was being sent from the alembic library, which is the package responsible for database schema versioning and migration.
That's what is causing CL2 2.1.3 to crash during the migration from the 2.0.0 GALAXY schema to the current schema. It's being sent to stdout (or stderr), there was nowhere for it to go, so a cx_Freeze dialog window is created.
In the act of doing so, alembic is prevented from stamping the current/HEAD version number into the GALAXY database, and from then on, unless you manually stamp it with the correct number as outlined in the procedure I posted above , you'll get another lovely cx_Freeze dialogue window from alembic, because it's trying to add the navbeaconscan column to the galaxy table in the GALAXY database, and that column already exists.
BEWM!
And so endeth the Root Cause Analysis
I currently have a 2.1.4 beta 2 available for download at : https://www.dropbox.com/s/pgsz3rdkcmpo4by/Captain's Log 2_2.1.4 beta 2_setup.exe?dl=1 if you want to test it - there have been a number of bugfixes in it.
Regards
Okay so, a lot of the crashes in Captain's Log is because it's a Python program built as a Windows application.
When it's built as a Windows GUI application, standard output messages, and standard error messages, which would normally get sent to a text console, have nowhere to go.
So in Captain's Log's case, whenever something gets sent to stdout or stderr, and because it's been turned into a Windows GUI EXE, you'll get those horrible cx_Freeze dialogue windows with the error messages that were meant to go to the console, and the program just basically crashes out.
The solution - and something I should have put in place a long time ago - is to divert stdout and stderr to some kind of GUI text widget.
I've done this now.
In addition, I've started using Python's Logging functionality (again, something I should have used a long time ago), which will also send logging messages to this text widget I've added.
The result, is this...
The above is what happens whilst checking and migrating the GALAXY.db from the CL2 2.0.0 schema, to the 2.1.3 schema.
Notice the
Code:
C:\Python34\lib\site-packages\alembic\util\messaging.py:69: UserWarning: Skipping unsupported ALTER for creation of implicit constraint
warnings.warn(msg)That was being sent from the alembic library, which is the package responsible for database schema versioning and migration.
That's what is causing CL2 2.1.3 to crash during the migration from the 2.0.0 GALAXY schema to the current schema. It's being sent to stdout (or stderr), there was nowhere for it to go, so a cx_Freeze dialog window is created.
In the act of doing so, alembic is prevented from stamping the current/HEAD version number into the GALAXY database, and from then on, unless you manually stamp it with the correct number as outlined in the procedure I posted above , you'll get another lovely cx_Freeze dialogue window from alembic, because it's trying to add the navbeaconscan column to the galaxy table in the GALAXY database, and that column already exists.
BEWM!
And so endeth the Root Cause Analysis
I currently have a 2.1.4 beta 2 available for download at : https://www.dropbox.com/s/pgsz3rdkcmpo4by/Captain's Log 2_2.1.4 beta 2_setup.exe?dl=1 if you want to test it - there have been a number of bugfixes in it.
Regards
Last edited:
Whether version 2.1.3 is compatible to old versions, for example 1.4.4? It is a pity old to lose expeditions.
And version 1.4.4 still working?
And version 1.4.4 still working?