Maps that need compatibility settings.

[Graf Zahl]

No, you cannot just raise the floor in those sectors. The setup is supposed to fake a different light level. This is going to require more work: Raise those sectors to the floor and add a floor light transfer to them. You also have to make sure that this doesn't alter monster movement possibilities too much som some may also require block monster line flags.

[drfrag]

This has happened to me many times, falling into a pit with a monster. I think it cannot happen with infinitely tall monsters, have you tried that map with a different engine?

[Graf Zahl]

Correct, but some of those pits do not have any monster in them!

[XxMiltenXx]

So I get some code like this:

Code: Select all • Expand view

            OffsetSectorPlane(148, Sector.floor, 1136);
            SetLineFlags(827, Line.ML_BLOCKMONSTERS);
            SetLineFlags(828, Line.ML_BLOCKMONSTERS);
            SetLineFlags(829, Line.ML_BLOCKMONSTERS);
            SetLineFlags(842, Line.ML_BLOCKMONSTERS);
            level.sectors[148].SetPlaneLight(Sector.floor, level.sectors[122].GetLightLevel() - level.sectors[148].GetLightLevel());


This way the sector floor will be raised, then the lines around it will block all the monsters. However, shouldn't flying monsters be excluded somehow?
And then the floor plane of that sector will be darkened to match the surrounding sector.

[Graf Zahl]

I think the sectors I mentioned can be done without the blocking. You only need to do that in areas where it can actually affect monster mobility.

[Player701]

"Out of bound nodes"
Out of sector boundaries nodes"

Wow, that looks even worse than Plutonia 2 MAP25. I wonder how bad those node errors can get...

[XxMiltenXx]

So, here's the full code for the compatibility file for darken map 12. I ignored small sectors (line length 16). Concerning blocking some lines I left all unblocked. There are only 2 instances where it changes gameplay.
The hell knight in the bottom left wouldn't be able to walk out of this corner there without the fix:

and these 4 pinkies would be stuck without the fix:

Should I add blocking for the corresponding lines or are those changes negeglible?

Code: Select all • Expand view

         case '01592ACF001C534076556D9E1B5D85E7': // Darken2.wad map12
         {
            OffsetSectorPlane(126, Sector.floor, 1088);
            level.sectors[126].SetPlaneLight(Sector.floor, level.sectors[125].GetLightLevel() - level.sectors[126].GetLightLevel());
            OffsetSectorPlane(148, Sector.floor, 1136);
            level.sectors[148].SetPlaneLight(Sector.floor, level.sectors[122].GetLightLevel() - level.sectors[148].GetLightLevel());
            OffsetSectorPlane(149, Sector.floor, 1136);
            level.sectors[149].SetPlaneLight(Sector.floor, level.sectors[122].GetLightLevel() - level.sectors[149].GetLightLevel());
            OffsetSectorPlane(265, Sector.floor, 992);
            level.sectors[265].SetPlaneLight(Sector.floor, level.sectors[264].GetLightLevel() - level.sectors[265].GetLightLevel());
            OffsetSectorPlane(279, Sector.floor, 1072);
            level.sectors[279].SetPlaneLight(Sector.floor, level.sectors[267].GetLightLevel() - level.sectors[279].GetLightLevel());
            SetSectorTexture(279, Sector.floor, "OMETL13");
            OffsetSectorPlane(280, Sector.floor, 1072);
            level.sectors[280].SetPlaneLight(Sector.floor, level.sectors[267].GetLightLevel() - level.sectors[280].GetLightLevel());
            SetSectorTexture(280, Sector.floor, "OMETL13");
            OffsetSectorPlane(281, Sector.floor, 1072);
            level.sectors[281].SetPlaneLight(Sector.floor, level.sectors[267].GetLightLevel() - level.sectors[281].GetLightLevel());
            SetSectorTexture(281, Sector.floor, "OMETL13");
            OffsetSectorPlane(292, Sector.floor, 1056);
            level.sectors[292].SetPlaneLight(Sector.floor, level.sectors[291].GetLightLevel() - level.sectors[292].GetLightLevel());
            OffsetSectorPlane(472, Sector.floor, 1136);
            level.sectors[472].SetPlaneLight(Sector.floor, level.sectors[216].GetLightLevel() - level.sectors[472].GetLightLevel());
            OffsetSectorPlane(473, Sector.floor, 1136);
            level.sectors[473].SetPlaneLight(Sector.floor, level.sectors[216].GetLightLevel() - level.sectors[473].GetLightLevel());
            OffsetSectorPlane(526, Sector.floor, 1024);
            level.sectors[526].SetPlaneLight(Sector.floor, level.sectors[525].GetLightLevel() - level.sectors[526].GetLightLevel());
            OffsetSectorPlane(527, Sector.floor, 1024);
            level.sectors[527].SetPlaneLight(Sector.floor, level.sectors[500].GetLightLevel() - level.sectors[527].GetLightLevel());
            OffsetSectorPlane(528, Sector.floor, 1024);
            level.sectors[528].SetPlaneLight(Sector.floor, level.sectors[525].GetLightLevel() - level.sectors[528].GetLightLevel());
            OffsetSectorPlane(554, Sector.floor, 1024);
            level.sectors[554].SetPlaneLight(Sector.floor, level.sectors[500].GetLightLevel() - level.sectors[554].GetLightLevel());
            OffsetSectorPlane(588, Sector.floor, 928);
            level.sectors[588].SetPlaneLight(Sector.floor, level.sectors[587].GetLightLevel() - level.sectors[588].GetLightLevel());
            OffsetSectorPlane(604, Sector.floor, 1056);
            level.sectors[604].SetPlaneLight(Sector.floor, level.sectors[298].GetLightLevel() - level.sectors[604].GetLightLevel());
            OffsetSectorPlane(697, Sector.floor, 1136);
            level.sectors[697].SetPlaneLight(Sector.floor, level.sectors[696].GetLightLevel() - level.sectors[697].GetLightLevel());
            OffsetSectorPlane(698, Sector.floor, 1136);
            level.sectors[698].SetPlaneLight(Sector.floor, level.sectors[696].GetLightLevel() - level.sectors[698].GetLightLevel());
            OffsetSectorPlane(699, Sector.floor, 1136);
            level.sectors[699].SetPlaneLight(Sector.floor, level.sectors[696].GetLightLevel() - level.sectors[699].GetLightLevel());
            OffsetSectorPlane(700, Sector.floor, 1136);
            level.sectors[700].SetPlaneLight(Sector.floor, level.sectors[696].GetLightLevel() - level.sectors[700].GetLightLevel());
         }


Wow, that looks even worse than Plutonia 2 MAP25. I wonder how bad those node errors can get...

This is just how I named it, but from the pictures provided you can guess why I named it like that. Dunno if those bad nodes actually affect gameplay or not.

[Player701]

Another BSP glitch in Plutonia 2, this time in MAP29:

Code: Select all • Expand view

gzdoom.exe -iwad plutonia -file pl2.wad -warp 29 -nomonsters +"warp -3906 -1628"

The player ends up slightly below the floor level, which prevents them from getting to the teleporter without jumping. This is again due to a subsector errouneously referencing the wrong sector (749 instead of 783), and is probably caused by sector 749 having overlapping lines. Rebuilding nodes does seem to fix the issue, however, so I'm providing another PR to fix this.

[Player701]

So I was playing Alien Vendetta MAP28, and by the end of the map I was 1 item short of getting 100% items. It turned out to be a soulsphere in a secret area that can't be reached by normal means, at least in GZDoom. While doing some research on this, I stumbled upon this thread, and it turns out the cause of the problem is that the soulsphere's center is located directly on a line between two sectors with different heights. So I thought, why not just move the soulsphere slightly to get rid of this problem? This PR moves the soulsphere's position to the center of the "window" sector in that secret area and makes it reachable again.

Test with the following command-line parameters (Get Alien Vendetta here):

Code: Select all • Expand view

gzdoom -file av.wad -nomonsters -warp 28 +"warp -884 48"

and turn 90 degrees left as soon as the level starts.

Maybe I should also fix this for the old release? It looks like this map was changed in the second release, and, AFAIK, the first release is still around somewhere, so if you think I should fix it for the old version too, I will change the PR.

Also, that thread I linked above mentions MAP10 of the same WAD as well, but I'm not sure if there's anything wrong with that map (played through it myself a few days ago and everything was fine). If anyone knows of any problems with MAP10, please post more info abut it. Thanks

[Graf Zahl]

Good find. Back then the compatibility system wasn't sufficiently refined to handle this case.
This is another of those WADs that was made in the source port area by die-hard vanilla users and shows several issues with ports as a result.