You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Enabling vertical FOV doesn't affect FOV at all. I have to manually override FOV to make it work. But that affects on-screen prompts so it's unusable.
Desktop and VR (please complete the following information):
Windows 11
GeForce RTX 4070 Ti
Ryzen 7 5800X3D
Additional context
Up until version 1.5.1 it was working correctly. That is enabling vertical FOV actually enabled vertical FOV and its adjustment didn't affect HUD. After the change introduced in 1.5.2 it's as broken as Global FOV as it affects HUD. Ultimate Trainer is capable changing FOV without affecting anything, so clearly it's possible to make it work, but it shouldn't be required for a functionality that was working just fine a year ago.
As reported by different user, FOV adjustment is broken even in VR: #941
The text was updated successfully, but these errors were encountered:
Describe the bug
Enabling vertical FOV doesn't affect FOV at all. I have to manually override FOV to make it work. But that affects on-screen prompts so it's unusable.
Upload logs and any crash dumps
re2_framework_log.txt
Identify the REFramework version
1.5.2, commit f0f73b2
To Reproduce
Steps to reproduce the behavior:
Expected behavior
REFramewrok should convert game's horizontal FOV to vertical one and not affect HUD
Screenshots
Default FOV:
Vertical FOV:
Vertical FOV Override:
Vertical FOV in 1.5.1:
Desktop and VR (please complete the following information):
Additional context
Up until version 1.5.1 it was working correctly. That is enabling vertical FOV actually enabled vertical FOV and its adjustment didn't affect HUD. After the change introduced in 1.5.2 it's as broken as Global FOV as it affects HUD. Ultimate Trainer is capable changing FOV without affecting anything, so clearly it's possible to make it work, but it shouldn't be required for a functionality that was working just fine a year ago.
As reported by different user, FOV adjustment is broken even in VR: #941
The text was updated successfully, but these errors were encountered: