Release [Explorer's Application] Captain's Log

Hi,
after exporting a database to csv and restarting Captain’s Log I get the following error:


http://s2.postimg.org/dd0p96emx/captainslog.jpg

Reinstalling CL did not do the trick, neither did renaming another DB to 'default'. End of my line here :D
Any idea what that means?

Running Win 10 by the way if that helps and doesn’t make me a moron :)


Fly safe!
Andrew

Hi Andrew, I answered on my homepage but I'll repeat here...

Hi Andrew,

Has there been a new file created with the extension “.db” ?


The error message indicates that the bit of code that adds a database to the database table in the db manager is crashing because what it thinks is a database file (file with a .db extension), isn’t a database file.


I suggest you go into your database directory, order the listing by date, see which is the newest file there, and move it out of that directory. Then restart CL.


Regards

EDIT: I have answered the email you sent to me personally, and you now know why that happened. :)

(It wasn't the fault of Captain's Log, for the benefit of those who might now be afraid to export their database to CSV ;) )

Regards o7
 
Last edited:
I removed it. CL now shows the initiation screen and then aborts with this:

captainslog2.jpg
 
I removed it. CL now shows the initiation screen and then aborts with this:

http://s15.postimg.org/bw0x2033v/captainslog2.jpg

You really are making me work for my money y'know ;)

Quit messing up your CL folder! :)

I think for you, you're better off starting with a completely new set of config files and blank data, then gradually moving in each .db file to the CaptainsLog data directory as follows...

Okay. Exit CL.

Browse to %LOCALAPPDATA%

Rename the existing CaptainsLog folder to something else, say: CaptainsLog_OLD or something.

Run Captain's Log and configure it.

A new CaptainsLog folder will be created in %LOCALAPPDATA%, along with a default database file (default.db) and a stars/planets values database file (cl_values.db)

CL is ready to use as before.

Now you can exit CL, and copy each of the old database files you've created (filename.db) into the new CaptainsLog folder - except for captainslog.cfg, cl_values.db, and possibly default.db - leave those well alone. Do not copy those back.

When you next open CL, those copied database files should now be available in the Database Manager so you can switch to them.

Regards.
 
Thanks for creating this. I just installed it and it's exactly what I need, even if I didn't know it at the time.

I was previously using EDDiscovery but I heard that it requires the original log files to function correctly while Captains Log preserves all stars in its own database so I decided to try it out. I did consider Captains Log before I picked EDDiscovery but I was turned off by the appearance of it in the guide screenshots and preferred EDDiscoverry's more standard look. After using it though I found it worked well visually while in-game.

Would it be possible to have a colour setting which changes the appearance from blue to other colours, kinda like ED's hue rotation? I'd love to have it match up with my hud colours (default at the moment).

Cheers
 
Thanks for creating this. I just installed it and it's exactly what I need, even if I didn't know it at the time.

I was previously using EDDiscovery but I heard that it requires the original log files to function correctly while Captains Log preserves all stars in its own database so I decided to try it out. I did consider Captains Log before I picked EDDiscovery but I was turned off by the appearance of it in the guide screenshots and preferred EDDiscoverry's more standard look. After using it though I found it worked well visually while in-game.

Would it be possible to have a colour setting which changes the appearance from blue to other colours, kinda like ED's hue rotation? I'd love to have it match up with my hud colours (default at the moment).

Cheers

What's wrong with Gutamaya Blue? 0.o

Nah just kidding.

I'm currently working on getting CL to run on Macs. This is taking longer than expected (and more work), but I'm also adding in bugfixes and enhancements.

Currently the colour scheme is hard-coded. It'll be quite time consuming to get that into a customisable state, again due to turning hard-coded stylesheets into stylesheets with configurable colours, so bear with me on that one. Might not happen in the next release, but it should happen eventually.

Regards o7
 
I've found a small bug in the program. If you delete an entry from the 'System Bodies' list that you have created, it doesn't remove the planet from the counter on the statistics tab. I spent ages going mad looking for an earthlike in the system entries as i thought I had discovered less than the log stated.

It's not a major issue, and is resolved by restarting captain's log, as the counts are rebuilt when loading the db entries. It did however confuse the life out of me...

I also have a small request. Could you add a generic placeholder body into the system bodies entry system with a zero value, as it offends my OCD to have gaps in the numbering whenever there is a star as a planetary body.
 
Greetings CMDR Rushmere o7

I've found a small bug in the program. If you delete an entry from the 'System Bodies' list that you have created, it doesn't remove the planet from the counter on the statistics tab. I spent ages going mad looking for an earthlike in the system entries as i thought I had discovered less than the log stated.

It's not a major issue, and is resolved by restarting captain's log, as the counts are rebuilt when loading the db entries. It did however confuse the life out of me...

Thank you for that bug report.

I have tracked down the bug and it is now fixed.

You'll see that fix when the next version of Captain's Log is released.

I also have a small request. Could you add a generic placeholder body into the system bodies entry system with a zero value, as it offends my OCD to have gaps in the numbering whenever there is a star as a planetary body.

I don't think that's going to happen - as far as I'm concerned, stars are stars, and I'm not caring whether they're given a designation as a system body or not. They're recorded as a star in the system. Adding some generic thing in the system body entry system isn't as straightforward as you think - I'd have to also update the database schema, which would entail converting old databases into the new format.

I'm right in the middle of trying to get Captain's Log to run on Macintosh OS X as well, which is what the next release is really going to be about. This is taking a bit of time for various reasons, bit once this is accomplished the same codebase can be used for both Windows and OS X without me keeping two separate branches of CL source.

The advantage of that becomes clear when bugfixes and enhancements are only done to one source code branch.

Anyway - thanks for the bug report. Fix is in and waiting to be released when CL is ready for OS X :)

Regards o7
 
Captain's Log on OS X

Well, I'm yet one step closer to get Captain's Log running properly on OS X...

Screen Shot 2015-10-19 at 23.12.06.png

Still a lot of work to go though. So far, I've gotten the initial configuration window working. It saves and loads the configuration too. Also auto-creates an AppConfigLocal.xml file to enable verbose logging. The main window comes up, the other windows as well.

Next up is to get it detecting ED is running on the Mac, amongst a shed-load of other things.

Best of all, I'm using the one codebase - just adding in platform detection and running either Windows or Mac-specific code depending on which platform it's running on - so no messing about with different code branches, meaning bugfixes and enhancements can be done for both platform versions at once.

Onwards and upwards ;)
 
getting an error when trying to run the program after todays update (worked fine before)

Edit: uninstall then reinstall same error message
Verboselogging is on


---------------------------
cx_Freeze: Python error in main script
---------------------------
Traceback (most recent call last):
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2072, in _wrap_pool_connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 376, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 708, in _checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 480, in checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 1146, in _do_get
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 323, in _create_connection
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 449, in __init__
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 602, in __connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\strategies.py", line 97, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\default.py", line 385, in connect
sqlite3.OperationalError: unable to open database file

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "C:\Python34\lib\site-packages\cx_Freeze\initscripts\Console.py", line 27, in <module>
File "CaptainsLog.py", line 3845, in <module>
File "CaptainsLog.py", line 1815, in __init__
File "CaptainsLog.py", line 743, in __init__
File "CaptainsLog.py", line 876, in create_default_values_db
File "C:\Python34\lib\site-packages\sqlalchemy\sql\schema.py", line 3622, in create_all
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 1853, in _run_visitor
File "c:\python\32-bit\3.4\lib\contextlib.py", line 59, in __enter__
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 1846, in _optional_conn_ctx_manager
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2037, in contextual_connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2076, in _wrap_pool_connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 1405, in _handle_dbapi_exception_noconnection
File "C:\Python34\lib\site-packages\sqlalchemy\util\compat.py", line 188, in raise_from_cause
File "C:\Python34\lib\site-packages\sqlalchemy\util\compat.py", line 181, in reraise
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2072, in _wrap_pool_connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 376, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 708, in _checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 480, in checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 1146, in _do_get
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 323, in _create_connection
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 449, in __init__
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 602, in __connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\strategies.py", line 97, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\default.py", line 385, in connect
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) unable to open database file

---------------------------
OK
---------------------------
 
Last edited:
Thanks for this VERY useful tool. Only been using it for a couple of hours but I cant help thinking that FD should have included something like this from the beginning.
 
After today patch ceased to appear in the new system the Captain's log. Very sad. I'm used to this handy utility.
 
getting an error when trying to run the program after todays update (worked fine before)

Edit: uninstall then reinstall same error message
Verboselogging is on


---------------------------
cx_Freeze: Python error in main script
---------------------------
Traceback (most recent call last):
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2072, in _wrap_pool_connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 376, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 708, in _checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 480, in checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 1146, in _do_get
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 323, in _create_connection
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 449, in __init__
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 602, in __connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\strategies.py", line 97, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\default.py", line 385, in connect
sqlite3.OperationalError: unable to open database file

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "C:\Python34\lib\site-packages\cx_Freeze\initscripts\Console.py", line 27, in <module>
File "CaptainsLog.py", line 3845, in <module>
File "CaptainsLog.py", line 1815, in __init__
File "CaptainsLog.py", line 743, in __init__
File "CaptainsLog.py", line 876, in create_default_values_db
File "C:\Python34\lib\site-packages\sqlalchemy\sql\schema.py", line 3622, in create_all
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 1853, in _run_visitor
File "c:\python\32-bit\3.4\lib\contextlib.py", line 59, in __enter__
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 1846, in _optional_conn_ctx_manager
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2037, in contextual_connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2076, in _wrap_pool_connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 1405, in _handle_dbapi_exception_noconnection
File "C:\Python34\lib\site-packages\sqlalchemy\util\compat.py", line 188, in raise_from_cause
File "C:\Python34\lib\site-packages\sqlalchemy\util\compat.py", line 181, in reraise
File "C:\Python34\lib\site-packages\sqlalchemy\engine\base.py", line 2072, in _wrap_pool_connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 376, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 708, in _checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 480, in checkout
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 1146, in _do_get
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 323, in _create_connection
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 449, in __init__
File "C:\Python34\lib\site-packages\sqlalchemy\pool.py", line 602, in __connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\strategies.py", line 97, in connect
File "C:\Python34\lib\site-packages\sqlalchemy\engine\default.py", line 385, in connect
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) unable to open database file

---------------------------
OK
---------------------------


Hrm. I don't think that's got anything to do with the update. It looks like CL can't create the cl_values.db database - which is the database which contains all the values for stars and planets.

Have a look in %LOCALAPPDATA%\CaptainsLog - that's where CL creates its database and configuration files - did you run CL as Administrator before and are now running it as a normal user?

Try removing the file cl_values.db if it exists. Also try reconfiguring CL by removing the file called captainslog.cfg

Regards

- - - Updated - - -

After today patch ceased to appear in the new system the Captain's log. Very sad. I'm used to this handy utility.

After every game update, verbose logging is disabled.

You need to run Captain's Log before running the game - in fact it's good practice to always run CL before running the game launcher.

If you haven't done so already, exit the game, and CL, then launch CL, then the game - that should do the trick.

Regards o7
 
After every game update, verbose logging is disabled.

You need to run Captain's Log before running the game - in fact it's good practice to always run CL before running the game launcher.

If you haven't done so already, exit the game, and CL, then launch CL, then the game - that should do the trick.

Regards o7
Thank you.
After rebooting ED went to appear new system. But generally strange - my Captain's log is in the startup windows
 
Seems I'm getting a weird startup error.

cx_Freeze: Python error in main script

Traceback (most recent call last):
File "C:\Python34\lib\site-packages\cx_Freeze\initscripts\Console.py",line 27, in <module>
File "CaptainsLog.py", Line 3845, in <module>
File "CaptainsLog.py", Line 2109, in __init__
File "CaptainsLog.py", Line 3664, in getsystemstardata
AttributeError: 'NoneType' object has no attribute 'close'

happened after i tried to import my eddiscovery and netlogs and restarted it, tried reinstall didn't fix it any ideas?

Fixed:

Apparently happens when database is not found? program kept running behind the error and I created a new database and defaulted to it, now it works fine.
 
Last edited:
Seems I'm getting a weird startup error.

cx_Freeze: Python error in main script

Traceback (most recent call last):
File "C:\Python34\lib\site-packages\cx_Freeze\initscripts\Console.py",line 27, in <module>
File "CaptainsLog.py", Line 3845, in <module>
File "CaptainsLog.py", Line 2109, in __init__
File "CaptainsLog.py", Line 3664, in getsystemstardata
AttributeError: 'NoneType' object has no attribute 'close'

happened after i tried to import my eddiscovery and netlogs and restarted it, tried reinstall didn't fix it any ideas?

Fixed:

Apparently happens when database is not found? program kept running behind the error and I created a new database and defaulted to it, now it works fine.

Thanks for that.

I've actually already added in additional error checking to the next version of CL to make it more robust when it comes to handling databases. This is in connection with getting CL running on OSX - which it is fully doing now ;)

Lots more bugfixes too.

I just need to do some more work then I'll be able to release an update to the PC version and simultaneously launch the OSX release.

This will be happening Soon[tm]

Regards o7
 
Back
Top Bottom