Hornet81

@JeffreyC, Were they RDY? Keep in mind that when you select the Mavs the gyro need time to spool up. They E needs 30 seconds and the E2 90 seconds. Every time you deselect them the gyro will spool down. Let us know @JeffreyCif it worked.

Seems that the MAP pb issue has been fixed. If it is not coming in another hot fix should be in the next coming update.

Hi @Aernov, Thanks for the report. We are going to have a look into that.

Hi guys, Can you confirm you are still having the same issue after this last update?

Hi guys! I have been testing your issue in SP and MP and it worked. Could you send us a track and give us more information on what server or when you get that? thanks

Hello guys, Thanks for the report! We will check that issue ASAP and let you know. Regards,

Hello guys, Thank you for the report. We will have a look into this and let you know.

Hi @dresoccer4, Thanks for the report. Could you try to switch off the Depth of field and motion blur in DCS settings and try if you get the same result? Regards

Thanks @Kappa for the report, So if that is fixed we are going to move the report to SOLVED. Regards

@Bog9y, Yes I noticed that it was just one time. I filled the report as the variation correction was not applied, and this happens in all maps. So they are working on it now to fix it and should be solved in the next update. Thanks again for the report

Larnaca airport GP is not detected when established on the LOC at any distance. The GP is detected when overflying the runway. Seems that the GP range is way small.

@Bog9y The F10 Map is a grid north. I tested the Waypoint offset as well and you don’t get that error. It only happens with the T/OS.

Thanks for the report @BigMotor, It has been notified to the team. Regards,

@Wisky @Bog9y After more tests performed it seems to me that the issue is due to the wrong application of the Variation. The higher the variation (Nevada variation 12.1 E) the farther WEST the T/OS position is compared with were it should be. I add that to the bug system so they can fix that in the next update. Thanks again for the reports.

@Bog9y @Wisky I have been running some tests regarding the TCN offset. The position of the TCN offset point in my tests were correct and quite accurate. In the example I wanted to add an offset point on the radial 090/2.5 NM from the KBL TCN. I added a HMMV on the sample place, radial 090º/2.499 miles from the KBL. I have introduced the RADIAL 090º on the BRG box from ODU and 2.499 in the RANGE with T/OS boxed. The T/OS point goes in the correct position. Flying towards the offset point the plane overflies the T/OS with a precision of +/- 300-400 m error which it could be because of multiple errors like not placing the HMMV in the perfect place, flying error, etc. The error does not look too big for me however I will send that to Razbam and see what they think about that. I tested with both TRUE and MAGNETIC with the same result.

Hi @Bog9y, Thanks for the detailed report. We will run some tests using your escenario and see if we can reproduce the same issue. Regards

Hi @Brainfreeze, Thanks for your report. The team is investigating if it should be as you are saying. Regards

@lukeXIII Do you mean that instead of the HDG bug should display the HDG value required to intercept the course to the waypoint?

@Thanatos31 Thanks for the report! I send that to the Razbam team so they can fix that.

Hello guys, @Thanatos31 Do you have this reading problem with all maps or with some of them?

Hello guys! Thanks for the report. This has already been notified. Should be fixed in the next update.

@JackHammer89, Can you confirm that the issue has been resolved? If that is the case we would like to change the status of this report.

Hi @JIGGAwest, Thanks for the report. We had a look on your track and we noticed you skipped to enter the 1st waypoint as blank. What I mean is that the first mark point in the F10 map, must be in the target area ( does not matter the location as long as it is in the target area) and you should not write any name. The second waypoint should be over the specific target and marked as T01, the second T02, and so on. If you proceed like this you should not have any issue.

I would suggest you to repair your DCS and install the latest update if you not have already installed. Try this: Go into your ... \Eagle Dynamics\DCS World [openbeta]\bin folder. There, hold Left Shift and right click and click "Open Command window here." and then use one by one to clean up first, and then repair.

Could you send us a track so we can check your issue? Thanks