Skip to content

v2.5-beta7-mono[Linux+MacOS]

Pre-release
Pre-release
Compare
Choose a tag to compare
@Premo36 Premo36 released this 28 Mar 16:02
· 11 commits to mono since this release

Please read this whole page before downloading. This is the download for the mono version, that is intended to be used on Linux/Mac.
If you're on Windows, please download the windows version here https://github.com/Premo36/DML2.X/releases/tag/v2.5-beta7

What is mono

It's an open source implementation of Microsoft's .NET Framework. Long story short, given that your C# application is not too much complex, you can make it work under mono in fairly low amount of time, and this will allow your Windows .net application to run under any OS where the mono runtime can be installed. Tought I would NOT recommend it for new project, due to how old and limited the project technology is (it do not work with WPF or really anything newer then winform...) and by how scarce and outdated the documentation is.

What do I need to use this DML 2.X version?

NOTE: If your are on Windows, this version is NOT for you!
You need to download and install the stable `mono-complete` for your operating system following the instruction on the official mono project website .
If you're on a Linux based OS, you may have the mono-complete package available on your distro repos, but it's usually an older version so it's better that you still follow the instruction from the mono project website and install it that way.
If you're on a Mac OS system, while DML 2.X under mono should work as well as on Linux, I couldn't test it myself as I don't own a mac.
Once `mono-complete` is installed, you should be able to open DML 2.X by simply double-clicking on the `.exe`. If that does not work you may open it trough the console by navigating to the folder where the DML 2.X it's located, writing `mono "DML v2.5 mono.exe"` (note that the .exe name will be different during the beta, you have to write the precise, full `.exe` name, writing "mono DML" and then pressing tab should autocomplete to the correct name) and pressing "enter" on your keyboard.
This version of mono is a modified version from the windows one, all the core functionality works and, as a plus,it follows the user dark/light theme (On Linux at least), but it may have some minor graphical issue and the check for update as been disabled as it would crash DML 2.X.
On Linux, to quickly found where a sourceport is installed (assuming you've installed trough your package manager) you can write in the console `whereis gzdoom` (where gzdoom is your sourceport name), which will output the path to the executable.

Changelog v2.5 Beta N° 6 Mono => v2.5 Beta N°7 Mono

  • Fixed bug where the workaround for 'bind [KEY] "save quicksave.zds" ' did not work under Linux(#22 ).
  • Fixed bug where the autoload selection was resetted to "-" each time a preset was deleted (#23 ).
  • Changed "Autoload preset" label to just "Autoload"

Note: The workaround that make the custom saving method 'bind [KEY] "save quicksave.zds"' work, right now only works on WIndows/Linux (tested on recent gzdoom/zandronum version installed trough apt) , if you're on Mac OS the workaround will not work.

Changelog v2.4 => v2.5 Beta N°7 Mono

  • Now it works under Linux/Mac trough mono!
  • The preset name it's now fully visible while browsing the preset list, no matter how long the preset is (#13).
  • Mods list "Order By" value it's now kept between application launches (#8).
  • Preset order can now be changed via the software settings. Possible order are "Alphabetical - Ascending", "Alphabetical - Descending" , "Date - Ascending" and "Date - Descending" (#11).
  • Mods list can now also be ordered by "Date - Ascending" and "Date - Descending".
  • In order to make DML 2.X more portable, the DMLv2.ini now store just the name and not the whole path of the alternative sourceport configuration file (#9) .
  • The "please insert a preset name" error message as now an error icon instead of a information one (#18).
  • Added a workaround that mitigate the gzdoom bug where quicksave made with 'BIND [KEY] "SAVE QUICKSAVE.ZDS"' are saved in the wrong folder. Can be enabled in DML 2.X preferences. (#14) .
  • The selected mod can now be pushed directly to the top/bottom of the list in the mod order window also by using pageUP/pageDOWN (#19).
  • Now the mod that you always use can be placed in a preset and loaded automatically each time you play, just select the preset in the "autoload preset" combobox in the "Game" section of DML 2.X (#20).
  • Updated the renderer selection in order to work with the newest gzdoom releases(#21).
  • Added a monero address in the welcome/about windows and readme txt, in case anyone wants to donate.

WARNING: This is a beta release

Please keep in mind that this release is to be considered as a beta software, because I still haven't fully tested it yet. It may be unstable, crash, become sentient etc... so use with at your discretion... as this new beta is so much beta that I may call it even an alpha!
While using any release of DML 2.X tagged as "beta", ignore the "new version" notification, as those are linked to the official stable releases, not with the beta ones.
As any release I made of this software, this one also gets detected as "Malicius" on virus total by Malwarebytes (+ some other AVs). As they never really fix the detection but usually just whitelist the single exe, everytime I made a new version I have to go again trough the process of contacting each antivirus and report my software as a false positive. Now I've stopped doing that for beta releases, so be advised that your antivirus may report it as a threat: it's not. But you don't have to belive me, as "don't worry, it's safe " it's exactly what a malicius developer will say about his not-so-safe software, so feel free to take a look to the sourcecode and compile it yourself if you wish.

How to update from an older DML version

  • DML v2.2 (or newer): You can just replace the old .exe with the new one keeping all your configuration files, and it should work right away, but just to be extra safe, go ahead and make a backup before updating, so if it messes up your presets or configuration files you can restore them without the need of re-configure everything from scratch. If you still have the "P36_UTILITIES.dll" you can safely delete it as it's no longer used since v2.2b.
  • DML v2.1: Move all the contents of %AppData%\Roaming\P36_Software\DMLv2\ inside the CONFIG folder next to dml exe, then follow the v2.2 (or newer) instructions.
  • DML v2.0/v2.0b: You have to first download the 2.1 version, go trough the presets update procedure (explained in the 2.1 readme) and then follow the v2.1 instructions.
  • DML v1.0/v1.1: There is no way to update from 1.X to 2.X, you will have to recreate your presets from scratch.

Where is the README v2.5.txt?

Starting from beta N°7 the updated (but still wip) readme is included. It should include every new feature. If something it's missing or not clear, feel free to contact me!

I've found a bug/something is not working right/I have a suggestion/I want to contact you

If you find any bug with this version please report it trough github (if you're familiar with it), or by sending an email at [email protected] with subject "DML 2.5 Beta 7 Mono *Here your OS* Bug - *Here describe the bug in a few words*" and in the mail itself try to explain with much accuracy and details as possible what happened, what did you expect it should have happened and a step by step guide on how to reproduce it, as if I can't reproduce it on my end, I can't fix it.

If you just want to contact me you can get in touch via email: [email protected]