Release 2.6.3

This is a minor release. It is necessary to update ExploData to correct some issues with variant naming exceptions.

Changes

• Should now fully handle exceptions to variant naming (Stratum Aranaemus)
• Corrections to several flipped temperature min/max rules
• Allow multiple parent star color variants (not always direct parent star)

ExploData

• Structural changes to data for dealing with variant naming exceptions
• Add checks and database entries for 'fully mapped' systems (this column was already in the database but wasn't being set)

Release 2.6.2

Fixes:

• Updates to Stratum Aranaemus variant detection / parsing
• Ensure main star type and luminosity are parsed when scanning
• Updates to Bacterium Cerbrus ruleset

ExploData

• Structure changes to handle Stratum Aranaemus variant data
• Numerous additions / corrections to variant / color info / requirements

Release 2.6.1

This is primarily a bugfix release.

Fixes

• Remove old incomplete scan locations and scan progress, regardless of your current location, when a new scan is started
  • Previously was only applying to scans within the current system
• Improved startup handling under certain conditions
• Remove extraneous color processing (this is handled by ExploData)
• Fix a scan distance of 0 being evaluated as None for purposes of exclusion
  • This was caused by codex entries getting triggered by a bio scan making identical scan and waypoint locations
• Fix a typo in the Clypeus Margaritus ruleset applying the wrong body type

ExploData update

• Optimize database filesize during shutdown (run VACUUM)
• Database schemata are unchanged

1.0.5

• Fix a possible migration issue to db v3

Version 2.6 - ExploData and Display Updates

ExploData Database Handler

In order to facilitate providing a database backend for multiple plugins, the database portion of version 2.0+ has been migrated to a new, standalone EDMC plugin / module package.

Reimporting past journals is recommended, though only necessary if you use Pioneer. Journal import history has been reset. Additional data will be collected.

Please review the installation instructions.

Please report any issues.

Display Updates

• Display options for completed scans
  • Checkmark (old behavior)
  • Hide
  • Hide when in the system / unfocused view
• Customizable altitude for the 'near surface' focus option

Other fixes

• Fix for missing Bacterium Volu variant
• Journals will use the filename to sort when importing by parsing the datetime
• Add missing body type to several tussock species
• Corrections to codex parsing for Horizons species
• General database structure improvements
• Add coordinates for planetary nebulae and optimize the distance check code

ExploData 1.0.1 - 1.0.3

• Fixes for some possible migration issues

Release 2.5.4 - Missing Codex Entries and Journal Import

Apologies for the flurry of updates, but I've been rushing to fix issues in 2.5 and letting some things slip through cracks. With any luck, this will be the last patch for at least a few days.

This release contains two major feature updates as well as a few fixes.

Codex Entries

Calculated species / variants that are not logged in your codex will now display a memo emoji (📝). If you enable the detail list, the specific colors and species will be marked as well.

For the best results, you will want to import your old journals.

Journal Importing

A button has been added to the settings pane to initiate importing of historic journal data. This will add a progress display to the main BioScan display pane. This process can run in the background while you continue to use EDMC. Unfortunately, the current processing method does take a fair amount of time and may take a while if you have many years of data to parse, though this will depend on how much exploration data you have logged as well.

This process may be started and stopped at will, and the journals that have been fully processed will be skipped the next time you start importing again. (The process will shut down gracefully if you close EDMC.) Just remember to restart the import the next time you run EDMC.

Other Changes

Database Updates

A number of changes were applied to the database structure for region tracking and better handling of certain data types. Basic scans, when missing a DSS, don't log some planetary data, as an example. Though these migrations were tested a fair amount, if you run into problems starting BioScan please report the issue and any relevant EDMC logs.

Fixes / Additions

• Add some additional sectors to the guardian map
• Handling for basic scan data (missing materials, atmosphere, temperature, etc.)
• Prevent adding the same atmosphere gasses multiple times
• Require star coordinates and safety checks for generic locations (CQC)
• Ensure stars use the correct identifier in the active star list

2.5.1

• Migration fixes for version 2.5 that was causing issues with existing 2.0 installs
• Added variant / species display for the missing codex entries on the detailed display
• Error messages for failures during journal parsing and database migration
• Ensure we get the relevant main star properties when loading from the database
• Various display updates (ex. added tenth to journal progress percentage)

2.5.2

• Fix for journal threading causing strange display issues on Windows

2.5.3

• Fix star distance not getting set by scans / EDSM

2.5.4

• Fix typo causing crashes if loading a saved system
• Fix repeating codex icons in detail display by deep copying the result data before modifying the display

Installation

• If you use the Windows EXE version of EDMC, you must use the windows exe archive
• If you run EDMC with Python directly, use the native python archive and install the requirements (see the readme instructions)

Release 2.0

Persistent Database

Version 2.0 introduces a persistent database to BioScan. This means that restarting EDMC or resuming a session will retain your data and progress. Scan progress, waypoints, and system data are all preserved. Revisiting a previous system will pick up right where you left it.

This integration includes basic support for multiple commanders. Scans and waypoints are saved based on your active commander while system and biological data is global. Keep in mind that separate computers will not share the same database file without user intervention.

The database is saved to a bioscan.db file in the main data directory for EDMC above the plugins directory. (%LOCALAPPDATA%\EDMarketConnector or the equivalent location on Mac/Linux.)

This should lay the groundwork for implementing codex tracking and marking species and variants that have not yet been scanned. Eventually, journal parsing could be added to read all historic journal files to populate the database with past data.

Other changes

• Atmosphere composition was not being pulled from EDSM

Changes from RC

• Slight packaging adjustments to provide a slimmer download for native python users
• Some minor optimizations

Compatibility notes

• EDMC versions running python 3.11 are absolutely required for this version
• The integration requires the use of the SQLAlchemy python package and some dependencies which may conflict if another plugin provides this package

Installation

• If you use the Windows EXE version of EDMC, you must use the windows exe archive
• If you run EDMC with Python directly, use the native python archive and install the requirements (see the readme instructions)

Release 2.0 - RC1

This is a Release Candidate

Please note that due to significant changes in this version, there is a greater than normal chance that unresolved bugs exist in this release. If none have been discovered after additional testing, it may be promoted to a full release.

Persistent Database

Version 2.0 introduces a persistent database to BioScan. This means that restarting EDMC or resuming a session will retain your data and progress. Scan progress, waypoints, and system data are all preserved. Revisiting a previous system will pick up right where you left it.

This integration includes basic support for multiple commanders. Scans and waypoints are saved based on your active commander while system and biological data is global. Keep in mind that separate computers will not share the same database file without user intervention.

The database is saved to a bioscan.db file in the main data directory for EDMC above the plugins directory. (%LOCALAPPDATA%\EDMarketConnector or the equivalent location on Mac/Linux.)

This should lay the groundwork for implementing codex tracking and marking species and variants that have not yet been scanned. Eventually, journal parsing could be added to read all historic journal files to populate the database with past data.

Other changes

• Atmosphere composition was not being pulled from EDSM

Compatibility notes

• EDMC versions running python 3.11 are absolutely required for this version
• The integration requires the use of the SQLAlchemy python package and some dependencies which may conflict if another plugin provides this package

Patch Release 1.7.1

• Fix the genus ID for Brain Trees which should prevent some issues that were happening
• Add another sector to the Guardian sector list
• Some changes for code readability

Release 1.7 - Waypoints

This release adds a new feature, Waypoints.

Waypoints

When scanning a species with the composition scanner (via the ship or SRV), your current position will be logged to the species data if the species has yet to be fully analyzed.

If you are not actively scanning a species, all species with active waypoints will display the nearest waypoint to your location. This includes a distance and bearing along with an indicator about the number of degrees and direction to turn to face that heading. Once you begin scanning a species, the nearest waypoint that is outside of the range limit of any scanned samples will be displayed beneath the top progress display. The other genera waypoints will be hidden while the scan is in progress, though additional comp scans will continue to add to the available waypoints.

Note that the waypoints use your current location when logged, so try to get close to the sample you're scanning for best results.

This feature can be toggled in the settings.

Also

Some additional corrections and additions were made to Horizons species requirements

ToDo

When adding a waypoint, we may want to ensure a minimum distance between coordinates to prevent a bunch of extraneous waypoints getting logged.

Patch Release 1.6.2

• Improved sorting of genus / species results (everything should sort alphabetically by genus now)
• Fix a bug in the main star luminosity check code causing some Horizons flora to crash the plugin
• A few more species requirements updates, mostly to Horizons species