AstonMartinDBS

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:

I've created a simple Training mission 900 TF-51D Training.miz for the TF-51D at the Normandy. When I try to open this mission via ME and select it, the red message "List of required modules" followed by "TF-51D Mustang by Eagle Dynamic" is displayed. This occurs with all QuickStart missions as well as with the default training mission "3_taxi_TF51.miz" for the TF-51D delivered by ED. Other training missions are obviously not affected: Notes: The affected missions can be opened and flown despite this error message. Steam version of DCS World installed (current OB)

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).

Thx for sharing your mission! Works well. But is there a trigger where you don't have to choose which bomb to hit the target with, so it doesn't matter which bomb hits the target? I've attached a modified version of your mission (added a F/A-18C with a loadout of 8 Mk-82s). Caucasus FA-18C Test Mission Oil Gas Bomb.miz

I don't know if the core issue returned to DCS with the current OB or if it is an issue by mission design, but one of my F-16C wingmen crashed into my back while taxiing to the runway/preparing for takeoff. This happened three times in a row with the same mission. For description watch please. A trackfile is available as well (Mission 'King of the Hill' @Syria).

This script for the TARGET software enables you to bind every single switch position of your TM HOTAS Warthog. Note: You have to reset the most bindings within DCS when you use this script. Another option is to manually add a special action in the .lua file for your desired ON/OFF state. After editing the .lua you're able to bind the button/switch within DCS (via Options/Controls) to the new generated action.

I've tried this Syria mission now three times and the same issue occured every time: After the startup of my cold Viper I taxied to the runway. As soon as I stopped at the runway for the latest take off procedures wingman 1 of 3 crashed into my back and damaged my and his viper. Track attached. I don't know if it is a mission specific issue or if this old (already fixed) issue returned to DCS. Download the trackfile of my third try here.

No, I have a single monitor setup. Resolution is 4k/UHD (3840 x 2160 px).

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.

Just watch this tutorial from Wags to change WP settings (elevation for instance) inflight: To find the correct elevation of a desired position use the F10 map.

Thread is marked as [REPORTED], so it's definitely a bug. Otherwise it would have been marked as [CORRECT AS IS].

This tutorial from Wags shows how you can edit the threat tables:

Thx!

Is it intended, that the use of WPDSG affects all stations, as soon as QTY is set? I made a JDAM run with 4 GBU-32 on stations 2, 3, 7 and 8 and tried to designate WP 1 to WP 4 to those stations in TOO mode. When I use QTY and select all four stations after the assignement of the targets all works well: FA-18C JDAM TOO WPDSG ok.trk But when I use QTY and select all four stations before assigning the four targets via WPDSG all previous stations get overwritten and only the last assigned target will be hit: FA-18C JDAM TOO WPDSG weird.trk Is this behaviour normal or a bug?

This issue concens to AGM-154A only. The AGM-154C works well AFAIK.

Have the same issue with current OB (2.5.6.58125), which is easy to reproduce. AGM-154A release @ 30 k ft EFUZ: INST TERM: all default Result: 4 or 4 JSOWs in TOO mode FA-18C AGM-154A TOO Issue.trk and 3 of 4 in PP mode FA-18C AGM-154A PP Issue.trk flew over the target area and crashed into the ground. Same behaviour occured for me first in the combat mission "Patriot Express" (yesterday).

Thread is still marked as [NEED TRACK REPLAY] - so do you need another track?

Try this one:

Sehr schön! Ich frage mich grad nur, wie du es sooo lange ohne DCS aushalten konntest. Für mich warst du dank deiner Tutorials aber eigentlich nie "weg" - habe mir erst unlängst wieder einen Großteil deiner A-10C-Reihe reingezogen. In vier Jahren dürfte sich doch einiges getan haben...

Du sagst es. Finde das alles ziemlich eigenartig.

Genau. Zum Vergleichen mit deinen Settings habe ich dir mal zwei meiner .diff.lua angehängt: F/A-18C (Pitch, Kurve 0) RIGHT VPC Stick WarBRD {88D1F1E0-802F-11ea-8003-444553540000}.diff.lua A-10C (Rudder, Kurve 32) T-Rudder {2113B370-3BDA-11ea-8001-444553540000}.diff.lua PS: Zum Bearbeiten der .lua-Files empfehle ich dir Notepad++

Nachdem du deinen Config-Ordner gesichert hast könntest du ja noch versuchen, deine X52-Pro-Settings testweise für z. B. die MiG-15bis zu löschen: %USERPROFILE%\Saved Games\DCS\Config\Input\{Modulname}\joystick\{Logitech X52 Pro Flight Control System}{X52-Pro-ID}.diff.lua DCS wird die .diff.lua nach einem Neustart für den X52 Pro automatisch neu generieren und du kannst/musst dann die Bindings für den X52 Pro komplett neu belegen. Vielleicht ist dann das Problem endgültig gelöst. Sollte es nach dem Löschen der X52-Pro-Settings (andere/neue) Probleme geben, dann kannst du die alte .diff.lua einfach aus der Sicherung wiederherstellen, also in den o. a. Ordner kopieren. Sollte der Test aber erfolgreich sein, dann kannst du diesen Vorgang für die restlichen Module, bei denen dieses eigenartige Problem ebenfalls auftritt, wiederholen.

Also, dass die Treiber dieses eigenartige Problem verursachen, kann ich nicht ganz nachvollziehen, aber bitte... Ich habe bis zum Kauf der TM HOTAS Warthog- und WarBRD-Kombination die (relativ alten) 64-bit-Treiber v7.0.53.6 für meinen X52 Pro benutzt, wobei ich die (Profiler-)Software von Saitek/MadCatz/Logitech gar nie installiert hatte. Lief jedenfalls wunderbar mit DCS. Auch wenn es jetzt überhaupt nichts mit deinem gegenständlichen Problem zu tun hat, muss ich dir als X52-Pro-Besitzer unbedingt diesen Thread empfehlen:

Thank you so much for this hint @tagomago! DCS runs absolutely smooth now. I observed no more stuttering since deactivating vSync in DCS and setting vSync to "Fast" in the nVidia control panel (all other settings are default): Here are my DCS system settings:

Das soll mal einer verstehen. Würde dein Problem jedenfalls im offiziellen Bug-Forum für Controller-Probleme (Englisch) posten.