So yesterday we played tm3_zuggzugg, a treat of a small FFA/tourney map!

Unfortunately one of the teleporters causes the player to become stuck upon exit. We've seen this in other maps as well, such as (Atomic Flow). This seems to have something to do with higher FPS (at least zuggzugg does) and we were able to exit the transporter fairly reliably by capping our FPS at 60 or less. I have a suspicion this is also why the jump pad trajectories are sometimes WAY off in certain maps too.

Is there a way to fix this in the game? If not, what would be the right way to do it? Some of these maps are REALLY good, and deserve to work properly in modern games.
Edited 20 seconds after the original posting.

Have you tried with pmove_fixed 1?

Hey thanks for the reply. I hadn't heard of this before, but it doesn't seem like this would help:
"This really only applies when computers are too slow to maintain a frame interval equal with pmove_msec. Anything that runs at 30fps or more (or at least faster than pmove_msec) pretty much renders the pmove_fixed variable irrelevant. "
old.reddit.com/r/q...ixed_on_or_off/

looks like a mapper fail, they put the teleporter exit too close to the wall.

you can move the teleporter exit and have a fixed version for your server. it's an easy enough process, but depending on where you're playing, it might not work (sv_pure 1 is a nuisance, i think everyone needs to download the fixed version if you have this enabled).

import the bsp into netradiant-custom (file -> import -> tm3_zuggzugg.bsp), move the entity, then recompile with only the flag "-onlyents" enabled. you now have a fixed bsp.