Screenwipe between hub maps
Moderator: GZDoom Developers
Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Screenwipe between hub maps
Someone informed me that an updated hub WAD I released recently was having issues losing progress between connecting maps. I tried moving my GZDoom config file out of the folder temporarily to reset everything and I noticed that map transitions within hubs now have screen wipe effects. Is this a bug or a new feature?
Re: Screenwipe between hub maps
It's the current version of GZDoom, BTW. 4.14.2. It happens with ANY hub wad. No mods loaded, this occurred when I moved the config file out of the GZDoom folder and the problem went away when I put it back again.
Re: Screenwipe between hub maps
I've been trying to replicate this and I can't. If I go between maps in a hub, I get no wipe but if I go between non-hub maps, or menu to map etc, I get whatever wipe I have chosen.
It might be useful to know that there is a variable called wipetype and this can be set different for the different games that GZDoom supports. The variable is stored in your ini file and, given that the presence/absence of your config file seems important, this might be relevant.
From the Wiki:
wipetype (integer)
Default: 1
Selects the type of screen wipe to use. There are currently four possible settings for this cvar:
0:No wipe
1:Melt
2:Burn
3:Crossfade
So, maybe search through your ini file for the word "wipe" and see what's there.
It might be useful to know that there is a variable called wipetype and this can be set different for the different games that GZDoom supports. The variable is stored in your ini file and, given that the presence/absence of your config file seems important, this might be relevant.
From the Wiki:
wipetype (integer)
Default: 1
Selects the type of screen wipe to use. There are currently four possible settings for this cvar:
0:No wipe
1:Melt
2:Burn
3:Crossfade
So, maybe search through your ini file for the word "wipe" and see what's there.
Re: Screenwipe between hub maps
Before removing the .ini folder my wipetype setting was 3, now it is one. But before I removed the .ini file, there was no screenwipes for hub transitions at all. I tried reinstalling from the zip folder for 14.4.2. Still happening. I may upload a video demonstrating the problem at some point.
Re: Screenwipe between hub maps
As a matter of interest, have you also looked in Documents/My Games/GZDoom ?
If you run GZDoom without specifying/creating a local ini file, it will create one there for you.
The console command whereisini will also tell you the exact location of the ini file that GZDoom is using.
If you run GZDoom without specifying/creating a local ini file, it will create one there for you.
The console command whereisini will also tell you the exact location of the ini file that GZDoom is using.
Re: Screenwipe between hub maps
I have, and moved it out of the folder to force it to create a new ini file. Problem persists. Only the melt effect, which is default. It beats me as to why hub transitions are doing this, irrespective of the hub wad.Enjay wrote: ↑Thu Aug 14, 2025 2:35 pm As a matter of interest, have you also looked in Documents/My Games/GZDoom ?
If you run GZDoom without specifying/creating a local ini file, it will create one there for you.
The console command whereisini will also tell you the exact location of the ini file that GZDoom is using.
Re: Screenwipe between hub maps
That's why I was wondering about the other locations. If you have moved your ini out of the GZDoom install folder (which is how I read your post - not sure if that's correct), it may have created one in "Documents/My Games/GZDoom". If so, all moving the file is doing is getting GZDoom to use the one in that folder rather than creating a new one from scratch. If all that has happened, then there might be some unusual setting in the one from "Documents/My Games/GZDoom".
However, I have now replicated the issue. The problem is, I'm not sure why it happens.
If I use my existing ini file (gzdoom_portable.ini in my GZDoom folder) then, with the attached MAPINFO created for testing purposes to put map01 and map02 of Doom2 into a hub (with altered music and skies as a quick chek to make sure the file has loaded) I get a screen wipe when I start the game, and no screen wipe when I transition to map02. All as expected.
If I remove the ini file in my GZDoom directory and allow GZDoom to create a new one in Documents/My Games/GZDoom then I get a screen wipe when starting the game (as expected) but I also get one when going from map01 to map02 (not expected).
Unfortunately, my gzdoom_portable.ini has a lot of stuff in it from various projects, so it's hard to navigate. I've searched for a few obvious things to compare between the two inis but I can't find what is causing the difference.
The MAPINFO if you want a quick easy test:
And here's a video of the difference between my two inis using the mapinfo.
Both videos with GZDoom 4.14.2.
The only settings that I changed in the new ini before recording the video was the movement and use keybinds, inverted mouse look and autorun so that I could actually control the player without fumbling around all over the place. WASD is a nightmare for me!
However, I have now replicated the issue. The problem is, I'm not sure why it happens.
If I use my existing ini file (gzdoom_portable.ini in my GZDoom folder) then, with the attached MAPINFO created for testing purposes to put map01 and map02 of Doom2 into a hub (with altered music and skies as a quick chek to make sure the file has loaded) I get a screen wipe when I start the game, and no screen wipe when I transition to map02. All as expected.
If I remove the ini file in my GZDoom directory and allow GZDoom to create a new one in Documents/My Games/GZDoom then I get a screen wipe when starting the game (as expected) but I also get one when going from map01 to map02 (not expected).
Unfortunately, my gzdoom_portable.ini has a lot of stuff in it from various projects, so it's hard to navigate. I've searched for a few obvious things to compare between the two inis but I can't find what is causing the difference.
The MAPINFO if you want a quick easy test:
wipetest.pk3- (246 Bytes) Downloaded 3 times
Both videos with GZDoom 4.14.2.
The only settings that I changed in the new ini before recording the video was the movement and use keybinds, inverted mouse look and autorun so that I could actually control the player without fumbling around all over the place. WASD is a nightmare for me!
Re: Screenwipe between hub maps
OK, well I've just spent an hour going through my ini file, bisecting it to delete sections and keep doing it until I made a change that altered how wipes work, and then drilling down into smaller and smaller sections until I (hoped) I could find the option responsible.
I have failed.
Either I cocked it up (several times - not impossible), or there is something weird at play here - like maybe the interaction of two (or more) variables, or one of those weird situations where something is addressing memory incorrectly and causing inconsistent results.
e.g. if I delete the entire [GlobalSettings] sections of an ini, I can change how the hub transition happens. However, if I then put it back and trim out half, put that back and then trim out half of that, and half of that, and half of that... eventually I get to a point where there are only a tiny handful of entries left that haven’t been checked and removing them makes no difference!
But, if I then go back and delete the whole [GlobalSettings] section again - despite having done it bit by bit earlier, I can again change how the hub wipe happens. 
So, sorry, I've tried to track down an option that could be responsible for this and failed.
I have failed.
Either I cocked it up (several times - not impossible), or there is something weird at play here - like maybe the interaction of two (or more) variables, or one of those weird situations where something is addressing memory incorrectly and causing inconsistent results.
e.g. if I delete the entire [GlobalSettings] sections of an ini, I can change how the hub transition happens. However, if I then put it back and trim out half, put that back and then trim out half of that, and half of that, and half of that... eventually I get to a point where there are only a tiny handful of entries left that haven’t been checked and removing them makes no difference!
But, if I then go back and delete the whole [GlobalSettings] section again - despite having done it bit by bit earlier, I can again change how the hub wipe happens. So, sorry, I've tried to track down an option that could be responsible for this and failed.
Re: Screenwipe between hub maps
Enjay wrote: ↑Fri Aug 15, 2025 9:34 am That's why I was wondering about the other locations. If you have moved your ini out of the GZDoom install folder (which is how I read your post - not sure if that's correct), it may have created one in "Documents/My Games/GZDoom". If so, all moving the file is doing is getting GZDoom to use the one in that folder rather than creating a new one from scratch. If all that has happened, then there might be some unusual setting in the one from "Documents/My Games/GZDoom".
However, I have now replicated the issue. The problem is, I'm not sure why it happens.
If I use my existing ini file (gzdoom_portable.ini in my GZDoom folder) then, with the attached MAPINFO created for testing purposes to put map01 and map02 of Doom2 into a hub (with altered music and skies as a quick chek to make sure the file has loaded) I get a screen wipe when I start the game, and no screen wipe when I transition to map02. All as expected.
If I remove the ini file in my GZDoom directory and allow GZDoom to create a new one in Documents/My Games/GZDoom then I get a screen wipe when starting the game (as expected) but I also get one when going from map01 to map02 (not expected).
Unfortunately, my gzdoom_portable.ini has a lot of stuff in it from various projects, so it's hard to navigate. I've searched for a few obvious things to compare between the two inis but I can't find what is causing the difference.
The MAPINFO if you want a quick easy test: wipetest.pk3
And here's a video of the difference between my two inis using the mapinfo.
Both videos with GZDoom 4.14.2.
The only settings that I changed in the new ini before recording the video was the movement and use keybinds, inverted mouse look and autorun so that I could actually control the player without fumbling around all over the place. WASD is a nightmare for me!
Yeah, I simply dragged the ini file from my GZDoom folder onto the desktop so that GZDoom would create new ini file in the folder from scratch with default settings. That's when the screenwipes between hub maps started happening.
I also tried this on my other PC which has 4.6.0 on it, and the screen wipes were never a problem when trying to replicate the problem there until I updated it to 4.14.2 on there, so there appears to be a mysterious bug with the latest version of GZDoom.