by Enjay » Fri Oct 10, 2025 3:21 pm
A dev build should work in exactly the same way as regular GZDoom. i.e. it should work if you unzip it to a folder (not in Program Files), provide it with a suitable IWAD and... that's it really.
I don't know your model of graphics card, but Intel cards can be a bit troublesome. However, if you are able to get the current official version of GZDoom working, that probably shouldn't be an issue. Perhaps someone who knows your hardware better can comment more meaningfully on that.
It could be that your antivirus software is doing something with the dev build. If it doesn't recognise the exe, it might be preventing access to it - but if task manager reports it as running, then maybe not.
If you suspect your ini might be an issue, then don't just copy it to the folder, but also call it gzdoom_portable.ini
That will make GZDoom behave like a totally portable installation - it will use that ini file and not try to read from one stored in... wherever the current standard for Windows keeping ini files is (Documents/My Games... I think). This works with official GZDoom too btw - like I said, official builds and dev builds arevery similar, except for the caveat that the dev build is a work in progress (and thereby has features and fixes added since the last official build) and the official build is to release standard.
If you want to confirm which ini your game is using, type whereisini at the console and it will tell you. Of course, you have to be able to get the game to run to do that.
[edit]And just to confirm, I just downloaded the build that you have been trying and fired it up. On my system it started no problem at all. So, that confirms that the build itself is OK, even if it doesn't help you very much.[/edit]
A dev build should work in exactly the same way as regular GZDoom. i.e. it should work if you unzip it to a folder (not in Program Files), provide it with a suitable IWAD and... that's it really.
I don't know your model of graphics card, but Intel cards can be a bit troublesome. However, if you are able to get the current official version of GZDoom working, that probably shouldn't be an issue. Perhaps someone who knows your hardware better can comment more meaningfully on that.
It [i]could[/i] be that your antivirus software is doing something with the dev build. If it doesn't recognise the exe, it might be preventing access to it - but if task manager reports it as running, then maybe not.
If you suspect your ini might be an issue, then don't just copy it to the folder, but also call it gzdoom_portable.ini
That will make GZDoom behave like a totally portable installation - it will use that ini file and not try to read from one stored in... wherever the current standard for Windows keeping ini files is (Documents/My Games... I think). This works with official GZDoom too btw - like I said, official builds and dev builds arevery similar, except for the caveat that the dev build is a work in progress (and thereby has features and fixes added since the last official build) and the official build is to release standard.
If you want to confirm which ini your game is using, type whereisini at the console and it will tell you. Of course, you have to be able to get the game to run to do that.
[edit]And just to confirm, I just downloaded the build that you have been trying and fired it up. On my system it started no problem at all. So, that confirms that the build itself is OK, even if it doesn't help you very much.[/edit]