|
Notes |
|
|
(0006502)
|
|
Dusk
|
2013-06-24 23:05
(edited on: 2013-06-24 23:08) |
|
Confirmed during testing session on 1.1-130512-1932, sv_barrelrespawn and alwaysapplydmflags must be set
- a newly connecting client percieves the barrel as stuck in mid-explosion, as pictured
- barrels appear to vanish, reappear and then "jump" before detonation if shot after respawning
1.0 does not exhibit the behavior.
// [RH] Pretend as deathmatch for purposes of dmflags
// EXTERN_CVAR (Bool, alwaysapplydmflags)
#define alwaysapplydmflags true
pls thx
|
|
|
|
|
|
"Ghost" barrels always spawn at coordinate pair (0,0). The barrels that appear here are jointed to other barrels across the map that have respawned and appear to spam explosions when other respawned barrels have exploded. Barrels at this position appear with IDDT but can be passed through (with laggy collision through void space). |
|
|
|
|
|
We should find the latest beta build which didn't have this problem... |
|
|
|
|
|
This problem was introduced with the fix in e46657a3e75d7b5009a5aa1f2002f79f0789d7c3. |
|
|
|
|
|
While working on a fix I ran into 0000949 again. Can somebody check and report whether GZDoom fixed the problem yet in 0000949? |
|
|
|
(0006608)
|
|
Arco
|
|
2013-07-10 17:09
|
|
|
GzDoom does not appear to have that issue fixed in it's latest verision. |
|
|
|
|
|
I made a fix that doesn't rely on a GZDoom fix. Needs to be tested in the next beta build. |
|
|
|
(0006641)
|
|
Dusk
|
2013-07-14 21:49
(edited on: 2013-07-14 22:15) |
|
When a respawned barrel is shot, the barrel just vanishes on the client. It still deals damage though. This only happens after the barrel has been shot once and has respawned.
EDIT: Looks like they warp to (0, 0) on the client-side before detonating. Some barrels instead seem to fall from mid-air when detonating.
In addition, a barrel in gw2.wad map18 at -494 425 seems to disappear after first punched. It came back after being punched again. Also alwaysapplydmflags remains being annoying.
|
|
|
|
|
|
I think this is a different problem, i.e. neither caused by e46657a3e75d7b5009a5aa1f2002f79f0789d7c3 nor by its fix. Can somebody check if this is any different in 1.0 and if so, identify the first 1.1 beta build that had this problem? |
|
|
|
(0006645)
|
|
Arco
|
|
2013-07-15 14:47
|
|
Upon testing this in different versions, it appears that this problem was introduced at v1.1 130120-0905. Although it's rarity is more persistent on this version, I managed to make the barrels to warp to (0,0) by simply shooting at them, but their actors where they where originally are still there until the barrels cease to exist.
Any other erratic behavior was not observed, and this issue does not happen in all variations in v1.0. |
|
|
|
(0006647)
|
|
jwaffe
|
2013-07-15 15:43
(edited on: 2013-07-15 15:44) |
|
Yesterday during testing I made a wad that makes it easy to illustrate this "warp to 0,0" behavior; 0,0 is at the exact intersecting corner of the four colored squares in the map.
Attached: See MAP01_BarrelWarpTest.wad
I'm not sure if this has been said already, but only the respawned barrels have a problem, the barrels originally placed in the map explode normally.
|
|
|
|
|
|
The problem surfaced with this changeset but is actually caused by a bug that was already in 1.0. This should fix the issue. |
|
|
|
(0006657)
|
|
Arco
|
|
2013-07-15 19:43
|
|
Quote from "Torr Samaho"
The problem surfaced with this changeset but is actually caused by a bug that was already in 1.0. This should fix the issue.
Interesting. I didn't noticed anything with the barrels when I was testing 1.0, though it could have something to do with 0000817.
Quote from "Torr Samaho"
This should fix the issue.
And it is indeed fixed. |
|
Screenshot_Doom_20130624_184604.png (114,170) 2013-06-24 22:59
MAP01_BarrelWarpTest.wad (3,162) 2013-07-15 15:41