AstonMartinDBS

Mission setup: Map: Caucasus Targets: 4 static tanks Hornet: each tank has a WP 1 - 4 at ground level Flight: HSI/DATA/PRECISE activated JDAM full aligned prior release Issue: WPDSG doesn't point the TGPs exactly to the selected WP/Target, that counts for the LITENING as well as for the ATFLIR Each WP shown in the ATFLIR is several meters offset from the ME WP, which has been set exactly on target (and at ground level, of course). Tracks: (removed) Notes: This issue occurs in the F-16C (see https://forum.dcs.world/topic/316221-jdam-and-targets-of-opportunity/?do=findComment&comment=5124926) and in the A-10C II (see https://forum.dcs.world/topic/316657-tgp-inaccurate/) as well. So the problem appears also in other modules and is might related to the core. Also the JDAMS are quite inaccurate, too. Only two of four JDAMs hitted their target directly. But I don't know if this inaccuracy is realistic or not.

Should I create a new thread for the TGP offset issue?

I can confirm this behaviour. Indeed, there is a huge offset to the targets, when the TGP is pointing at the four WPs (all four WPs have been set to ground level). WP1/TGT1: WP2/TGT2: WP3/TGT3: WP4/TGT4: You can use this mission for testing (extracted from @TobiasA's Track): CA F-16C Test GBU38.miz

In the AH-64D Mission "Reservoir Fight" I've been ordered to land at the "Jump FARP" for briefing and rearming. I landed at the FARP, close to the supply vehicles, but at my request for rearming I got no response from the ground crew. Engine was shut down, APU runnin', door open. Track (~20 MB): https://drive.google.com/file/d/1K8_pZzTJ4g2mEyK3OvtblydxVZa3kjSz/view?usp=sharing Is this a general or mission bug or just an user error?

I was able to hit all four BTRs. One was a direct hit and three were very close. NV F-16C GBU accuracy.trk

I downloaded the first track (Test-TOO-GBU-38-1.trk) and was able to watch it (latest DCS OB installed). The mission is placed in Nevada. If you don't have this map you cannot see those missions or tracks.

If you haven't already seen, I strongly recommend the excellent AH-64D TSD turorials from @Wags: TSD Basics, TSD Points and TSD Navigation.

Simply press LAlt+Y (or LAlt+Z if you use a german keyboard layout) to switch through different coordinate types in the F10 map. Optionally you can switch the types by clicking directly on the coordinates in the F10 map (top left).

Will we ever get a fixed version of this mission?

v0.5.3 available: LASER has to be activated manually (as usual)

v0.5.2 available: adjustments to the latest DCS Open Beta update (2.8.1.34667.2): LASER is activated by default (fixed in v0.5.3);

Did you try to select "DCS: Black Shark 3 Upgrade"?

Oh, I've just tried to reproduce and answered but didn't double check for a similar report. Thanks!

You're right, there's an issue with the "Go to Waypoint"-option. In the attached sample mission you find a group of 4 tanks. The group has 6 WPs (0 ... 5), type is set to "On road" each. At WP 5 the tanks are ordered to return to WP 0. The group follows the WPs as intented on the road until WP 5, after that the group moves towards WP 0, but "Offroad" instead "On road" (issue #1). The group stops shortly before it reaches WP 0, so it won't start again from WP 0 (issue #2). @Arashenstein: https://forum.dcs.world/forum/815-mission-editor-bugs/ is the better place for this bug report PG ME GoToWP Issue.miz

Is this the wrong subforum for the issue or why did we still get no response from ED after three months? Do we have any chance to get this fixed @BIGNEWY?

No changes in 2.8. Track file 05 PG FA-18C SC Case II WrongViewConditions.trk. The view conditions should be adopted to simulate correct conditions for a Case II Recovery.

Already tested without any issues on the current OB. Are you using the Stable version @Nate Kott? Pls share a track instead of a video, if you can reproduce the issue.

The problem is maybe fixed in the next OB, if you report the translation issue soon. Make a screenshot of the affected bindings and describe exactly what's runnin' wrong. I sadly cannot confirm or report because I use the english language version of DCS.

Have you already reported this in the following thread?

Well, I forgot to remark, that I'm using the DX128 script for my TM Warthog. The script allows you to bind every single button/switch position. For further information see

Änderung auf "Punkte" sollte das Problem lösen. @EagleEye wird sich das sicher anschauen.

Of course, TrackIR doesn't need much power, but propably the summation of all devices connected to the hub induces the problem - or simply this:

I use an internal PCIe-Card with 7 external USB-ports. The card gets additional power from the internal power supply. I never had a problem with my USB devices connected to this PCIe-Card. AFAIK most external USB hubs cause problems with power-hungry devices - even with external power supply.

They are still present and working for me in the current OB 2.7.17.29140

Disable VSync within DCS options and Set VSync in the nVidia Control Panel for DCS.exe to "Fast" ...and here is another possible solution: