[Fixed][1.32] Doom E4M1 problem with the red key-door.

[Doom_addict]

In E4M1 (Ultimate Doom) there is the door with the red key in east part of the map. This door (after finding the red skullkey) can opened only once, it closes immediately and then it can never be opened anymore, even when you opened the door and don't enter.

Summary: It opens once and close immediately forever.

Imho the door should stay open. Look also at:

http://www.youtube.com/watch?v=ej9f227sm3Y

Platform: openSUSE 11.3 and Vavoom 1.32 from repo with wadfile from Ultimate Doom (I bought this box many years ago).

[Ag3nTTeresa]

The same problem happens in Heretic on both the first and second level. I haven't made it any further due to this bug. The yellow key opens the door once and then never again. Any solutions so far?

[Firebrand]

This one is fixed in the latest SVN revision, you can get it from: http://svn.drdteam.org/vavoom/

[bar]

Is the solution solving a problem specific only to that map/door or to key-door? Or should every door be tested and "debugged"?
I found a problem with doors opening only once on doom with 1.32 version.
On a level, I can't remember which one, I was able to end it anyway.
On E1M7 there are at least two doors opening only once.
Those stuck doors don't require a key.

The archives in the link you provided look like windows binary.
How can I get a source tarball of the fixed version (or better, a patch for 1.32)?

[bar]

It seems to me that applying the following patch against 1.32 src tarball the problem is solved.

--- progs/common/linespec/VerticalDoor.vc.orig 2010-06-13 21:30:29.000000000 +0200
+++ progs/common/linespec/VerticalDoor.vc 2010-11-07 13:18:31.000000000 +0100
@@ -109,7 +109,7 @@
}

//HACK delay 0 means open
- if (Type == DOOREV_Raise && !Arg3)
+ if ((Type == DOOREV_Raise || Type == DOOREV_RaiseLocked) && !Arg3)
{
Type = DOOREV_Open;
}

Do you think that is correct or am I missing something else?

[Firebrand]

This one is fixed already, download the latest SVN revision from the link I posted above .

[bar]

As I wrote on post #3, in the link you provided I can find only Windows binaries.
I'm not using Windows, I'm using FreeBSD.

I've submitted a patch to update the vavoom port from version 1.30 to 1.32.
Actually the last 3 or 4 patches to keep the port working in FreeBSD has been submitted by me.
Then in 1.32 I've found the problem with the doors.
Luckily the patch has not been committed yet.

For some technical reasons, mainly because the FreeBSD port needs a downloadable source tarball, which AFAIK is not available for the latest svn revision (unless I create it and host it somewhere), I'm interested in fixing the problem in 1.32.

All I've asked is if you can kindly "give me a blessing" about the patch in post #4 or suggest something else.
In that case, well, I will be happy to reflect that in the FreeBSD port.

[b0rsuk]

I can't download a SVN build from the link posted above. Surprisingly, I don't use windows either.

By copying the link to the browser and modifying it, I managed to find this:

http://vavoom.svn.sourceforge.net/viewvc/vavoom/trunk/

Note the Download GNU Tarball link at the bottom of the page. I hope I can get this working.