Maps that need compatibility settings.

Is there something that doesn't work right in the latest GZDoom? Post about it here.

Moderator: GZDoom Developers

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!

Re: Maps that need compatibility settings.

Postby Gez » Tue Feb 04, 2020 3:50 am

http://manbitesshark.com/downloads.html

Those should be the latest versions (1.16 IIRC).
Gez
 
 
 
Joined: 06 Jul 2007

Re: Maps that need compatibility settings.

Postby Caleb13 » Sun Feb 09, 2020 6:09 am

Two infamous WADs Rootpain and do_it2 were recently discussed at Doomworld, but they don't work properly in GZdoom 4.2.4.

Rootpain:
-The fetus doesn't appear when you destroy the ovaries.
-The game doesn't crash if the fetus kills you (which was the best and creepiest feature, IMO).
-There is no "you've aborted the baby" text if you kill the fetus.
By some trial and error, I found out it works best with GZdoom 1.7.0, but the final text still doesn't appear. Here is Rootpain download link:

https://tinyurl.com/rhemrap

Do_it2:
-The lights don't dim after you use the knife.
-The player bleeds out indefinitely and doesn't die.
-The blood level in the bathtub doesn't rise.
The last version it (mostly) works is prehistoric Zdoom 2.2.0, I was unable to run earlier versions on my machine. Here is download link:

https://www.doomworld.com/idgames/level ... -f/do-it-2

And here a video how it should work:

https://www.youtube.com/watch?v=xsjrwj_sjXs
Last edited by Caleb13 on Sun Feb 09, 2020 6:49 am, edited 1 time in total.
Caleb13
Death will not be your end; your soul will burn in Hell forever!
 
Joined: 30 Jun 2010

Re: Maps that need compatibility settings.

Postby Graf Zahl » Sun Feb 09, 2020 6:42 am

Please fix your link to rootpain.wad
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: Maps that need compatibility settings.

Postby Gez » Sun Feb 09, 2020 6:45 am

Caleb13 wrote:https://archive.org/download/**LINK_DISABLED**.org_WAD_archive_part_R/rootpain.wad

This link doesn't seem to work, and I figure that the **LINK_DISABLED** part of the URL might be why.
Gez
 
 
 
Joined: 06 Jul 2007

Re: Maps that need compatibility settings.

Postby Caleb13 » Sun Feb 09, 2020 6:51 am

I can't fix it, the forum automatically changes/disables it. You can get the original link here in the post by Mad Butcher:

https://www.doomworld.com/forum/topic/6 ... d/?page=67
Caleb13
Death will not be your end; your soul will burn in Hell forever!
 
Joined: 30 Jun 2010

Re: Maps that need compatibility settings.

Postby 3saster » Sun Feb 09, 2020 6:51 am

One is a map were you kill and abort a fetus, the other is one where you walk into a bathtub to slit your wrists. Are these REALLY the maps that need GZDoom's automatic compatibility? They are dumb meme maps that are just meant to be edgy AF, adding compatibility for them would be severe overkill imo.
Last edited by 3saster on Sun Feb 09, 2020 6:57 am, edited 1 time in total.
User avatar
3saster
 
Joined: 11 May 2018
Location: Canada

Re: Maps that need compatibility settings.

Postby Rachael » Sun Feb 09, 2020 6:52 am

I tinyurl'd the link so that the forum doesn't try to fix it.

It was a link that mentions a server that is now defunct, of which the domain name leads to apparently some really nasty malware.
User avatar
Rachael
Webmaster
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support

Re: Maps that need compatibility settings.

Postby Graf Zahl » Sun Feb 09, 2020 7:22 am

Rootpain doesn't work anymore because the author was abusing undefined behavior. Instead of using a map spot he used a CustomSprite actor with undefined parameters. These got changed so that they destroy themselves rather than stick around. And considering this entire mod it's not something I'm going to add a workaround for.

As for Do-It-2, bad use of DECORATE: It calls A_Explode(1, 2, 0) where 0 is the flags word which overrides the XF_HURTSOURCE flag.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: Maps that need compatibility settings.

Postby Caleb13 » Sun Feb 09, 2020 9:21 am

Oh well, nevermind then. I also posted my findings at Doomworld, so people should be able to Google that Gzdoom 1.7.0 is the best for Rootpain.
Caleb13
Death will not be your end; your soul will burn in Hell forever!
 
Joined: 30 Jun 2010

Re: Maps that need compatibility settings.

Postby ketmar » Sun Feb 09, 2020 3:19 pm

>As for Do-It-2, bad use of DECORATE: It calls A_Explode(1, 2, 0) where 0 is the flags
>word which overrides the XF_HURTSOURCE flag.



wiki: XF_NOTMISSILE — Not a missile: if set, the calling actor is considered to be the source. By default, the calling actor is assumed to be a projectile, and the source is therefore considered to be the calling actor's target.
now, player's Target is `none`, so XF_HURTSOURCE should not matter here. either current `A_Explode()` is buggy, or the wiki should be fixed.
User avatar
ketmar
k8vavoom developer
 
Joined: 01 Oct 2016

Re: Maps that need compatibility settings.

Postby JPL » Wed May 27, 2020 10:39 pm

Ran into this old map on my stream tonight, and it crashes on start:

https://doomworld.com/idgames/levels/doom/g-i/ganymede

The comments on that page suggest that a simple node rebuild is needed to fix it. The map's checksum is
Code: Select allExpand view
B2F7FD45B6766A052F6486D9BEE9B36A // GANYMEDE.WAD e1m1


This is the sort of thing that can be handled from the zscript compatibility post-processor, right?
User avatar
JPL
 
 
 
Joined: 09 Apr 2012

Re: Maps that need compatibility settings.

Postby Rachael » Thu May 28, 2020 12:23 am

The crash needs to be fixed first, but if there are any further problems after that then rebuilding the nodes might be prudent.

I think a simple node rebuild "might"(?) still be available with compatibility.txt, not sure. It can be done with the postprocessor too, though, if I recall.
User avatar
Rachael
Webmaster
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support

Re: Maps that need compatibility settings.

Postby Graf Zahl » Thu May 28, 2020 12:58 am

Broken nodes can cause crashes that are hard to fix, I'M not sure if that's doable here.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: Maps that need compatibility settings.

Postby drfrag » Thu May 28, 2020 4:39 am

IMO it's not worth adding a compatibility entry for this, it's a random 1994 quality map. I mean the bad reviews discourage dowloading it and it always crashed in ZDoom.
Two linedefs have invalid sidedef numbers, Prb+ has no problem with that.

Edit: it runs with RUDE and Crispy but crashes with Chocolate Doom, monsters get stuck and sometimes don't see you.
Edit2: There are no warnings in the console (RUDE). GZDoom builder says:
Linedef 74 references invalid sidedef 65534. Sidedef has been removed.
Linedef 72 references invalid sidedef 65534. Sidedef has been removed.
User avatar
drfrag
Os voy a romper a pedazos!
Vintage GZDoom Developer
 
Joined: 23 Apr 2004
Location: Spain
Discord: drfrag#3555
Github ID: drfrag666

Re: Maps that need compatibility settings.

Postby drfrag » Thu May 28, 2020 8:59 am

From within VS rarely crashes and the console says:
Code: Select allExpand view
e1m1 - Hangar

Sidedef 92 has a bad sector
Unknown middle texture 'ªºß=I5â=' on second side of linedef 72
Unknown top texture 'ž¿=֠Á=' on second side of linedef 72
Unknown bottom texture '²CÑ=I•Ó=' on second side of linedef 72
Sidedef 95 has a bad sector
Unknown middle texture 'ªºß=I5â=' on second side of linedef 74
Unknown top texture 'ž¿=֠Á=' on second side of linedef 74
Unknown bottom texture '²CÑ=I•Ó=' on second side of linedef 74
User avatar
drfrag
Os voy a romper a pedazos!
Vintage GZDoom Developer
 
Joined: 23 Apr 2004
Location: Spain
Discord: drfrag#3555
Github ID: drfrag666

PreviousNext

Return to Bugs

Who is online

Users browsing this forum: No registered users and 1 guest