OpenXRay/xray-16

Hud fov.

Open

#1,446 opened on Sep 17, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (519 forks)auto 404
EnhancementGame assetsHelp wantedModmaker ExperiencePlayer Experiencegood first issue

Repository metrics

Stars
 (3,524 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe.

Since we already have FOV option as setting, possibly adding HUD fov would be great addition. Default COP rates are not best thing you can see here combined with high weapon recoil.

Describe the solution you'd like

  • Just adding hud FOV setting in menu
  • Main problem is that hud_fov cmd expects values in range 0...1, not 0...100. Probably console command should be updated to expect different range of numbers
  • With default settings some values above .7-.75 are cutting off hud rendering (usually stock). Changing src/xrEngine/device.h #define VIEWPORT_NEAR 0.2f to #define VIEWPORT_NEAR 0.05f helped me for most cases, but still stock rendering should be checked with extremely high FOV values near upper limits. + I am not also aware which side effects changing of this value can cause

Contributor guide

Research direction
Explore the hud fov console command in the codebase, update it to accept 0-100 range, and adjust the VIEWPORT NEAR define in src/xrEngine/device.h to accommodate high FOV values. Verify no rendering issues with extreme FOV.
Tech stack
cpp
Domain
game dev
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30