[Feature Request] Allow teleport view angles (Pitch/Roll) for players by separating camera angles from model angles

[Temmie2233]

As discussed in the previous issue regarding Hook_Teleport, base CS2 breaks playermodels when teleported with non-zero X (pitch) and Z (roll) angles. Currently, CS2Fixes aggressively resets these to 0.0f to prevent the bug.
While I understand that fixing the broken model is the priority, I am opening this feature request because restoring the ability to teleport players to look up/down is crucial for custom mapping (especially in ZE, MG, and movement modes).

Why is this feature important?

In Source 1 (CS:S and CS:GO), info_teleport_destination fully supported Pitch and Roll, and map makers have relied on this for over a decade. By forcing the player's view to a flat horizon in CS2, several major map design elements are broken:

1. Map Ports & Legacy Compatibility: Hundreds of legacy ZE and MG maps are currently being ported to CS2. Many of these rely on specific teleport angles. Without this feature, map porters have to manually redesign teleports, or players end up looking at walls/horizons instead of the intended direction.

2. Boss Fights & Cinematic Events: In ZE maps, players are frequently teleported to boss arenas. Map authors often use downward or upward pitch to instantly draw the players' attention to a boss above them or a hazard below them. Forcing them to look straight breaks the intended visual direction.

3. Vertical Gameplay Flow (Falling / Launching): In movement maps or ZE traps, players are often teleported into falling pits or launched upwards. If a player is teleported to fall down a deep shaft, forcing their camera to look perfectly horizontal feels incredibly disorienting and unnatural. They should be looking down.

Proposed Feature Implementation
As briefly discussed before, the ideal solution would be to satisfy both the engine's limitations and the mappers' needs:

• For the CCSPlayerPawn (The Model): Keep the current fix. Strip the X and Z angles so the physical character model remains unbugged and stands upright.

• For the CCSPlayerController (The Camera): Intercept the intended teleport angles and manually apply the X/Z rotation to the player's actual camera (e.g., via m_angEyeAngles or similar camera vectors).

Conclusion
Since Valve hasn't officially fixed the underlying CS2 engine bug yet, server plugins like CS2Fixes are the only hope for map developers to regain this lost Source 1 functionality. Implementing this split-angle workaround would be a massive quality-of-life improvement for the custom map ecosystem.

Thank you again for your time, consideration, and the hard work you put into this project!

[Vauff]

Do you mind providing some example maps? As I mentioned in the other issue, the only breakage I noticed seemed to be incidental usages.

[Temmie2233]

Do you mind providing some example maps? As I mentioned in the other issue, the only breakage I noticed seemed to be incidental usages.您能否提供一些示例地图？正如我在另一个问题中提到的，我注意到的唯一问题似乎只是偶然使用造成的。

Sure, here are two specific examples where this is 100% intentional and currently impossible to bypass without plugin assistance:

1. ze_gris (RTV Stage Drop)
   In the original version of ze_gris, there is a mechanic in the RTV stage where players who fall are teleported back up into the sky to drop down again. The map author deliberately set the teleport destination with a diagonal, downward pitch. This is a highly intentional design choice to give players better spatial awareness and a better visual experience of falling towards the arena. Forcing the pitch to 0 makes players look straight at the horizon while falling, completely ruining the intended cinematic and gameplay experience.
2. mg_reverse (My own map) & CS2 VScript Limitations
   I can speak directly from my own experience developing mg_reverse. The map relies heavily on VScript for teleportation. Before the AG2 update, applying X/Z angles to teleports worked perfectly. After AG2, it causes the player models to tilt and bug out at weird angles (which your hook correctly tries to prevent).
   However, here is the core issue: currently in CS2 VScript, there is no way for a mapper to independently modify a player's eyeangles without modifying the pawn's base angles.
   Historically, mappers just changed the base angles (or used Teleport), and the engine synced the camera automatically. Since VScript lacks the API to separate the model angle from the camera angle, mappers are stuck.
   This is exactly why we need a server plugin to step in and make this correction: stripping the X/Z from the pawn model (to prevent the AG2 model tilt bug) while passing those intended X/Z values to the controller's camera (so the map's scripted view direction is preserved).
   These aren't incidental mistakes, but deliberate design choices paired with current engine API limitations. Having CS2Fixes handle this separation would perfectly bridge this gap for the mapping community.