Repository navigation
DML v2.6-Beta2
Pre-release
Please read this whole page before downloading, or at least the "WARNING: This is a beta release" section.
If you're on Linux/MacOS, read the "How to run on Linux/Mac OS" section.
(Beta 1 was an internal beta that only included #29)
Changelog v2.5 => v2.6 Beta N°2
- Start a game right away by passing to the DML exe the preset name as start argument. More info below (#29 - Thanks to @StephenChamberlain for implementing this feature)
- Now the same .exe (and features) works under Windows & Mono. No longer two separate builds (#37)
- New version notification now is available also under mono (#37)
- Removed Tank Rider links (#38 - More info about it in the github issue)
- Removed support email, made no sense having two different emails... just use info@p36software for everything (#39)
How to directly play a preset on app launch
Be sure to configure/test the preset beforehand within DML 2.X. Requires at least the sourceport/iwad to be saved in the preset, otherwise it will default to the last used ones, which are not granted to be the correct one. Preset name with spaces are not handled correctly, update the preset name to use "_" instead of spaces.Example, your preset is Psychophobia UnofficialPatch. First of all update it so the name does not contain spaces. Now that you have Psychophobia_UnofficialPatch, be sure that the all the mod are included and in the correct order and that the sourceport and the original game are saved in it aswell. Give it a test within DML 2.x and tweak if needed. Once satisfied close DML 2.X.
Note: preset name is CASE SENSITIVE, so Psychophobia_UnofficialPatch != PsychoPhobia_UnofficialPatch.
Example on Windows:
DML_v2.6-Beta2.exe Psychophobia_UnofficialPatch
Example on Linux/Mac (same as windows but you have to prepend everything with "mono"):
mono DML_v2.6-Beta2.exe Psychophobia_UnofficialPatch
Once ensured that the command is working, you can create shortcut/shell script to start your favorite modpack right away!
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...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 "Malicious" on virus total by some 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, so be advised that your antivirus may report it as a threat: it's not. But you don't have to believe me, as "don't worry, it's safe " it's exactly what a malicious 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.
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 info@p36software.net with subject "DML 2.6 Beta 2 *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 you expected to happen, 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.How to run on Linux/Mac OS
NOTE: If your are on Windows, you don't need to do anything of this, do NOT install mono on Windows!Mac OS, while technically supported via mono the same way as Linux, is not "officially" supported, the only reason for the lack of support is that I don't own a mac, but it might work, so give it a try. If you succeed in get it to working please get in touch info@p36software.net
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.
Once mono-complete is installed, you should be able to open DML 2.X by simply double-clicking on the .exe. If that doesn't work you may open it trough the console by navigating to the folder where the DML 2.X it's located and starting it with "mono dml_exe_here" . For example mono DMLv2.6-Beta2.exe
On Linux, If you're using a dark theme it might start with a sort of "automatic dark mode" that I did not code in, so some text might be hard to read. If that the case and you want a look closer to the windows version, prepend GTK_DATA_PREFIX= to the console command. For example GTK_DATA_PREFIX= mono DMLv2.6-Beta2.exe
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. If you're using the file dialog that opens with "ADD..." you'll need to change the filter, as by default shows only .exe
On mono, be aware that there is a bug on the MODS list (More info #40). I've "fixed" it on preset change, but is still not fixed on manual mod selection. For example you select X mod, then one by one you unselect them by clicking on them again, when you unselect the last mod, the first mod at the top of the MODS list get automatically selected. This bug was already present in v2.5 and only occurs when using mono.
