Notes |
|
(0011541)
|
Edward-san
|
2015-01-25 15:54
(edited on: 2015-01-25 15:59) |
|
Reporting what I found regarding the inconsistency between zandronum and zdoom:
zandronum 2.0 inherits a bug from zdoom 2.5, which was reported here and the example wads here belong to that (if you test the harmless example wad offline, the door does not push you away).
That was fixed in r2620. This commit also fixes two bugs which were reported: APROP_Invulnerable not working, 7-years old bug at that time and the ArmorFactor issue, which happen both also in zandronum 2.0.
I could apply the patch to zandronum 2.0 without problems and this makes the poly door in the example wads work exactly as in zdoom trunk.
|
|
|
|
After fixing it, regarding the offline and online inconsistency: when a player gets in the way of the polyobject, the client will see the polyobject continuing the rotation, even though it should not and should wait for the obstacle to get pushed away. |
|
|
|
I started to look into the issue. The problem is that the client doesn't check locally whether the door is blocked, while the server doesn't inform the client about the block either.
I think this problem crept in with TIHan's poly object door changes. I'll see what we can do about this. |
|
|
|
This should fix the issue. |
|
|
|
While I can't run it because I have linux, offline I reported a bug to zdoom which happens also in zandronum and regards a possible way to break the door. Sadly it's still in review, I hope randi or graf can accept one of the two patches I made to fix it.
|
|
|
(0011583)
|
cobalt
|
2015-02-01 20:37
|
|
|
|
|
Yeah, the online fix works fine for me. Waiting for more feedback to confirm this. |
|