Lord Vader

Hi @cha5er This is a very broad conclusion you reached there. Lot's of things could be at play, such as server performance, mods, scripts, etc. Also a good tip when performance drops happens is to delete the FXO and Metashaders folders to verify it's not a shader compilation issue. Please try a clean mission with the aircraft mentioned, record a track with both sides, and share here, please. I tried to fly the AH-64D with the OH-58D and vice-versa and could not see that fps impact you are mentioning.

Hi @Bmcintosh19 Steerpoints and markpoints will be affected by INS drift in regards to TGP SPI tracking. You also need to pay attention to perspectives and parallax errors. Furthermore, INS drift with GPS available is not more or less degraded over time, it degrades through various factors but self corrects, since the Kalman filter will begin to make corrections immediately according to GPS raw data. If you read our white paper you will understand the GPS data is very noisy, creating constant errors and corrections that are even visible if you zoom in with the TGP.

No more tracks required. We'll be testing this internally to verify if this is a condition on your own server or a general problem. Thanks.

We will have a look, it does indeed look strange in your tracks, but we need to reproduce it to make sure it's not just a server sync problem.

@RokaOvO A track file is a recording, like a black-box file than can be saved for further analysis. When in multiplayer, it's automatically stored in "C:\Users\USERNAME\Saved Games\DCS\Tracks\Multiplayer". That's the file we need, preferably the client file and the server file of the same session. But again, if you have multiple scripts or mods, please try to recreate the issue without them or these track files will not replay correctly.

Hey @Ballinger French I've raised this internally for analysis. Thanks.

Sorry, Tacview is a very robust tool to analyse flight and other characteristics but we cannot use it to debug issues in DCS.

Hello again @Maverick806 I can see in your track that the switch seems to be pressed all the way down to close the canopy. You say it's involuntary and I believe you but, in the track, all it's saying is that the button is still being pressed. I took over this track and tried to do exactly like you describe LCTRL+C, then mouse click back, then LCTRL+C again and I could not reproduce. I even tried with a button assigned to my joystick and it worked fine, even interrupting the movement halfway. I am sorry but I think you have some input issue on your side. I'm not sure what could be.

Hi @RokaOvO, your English is fine. We would require a short track replay of the event you're describing as it's a bit hard to replicate with just your description. Please supply a track replay of the client seeing the missile, as well as the server track, if possible. Just be warned that weapon desync can happen in servers running heavy scripting and/or mods. If that's the case, we ask that these tracks are recorded in standard servers running default files only.

Morning @Jself Can you please try again after yesterday's patch? I just tested your track and can't see the weapon settings reset you mention.

Hello @MeatServo Please send publicly available non-classified information that confirms this behaviour you believe to be inaccurate to @BIGNEWY via private message.

Hello @Razor18 I can check if the IFEI can really be set in a near blank status. Sounds counterproductive as this is a vital instrument but maybe it does require a tweak. No promises, though. As for the other items, I'm sorry but I don't get what you're getting with the ALR-67 and HMD. I can get them both to a very dim setting. Both dimmers work ok.

Hi @DummyCatz We've been investigating this potential issue you described for some time, while we fine tune the FCS, including the rudder performance. Your track is fine for that purpose and we thank you for that.

Hi @jack333 Please include a short track of the issue you're reporting so we can analyse what's going on. Thanks.

Hey @ReveWolf The DCS: F-16C Viper is a complex aircraft, composed of several different systems and weapons that we thrive to improve and refine over time. The aircraft is also in an Early Access stage, meaning we're still developing it, leading to some potential changes in procedures and logics over time, this is something you assume will happened once you are dealing with ongoing projects. Currently, the manual for this module is also undergoing extensive revisions by our team to make sure it reflects the actual, most recent and true-to-life procedures, as far as simulation goes, of course. So the best way to keep up with this module is to follow our changelog that includes all updates and changes to these logics, most recent videos from Matt Wagner and even our forum posts of the Mini-Updates in the general area and other reports that have been addressed earlier, like it was suggested to you. The discussions you started were all about known issues and we replied to the items as applicable. If you wish to review these previous items reported in the forum, they may demand a bit of searching but they are open to consultation. Thank you for your dedication and we hope you get your matters resolved.

Ah! Ok, the fuel tank jettisoning creating issues with ordnance is a known issue. We're trying to fix it as soon as possible internally. We're sorry for the inconvenience.

I see. Well, considering it's a momentary switch, by doing it the way you describe, you're interrupting the command, somehow, and it may as well enter a loop, which seems to correspond to the bug you're describing. I never done it this way. All I can say is that the command is LCTRL+C as well as the button assignment depends on a momentary press, if you don't do that it will never work correctly.

Glad to know it worked for you, @JabbyJabara.

Hey @Viper1031 Like previous stated by @Sinclair_76, the IDM self guiding capabilities in the current version are limited to the coordinates + drift delivered by the aircraft's MMC. For that matter, regardless of correct GPS coordinates you input, you will always send your own INS drift to the bomb. This is a realistic outcome. In the future, after a period of time, the weapon will be capable of self correcting it (if given the time), and make it more precise. For the time being, however, you will always need to designate the target using the onboard sensors (TGP, FCR, HUD) to guarantee the desired precision.

Hey @Gilligan The GPS Time status will only be obtained when the system can observe LOS with orbiting satellites. So, for example, if you are beneath an obstacle, like a Hangar, it may just happen you will not get the notification and need to wait until you leave the hangar to then get GPS Time status. Turning on MIDS before getting that status will introduce a Datalink error due to poor GPS time information, however. This particular step is very important and if not respected it could result in datalink position failures.

Hey @jackmckay Indeed when using preset steerpoints, you should only use the 1-24 range, reserving markpoints from 26 to 30. All others are still to be implemented, including the HSD lines, like @Lacementioned.

Hey @ReveWolf These are videos, not tracks. I have no idea what you did before, the tracks help us see and debug your actions, videos do not. In the first video, the bomb seems to hit within the acceptable margin of 5m CEP, assuming you assigned the target using TMS up (point track). The second video I can't tell if you TMS up, you seem to drop the bomb without designation, not sure, the bomb might be hitting beyond the desired zone due to INS drift. Please read other threads about precision degradation due to MMS information including INS drift. In any case, this is why we ask not to make bug lists in one single thread. We were talking about boresighting and now you're coming back to JDAM. This is a bit confusing to follow, not just for us, but also for the users searching for help. Bombs - We're working on JDAM self-guidance using GPS. For now, the procedure to drop any IDM and even dumb bumbs using CCRP is to designate with aircraft sensors or face the added drift from the aircraft's own INS errors. Mavericks - The boresighting procedure has been improved over time but we currently feel it's working as intended. Just make sure to follow the procedures correctly as stated in other threads here and the missiles will correctly track. Thank you for your time.

Thank you all for your patience and collaboration. I've reported this internally for analysis.

Hi @idenwen I've just tested this myself and cannot reproduce this bug. If you have modified files, I would suggest you temporarily reset them and try again.

Hi @idenwen This is by design. If you take a look at the lower screen, the advisories are there.