Callsign JoNay Posted November 7, 2023 Posted November 7, 2023 I'm sure this has been asked before, but I couldn't find the existing topic. I'm curious why ED models the size of the HMD/HMCS based on FOV but they model the NVGs as a fixed size on our displays.
Callsign JoNay Posted November 11, 2023 Author Posted November 11, 2023 Bump. Nobody sees the inconsistency going on here?
draconus Posted November 19, 2023 Posted November 19, 2023 (edited) Yes, NVG circle should have fixed fov based on the device. They corrected it for VR recently but it's wrong again in 2.9.1. Nevertheless it's wrong in both 2D and VR that it stays fixed against the screen even when you change the fov (zoom). Edited November 26, 2023 by draconus 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Callsign JoNay Posted November 30, 2023 Author Posted November 30, 2023 Can anyone from ED comment? Oversight? Or you guys just like it this way for some reason?
Callsign JoNay Posted December 29, 2024 Author Posted December 29, 2024 See this clip for how BMS handles the angular size of the NVGs: https://www.twitch.tv/callsignsqueak/clip/EphemeralSwissCaribouUWot-UMhlSHWrxItyZluQ This is the proper way to do it. Why are the NVGs a fixed angular size in DCS? Can someone at ED please acknowledge this? The way it's currently implemented is highly inaccurate, and needs to be fixed.
Recommended Posts