Lord Vader

Hi @SturmVogel I'm afraid we can't use your track since once we replay it it asks to choose a slot to fly so we can't really observe what you did. In any case, some things can condition JDAM or other INS/GPS guided weapons, like the mission date (is it pre-GPS era?) or the faction (RED units have a slightly degraded GPS). We would require a new track with the issue occurring, preferably short, to understand what's going on. From my personal tests, the weapons are hitting within CEP.

Hi @ArturDCS I am sending this for internal analysis, thanks.

Hi @Antix70 The FCR is still WIP for the CPG station when added. Please wait for future corrections and enhancements.

Hey @Rongor We will be revisiting the DCS: F/A-18C manual in the future. This is a Early Access manual and this module has seen multiple adjustments and refinements on its procedures and logics. Thanks for bringing this up, we've added to our list of changes for a future update. For now, refer to page page 168 on the same manual for the correct steps to switch to STT.

Hi @Furiz I've sent this internally for analysis. Please bear in mind this will be a low priority item.

Thanks for the track @Voy If you read above,@BIGNEWY actually said the current behaviour is "correct based on available sources". I don't think we could be more clear. Again, we would require publicly available documented evidence that the RWR contacts should rotate with the plane's own rotation. We can't commit to changes that just "sound" logic for the users. Unfortunately, flashcards are not an accurate source for our simulation.

Hi @Maxxox We will require a short track with what you are referring to in order to understand what is happening on your side. Just for clarification, TMS Aft with the HAD page as SOI should undesignate a selected target.

Hi again. After a review of the procedures regarding this particular item, we are going to need some time to refine this particular system. So we ask you to be patient, for now the Datalink will work following the procedure stated on the changelog. In a future update this will be refined further. Thank you for your collaboration.

Hi all @Ivandrov and @itn I believe the DED Datalink GPS time and Sync may have an issue, however working as it is. I have sent this internally for analysis. @Suffer_Player I use norm alignment the datalink is not showing anything When performing a Normal Alignment, you need to confirm (or insert) the current Latitude and Longitude coordinates on the DED, which is something you don't do on your track. You will see datalink contacts when performing a stored alignment, because in that mode there is no need to confirm coordinates.

Hi again @Rhino704 Can you supply a track with this event happening?

Hi @rodri_1992lp There are many variables to consider here. We require a track replay to observe your actions. I have tried to drop a LGB myself and it's working as intended on my side.

Hey @Nightmare22 I followed your instructions to the letter and couldn't reproduce the error. Please make sure you're not using any mods as they can cause conflicts and even crashes if not updated. You can also try to delete the Metashaders and FXO folders on your Saved Games/DCS Folder to allow it to recompile. If the problem persists, please share your crash log so we can have a look a it.

Hi @WolfhoundCH It's kind of hard to understand what's going on. Some modded scenery objects can alter the terrain elevation, even outside their geometry. I've tested several locations on the Syria map around that particular GPS position and didn't see an issues taking off from the ground. I can only assume the objects in that mission are causing the issue. If you can replicate it without the objects in place, please create a simple track (no mods) with it happening and we'll take a look.

Hi @shagrat We are also aware of this issue for some time. It's reported, just not a high priority for now. We'll address it soon.

Hi @Seether1980 I was also unable to reproduce in a mission of my own. I could see all aircraft correctly setup in Datalink (Net and Own IDs) both on TAD as well as the HMD. We would need a short track replay of this occurring on your side as well as your wingman so we can understand what may be happening.

Hi @Rhino704 I was able to assign it to a USB device (a gamepad) with no issue as you can see here. I was unable to actually reproduce this issue you describe. Just to make sure, are you testing this with weight on wheels? If you activated this with the gear up, you'll get no warning light.

Hi all. Thanks for reporting this. I've raised this internally for analysis. Hopefully we'll have this sorted soon.

Hi @SickSidewinder9 We will require a replay track example of this occurring.

Hello Moonshine I can see only the elevation data is slightly off every time CZ is performed. Lat/Long seems ok. I will ask the team about this internally. We'll need to verify it more carefully.

Hey @Yeti42 We need to see it happening and the best way is using a track replay. I just performed a landing with more or less the steps you described and couldn't reproduce it either.

Hi @wiwa23 I've reported this internally for analysis.

Well, I'm sorry, but I am able to close and lock, as well as unlock and open correctly using both the switch and the handle (spider lock) bindings. Make sure the side locks are in place before engaging the handle. Also make sure the button/switch you're using on your HOTAS is in working conditions.

Hi @Tholozor I've reported this internally, thanks.

Hi @[DE] T-Bone Yes, we are aware the PNVS needs some fine tuning. It's been reported for some time and we're still working on it. Thanks anyway.

Hi @Gizzy This is very hard to follow just by reading. Instead of the mission file, please post a track so we can see what's going on while you're doing it. I would also suggest you post tracks for each item if possible.