AstonMartinDBS Posted December 26, 2020 Share Posted December 26, 2020 (edited) At least since OB 2.5.6.59398 (17.12.2020) there is a little issue with the ruler tool in the F10 Map: first right click generates/initiates the ruler at the cursor position as intended moving the mouse around shows the end position of the ruler far offset of the mouse cursor second right click sets the target position for the ruler correct Remarks: single monitor configuration @4k/UHD no mods installed Demo: Logfile: dcs.zip BTW: Within the mission editor the ruler works without issues. Edited December 31, 2020 by AstonMartinDBS Added remarks and DCS system settings 1 [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
Bones1775 Posted December 26, 2020 Share Posted December 26, 2020 do you run multiple monitors in game? i do and was having this issue as well as a mismatch of map coordinates. switched to a single monitor set up and both problems went away. Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted December 26, 2020 Author Share Posted December 26, 2020 42 minutes ago, Bones1775 said: do you run multiple monitors in game? No, I have a single monitor setup. Resolution is 4k/UHD (3840 x 2160 px). 1 [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
kirreen Posted December 26, 2020 Share Posted December 26, 2020 (edited) I've got this exact issue for a couple of the latest version, not sure when it started as it noticed it during after a break from DCS. Playing in VR on a Rift CV1, the only mods I have are kegetys vr shaders, but I get the same issue before applying the mod after updating DCS. Edited December 26, 2020 by kirreen 2 Link to comment Share on other sites More sharing options...
Schweppes Posted December 27, 2020 Share Posted December 27, 2020 Rift S user here! I got the same problem with the ruler,no mods and it happened after latest patch. 2 Link to comment Share on other sites More sharing options...
justrabbit Posted December 30, 2020 Share Posted December 30, 2020 (edited) I have the same issue, but even worse is that the TPod also does not slew to Steerpoint/waypoints and when planning a mission it suddenly becomes almost impossible to find targets as Tpod is not looking at target area. Also running 4K and have tried to change resolution to fix, but without finding a solution, sadly. Edited December 30, 2020 by justrabbit Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted December 30, 2020 Author Share Posted December 30, 2020 49 minutes ago, justrabbit said: TPod also does not slew to Steerpoint/waypoints Little OT, but make sure that the elevation of your WP is set to the ground elevation (refer map for correct height or enter an elevation of 0 in the ME for the TGT WP). 1 [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
TOViper Posted December 31, 2020 Share Posted December 31, 2020 On 12/27/2020 at 11:09 PM, Schweppes said: Rift S user here! I got the same problem with the ruler,no mods and it happened after latest patch. Rift CV1 user here, I go the same problem with the ruler when using the map F-10 view, although I don't have this problem when using a single screen. 1 2 Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1 Link to comment Share on other sites More sharing options...
justrabbit Posted January 2, 2021 Share Posted January 2, 2021 On 12/30/2020 at 7:49 PM, AstonMartinDBS said: Little OT, but make sure that the elevation of your WP is set to the ground elevation (refer map for correct height or enter an elevation of 0 in the ME for the TGT WP). The problem is even there when adding a steerpoint in game. TPod will still look at another location. It is very strange. Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted January 2, 2021 Author Share Posted January 2, 2021 (edited) 2 hours ago, justrabbit said: The problem is even there when adding a steerpoint in game. TPod will still look at another location. It is very strange. Your TPOD issue is definititely another issue than the here discussed map ruler issue. First of all you should check if your problem already has been reported. If not, save a track file which shows your issue, create a new thread and add the track file - namely in the correct forum (related to the affected module). Read this btw: Edited January 2, 2021 by AstonMartinDBS 1 [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
justrabbit Posted January 4, 2021 Share Posted January 4, 2021 On 1/2/2021 at 4:38 PM, AstonMartinDBS said: Your TPOD issue is definititely another issue than the here discussed map ruler issue. First of all you should check if your problem already has been reported. If not, save a track file which shows your issue, create a new thread and add the track file - namely in the correct forum (related to the affected module). Read this btw: Thank you. Yes I have been looking around. I assumed the problem was related. New here so it is not easy to know where and what to search for and when i saw this I assumed this was the problem. If you could help with where to search . Would this be a general question, weapons issue. Do not see the modules, so i find it a bit overwhelming when not knowing what to search for. Link to comment Share on other sites More sharing options...
Flappie Posted January 4, 2021 Share Posted January 4, 2021 You will find them all here. They each have a dedicated "Bugs and Problems" section. 1 Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
wydra91 Posted January 16, 2021 Share Posted January 16, 2021 +1 to this. I have my MFCD's exported to a monitor that is to the left of my game monitor. It appears the coords originate on the top left of the "window" and don't resize with the GUI. Everything about my GUI is fine, with the exception of the coords in F10, and the Ruler. Any chance we can get this looked at ED? Moving my MFCD monitor to the right isn't an option due to the way my screens are set up. Link to comment Share on other sites More sharing options...
streakeagle Posted January 17, 2021 Share Posted January 17, 2021 I am glad I am not alone. I finally took the time to experiment to try different aircraft and online/offline modes. But any time I am in the F10 map view, the displayed co-ordinates are incorrect and the ruler doesn't work right. I am using only a single monitor. ED had to have broken this fairly recently. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
AstonMartinDBS Posted January 27, 2021 Author Share Posted January 27, 2021 Issue has been fixed in current OB. Thx @ED! [Modules] A-10C, A-10C II, AH-64D, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 64 GB DDR5-5200, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H Link to comment Share on other sites More sharing options...
NyarlathotepZ Posted June 1, 2021 Share Posted June 1, 2021 My problem is still there, with 1 main monitor and 1 monotor on the left. Everything is fine, except the first loading screen and F10 map. 1 Link to comment Share on other sites More sharing options...
Recommended Posts