Odd prop collisions after TTT run in conjunction with other fretta gamemodes...

[jimbodude]

On my server, we run several fretta gamemodes, but every time after running TTT, prop collisions in any post gamemodes are messed up; they no longer collide with players at all, and most of them don't collide with the world.

This strange occurence is only happening with TTT, and was wondering if anyone had any suggestions, or an explanation?

My TTT cvars are currently:

ttt_postround_dm 1
ttt_no_nade_throw_during_prep 1
ttt_namechange_bantime 1
ttt_lastwords_chatprint 1
ttt_always_use_mapcycle 1
ttt_time_limit_minutes 45
ttt_karma_low_ban 0
ttt_karma_low_autokick 1
ttt_karma_low_amount 600
ttt_log_damage_for_console 1
ttt_ban_type "sm"

[Bad King Urgrain]

When a new gamemode loads (or the map changes), this occurs on a clean Lua instance. This means virtually anything TTT does can in no way influence other gamemodes. There are only two ways the server can be affected in a way that interferes with other gamemodes:

- Convars set by TTT. This is unlikely, as the only ones TTT modifies sets are mp_friendlyfire 1 (required for lag compensation) and sv_alltalk 0 (only if it's on). Neither is physics-related obviously.

- GMod bugs that somehow retain TTT specific things even after changing map/gamemode. I have never seen anything like this, and even if they exist I have no idea where these would be, because TTT doesn't do anything weird with props.

I also know there exist other Fretta servers that include TTT, who have not reported any issues to me, making it less likely that this is a fundamental issue with either TTT or gmod.

So I don't see what could cause this.

[jimbodude]

Thanks very much for your reply.

I just found it odd as this error isn't occurring after running any other gamemode, so I naturally assumed it was something to do with TTT.
I have no addons installed, except metamod + sourcemod, so I don't think the problems lies there.

I guess I'll look further into the configuration of my server and see if I can come up with something.

[Manmax75]

Do you have any anti-lag or prop-protection type things installed or inbuilt with anything?

[jimbodude]

I do not. I only have Sourcemod + Metamod, and then the gamemodes.

My gamemode list:

910
ascension
bombtag
claustrophobia
crash_n_smash
ctf
deathrun
dogfightarcade
Firefight
FortwarsX
freezetag
garryware
koth
lasertag
melonracer
OneInTheChamber
plane_crazy
prop_hunt
Psychokinesis
sandbox
sniperwars
Snowball
stalker
suicidebarrels
terminal_velocity
TremblingTiles
uhns
ultimatechimerahunt
ultimatedodgeball
zombieonslaught

+ TTT, although I disabled that right now.

[Bad King Urgrain]

Do you happen to know if going from TTT to Ascension would cause the boxes in Ascension to exhibit the issue? Because that is something I could easily test on my local srcds (both gamemodes being in there by default). If there's a different small gamemode I can get somewhere that you have observed the issue in, then that would be an option as well.

[jimbodude]

Yes, Acension is one of the gamemodes that you can clearly notice this obscurity in, as the boxes will no longer collide with the platforms, and most of the world.

[NaRyan]

With the problems you are describing I always had the same issues on my fretta server, however it was always after ultimatechimerahunt had been played.
After removing that the problems stopped.

Just noticed this post in the UCH gamemode thread on facepunch
Peep saying about same problems with prop collisions in any post gamemodes.
Could it be that UCH is the problem on your server?

[jimbodude]

That person is actually me. Shortly after posting this, I found out that it occurred in UCH too. TTT followed by another gamemode = prop collisions messed, and the same for UCH. Since we ran Dodgeball, TTT, then dodgeball to test this, I doubt that UCH could be the cause here. That said though, running dodgeball, UCH, then dodgeball causes the same effect as running TTT there.

[jimbodude]

Any news? Was anyone able to reproduce this?

[Bad King Urgrain]

I've just tested this. Started my DS, running TTT, joined and voted to switch to prop_hunt, on de_dust. Made a bot join so I could start a round, as a hunter. When I walked into props they worked properly. Shooting them also worked.

So it looks like I can't reproduce it on my server.

[phoenixf129]

To be honest, it sounds very much like a content mount error.