Lord Vader

Hey @JimmyWA Both GTM and RMAP are perfectly capable of picking up aerial targets. But, of course, ATM is specifically designed for that task.

Thanks for the track @Tomcat388thwe'll have a look. But currently, all I can ask is that you guys wait for the future updates we're working on and try again. A lot of logics are being tuned right now.

Hello @Thomas_GER As a rule for this kind of reports, always try to include a track of the event, in this case from both aircraft pilots for our analysis. In any case, during our internal tests we were able to identify the issue and have reported it to the team.

@Ogata_Rina The DCS: F/A-18C is not "broken". We understand some modes are not working as intended, but overall the radar is being improved extensively. Stay tuned for future updates where we will bring refinements and corrections.

Again, it's not explained what happened in that graphic. I am unsure if, for example, there were some extreme accelerations or GPS suffered some sort of interference for the purpose of demonstrating degradation. Under normal circumstances, yes, if there is a degradation over time, the Kalman filter will continuously try to remove the maximum amount of errors possible.

That was a demonstration over a long period of time. This could be caused by various factors that were not explained in that graphic. Basically, manoeuvring and acceleration can influence the deviations, but you'll notice the filter will eventually reduce the deviation over time.

Oh I see, If you consult our white paper, you can see that the Kalman filter output error can get to about 15m. https://www.digitalcombatsimulator.com/upload/medialibrary/941/fsjcbyvt707ib9q7s7szpsra373gxak7/F-16_INS_White_Paper.pdf

Hi, according to the publicly available documentation the CEP for the GBU-31/38 JDAM is 5 meters. We have modelled this accordingly in DCS. Just be aware that currently the JDAM self-guidance/correction is WIP so if you drop a bomb without a sensor track (FCR, TGP), the bomb will only get the information the MMC sends, which included INS drift.

Hi all In normal circumstances, the TPOD will hold an optical lock fairly well. However, if something obstructs the view, effectively interfering with the optical lock, of course the point track can have trouble maintaining track. As suggested, area track should be engaged in such conditions. Which seems to be the conditions set by the original reporter. However, we are interested in seeing your tracks if this is a recurrent issue as described. Please do post tracks here for our analysis.

@lwalter That's unfortunate but I'm glad you sorted in the end.

Hey @P3CFE Good point, I've reported this internally.

Hello @Eclipse I'm not sure what happened here, but in this track, after selecting the control measures, you never perform any of the tasks requested by the narration. Again, I took over the controls, performed the necessary actions and the mission progressed beyond targeting both BMPs with IAT.

@tanker82 I'm sorry but that zip file you shared just doesn't replay correctly. It's huge with 200+ MB and it appears to be from the entire server. Regarding the issue you describe, please try a simple mission with the same conditions and verify if you see something similar. Sometimes there could be small sync issues with telemetry that may show something like your video but, in fact, this could just have been a case of your CPG not being able to correctly track the moving target. Trying it on my own in a simple mission, George hit the aerial targets so we can't say this was a global issue. But please, if you can reproduce this in a simple, single player setup, do update us.

Hi @Rhino704 I cannot reproduce this in the latest DCS version using default skins. Please verify if you have third party textures or mods installed, disable them and try again.

Hi @Eclipse I just tested that mission and couldn't reproduce the issue you describe. The "press spacebar" prompt doesn't appear immediately, only until the narrator finishes, but it does appear afterwards. Please provide a track file of your issue so we can analyse.

Like mentioned in the other thread, third party programs that use simple telemetry do not offer a clear picture of the events. We need track files to analyse conditions.

Hello @tanker82 We cannot analise issues using third party items, especially since they replicate telemetry. Please provide a track file of the event in DCS. We couldn't replicate this on our side.

That's another matter for another forum. Please don't mix subjects.

Hey @JimmyWA Great to see you had this solved. Since I couldn't reproduce this with my own controls lead me to believe it must have been a binding issue. Thanks @TFSfor the valuable tip.

Hey @twistking We're still working on this aircraft lighting system. Whatever tweaks and improvements will be done according to real life data and/or SME feedback.

Hi @Overrun Thanks for bringing this to us. I've reported this for analysis, looks like a digit was wrongly set.

Hello @Topper81 From your track, I can see your engagement and correct Mark point 26 creation. However, when you turn around to reengage with the Maverick, please note you are in EOS-VIS mode and that sets SPI to the square cursor slaved to the flight path vector (until you move to designate visually via the HUD). Remember the TPOD will always follow SPI and if you don't move out of that default position, it will continue follow the FPV. Once I noticed this, I took control of your track, selected EOS-PRE on the Weapon page, then CZ on the TPOD and it immediately slewed to markpoint 26. Hope this helps.

Hello @Nealius Unfortunately your track doesn't replay very well. It's running several scripts (Mist, CTLD) and we require clean installations to make sure it's not a script interfering with the operation. I tried to follow your steps carefully in an MP environment and couldn't reproduce the issue you described. In step 4, are you pressing TMS to go point track and then press it again to record the coordinates? This is a known item that sometimes confuses people. I managed to cue the TPOD to the correct steerpoints 1 and 2 created by hand, and Mark points 26 and 27 created with the TPOD. Looking forward to your reply.

Hi @JimmyWA Maps shouldn't make a difference. Unless these maps have some bigger obstacles that could hide the helicopters, but of course I'm sure you figured that too. We're still analysing this item with aerial targets using GTM or RMAP. Just please bear in mind that ATM is not yet available in the DCS: AH-64D.

Looking forward to your conclusions. All the best.