goestrip Posted December 20, 2020 Posted December 20, 2020 Since last friday update, the F10 ruler tool doesn't really work. the ruler is drawn from a position (i can't understand the logic of it) to an offset position of the mouse cursor. It's unusable. It works normally if not in VR. 1
Dunx Posted December 21, 2020 Posted December 21, 2020 +1 ROG Z690 Hero ● i9-12900K 5.5GHz ● Giggy RTX 3090 OC ● 32GB 4800MHz ● Firecuda M.2s ● Reverb G2 ● Win11Pro //// A10CII ● AH64D ● AJS37 ● AV8BNA ● C101 ● CEII ● F16C ● F5EII ● F86F ● FA18C ● FC3 ● I16 ● KA50 ● M2000C ● MI8 ● P47D ● SA342 ● SPIT ● UH1H ● Y52
Flappie Posted December 21, 2020 Posted December 21, 2020 Are you using a DCS screen definition lower than your Windows screen definition? ---
Taz1004 Posted December 21, 2020 Posted December 21, 2020 I can confirm. Not sure what you mean by screen definition but if you mean resolution, there's no resolution setting for VR. It sort of works if you right click on starting point, ignore the real time line, and just click on the end point with your mouse. It's just that after first right mouse click, the line drawn is off. Better Smoke - Better Trees Caucasus - Better Trees Syria - Better Trees Mariana - Clear Canopy Glass
Chroma99 Posted December 21, 2020 Posted December 21, 2020 I can also confirm, and one of my friend too. Both in VR. 1
Thadeyus Posted December 21, 2020 Posted December 21, 2020 +1 I dont use VR but have the same bug. I seems depending on your F10 Zoom status. This will be a Bug with the courser reporting and the screen resolution. On maxed zoom out on Persian Gulfe Map it’s more than +10°. I use 3 screams left screen is LDDI middle Screem is the Viewport and Right Screem is RDDI.
ED Team BIGNEWY Posted December 24, 2020 ED Team Posted December 24, 2020 I have reported this to the team for checking thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Donglr Posted December 24, 2020 Posted December 24, 2020 I think this is related to https://forums.eagle.ru/topic/256349-easting-coordinates-in-f10-map-wrong
Hawkeye_UK Posted December 27, 2020 Posted December 27, 2020 +1 --------------------------------------------------------------------------------------------------------------------------- DCS & BMS F4E | F14B | AV-8B | F15E | F18C | F16C | F5E | F86 | A10C | JF17 | Viggen |M2000 | F1 | L-39 | C101 | Mig15 | Mig21 | Mig29 | SU27 | SU33 | F15C | AH64 | MI8 | Mi24 | Huey | KA50 | Gazelle | CH47 | OH58D | P47 | P51 | BF109 | FW190A/D | Spitfire | Mossie | CA | Persian Gulf | Nevada | Normandy | Channel | Syria | South Atlantic | Sinai | Kola | Afgan | Iraq Liquid Cooled ROG 690 13700K @ 5.9Ghz | RTX3090 FTW Ultra | 64GB DDR4 3600 MHz | 2x2TB SSD m2 Samsung 980/990 | Pimax Crystal/Reverb G2 | MFG Crosswinds | Virpil T50/CM3 | Winwing & Cougar MFD's | Buddyfox UFC | Winwing TOP & CP | Jetseat
Dangerzone Posted December 27, 2020 Posted December 27, 2020 +1. However for me - it's incorrect until I click the destination point, at which time the line 'jumps' from my source to destination and gives me the correct distance and bearing and draws correctly. (ie, while it's in the 'free ruler' mode where I've selected the start but haven't clicked on destination it doesn't work. To click on the destination I ignore where the line is pointing and just put my cursor where I want the destination and click and then the line fixes itself up).
Ziptie Posted December 27, 2020 Posted December 27, 2020 (edited) On 12/24/2020 at 1:30 AM, BIGNEWY said: I have reported this to the team for checking thank you +1 for the problem with the ruler when using VR. You have to click where you want the ruler to start and then click where you want the ruler to end, before the ruler will "align properly." Also noticed that the bearing listed on the ruler is different than the bearing listed at the top of the F10 map. This is an exceptionally annoying bug that is very difficult to handle when using VR. I switched to 2D and it worked as it had before (normally). Back to VR and is behaving "broken." Cheers, Ziptie Edited December 27, 2020 by Ziptie i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria
admiki Posted January 5, 2021 Posted January 5, 2021 I have same problems, but also with MGRS readout in VR. 2D works fine
wydra91 Posted January 16, 2021 Posted January 16, 2021 On 12/24/2020 at 1:30 AM, BIGNEWY said: I have reported this to the team for checking thank you Just a heads up @BIGNEWY I stumbled into this post when trying to figure out why I am having the same problem. In my case, I'm not in VR, but I have my MFCDs exported to a monitor to the left of my main one, aligned with the bottom. My coords appear to be offset exactly to the left, but not down. So it appears that the Ruler and Coordinate system are scaled to the overall window size and not the GUI window size as reported in the monitorconfig.lua.
Recommended Posts