Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • EDuke32 EDuke32
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 98
    • Issues 98
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Richard Gobeille
  • EDuke32EDuke32
  • Issues
  • #190
Closed
Open
Created Aug 20, 2021 by Dino Bollinger@dibollingerDeveloper

Polymer: HUD models are not affected by the chosen FOV, and are rendered too close to the screen

This issue affects HUD 3D models such as the ones used by the HRP, and was introduced in r7329 (afdc7b52).

In Polymost, if the player increases the chosen FOV, the 3d model weapon will be drawn further away from the camera position, while in the case of Polymer the weapon remains at the same relative distance to the camera. Additionally, in r7329, the default position of the 3d model was moved closer to the camera in Polymer, breaking existing mods such as the HRP.

The following images show the model position at an FOV of 120. Note that in Polymost this works correctly, while in Polymer the 3D Model position is the same relative to the player, as if it were a 2D sprite. In Polymer the position is roughly equivalent to a FOV of 70.

This is probably a case of it just not having been implemented, rather than something introduced by that commit directly. The commit just exposes the problem.

Polymost: duke0131

Polymer: duke0132

Test files: pistol_hrp.zip

Assignee
Assign to
Time tracking