Skip to content

Releases: Asnivor/MedLaunch

MedLaunch v0.4.0.0

21 Jan 12:33
Compare
Choose a tag to compare

Beta release

https://github.com/Asnivor/MedLaunch/releases/tag/0.4.0.0

Important Release Notes

** This MedLaunch release is ONLY compatible with version 0.9.41.x of Mednafen. Do NOT upgrade if you are not planning to update Mednafen also **

Notable Additions

  • Implemented config control changes for the latest Mednafen release
  • Added a Mednafen version check on game launch (to avoid errors with wrong versions)
  • Fixed some minor errors in the Mednafen config control names
  • Added tooltips on config controls based on Mednafen documentation (can be turned off/on in settings)

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.41.x branch - 64-bit version is required if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Ensure you have the correct version of Mednafen installed (v0.9.41.x)
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
  • In settings change your mednafen directory if you installed the new version of mednafen somewhere else
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
  • In settings change your mednafen directory if you installed the new version of mednafen somewhere else

MedLaunch v0.3.1.0

09 Jan 14:07
Compare
Choose a tag to compare
MedLaunch v0.3.1.0 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Notable Additions

  • Fixed 'Joystick Axis Threshold' config value not saving to database

Important Release Notes

This is a very small bugfix release.

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.3.0.1

22 Dec 15:57
Compare
Choose a tag to compare
MedLaunch v0.3.0.1 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Notable Additions

  • Implemented color picker/canvas control for all Mednafen hex-color related options (lightgun crosshair colors etc..)
  • Bugfix to stop application exception when trying to 'Browse Game Data Folder' when the game does not have a GDBID set in the database

Important Release Notes

This is a quick bugfix release that also bundles a Mednafen config colorpicker control.

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.3.0.0

22 Dec 09:28
Compare
Choose a tag to compare
MedLaunch v0.3.0.0 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Notable Additions

  • Many bug fixes (see changelog for full details)
  • Various UI style enhancements (more consistent controls and mouse cursor change over controls)
  • Implemented games library datagrid sorting memory (per session only)
  • Vastly improved 'Save Settings' execution speed
  • Added ability to set custom fullscreen resolutions
  • Details of unhandled exceptions (application crashes) are now written to 'Exceptions.log' in the root of the MedLaunch directory
  • A merged 'DAT' file (json) has been created and will be shipped with each release. Using TOSEC, NOINTRO, TRURIP & REDUMP roms will be detected on import (and re-scan) based on MD5 checksum and game name, country, year and publisher will be populated in the games library grid (where information is available). Year and publisher will be overwritten when game data is scraped from online
  • Added context menu option to re-scrape all game information for a system (rather than just trying to scrape for games that have no previously been scraped). This will download all content again

Important Release Notes

In this major release there have been many low-level changes to the way MedLaunch functions 'under the hood'. If you have any issues upgrading from an older version of MedLaunch it is recommended that you attempt a fresh install. I haven't however seen any upgrade issues during testing.

In order to populate the new grid fields in the games library you will have to rescan your existing ROMs. This will automatically attempt to match them using MD5 hash with the merged DAT that now ships with MedLaunch.

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.2.20.0

22 Nov 19:18
Compare
Choose a tag to compare
MedLaunch v0.2.20.0 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Important Release Notes

This latest release completely overhauls much of the Games Library code, along with the underlying database structure. These changes should provide much better performance for large libraries (so far tested with approx 20,000 games in the library).

Because of the database changes, you will find that updating your current version of MedLaunch results in all the games in your library showing as not scraped. You will have to scrape them again - although if any media files have been previously downloaded these will be found once scraping has been completed.

Notable Additions

  • Fixed pce-cd games not being found when doing a batch scrape
  • Added option (disabled by default) to always import Mednafen cfg files when MedLaunch starts
  • Major performance gains on games library datagrid (dirty flag updates to in-memory data rather than individual database calls everywhere)
  • Several secondary scraper edge-case bugfixes
  • Added scraped data related columns to main games library datagrid

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.2.15.0

17 Nov 15:18
Compare
Choose a tag to compare
MedLaunch v0.2.15.0 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Notable Additions

  • Fixed media content from downloading when option is de-selected in settings
  • Fixed launch strings not being passed to mednafen for PCE CD games
  • Fixed (unneeded) pcecd.cfg config being created in mednafen folder
  • Fixed game scraping local match for PCD-CD games (games were not being found)
  • Added option to set the size of the image tooltip popups (based on a percentage of the current MedLaunch window size)

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.2.14.5

16 Nov 12:57
Compare
Choose a tag to compare
MedLaunch v0.2.14.5 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Notable Additions

  • Fixed control iteration bug where pce_fast (and possibly snes_faust) command line arguments were not being generated correctly
  • Mednafen config backups are now stored in the MedLaunch folder (.\Data\MednafenCFGBackups)
  • Fixed some config controls not setting correctly
  • Added messagebox on initial database creation - asking whether user wants to enable auto-check for updates on start

Important Release Notes

This branch (0.2.14.x) implements some BIG changes in the way that MedLaunch handles configurations on disk. The 'Base Configuration' filter has been completed removed so that you just have a separate button for each system.

An option has been added to settings (on by default) that saves a system-specific cfg file to the root of the Mednafen directory whenever you launch a game. You can disable this in the settings but there is less chance of a screw-up if you don't. If you are precious about these cfg files (nes.cfg, psx.cfg etc.) then please back them up before you proceed.

You will also notice an amber button on the Configs page called 'IMPORT ALL CONFIGS FROM DISK'. When you click this the following happens:

  • The contents of the main Mednafen configuration file are loaded into MedLaunch (mednafen-09x.cfg)
  • All general (non-system-specific) options are applied to EVERY system configuration in MedLaunch
  • Then every single system config file (snes.cfg, pce.cfg etc.) is loaded into MedLaunch and applied to the correct system

You are also asked if you want to import all configs every time you choose a new Mednafen directory within MedLaunch.

You can also right-click on a system filter in MedLaunch and choose to import just the system.cfg file from disk for this system (useful if you have made manual changes to a system.cfg file and want to import these changes into MedLaunch without having to import every config, and before it gets overwritten by running a game).

When you launch a game all config options for the selected system are still supplied via the command line (therefore the mednafen-09x.cfg file is updated automatically by Mednafen itself)

Please note: Netplay and Server settings are still independent of system configurations. You can set these up once in MedLaunch and not have to worry.

Finally there is another setting (also on by default) that creates a uniquely named backup of your existing Mednafen-09x.cfg file (in the root of the Mednafen directory) every time you start MedLaunch.

Hopefully these changes will mean that the way MedLaunch handles configurations is more intuitive to the average user, and more functional for those people who want to generate config files through a GUI for use in other Front-Ends/Launchers.

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.2.14.2

16 Nov 00:01
Compare
Choose a tag to compare
MedLaunch v0.2.14.2 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Important Release Notes

This version implements some BIG changes in the way that MedLaunch handles configurations on disk. The 'Base Configuration' filter has been completed removed so that you just have a separate button for each system.

An option has been added to settings (on by default) that saves a system-specific cfg file to the root of the Mednafen directory whenever you launch a game. You can disable this in the settings but there is less chance of a screw-up if you don't. If you are precious about these cfg files (nes.cfg, psx.cfg etc.) then please back them up before you proceed.

You will also notice an amber button on the Configs page called 'IMPORT ALL CONFIGS FROM DISK'. When you click this the following happens:

  • The contents of the main Mednafen configuration file are loaded into MedLaunch (mednafen-09x.cfg)
  • All general (non-system-specific) options are applied to EVERY system configuration in MedLaunch
  • Then every single system config file (snes.cfg, pce.cfg etc.) is loaded into MedLaunch and applied to the correct system

You are also asked if you want to import all configs every time you choose a new Mednafen directory within MedLaunch.

You can also right-click on a system filter in MedLaunch and choose to import just the system.cfg file from disk for this system (useful if you have made manual changes to a system.cfg file and want to import these changes into MedLaunch without having to import every config, and before it gets overwritten by running a game).

When you launch a game all config options for the selected system are still supplied via the command line (therefore the mednafen-09x.cfg file is updated automatically by Mednafen itself)

Please note: Netplay and Server settings are still independent of system configurations. You can set these up once in MedLaunch and not have to worry.

Finally there is another setting (also on by default) that creates a uniquely named backup of your existing Mednafen-09x.cfg file (in the root of the Mednafen directory) every time you start MedLaunch.

Hopefully these changes will mean that the way MedLaunch handles configurations is more intuitive to the average user, and more functional for those people who want to generate config files through a GUI for use in other Front-Ends/Launchers.

Notable Additions

  • Fixed config import bug with non-valid values

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.2.14.1

15 Nov 22:42
Compare
Choose a tag to compare
MedLaunch v0.2.14.1 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Important Release Notes

This version implements some BIG changes in the way that MedLaunch handles configurations on disk. The 'Base Configuration' filter has been completed removed so that you just have a separate button for each system.

An option has been added to settings (on by default) that saves a system-specific cfg file to the root of the Mednafen directory whenever you launch a game. You can disable this in the settings but there is less chance of a screw-up if you don't. If you are precious about these cfg files (nes.cfg, psx.cfg etc.) then please back them up before you proceed.

You will also notice an amber button on the Configs page called 'IMPORT ALL CONFIGS FROM DISK'. When you click this the following happens:

  • The contents of the main Mednafen configuration file are loaded into MedLaunch (mednafen-09x.cfg)
  • All general (non-system-specific) options are applied to EVERY system configuration in MedLaunch
  • Then every single system config file (snes.cfg, pce.cfg etc.) is loaded into MedLaunch and applied to the correct system

You are also asked if you want to import all configs every time you choose a new Mednafen directory within MedLaunch.

You can also right-click on a system filter in MedLaunch and choose to import just the system.cfg file from disk for this system (useful if you have made manual changes to a system.cfg file and want to import these changes into MedLaunch without having to import every config, and before it gets overwritten by running a game).

When you launch a game all config options for the selected system are still supplied via the command line (therefore the mednafen-09x.cfg file is updated automatically by Mednafen itself)

Please note: Netplay and Server settings are still independent of system configurations. You can set these up once in MedLaunch and not have to worry.

Finally there is another setting (also on by default) that creates a uniquely named backup of your existing Mednafen-09x.cfg file (in the root of the Mednafen directory) every time you start MedLaunch.

Hopefully these changes will mean that the way MedLaunch handles configurations is more intuitive to the average user, and more functional for those people who want to generate config files through a GUI for use in other Front-Ends/Launchers.

Notable Additions

  • Overhauled the database config tables (to more closely mirror Mednafen's config files)
  • Implemented import-config-from-files functionality
  • Added option (on by default) to backup Mednafen configuration on disk when MedLaunch first starts
  • 'Base Configuration' config filter has been removed and the way MedLaunch handles Mednafen config arguments has been completely overhauled (if updating rather than new install of MedLaunch please ensure that you 'Import All Configs' once before launching a game
  • Added option to automatically save system.cfg file in the Mednafen directory on game launch (enabled by default). It is recommended that you leave this on to avoid any inconsistencies when importing configs into MedLaunch. As above definitely do an 'Import All Configs' on first run and backup your pre-existing system.cfg files if you don't want them tampered with

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch and 64-bit version if you want to emulate Saturn games).
  • You are then prompted to choose whether to import all config settings from your Mednafen folder into the MedLaunch database (this is recommended).
  • If you currently use system-specific config files with Mednafen the settings from these will be imported with the above process. However MedLaunch will write to these files when you launch a game - so back them up somewhere if you are not happy with this.

Upgrade

Preferred Method:
  • Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button
Manual Method:
  • You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.
  • Once MedLaunch has upgraded, go to the 'Configs' tab and click the 'IMPORT ALL CONFIGS FROM DISK' button

MedLaunch v0.2.11.1

10 Nov 15:45
Compare
Choose a tag to compare
MedLaunch v0.2.11.1 Pre-release
Pre-release

See the full Changelog for the full list of changes and the Roadmap for things on the horizon.

Notable Additions

  • Bufix to update checker

New Install

  • Extract this release to a folder, run the 'MedLaunch.exe' executable and choose your Mednafen directory (must be the Mednafen 0.9.39.x branch).
  • If you currently use system-specific config files with Mednafen it is recommended that you setup a new Mednafen folder (extract Mednafen to a new folder) to avoid issues.

Upgrade

  • Preferred Method: Automatically download and upgrade using the 'Updates' tab within MedLaunch itself.
  • Manual Method: You can safely extract this new release over an existing MedLaunch folder (providing you do not have MedLaunch running at the time)
  • Once extracted run the MedLaunch.exe executable and your current database will be upgraded before the application starts proper.