-0303- Posted December 19, 2020 Posted December 19, 2020 (edited) Update, rewrote this entirely. Bug more than cosmetic. Distance & direction shown top screen is wrong after applying Ruler when game resolution differs from monitor resolution. Found other additional (minor cosmetic?) bug: Fullscreen moving cursor F10 map show wrong elevation and N E position. Five images (a, b, c ,d, e) to illustrate. Game resolution 1280x768 (lowest possible). Ruler between center runway Senaki to center runway Nalchik. a) Game in window works correct (1280x768 game inside 1920x1080 monitor resolution). Distance & direction correct (red circled top screen and Ruler). b) [LAlt + Return] to fullscreen monitor resolution (1920x1080). Cursor is hovering Nalchik center runway (red arrow). Ruler not drawing correctly (green arrow). Distance & direction incorrect (red circled top screen and Ruler). Should (still) be distance 104 nm and direction (HDG) 35 degrees. c) After rightclick center Nalchik. Distance & direction top screen and Ruler are different (red circled). Distance & direction shown on Ruler is correct. Distance & direction top screen is wrong. Image d) and e). The additional bug. While moving cursor over F10 map elevation and position (up left corner) differs between game-in-window and game fullscreen. Cursor position at red arrow. Position: Imagine lines crossing Gudauta due south & Kobuleti due west. d) game-in-window and e) game fullscreen. 5698 feet sea level? Position N and E also differs. d) in-game-window shows correct e) Elevation and position N E differs. Clean install, clean Saved Games yada yada. Used Training > TF-51D > Takeoff Solo Practice to take images. Closely related also annoying bug. Edited January 3, 2021 by -0303- Intel Core i7 3630QM @ 2.40GHz (Max Turbo Frequency 3.40 GHz) | 16.0GB Dual-Channel DDR3 @ 798MHz | 2047MB NVIDIA GeForce GT 635M | 447GB KINGSTON SA400S37480G (SATA-2 (SSD))
Thadeyus Posted December 23, 2020 Posted December 23, 2020 Sorry, but this one is not cosmetic, I think it’s essential It affects the Position Display in the F10 Map. It seems like there are 2 „Coursers“ in the F10 Map. One for clicking Things wich work Good. The second one for Position tracking and game related stuff. This 2nd „courser“ is dependent on the Screem revolution as it seems. As a result the position tracking and Ruler are off. That’s especially bad If you want to set your owne Waypoints in an F18 and relay on the map data.
-0303- Posted January 2, 2021 Author Posted January 2, 2021 Ping. Update, rewrote top starting post entirely. Bug more than cosmetic. Intel Core i7 3630QM @ 2.40GHz (Max Turbo Frequency 3.40 GHz) | 16.0GB Dual-Channel DDR3 @ 798MHz | 2047MB NVIDIA GeForce GT 635M | 447GB KINGSTON SA400S37480G (SATA-2 (SSD))
-0303- Posted January 27, 2021 Author Posted January 27, 2021 All seems fixed now with DCS 2.5.6.60645 Open Beta patch. Distance & direction fixed. Quick look elevation and N E position seems fixed too. Intel Core i7 3630QM @ 2.40GHz (Max Turbo Frequency 3.40 GHz) | 16.0GB Dual-Channel DDR3 @ 798MHz | 2047MB NVIDIA GeForce GT 635M | 447GB KINGSTON SA400S37480G (SATA-2 (SSD))
Recommended Posts