Possible collision physics issue on unreleased etf_furious map

[ensiform]

See https://www.youtube.com/watch?v=qZKw_BpYLkk

[ghost]

Hi, I just want to note that I think this bug is not ETe specific. It's an idtech3 bug that has been there since Q3A (1999). You can see this in q3tourney3 for example, and many, many other idtech3 maps. The problem occurs when you collide against a wall that is not 100% perpendicular. Simply put a cuboid clip brush over the obstacle.
Though, you are right it would be better to fix it by source code than by map geometry. Personally I never found a fix for it. Tremulous/Xreal fixed it iirc, by accident I think, because of their wall-climbing ability. Hmm..

[ensiform]

So it could be reproduced in regular ET engine then?

[ghost]

Yeah! You can reproduce this in any idtech3 game (at least I'm aware of). This means Q3, RtCW, ET and all mods and standalone games based upon it. Maybe I am wrong, but the only idtech3 game that don't behave this weird is Xreal (Tremulous pmove code), as already said.
You can even reproduce the issue in Jedi Academy. The map was called 'Yavin Training Arena' or something... You are more Jedi expert than me, so I think you know the map...
Maybe it is also worth to note that the issue is caused inside the pmove code imo (you can see this by making the bounding box visible if the game supports that (ET, Spearmint)), cgame suffers more or less depending on game. In Q3 games the effect (on the playermodel with cg_thirdperson 1) is more significant than in games >= RtCW. I don't know why, maybe because of the different animation system?
Nevertheless, the bobbing of the bbox and the view shaking (cg_thirdperson 0) are equal for all games.

It really depends on map geometry. As soon as a wall is not perpendicular (the bottom of the wall is nearer than the top, like a pyramid) than the issue occurs. Therefore nearly everywhere inside the tunnel of 'fueldump' the issue can be reproduced, even with regular ET engine.

[ensiform]

Not sure if I should close or just reclassify and push lower. Its not really an issue since the map is unreleased and can eventually be worked around.

[ghost]

Only you can decide what is right.
Imo, it depends on what the goal of your project (ETe) is. If the goal is to make another engine that is compatible with default assets (maps), then it would be a good idea to fix this bug because already compiled maps can not be fixed. But you also know that yourself ...
If you don't care about already released maps, then this problem is not so serious, map makers must fix it by using proper clip brushes ...
just some thoughts.