Lord Vader

The best way to confirm it is by going in the comm menu without tuning a station and try to call any option. If your radios are automatically tuned, then yes, Easy Communications is active.

Hi @SnapRoll Thank you for bringing this to us, we've reported it internally.

Hi all We're sorry for this inconvenience. Let's see what can be done, no promises at this time.

Hey @TobiasA Thank you for this report. I've raised this internally for analysis.

Hi @JabbyJabara Please set the DSU-33 with a proper tail fuse to explode (you set "plugged" on the tail fuses). If you do so, you'll see it operate as intended, exploding the bomb 20ft above ground (default altitude). I passed your suggestion about a manual update regarding this. Thanks.

Hi @Namco51 Once more, I am pressing the LCTRL+C key to close the canopy and it is a momentary switch. The canopy will only close while I'm holding this key combination. The same thing happens when using the mouse to press on the switch down. I also tried to assign a button on a joystick and it works fine. Not sure what your keybinds or configurations are, but again, I don't have a situation where the "Canopy- OPEN/CLOSE" switch stays stuck on the down position. So it's got to be something on your side.

Hi @Talvid Now I see it. Thanks for the explanation and example. It seems you are using the "Easy Communication" option in the Mission Editor for this mission. In that mode, the radio comms are handled in "AUTO" mode, meaning that you can select whatever frequency you want on the comm menu and DCS will decide what radio to use (VHF, UHF, INT, etc). So that's why you are seeing the rotary switch move and you still can hear the ICS. If you want realistic operations, remove the "Easy Communications" for the missions you want and then you can operate that switch realistically.

Hello all. Tried very much to reproduce this issue, seems rather erratic enough to present to internal analysis. I've raised it internally, let's see if we can find the culprit. For the time being, make sure your settings for the bombs are correctly setup in Mission Editor and it corresponds with the aircraft own BA setting. Also @skywalker22, in your track setting a 300ft BA is unrealistic. The very minimum is 700ft, the "acceptable" minimum is 900ft but for these weapons the default BA is 1500ft.

Hi @Furiz We're still improving the fuze settings and presets. Thanks for letting us know about this, I've added it for our internal analysis.

Weird. I will ask for more testing to see if we can catch this particular one. I just tested again in yet another mission and again couldn't reproduce this.

Hi @Rac3rX This one is a bit hard to understand. I can indeed observe what you say in both your tracks. However, when I try to reproduce it in a fresh new mission on my side, I can't see the bug, the bombs hit as expected. Given that there were some important and deep changes to these weapons in terms of fuses and burst altitudes, it's possible that older missions might not work properly. Can I ask you and the other repliers to try a fresh mission and confirm this bug? Thank you for your precious cooperation.

Hello again @Shibiswag I've reviewed your track with the AGM-65D Maverick and saw that you are attempting to boresight the missiles establishing targets closer than desired for a proper alignment. As previously stated several times, boreshighting these missiles should be above 3nm (at least) to guarantee there is no introduction of parallax errors. There will never be an engagement of an AGM-65 at the distances you performed on you track. The best advice is to boresight the missiles mid-air, enroute to the mission area, guaranteeding proper ranges. Regarding the previous error that was corrected, it had to do with an improper alignment mid air and completely offset from the intended alignment. That has been fixed in this newest DCS version as you say by being able to observe on your track. If you still feel this is a bug, let me know what I missed.

Hey @kendoric2 Thanks for your feedback, I've raised this with the team.

Regarding JDAM, it has been stated previously that with Pre Planned targets it is expected the bomb accumulate INS errors introduced by the aircraft's MMC. For that reason, at least until we refine the weapon self guidance features (WIP), you are required to acquire targets with on board sensors (FCR, TGP, HUD) to guarantee a precise hit. As for the Mavericks, I will take a look at your track and will address it if necessary.

Regardless of how it's classified, rest assured we're handling it anyway. Once more, the original preset logic did not contemplate these new features. It would be a bug if we had originally designed this way but it didn't work. Thanks for understanding and stay tuned for future updates.

Hi @Kid18120 I've raised this internally for analysis. Thanks.

Like I said, the system was not originally taking into account these new settings and may not work as you'd expect. We'll review this internally and see what can be done. Again, thank you for your feedback.

Hi @BarTzi Currently the saved presets do not take fuse/laser code/aspect settings into account. Only bomb type and quantity. We will present this to the team to see if we can make it a feature for a future update.

Hi @BarTzi Indeed that's an odd one. Thanks for bringing this to us, I've raised this internally for analysis.

Hello @Talvid Keep an eye out for this one. If you have it again, make sure to capture it in a track and let us know. I'm inclined to a conflict in your hardware assignments, like @Yurgonsuggested as well.

Hello again, @skipparoo Like we already said above, we cannot provide support for other operating systems/platforms. It is clearly listed what the prerequisites are here: https://www.digitalcombatsimulator.com/en/downloads/world/stable/ Thanks for understanding.

Hi @JeRe Thanks for bringing this up. We are aware of this particular item and we'll be improving the pilot body animations in future updates.

Hi, @dtpilot247 As it was said, the gear animation was previously reported and is scheduled to be improved in time. And, like you said, other important items have been (and will be) implemented on the DCS: F-16C. Rest assured this isn't forgotten and will be addressed.

Hi again @vctpil, thanks for the replies. Unfortunately, I don't have those mods installed so I couldn't test your track files. However, I created my own simple mission with one target, JTAC and both the F-16C and F/A-18C. JTAC did reply to me as lead or as wingman on either aircraft. You can try this mission on your side and see if it works: JTACtest.miz (feel free to edit it to your preference). We did identify an issue a few days ago with some JTAC callsigns not working, but keep it "Darkstar" for now and try it out.

Hi @SUHANG If you have this issue and you don't own the DCS: Supercarrier, this is a known issue. We're working on it. Thanks.