Hornet81

@Svend_Dellepude @Pacbeachdr @Wisky Seems the logic is this: Left side: L outboard external - L inboard external - Internal Wing tanks - L & R front tanks - L feed tank. Right side: R outboard external - R Inboard external - Internal Wing tanks - Rear tank - R feed tank. I will send it to SME and add it to the bug system. Thanks

@Aernovthanks for the track. We are checking your issue. @airborneyodaDid you have the Master arm to ARMED? If the next conditions are not met you can not set the laser to ARMED. These are the conditions: Landing Gear UP Airspeed > 100 KCAS Master Arm: ARM Master Mode: AG TPOD SWFOV mode: OFF TPOD must be either Area or Point Locked or be slaved to a System Designation.

@Svend_DellepudeYeah this is how it should be. Fuel from the left and right feed group ( L/R external tank, L/R internal wing tank, L/R front tanks and L/R feed tanks) is transferred to their respective center feed tank and then to the engine by a boost fuel pump.

Hello guys, Thanks for the report. I will have a look on that. @JIGGAwest Could you attach another track experiencing the issue but this time with a mission that does not require a mod? Regarding the 00000000 coordinate. Are your experiencing every time you turn the A/G or only for the first time? Which map are you experiencing the issue? Regards,

Hi @Aernov, I have tested your issue and I can not reproduce it myself. Would you be so kind to attach a track when having the problem? Thanks

@StevanJ Thanks for the report. This has been already reported. Razbam is already taking care of it internally.

Hello guys, Thanks for the report and all suggestions. I have added your request internally. Regards

@Flagrum, I will have a look on that.

Hi @Kappa, Thanks for the report. I confirm the bug. Seems that the two axis are inverted. That only happens when the TPOD is in INS and in HUD DES / SLV DES Added to the bug report. Regards

Hi guys, Thanks for the report. This has been reported to Razbam internally.

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

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

@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

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

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.

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

Hi Radsr30, I have checked your track. The reason why does not start is because your lever is not in the cutoff position. Lift up the cutoff lever and move your thorttle backwards. This will make begin the start up sequence. Hornet81

@Radsr30 Could you post a track when having the issue? so we can try to help you regarding the problem...