Parkour

Much like the La Combattante II, the FFG Oliver Hazard Perry is destroying itself when it opens fire on sea targets. Skill set to expert. Once it launches, the FFG Oliver Hazard Perry forward missile launcher shoots itself. Please @BIGNEWY, let the team know these two naval vessels need to be fixed asap as it ruins many naval encounters. An example *.miz file attached that shows the issue with both the La Combattante and FFG Oliver Hazard Perry. It appears to be related to the speed of the vessel. Thank you! FFG Oliver Perry and La Combattante II Self Destruct.miz

JTACs don't work on a dedicate server. Only AFACs. If a dedicated server has a JTAC working, they're probably using some form of LUA scripts. The default Mission Editor won't allow JTACs to work on a dedicated server. Here is my original post from May 1st: https://forum.dcs.world/topic/373001-jtacs-are-not-working-in-multiplayer-on-a-dedicated-server/

This issue is still occurring. Nothing is fixed. The La Combattante II is still shooting itself with its own missiles and sinking itself as of Patch 2.9.16.10523

It appears that many of my SOUND TO ALL Actions are encountering a bug in the Mission Editor that prevents them from 1) playing during the mission and 2) has a UI bug that removes the options to change the file and/or adjust it. This is not limited to one mission, but at least 3 of my missions so far. See the attached images. The only way to fix it is to delete the SOUND TO ALL Action and add it back again as a New action. Anyone else encountering this issue since DCS 2.9.16.10523? Thanks

Just found this after a few hours searching for the old one thinking the feature was removed. Thank you all for posting the update on how to enable this feature again!

@Mistermann Thank you for this post! Three years later, I find this and its perfect guidance on creating realistic comms audio files. Thank you! Thank you!

Tip for those that use this guide in the future and still can't get the FARP to work - ensure there are no enemy units within 1nm of the FARP, as it will cause the FARP to be contested and the Ground Crew will no longer respond to radio commands.

Correction. There is more broken with this mission. Fixing the F-4 won't resolve the issue of missing AI trigger pushes and other issues. Attached is a fixed mission to replace the fundamentally broken version found in DCS under the F-14 missions. HB Pitching Deck - FIXED - Hot Supercarrier Co-op.miz

Does anyone have a .miz that utilizes JTACs that are confirmed to work on a DEDICATED server as of May 1st?? Not single player. Thanks!

I have been unable to get JTACs to work in multiplayer on a dedicated server when not using any scripts. I am only using the mission editor Advanced Waypoints options. I have tried all the troubleshooting in the thread below, but at no time while in a multiplayer section does the JTAC respond. In addition, the JTACs will only display their vehicle type (not their callsign) in the manu (occurs with easy comms on or off). There has to be some bug in the way a dedicated server is handling JTACs as the same exact mission will work perfectly in Single Player with the JTAC responding to comms as well as being displayed by their callsign in the comms menu. Please Eagle Dynamics, look into this issue as it essentially makes JTACs useless in multiplayer without resorting to scripting. Posting this as the other thread is marked "fixed" but it is obviously not. Attached is a simple JTAC test mission used on a dedicated server as well as the mission from the thread below that also does not work on a dedicated server. Thanks! JTAC Test.miz Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2_FIXED.miz

I'm experiencing the exact same issue. I can not get JTACs to work in multiplayer at all; however, AFACs work fine. I have tried every conceivable combination in the last few days verifying the dedicated server isn't preventing something, double checking my own mission and the mission linked above by @Flappie. I have tried every combination of both easy comms and regular comms, both radios, frequency settings in manual or preset (both in aircraft and in the mission). No matter the change, the JTACs always show as Axeman and do not respond. Whereas the same exact mission in single player works find with the correct JTAC names and responses. There is definitely an issue with JTACs in multiplayer working when not using scripts and just using the basic advanced waypoint functions. @Flappie Are you able to verify again that the dedicated server is working correctly. Is there any server online that has JTACs in a mission that is working? Attached is the same file linked above that was used for a multiplayer test. I also included a very simple basic JTAC mission that works fine in single, but doesn't respond in multiplayer. Thanks! Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2_FIXED.miz JTAC Test.miz

The "HB Pitching Deck" mission is broken at the moment due to the F-4 Phantoms used the mission editor are no longer available to Iran. This causes the two F-4s (one needed for some initial triggers in the mission) to not perform correctly and it appears as RED in the aircraft options for Iran. The end result is the mission critical F-4 has no valid Waypoints and no AI triggers available. The F-4 will RTB without ever entering the critical triggers. Updating the two F-4s in the mission to the available Iranian F-4-45MC, arming them, and adding their waypoints back into the mission will resolve the issue. Everything else appears to be working. Thank Heatblur for a great aircraft!

@BIGNEWY and Eagle Dynamics. Thank you for adding the ability to turn off the spotting dots for VR users. My squad and I have been flying again since the patch and we love it again. We have actually started buying modules as well. You can actually see the number increase of players again in SteamDB player counts since this patch as I'm sure many other VR users have returned. Thank you for listening to me rant and be a squeaky wheel. Thank you for giving us our immersion back. Parkour out.

THANK YOU!!! Just tested and the Spotting Dots are able to be turned OFF in VR. Thank you Thank you! Best Christmas Present Ever. There are no more large squares around the aircraft or ground targets when turning it off in VR. I love it!! Immersion is back on the table!

It's a simple matter to enable VR users to turn OFF the spot dots. Not tune it for every headset. Not take into account every possible pixel density out there. Not get it to your "white paper" design spec. Simply put in a if/then statement that doesn't call the spotting dot rendering function if the VR user doesn't want black squares. It shouldn't take 8,500 hours to figure out. We are just getting frustrated and patience is not running thin, its gone. You wanted our feedback, you asked for it, and you'll keep getting it until you give us back what we used to have. Here is some sample code to cut down on those man hours.. #include <iostream> #define DISABLE_FUNCTION 1 #if !DISABLE_FUNCTION void myFunction() { std::cout << "Function is running!" << std::endl; } #endif int main() { #if !DISABLE_FUNCTION myFunction(); #else std::cout << "Function is disabled." << std::endl; #endif return 0; }