Page 1 of 2

Doom Legacy wad errors

Posted: Sun Aug 12, 2018 3:45 pm
by Guest
I've tried to play a couple of wads originally for the Legacy source port, which seems to have worked in GZDoom in the past.

Phobia The Age: https://www.doomworld.com/idgames/level ... r/phobiata
Trying this is GZDoom 3.2.4, its not possible to start the first level, or other maps I tried to warp to. It simply says "No deathmatch starts". I tried it in 2.4.0, and it starts correctly (haven't played it much yet).

Hi-Tech Hell 2: https://www.doomworld.com/idgames/level ... s/g-i/hth2
This seems to work well enough up to a point in MAP03. It uses FraggleScript quite extensively. Pressing a switch for script 224 to activate an elevator (you need to do some other things first, to be in the right state), there is a camera sequence. I think the camera moves quite differently from what its supposed to do. But the main problem is that the player never regains control, so I can't go on. This happened in both GZDoom 3.2.4 and 2.4.0. There is a playthrough on Youtube which works and seems to use GZDoom.

Are these wads supposed to work in GZDoom? Is there a version which should have better compatibility? Is there any way to regain control from the camera when it gets stuck like this?

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 12:27 am
by Graf Zahl
Please retest with 3.5.0. 3.2.4 is already several months old.
Aside from that, Phobia: The Age is officially not supported and also not 100% compatible with GZDoom but I believe the deathmatch start problem has already been fixed.

For HTH2 please post a savegame with the player standing right before the switch that needs to be pressed. It has been two years since I last played that mod, so apparently something broke afterward.

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 3:42 am
by drfrag
Owen Honeydale wrote: I think the camera moves quite differently from what its supposed to do.
I tested that wad not long ago. Are you playing with Brutal Doom by chance? (or any other mod).

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 12:51 pm
by Graf Zahl
Fixed the camera movement.

The original code was nearly unreadable thanks to the BAM angle format it used and I missed some of the logic buried in there when I dumped that old code and rewrote it from scratch for floating point.
Two things were missing: Movement direction is determined by the angular difference, and the function should not stop until the full angular distance has been covered, even if the camera has arrived at its destination before finishing the angular move.

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 1:49 pm
by drfrag
Owen Honeydale wrote:Pressing a switch for script 224 to activate an elevator (you need to do some other things first, to be in the right state), there is a camera sequence.
I'd swear cameras worked a few months ago, where's the location of that switch? (idmypos).

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 1:53 pm
by Graf Zahl
Type 'fpuke 225' in the console, you do not need to find the switch.
It's also just one particular mode of the moving camera that was having problems, that's why I didn't spot it when the code was rewritten 2 years ago.

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 3:39 pm
by Guest
Coming back to report after trying in 3.5.0, I see you've already identified and fixed it! Looking forward to the next release.

I found another thing which was broken in the older versions I tried and actually fixed in 3.5.0. There's a teleporter in MAP03 you activate with a switch. In the older versions it got an object right on the teleporter which made it unusable. This is fixed in 3.5.0.

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 3:40 pm
by Guest
Great to hear you found it. Looking forward to the next release.

Re: Doom Legacy wad errors

Posted: Mon Aug 13, 2018 5:59 pm
by drfrag
Graf Zahl wrote:Type 'fpuke 225' in the console, you do not need to find the switch.
Thanks, but for me now it's even worse. The movement seems right (i compared with ZDoom LE) but now the camera gets stuck and won't return to the player view (actually it won't even change to the other cameras). Before the travelling was wrong but it didn't get stuck.
This happens both with MinGW-w64 and VS v140_xp 32 bit builds on win 8.1 32 bit (core2 duo). Same with ZDoom32.

Re: Doom Legacy wad errors

Posted: Tue Aug 14, 2018 12:06 am
by Graf Zahl
It worked when I last tested it. Will have to re-check this evening. Looks like the exit condition test doesn't work anymore.

Re: Doom Legacy wad errors

Posted: Tue Aug 14, 2018 12:39 pm
by drfrag
I've just checked the DRD Team modern 32 bit devbuild and it's the same as expected. I cannot test the 64 bit build.
I type 'map map03', 'god' and 'fpuke 225' in the console.

Re: Doom Legacy wad errors

Posted: Tue Aug 14, 2018 12:50 pm
by Enjay
What's meant to happen?

In a 64 bit git build from the 12th, I get the following when using the above commands:

A quick fly over these consoles:
Image

A brief look at this guy:
Image

A look at these guys:
Image

Then I'm here and able to play:
Image

Re: Doom Legacy wad errors

Posted: Tue Aug 14, 2018 12:56 pm
by drfrag
Thanks but you need to try the latest 14th devbuilds.

Re: Doom Legacy wad errors

Posted: Tue Aug 14, 2018 1:13 pm
by Graf Zahl
Now it's fixed.

Re: Doom Legacy wad errors

Posted: Tue Aug 14, 2018 3:21 pm
by Enjay
drfrag wrote:Thanks but you need to try the latest 14th devbuilds.
Ah, I hadn't noticed that there were some newer builds up.

Not that it's important now, seeing as how Graf has fixed it, but with the 64 bit build from the 14th, on fpuking 225, I got the same as above but without the flight over the consoles. i.e. the camera switched straight to the side view of the imp, then the other view and then back to me in the nukage pool.