Lord Vader

Thanks for the tracks and video. I'm afraid your track cannot be used since it has multiple scripts and mods running. Also when I play it, it follows a KC-135 indefinitely. However, following your video and steps, I tried to reproduce the error to no avail. You can follow my test here in this track and maybe tell me what I did different from you: crash and repair.trk

Hi @Killg0re NL This situation sounds like a server or client lag issue. It's hard to say what happened here but to me it's clear one of you guys (probably you) had a sync issue and it was later resynced with the server and/or the other pilot. We'll keep an eye for future similar reports, of course. Feel free to report them it you experience this again.

I'm glad you sorted this one out. Happy flying!

There is some information on the DCS encyclopaedia that can help you understand some of these systems. It's not an extensive description, though, just general information. There are also some open source sites that list the most common air defense systems, their capabilities and operational usage. A quick search will reveal several, I'm sure.

Hi all We are aware of some canopy reflection issues. Stay tuned for future updates.

Hi @JetCat I sent this to our internal analysis as a low priority item. Thanks for your support.

Hi @Killg0re NL The tail rotor item is known and we're working on it. The other item with George repeating the message, we would require a track replay to analyse.

Hi @Leg2ion I can observe what you say on your track, but loading a fresh mission I cannot reproduce. I can see you are using a Helios multi-monitor configuration, can you try again with a standard configuration?

Hi @71st_Mastiff It's hard to say what happened to cause your crash to desktop. The track file doesn't replay the event, unfortunately, so we can't reproduce the problem. I can see this happened in a multiplayer server running some scripts. The fact it only occurs when you take off could mean there is a trigger for that event that may be causing issues. Other than that, I can see you have some mods installed and it's known some may cause some issues with modules. It's a good idea to unload them and try again on the same server just to check if the problem persists.

Hi @Islari This appears to be a local problem on your side. Looking through your log file, you have several mods, some of which may interfere with other modules, especially in multiplayer environments. Please try to deactivate or uninstall them temporarily and see if that solves your problem. You can also delete the FXO and Metashaders folders on your Saved Games/DCS folder to allow cache to be recompiled. Sometimes this also helps. It's also recommended to update your video card drivers, but I bet you already have it updated.

There must be some mistake here, I never said anything about a 13m CEP, someone else did. Like I said above, and I think I was quite clear in my explanations, this is just a matter of refining how the bomb self corrects, considering all the limitations, including those 30 seconds of GPS acquisition that some of you seem to be ignoring. Once more, we are using publicly available unclassified documents to simulate this, and no, we cannot use websites without official sources. We also cannot use interpretations to base our simulations, we need to be accurate. Just because a document doesn't mention or omits a certain condition or limitation, it doesn't mean it isn't there. Of course, we encourage anyone to help us improve the simulation. Thank you for your care.

Hi @bonesvf103 Unfortunately that track doesn't seem to be replaying correctly. So I just observed your video. There are many items to consider when placing a SAM site. The most obvious is coverage and obstacles, but it also needs to have proper components to it. Does that site contain a P19 "flat face" for continuous search? Considering you didn't have its "mud" (S), I'd say it's missing from the group. It most likely only had a "low blow" tracking station and that's designed to track a single target. Considering your friend was shot down but not you, this could very well be the case. I'd suggest you place this trio of units and test again in the same conditions. I did just that and it seemed to work fine.

Where is that source quoted from? The F-16.net link contains an interesting article but it's not an official document. Running through the mentioned sources on that article doesn't refer to official documents. Just brochures, reports and even broken links. I've never seen any official reference of 10 seconds GPS activation, btw. We can't rely on unsubstantiated information, sorry.

Hello again. Thank you all for your points of view. This has been reviewed by the team several times to deliver the best possible depiction of the INS, GPS and IDM behaviour. I can assure you we're trying to make these as realistic as possible, according to available public documentation. First of all, 30 meters is the maximum drift value possible. If you have a factor of 10 INS alignment quality you probably will never see that much drift. The IDMs are indeed primarily guided by INS, blending GPS data, not the other way around. The GPS guidance algorithm is only used to make corrections after about 30 seconds after release. If the target location is closer, reducing that period of time, it completely relies on internal INS and the only source for it is, of course, the aircraft's MMC. However, if the target is more than 30 seconds away, the GPS data can be used, but only to self correct the bombs own errors, especially with a long TOF. Again, like I said above, this ability to perform its own correction after those 30 seconds TOF is something that will be refined in the future.

Hi @Ghost Targaryen Indeed there has been no change to this assignment. However, people here already gave you an idea of some things that can happen, such has trying to run Easy Comms in missions or servers where that's turned off, this will force you to use the proper radio comm switches for communication. Try mapping the comm switches or PTT buttons for each plane and see if it helps.

REDFOR will now have a lower tier GPS access, meaning it's slightly less precise and will degrade over time up to a maximum degradation plateau (this depends on various factors, but should go above the maximum 30m drift expected with BLUEFOR GPS). Unrestricted SATNAV will only allow (on) or disallow (off) the ability to access the higher tier GPS guidance available for BLUEFOR. There is no option to not have GPS available right now, unless you move the dates back, before March 1994, but that will remove it for everyone. In the future, there could be more options to inhibit GPS but, not right now.

Hi @Killg0re NL It's hard to say what can cause such an issue, but my bet would be the incredible amount of lag was causing desyncs. When that happens, position errors can cause collisions and/or excess movement leading to aircraft overstressing. There are a lot of variables to account for when it comes to lag and desync, like poor server optimization or online connection, heavy scripting, mods, etc. In any case, we're investigating some reports of stability and, of course multicrew syncing is still being worked on the DCS: AH-64D.

Hi all. After the last INS refactoring, the GPS coordinate logic for all IDMs needs to be reviewed by the users, especially in older missions. Now, weapons like the JDAM, JSOW or WCMD will get the GPS coordinates and the INS drift from the MMC. This means that pure coordinates given to the weapon without a designation (via TPOD, FCR, etc) may introduce and undesired drift (up to 30m in the worse case scenario), adding to the weapon CEP itself (5m). So, as a rule of thumb, all targets sent to IDM weapons should be designated by one of the aircraft sensors for accuracy. In the future, some details may be changed, for example the ability for the weapon to have its own guidance. But, for now, this is working as intended.

Correct. There may be a few changes in the way this works in the future, but no promises.

Hi all. 1. It's a coalition side feature. Redfor as the name implies, pertains the red coloured faction, so any nation you choose to be there will have a degraded GPS quality. It's not by much, it just simulates the lack of military codes to gain access to the necessary network. You will still have guidance and updated positions, but the margins of error are slightly higher. 2. There are none. According to the documentation, both reach a factor of 10 in precision, so they do not differ except in the procedure and time to align. 3. I'm not sure what you intend to ask here. If you're asking for dates, then all missions before March 1994 have no GPS available.

Hi @Corrigan Some aspects of the ACM modes are still undergoing some improvements to make them more realistic. Please look forward to future updates to improve its performance. Thanks for understanding, these are complex systems.

In my own tests, I was never able to make this happen, even switching between RWS/TWS or with MRM override. I will continue to try and catch it but so far I am a bit inclined to something related to hardware assignment. I tried both an axis and a button for the elevation, no luck so far.

Olá @cesarferrolho, saudações Lusitanas. Indeed testing your track the ILS system seems to be inoperable, for some reason. But I can't really figure out why. However, trying my own mission from scratch, I was unable to reproduce the problem, so this is not a module problem, could just be on your side. This can be caused by an old mission with older data being loaded. I suggest recreating the mission itself and try again. If you wish, you can follow my track and observe I can make an eventless ILS approach to runway 07. ILSTEST.trk Try it yourself.

In order to understand if what you're seeing is a bug, we would need to see what you are doing exactly. Can you supply a track replay of what you're describing?

Hi again @Maxxox After analysing the current version and comparing the available public documentation, we've decided the MGC function is working correctly in DCS World It is only supposed to be used while in FLIR mode, becoming inoperable in the TV mode. If you feel this requires a revision, please send documented, publicly available evidence to @BIGNEWY and we'll gladly look into it in the future.