Landmarks: What they are and why they are broken

[CraftyCritter]

Landmarks are used in maps when mappers want to have a seamless transition between 2 places. This differs from regular teleports, as regular teleports teleport you to an exact 
location in the level while landmarks teleport you to a position offset from the landmarks position. Example video:

https://streamable.com/2k5tbv

Notice how even though I went through the same teleporter, I was still at the same height on the ramp the entire time.
There are good examples of broken landmarks on Silver 3's post so I won't post proof, but I encourage people to read his post so knowledge of the bugs on KZG is noticed and possibly something is done to fix them.

What is wrong with the landmarks:
When going through landmarks, the players angles are snapped to 0 0 0, which makes some maps either hard to complete (surf_drift_go) or impossible (surf_nostromo). This happens on all other maps with broken landmarks. This Isn't an angle that is shared by the start/stage zones when !back or !r is used. This issue does not happen during offline play. Examples of landmark angles from surf_drift_go:

Before s2 Landmark:
setpos -14417.970703 -5067.417480 -13666.388672;setang -0.579869 87.539848 0.000000
After:
setpos 6661.984863 -16008.321289 -6102.807617;setang 0.000000 0.000000 0.000000

Before s3 Landmark:
setpos -14164.572266 -14544.412109 -2786.415039;setang 1.601695 -179.529434 0.000000
After:
setpos -4302.438477 -14550.205078 1738.599121;setang 0.000000 0.000000 0.000000

I got these values with the console command "getpos". Notice how setang is set to 0 0 0 after each landmark.

Why they are broken:
I did my own testing by decompiling surf_drift_go and checking out the landmarks for myself. After looking at the teleports and comparing what they do on KZG, I found that only triggers with a set "Local Destination Landmark" have the issue.
Trigger with it set:

Trigger without it set:

I then tried changing the "Use Landmark Angles" option to yes, which sets the teleported player's angles to the landmark's angles, and the problem started happening. Proof:

https://streamable.com/rqet72 (first clip has Use Landmark Angles set to no, the second clip has it set to yes)

So the problem that KZG has is that the player's angles are being set to the landmark's angles instead of preserving them.

Possible Cause:
A possible cause of this happening is a plugin that forces the player's angles to be the same as the landmarks, and there is a plugin for this: 

https://forums.alliedmods.net/showthread.php?t=271455

If a plugin like that was added, I'm sure that it would have been added with good intentions but right now unless an admin can come forward and explain why they decided to add a a feature like this I see no reason for it to be installed. This isn't even a hard change, just remove the plugin and restart the server at night or when a new CSGO update comes out.

 

I have been surfing on KZG for about 2 years and have above average knowledge of the source engine, so please take this post seriously and don't ignore the issue (and all of silver 3's post issues) like the admins did when most of the times got glitched. 

Edited January 25, 2021 by CraftyCritter

[Cheems]

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[Bl@ñk (Bl@storious)]

have you told the staff that you made this post? i see noone's responded yet, maybe they haven't seen it yet?

[drk]

As far as I'm aware a lot of maps that have/had landmark issue have been fixed, If you find any in the future the best way to get it fixed is to either make a ticket on discord under #support or dm me directly through discord with the Map name, Stage/location of landmark issue and I will look into getting it fixed

drk#6492