We on the GZDoom development team have very limited knowledge about how well this works with older hardware. However, the results of the tests here may determine if this project is worth picking up and continuing in an official capacity.
As such, I've spent a couple hours creating a testing environment that should give us the information we need. Included in this package is the following:
- A slightly modified version of the GZDoom in question, with this new backend
- Modifications include updating the GZDoom core to a more recent version,
- and also removing some annoying debug messages.
- A slightly modified version of LZDoom 3.87c. (Compiled with MSVC for Vista and later only)
- This version of LZDoom is designed so that it can run side-by-side with GZDoom within the same folder. It simply renames game_support.pk3 to lzdoom_game_support.pk3
- .dll files to support both the GZDoom and LZDoom installations included in the package
- Source code for the modifications to both the GZDoom and LZDoom included
- Freedoom 1 & 2 (mostly because it's legal to distribute and it will run all of the included mods just fine, for purposes of this test)
- Frozen Time
- Phobos: Anomaly Reborn
- The Darkest Hour
- Vrack 3
- Knee-Deep in ZDoom
- A batch script meant to be used for this testing
- Savegames meant to be loaded by the batch files with the mods, trying to get as close as possible to the same points
We're mostly looking for people who have older hardware. OpenGL 2.x and OpenGL 3.x preferred. This mostly includes graphics chips that were new between 2004 and 2010.
Inside the folder there's a Testing - Open Me!.cmd file. This file will ask you what mod to load, and whether you want to load GZDoom or LZDoom for that mod. Naturally, we would like you to try each mod once with both.
Please load each mod with LZDoom first. After each mod is loaded, open the console, then type "bench". Please give it a few seconds. (The FPS counter will disappear when it is done). Then exit LZDoom. Do the next mod using LZDoom.
When you are done, please rename "benchmarks.txt" to "benchmarks-lzdoom.txt"
Now, do the same thing with GZDoom. Load each mod in GZDoom, one after the other. After each mod loads, open the console and type "bench". As before, give it a few seconds, wait for the FPS counter to disappear, and when it does exit GZDoom and move on to the next mod.
When you are done with the GZDoom batch, rename "benchmarks.txt" to "benchmarks-gzdoom.txt".
Once you have both benchmarks files, please stick them in a zip file and post a reply in this thread with those files attached. That will be really helpful, thank you! Please also let us know your CPU, how much RAM you have, and what GPU you are using, and whether you are using a 64-bit system or a 32-bit system.
Before you download this testing kit, please remember one thing: The scripts included in this folder are designed specifically for testing, and they are *not* meant to be installed in your actual LZDoom/GZDoom installation. In fact, DO NOT PUT THEM IN YOUR NORMAL LZDOOM OR GZDOOM FOLDER! The scripts will wipe your configs if they are in the same folder, and you do not want that. Don't say we didn't warn you! The scripts are designed to wipe the configs clean for every test, and you do not want them doing that to your real GZDoom files, so please don't do that! Keep them in their own separate folder, please.
Without further ado, here is the download link for the testing kit:
https://drive.google.com/file/d/1BgpjR4 ... sp=sharing (Both 64-bit and 32-bit system included in this package, it will be auto-selected)
Thank you in advance for any help you can provide!