Release [Explorer's Application] Captain's Log

[Genar-Hofoen]

I have a question. I forgot to open CL 2 on my current trip and missed a few jumps. So what I did was isolate only the logs relevant to my trip, create a new database, and run the scan all logs and import to the database, action. Now, EDD tells me that my trip has 584 jumps so far but after importing the logs, CL 2 says I have 645 jumps. It turns out that there are duplicate events imported, I think from logs that had a system jump in one and after I logged off the game and started again, CL 2 read the next log as a jump event and added it again. Everything else seems fine.

Is there a way to remove the duplicate systems? If not, is there any chance you may fix this problem in the new version?

Thanks in advance.

Last week I went over the log importer code, and fixed a couple of things in it which were similar to what you describe, so it may well have fixed what you've experienced.

It'll be in the upcoming CL 2.1 release - which should be on or before E: D 2.4 goes live.

 

[Aura Lorell]

Last week I went over the log importer code, and fixed a couple of things in it which were similar to what you describe, so it may well have fixed what you've experienced.

It'll be in the upcoming CL 2.1 release - which should be on or before E: D 2.4 goes live.

Thank you!

 

[Genar-Hofoen]

New Release : Captain's Log version 2.1.0

As per title, I am now releasing Captain's Log, version 2.1.0 "The Return Of Gravitas?"

This is a new feature and bugfixes release.

Do read the post and especially the Upgrade Note at the bottom before upgrading!

New/Headline Features

1) Estimated Planet, Star, System, and Trip Values.

As you scan planets and stars, Captain's Log will calculate the estimated value of each item. This is based on the formulae developed over at MattG's forum post.

The Info panel will display both the Estimated System Value and the Estimated Total Trip Value for that Trip database...

Estimated Star and Planet Values will be displayed in the Star Info Panel or the Planet Info Panel respectively...

2) Nav Beacon Scan Data

When Elite: Dangerous 2.4 is released, you will be able to obtain detailed star and planet scan data for 'known' systems - i.e. systems for which your ship's navigation data banks already contain the information about populated systems in the Bubble.

To obtain this data, you jump into a known system - say Shinrarta Dezhra - go to the system Nav Beacon, target it, which will scan the Nav Beacon.

NOTE: You will need to have a Detailed Surface Scanner for this.

Once the scan is complete, the Nav Beacon will supply your ship with detailed surface scans of every celestial object within that system.

Captain's Log 2.1.0 will convert and import that data in the same way such data is obtained by manual detailed surface scanning. Whilst this is happening, a small dialog window appears telling you it is doing so...

There may be many objects within a star system. Shinrarta Dezhra has something like 45 objects to import. Once this has completed, the data is presented in the usual way and similarly can be used the same.

Nav Beacon Scan data is treated differently by Captain's Log 2.1.0, in that Estimated Values will not be calculated for this data. Any Nav Beacon Scan data obtained will be indicated as such, instead of the Estimated Values...

3) Ring Data and Belt Data Added

Captain's Log always stored the Ring and Belt data for objects which had them - it just didn't display them. It does now

Belt data is displayed in Earth Lunar Masses (Moon Masses), and Ring data is displayed in Megatonnes (MT)...

4) Synthesis Materials Availability Indicator System Has Been Enhanced

Captain's Log 2.1.0 now has 4 main Explorer-related recipes which it checks the available materials in a system for; FSD Boost, AMFU Refill, SRV Refuel, and SRV Repair. It will check the availability of raw materials on landable planets for each of the Basic, Standard, and Premium synthesis recipes.

The icons have been changed in this version of Captain's Log. B = Basic , S = Standard, and P = Premium...

These B, S, and P icons are clickable.

When you click on one of those icons, a new type of Panel will appear on the right hand side, the System Materials Panel. This panel will tell you the top two landable planets in the system with the highest percentage of the relevant synthesis material for that recipe. It will also tell you the amount of materials you currently have in your materials storage. This feature will enable you to quickly decide which planet you can go to in order to obtain more of these raw materials.

For example, clicking on the S icon for SRV Repair, results in this Panel...

If you then click on the P icon for SRV Repair, the Panel will show you the Premium synthesis recipe for that, the top two planets in the system with highest % of materials, and your current stored raw materials quantity (or not)...

Changelogs

Quite a lot of work has went into Captain's Log 2.1.0, which isn't apparent just by looking at the GUI

The changelogs are basically the raw logs from my repository, so it's quite lengthy. Do read them for more information on bugs fixed or other work done which isn't mentioned or apparent above.

Spoiler

Version 2.1

- Now actually stores Axial Tilt values.
- Now displays Axial Tilt if that figure is available
- If importing and scanning all Journal files, update axial tilt values for planets with existing records and if Axial Tilt figures are available in the Journal file for that planet.
- Moved entire toolset from Python 3.4 to Python 3.5
- Changed landable planet icon from SVG to PNG as it was causing a crash
- Added beginnings of a statistics widget
- Added the necessary UI build scripts for stats widget
- Save EDSM database system count to config file for fast restart
- Read EDSM database system count from config file if it exists
- Only update config file EDSM db system count after an import
- Increase nightly dump download update refresh delay a little bit
- replaced human readable filesize library with in-app solution
- remove unused variables from journalparser
- remove confusing/unused duplicate of edsm function file
- Added beginnings of statswidget function
- Moved legacy stats variables from CL2 main code to stats module, renamed
- Added star & planet value formulae from MattG's forum post as functions.
- Removed some unnecessary (legacy) code.
- ValueFormula class removed from widget file & moved to its own file
- Planet Info Widget now shows estimated planet value
- Import & setup StatsWidget in main Captain's Log code
- Added a check during load of mainwindow X/Y coords and set to zero if out of bounds.
- If systray icon 'Reset Window Position' used, save coords.
- Added a .spec for pyinstaller
- No longer using cxfreeze, using pyinstaller instead. build.bat altered.
- Bodytype in planet formula now compares to lowercase string for use by other parts of the program.
- Total worth of planets calculated during planet table population
- Total worth of star calculated during star table population
- Total values returned to mainwindow code and added up
- Formatted values with commas for display
- Added estimated star value
- Added total estimated system value to info panel
- Total estimated value + title visible if total > 0
- ValueFormulae return a rounded up integer.
- Altered default star value in same style as default planet value
- Removed unnecessary k = 720 because k already is 720 by default.
- Changed the dimensions of the Overlay Widget
- Altered the layout of the Overlay Widget
- Moved Jumponium & AFMU indicator widgets
- Added Estimated System Value to Overlay Widget
- Added total value column to galaxy table.
- Added Axial Tilt to System Star table.
- JournalParser StarNoRings/Rings signal now one generic function (DRY)
- v2DBInterface adding Stars now 1 generic function (DRY)
- v2DBInterface Stars are now either added or modified if record exists
- Added Axial Tilt to StarInfoWidget panel
- Total estimated value for system stored in database, for statistics
- Make sure Axial Tilt is displayed if not None.
- Tell StarInfoWidget the Axial Tilt for display, if available.
- Remove extraneous txt variable
- Added Luminosity to SystemStar table.
- Corrected value in value formula
- Added Luminosity to parser and db interface
- Added Luminosity to star info widget
- Added GUI refresh forcing to various places in order to prevent CL2 GUI 'freezing' whilst adding a bulk load of star/planet data from a nav beacon scan.
- Further tuning of the journal parser
- Added a navbeacondata flag to GALAXY db table
- Added migration script
- Added preliminary work for upcoming NavBeaconScan event
- Removed two unnecessary signal emits from journalparser
- CL2 now shows total trip estimated value.
- Total estimated value ignores navbeacon scanned systems
- Added various navbeacon and value functions to DBInterface code
- Don't get EDSM nightly dump filesize when starting Captain's Log.
- Make getting EDSM nightly dump filesize WAY more resilient.
- Do not try to download nightly dump if EDSM appears to be down.
- Added code to deal with NavBeaconScan.
- If NavBeaconScan, don't update/refresh GUI until expected number of stars/planets have been processed by JournalParser/DBInterface.
- Update/Refresh GUI only when last star or planet has been processed.
- ValueFormula : White Dwarfs have a 'D' in their class, not a 'W'
- ConfigurationManager : live journal = 'Journal*', beta = 'JournalBeta*'
- When switching trip DB's, clear estimated system & calc tot. trip values
- Hotkey class : no need to check if running on Windows because we are.
- Created a RingWidget, to be used for star/planet rings/belts
- Show planet rings if it has them
- Fixed a bug where click signal for planet table was firing twice.
- Added star ring/belt data retrieval function in DBInterface.
- Removed DB id from ring dict in planet ring retrieval function.
- When star or planet selected, also retrieve and send ring data to relevant InfoPanel widget.
- Star Info Panel now shows either ring system or asteroid belts info.
- Star Ring data shows mass in moon (Lunar) masses.
- Star Asteroid Belt data shows mass in Megatonnes.
- Planet ring data now shows mass of rings in Megatonnes.
- Set stylesheets for ring widgets.
- Fixed a bug where clicking on the Star table called handler twice.
- Moved all ring info processing into 1 function (DRY).
- Ring/Belt inner and outer radius added.
- Corrected import journals function to point to new 'DRY' star add/modify
- Added new signals and counters to JournalParser for nav beacon scans
- Taught JournalParser to count but ignore Belt Clusters in Navbeacon scan
- Added a NavBeaconScanWidget for indicating we're chewing over such scans
- Added a function in DBInterface to mark a system as being navscan data
- Removed old non-DRY 'add star/add star+rings' functions from DBInterface
- Keep track of a system name highlighted on the Trip Jump table
- Added handling functions for various NavBeaconScan signals
- Added Icon Clicked signals to AMFUWidget.
- Reduced AMFUWidget flash count to 1, from 3, makes GUI response crisper.
- Added Icon Clicked signal to JumponiumWidget.
- Reduced JumponiumWidget flash count to 1, makes GUI response crisper.
- Added new System Materials Widget
- When loading a new Trip DB, refresh the global DBInterface.
- When loading a new Trip DB, refresh the GUI in the right order.
- Added stylesheets to SystemMaterialsWidget.
- Added populating of top two planets with relevant FSD Boost material % to SystemMaterialsWidget.
- Added SystemMaterialsWidget into application.
- Relevant Info panels/widgets display when relevant app areas clicked.
- Clicking on J1, J2, or J3 FSD Boost Mats indicator displays the SystemMaterials widget/panel.
- Added clicked signals to AFMU indicator icons.
- Added 5th Material listing labels to SystemMaterialWidget.
- Added display of AFMU Refill materials to SystemMaterialWidget panel by way of clicking on the relevant A1, A2, A3 AFMU Refill icons, which will show which 2 top planets in that system have the highest % of the relevant material.
- Ensure SystemMaterialsWidget set invisible when a trip jump entry has been selected.
- Send isnavbeacondata signal to PlanetInfoWidget.
- PlanetinfoWidget will say "Nav Beacon Data" instead of estimated value of planet, if system data was obtained via nav beacon scan.
- Added SRV Refuel Widget.
- Created new icons for Basic, Standard, and Premium synthesis.
- Mats widgets now use new icons for Basic, Standard, Premium synthesis.
- Added new synthesis icons to repository.
- Corrected from 'SRV Repair' to the more accurate 'SRV Refuel'
- Make the AFMURefill function use the generic synth widget.
- Make the Jumponium function use the generic synth widget.
- Delete obsoleted Jumponium & AFMURefill widgets.
- Make sure to set synth widget titles.
- Converting Info Panel into a self-contained class and widget.
- SRV Repair Synth Widget and handling logic added.
- System Synth Materials Widget shows quantity of mats required per recipe
- Add mat quantities to all synth recipes.
- Added 6th material to SystemMaterialsWidget
- Re-designed total trip value calculation database query, because sqlite has a limit of 999 query values, which is useless when number of jumps in a trip goes over that figure.
- Converted total trip value calculation into a thread, which will start running after trip DB has loaded.
- Total trip value is now its own python class/QObject.
- Total trip value calculation will update in realtime as it progresses.
- Added further support for LoadGame journal event.
- Added functions to display/hide various panels where relevant.
- Ensure System Mats widget, when called, gets set visible and the other panels get set invisible.
- Ensure total trip value gets updated when (non-Nav beacon) scan happens.
- Add parsing of Raw Materials from Journal to JournalParser.
- Add indication of quantity of raw material help by CMDR for each raw material required for a synthesis recipe.
- Initialise and update each count of a raw material a CMDR character holds, from the Player Journal data generated when a game is started.
- For each synthesis recipe and for each raw material in that recipe, send the raw material quantity held by the CMDR to the display panel.
- Added RawMaterialCollected signal to JournalParser.
- Added parsing of Raw Material collection to JournalParser.
- Keep track of which synthesis recipe is active.
- When collecting a raw material, add quantity collected to current count.
- Update display of stored raw materials after collection.
- ConfigFile class now holds the master raw materials quantities.
- ConfigFile class now loads and saves raw material quantities (i.e. the CMDR's raw materials quantities are loaded/saved from/to the INI file.)
- [Raw Materials] section added to INI file.
- Mainwindow code now refers to ConfigFile for raw materials counts.
- Reduced amount of code needed to initialise raw materials counts.
- Raw materials counts get saved whenever a material is collected.
- Added MaterialsUsed signal to JournalParser.
- MaterialsUsed signal triggered by Synthesis and MaterialDiscarded events
- Decrement CMDR materials when used, save to INI when this happens.
- Update materials counts in GUI when materials used.
- Include CommodityReward from MissionCompleted event in consideration of whether raw materials are collected by CMDR, in the JournalParser.
- Include the Ingredients list in the EngineerCraft event when considering if raw materials have been consumed by the CMDR, in the JournalParser.
- Added some code commenting and rename a variable to make more sense
- Added suitable Inno Setup file for creating install package due to new use of PyInstaller to create an application distribution.
- Some more adjustments to inno setup configuration
- Disabled an added Status panel for now - feature incomplete and will expand upon next release.
- Try to get the CL2 logo font to be consistent.
- Tell StarInfoWidget if system data is from Nav Beacon Scan
- If Star data is from nav beacon scan, say so, else display estimated star value.
- Captain's Log 2 version number bumped to 2.1.0

Upgrading Note

Be aware that Captain's Log 2.1.0 has switch toolkits to Python 3.5 64-bit. In other words, it is now a 64-bit only application.

Before upgrading, be sure to uninstall the previous version of Captain's Log.

You will not lose any of your data. Captain's Log 2.1.0 will use your databases as usual. It will also update the GALAXY database witha new schema, so first run of Captain's Log 2.1.0 may take just a little bit longer than usual. No user intervention is required for the database schema migration - it'll Just Do It[tm].

It is also recommended to back up your CaptainsLog2 folder located in %localappdata% before proceeding.

Download is available at https://captainslog.scarygliders.net/download/captains-log-2x/

Enjoy

 

[Aura Lorell]

Wow that's a lot of work you've put in there, totally amazing. Love the new additions.

One thing I noticed is that the trip scan value calculation when I opened the application was the same as the amount of the last system scanned. I created a new database to re-import my logs (to get rid of the duplicate jumps -- they are correct now) and Estimated Trip Value is still wrong (1,206,872) but not the same as the Estimated System Value (658,483).

Edit: When reopened the application the trip value was different: 2,919,990. And still wrong.

 

[Aura Lorell]

Also a suggestion for the overlay. The estimated system value can be in the same line as the Distance to Sol and the Odometer to save some space and make it smaller.

 

[Genar-Hofoen]

Also a suggestion for the overlay. The estimated system value can be in the same line as the Distance to Sol and the Odometer to save some space and make it smaller.

Said this to you on Discord, but for the benefit of everyone else:

I plan to do a complete revamp and overhaul of the Overlay system - it's a whole project unto itself, I have a ton of ideas I'd like to implement, and there was no way I could fit that work in before ED 2.4 is unleashed - it's also why the Jumponium and AFMU indicators are unaltered from the previous version

Regards o7

 

[piratejo]

Hi. Ive a problem

I´m upgrading to 2.1.0 but the program doesnt import any journal log.

I´ve created a new database and try to import a journal log, but nothing happen

Is there any place to download previous version 2.0.0, that works fine?

Thanks


EDIT:

SOLVED. I DON´T KNOW WHY....BUT SOLVED

 

[Genar-Hofoen]

Hi. Ive a problem

I´m upgrading to 2.1.0 but the program doesnt import any journal log.

I´ve created a new database and try to import a journal log, but nothing happen

Is there any place to download previous version 2.0.0, that works fine?

Thanks


EDIT:

SOLVED. I DON´T KNOW WHY....BUT SOLVED

Heh.

 

[Genar-Hofoen]

Version 2.1.1 Released (Hotfix for 2.1.0 plus some Enhancements & Alterations)

As per title, version 2.1.1 is released, hot on the tail of 2.1.0, for which a few issues were reported.

If you have already upgraded to 2.1.0, then simply install this over it.

If you are still using 2.0.0, remember to uninstall that one beforehand.

Download link :

https://captainslog.scarygliders.net/download/captains-log-2x/

I'm off to bed now. [zZzZz]

Changelog

- BUGFIX : check for Raw Material in journal entry the correct way.
- removed some debugging print() lines that shouldn't have been in.
- ENHANCEMENT : added a 'No. of jump events' counter when importing the Journal Files to a blank trip database, for additional feedback.
- BUGFIX : make sure estimated systems value updates on the Overlay
- ENHANCEMENT : display est. value or not on Overlay depending on nav beacon data and if value > 0
- ALTERATION : Changed layout of Overlay again based on feedback : made the Overlay shorter but also a bit longer, and moved a couple of widgets to the right hand side.
- ATTEMPTED BUGFIX : It appears there may be a problem with building Captain's Log using the new PyInstaller method. I have attempted to fix this, and hopefully the new package works.
- ENHANCEMENT : After loading a Trip database, Captain's log will now calculate the estimated system value for star systems in the trip which don't yet have an estimated value, which aren't Nav Beacon scan data, and which have star and planet scan data.
- ENHANCEMENT : whilst calculating Estimated Total Trip Value, the label will say "Calculating Trip Value", and when completed will revert to "Estimated Trip Value:"
- Version bumped to 2.1.1

 

[Straha Yeagar]

Just upgraded to 2.1.1. Fantastic work here that you continue to do!

Noticed the system payouts are not quite looking correct, especially when compared to ED Discovery v8.2.3.0. The most obvious example is a single black hole system I scanned. EDD Shows the body value as 56393 which is inline with what a BH should be, but CL shows the body value as 2991.

Another example is a system with a normal O, and B star. The O star shows 3908 in EDD and 3909 in CL, so close enough, but the secondary B star shows 3318 in EDD, but 62584 in CL.

Another one is an ELW in EDD shows a value of 639594, and CL shows the same ELW as 228931. In that same system, the F class primary shows the same in both EDD and CL within rounding of 2920, and 2921. The WW in that same system is again, the same within rounding of 229925 and 229924.

Spot checked a system with a WW CFT and again, the primary K class star was within rounding of CL being 2912, and EDD 2911, but the WW CFT was way different. CL showed as 468031, and EDD had it at 728939.

And just a last example as I think I have provided enough to show something is off...an A class Blue-White Supergiant in CL shows 58869, and in EDD, shows 3121.

Those are just the ones that I spot checked for system values. The only other quirky thing is that my trip value shows over 1 bil, and the leading number is cut off because it seems as if the trip value field is limited to nine places.

 

[Genar-Hofoen]

Just upgraded to 2.1.1. Fantastic work here that you continue to do!

Noticed the system payouts are not quite looking correct, especially when compared to ED Discovery v8.2.3.0. The most obvious example is a single black hole system I scanned. EDD Shows the body value as 56393 which is inline with what a BH should be, but CL shows the body value as 2991.

Another example is a system with a normal O, and B star. The O star shows 3908 in EDD and 3909 in CL, so close enough, but the secondary B star shows 3318 in EDD, but 62584 in CL.

Another one is an ELW in EDD shows a value of 639594, and CL shows the same ELW as 228931. In that same system, the F class primary shows the same in both EDD and CL within rounding of 2920, and 2921. The WW in that same system is again, the same within rounding of 229925 and 229924.

Spot checked a system with a WW CFT and again, the primary K class star was within rounding of CL being 2912, and EDD 2911, but the WW CFT was way different. CL showed as 468031, and EDD had it at 728939.

And just a last example as I think I have provided enough to show something is off...an A class Blue-White Supergiant in CL shows 58869, and in EDD, shows 3121.

Those are just the ones that I spot checked for system values. The only other quirky thing is that my trip value shows over 1 bil, and the leading number is cut off because it seems as if the trip value field is limited to nine places.

Thanks for the feedback, it's appreciated.

I'm busy working on a 2.1.2 release at the moment - more issues and wrinkles being sorted out, I'll include another pass at my implementation of the value calculation with that, and see where it's going amiss.

Maffs. I hate maffs.

 

[Jacobite]

I got the update 2.1.1 and it all seemed to go ok, this morn however it keeps crashing out after reading whichever log I try to load, having said that I did manage to click on the configure button before it crashed and it stopped whatever was happening so after trying to load several logs unsuccessfully I tried creating a new log and it seems to have worked again, not sure I`ve explained that too well but I hope it helps.

(update)...

after scanning a few systems I shut down CL to see if it would read what I had done with new log, it did with no problems so I restarted again to see if it still crashed out reading older logs.. IT DIDNT ! so now seems to be working again

its an excellent addition and I cant say I liked the thought of doin without it

 

[Genar-Hofoen]

Captain's Log 2.1.2 Released

NOTE : Uninstall any previous version of Captain's Log 2.x before installing this version.

Reason : Have reverted back to trusty, working, and reliable 32-bit Python 3.4 toolset - the 64-bit Python 3.5 toolset was a nightmare in comparison. Have also reverted back to the tried and trusted cx_freeze method of creating a distribution of the application.

Download from : https://captainslog.scarygliders.net/download/captains-log-2x/

Alternate download in case there are problems downloading from the site : https://www.dropbox.com/s/tk5adrgn43mpft2/Captain's Log 2_2.1.2_setup.exe?dl=1

Changelogs

- Disabled flash indicators on synth indicator widgets because pointless
- Moved all database session creation/management functions from legacy ConfigurationManager class, to V2DBInterface class
- Always refer to ConfigFile() class for important saved variables
- TargetDestinationWidget now uses own V2DBInterface() class for querying the database
- BUGFIX : fixed a lot of legacy cruft from CL1.x when dealing with databases
- ENHANCEMENT : Added a progress bar for the total trip value calculation for even more feedback - show % of trip jumps examined
- BUGFIX : Main Captain's Log functions now all use a V2DBInterface() class for when querying and updating databases, instead of being lost in a twisty maze of database sessions, all looking alike. It's all MUCH cleaner now and that particular bit of legacy CL1.x cruft has been exorcised, burned at the stake, shot with a silver bullet, and had a wooden stake shoved through its ashes, and the ashes nuked from orbit - it's the only way to be sure.
- BUGFIX : When importing journal files, ignore star or planet scans in journals where there was no prior FSDJump event (e.g. perhaps the starting Journal file doesn't have an FSDJump event and hence a System name to work with and it's too hard trying to ascertain the system name from a Scan event because how do you extract the system name from a planet name consistently?). This prevents the importer DBInterface from breaking, and breaking the whole import.
- Journal File importer now uses its own DBInterface class/DB session.
- ENHANCEMENT: Journal File importer now displays a count of Scans as well as Jumps whilst iterating through the journal files.
- Reverted back to 32-bit Python 3.4 toolset
- Version bumped to 2.1.2

 

[Jacobite]

downloaded and installed Thanks for all the work you do with this ! I think E.D should buy this off you and build it into the actual game ! that's assuming you wouldn't mind a substantial amount of money for it ?

P.S. if they do then hold out for a job with them keeping it current

Seriously though.. thanks m8.

 

[Genar-Hofoen]

Captain's Log 2.1.3 Released

A major showstopper bug fixed, amongst other bugfixes and enhancements/adjustments.

Uninstall previous version of 2.x before installing this one.

Download links at : https://captainslog.scarygliders.net/download/captains-log-2x/

Changelog

- BUGFIX : When validating Target Destination XYZ upper and lower bounds, ensure you are checking X and X, Y and Y and, Z and Z, instead of X&X, Y&X, and Z&X, dummy.
- BUGFIX : Don't set the overlay estimated system value with the estimated total trip value - that's a paddlin'
- BUGFIX : in a 'first time run' scenario, do create GALAXY.db and v2default.db BEFORE creating the first DBInterface instance, because DBInterface doesn't like having non-existent databases to not look at, and gets really very upset, and wrecks the whole program out of spite, coz that's how it rolls.
- REFINEMENT : On the Overlay, take the time and effort to craft an awesome sentence out of the 'Distance to <target system>' information, because it rolls off the tongue easier. And looks better too.
- REFINEMENT : Do not automatically select the first planet (if any) listed in the planet table, when you have either selected a new system, FSDJumped into a system for which you have planet data, or if you have scanned a planet in a system. This gets rid of that brief view of the information for the first planet in the planet table, in the Overlay. No more subliminal planet info!
- REFINEMENT : Adjust the positioning of the Atmosphere and Terraforming indicators on the Overlay, so that letters in the Atmosphere indicator with a waggly tail will not be cut off. No more screaming in agony for those poor letters as they get their tails cut off!
- BUGFIX : Estimated Value formula: Black Holes are type "H", not "B", mmm'kay?
- BUGFIX : Estimated Value formula: Do an exact match check for "N" or "B", mmm'kay?
- Version bumped to 2.1.3

 

[filthyneon]

I cannot run Captain's Log at all, latest version. Getting this error and it's getting on my nerves lol.

Anybody know why?

 

[Genar-Hofoen]

I cannot run Captain's Log at all, latest version. Getting this error and it's getting on my nerves lol.

Anybody know why?
https://i.imgur.com/gJCD4yr.jpg

Looks like you have a trip db which can't be found.

A possible remedy is going to %localappdata%\CaptainsLog2 in File Browser, and editing the captainslog2.INI file, and set activedb = v2default

This should load the default trip database.

I've actually right now put a safety check in the source code to check to see if the configured trip DB exists and if not, set the trip DB to load to v2default.

This fix will go into the next release, which won't be tonight as I'm exhausted having fixed a ton of stuff and made two releases today as well as the other releases in the last few days

If that hasn't fixed it, rename the CaptainsLog2 folder in %localappdata% and run CL2 - it'll go into First Run mode and set up fresh blank DB's. Then you could create a new blank DB and import Journal files into that.

I'm off to bed now.

Regards o7

 

[Ralph Vargr]

I cannot run Captain's Log at all, latest version. Getting this error and it's getting on my nerves lol.

Anybody know why?
https://i.imgur.com/gJCD4yr.jpg

That's what I'm getting.

 

[Ralph Vargr]

OK, renaming the folder, and installing 2.1.3 seems to have worked. Thanks!

 

[Goobertech]

Getting all kinds of errors when trying to install this newest version. Is there a good way to install an older version?