Revising a previous sugestion I made here, I took my time and made a patch:
I added a new MAPINFO property: ForceWiperEffect
Setting this property for a map, forces the Wiper at exit even if the level belongs to a hub. The Wiper shown depends on the user settings (Melt by default for Doom and so on). I know this could be more polished, but it's a start. I used r3757 as a base, so it's possible that the patch could be outdated. Be advised that this is the first patch I've ever made, so if it does not work, please tell me and I will upload the modified source files instead (along with a text file pointing out the lines I added).
New MAPINFO property: ForceWiperEffect
Moderator: GZDoom Developers
Re: New MAPINFO property: ForceWiperEffect
Cleaned up the patch, so it doesn't include unnecesary file changes.
- Attachments
-
hubwipers.zip- cleaned up version
- (1.06 KiB) Downloaded 146 times
Re: New MAPINFO property: ForceWiperEffect
This is interesting, but it should really be extended with a parameter to pick the parameter specifying which wipe style to use (along with a "User" option that I suppose could serve as the default, making it possible to submit this now and patch it later and keep it backwards-compatible).
-
Edward-san
- Posts: 1774
- Joined: Sat Oct 17, 2009 9:40 am
Re: New MAPINFO property: ForceWiperEffect
sincerely I don't like the idea someone imposes anything different from my screen wipe style (none wins)...
Re: New MAPINFO property: ForceWiperEffect
"None" is exactly what I'd use it for -- inter-map transitions can have huge seams if a fade is inserted into the middle, and currently only hubs disable it. A "NoWipeEffect" could achieve that, though.
- NeuralStunner
-

- Posts: 12328
- Joined: Tue Jul 21, 2009 12:04 pm
- Preferred Pronouns: No Preference
- Operating System Version (Optional): Windows 11
- Graphics Processor: nVidia with Vulkan support
- Location: capital N, capital S, no space
- Contact:
Re: New MAPINFO property: ForceWiperEffect
Most users probably don't change it from the defaults. (Personally I use Burn for Heretic/Hexen, though it's not really seen in the latter much.)
Simplest case would probably be a flag for Cluster definitions, to enable transitions if it's a hub. (Or force them off for that cluster, perhaps.)
Or it could be could be a Map property:
Simplest case would probably be a flag for Cluster definitions, to enable transitions if it's a hub. (Or force them off for that cluster, perhaps.)
Or it could be could be a Map property:
- Default (On for single maps, Off for hubs)
- Off (No transitions at all)
- On (Force user's chosen transition, even for hubs)
- Melt, Fade, Burn (Force a specific transition)
Re: New MAPINFO property: ForceWiperEffect
I agree with Edward-san, and that's the reason I didn't give it a parameter to specify a wiper type. I think it would be annoying for someone to be forced to see a transition even if they have them set to "none" in their options. That's why there are no parameters. HeXen's MAPINFO doesn't need this property, but Strife surely does, as Vanilla Strife crossfades between levels (which the user can disable if he/she so desires). Anyways, I'm gonna see what I can do about parameters.Edward-san wrote:sincerely I don't like the idea someone imposes anything different from my screen wipe style (none wins)...
Re: New MAPINFO property: ForceWiperEffect
Okay, adding parameters is a bit more complex than I first thought. So in the meantime, I added a "ForceNoWiper" property for maps, which disables the wiper transitions even if the map does not belong to a hub. "ForceNoWiper" takes a higher priority over "ForceWiperEffect", so if both are set for a map, "ForceWiperEffect" is ignored.
BTW, I also added "ForceWiperEffect" to Strife's MAPINFO, just in case
BTW, I also added "ForceWiperEffect" to Strife's MAPINFO, just in case
- Attachments
-
wipersnew.zip- Base: r3770
- (1.85 KiB) Downloaded 152 times
