Varial

Bug: Jester has problems locking while the pilot is in boresight mode Steps to reproduce: 1) As the pilot, press the cage button to place the radar in 5nm boresight mode 2) with the target plane in front, Hold down the Jester context menu button to attempt to initiate a lock Expected behaviour: Jester is able to lock the target Actual behaviour: Jester advises that he will attempt a lock, ("roger", "wilco") but is only successful a very small percent of the time. I've included both the mission track file as well as the .miz file. Here is a video of the bug: Otherwise loving the F4 so far! Thanks F4_Radar_Jester_Boresight_ACM_Lock_bug.trk F4_Radar_Jester_Boresight_ACM_Lock_bug.miz

I was able to get it working occasionally, but it seemed very random, or not clear what would cause it to break or work. I took your mission and moved the points around by a few feet which caused it to break again. So far the thing that seems to be breaking it the most is where you place the embark triangle waypoint for the KAMAZ's, That being said, I've had the most success distributing the troops between the transport group

Hello, I would like to report a bug that I've been experiencing quite often regarding troops embarking into transports. Included are the Track file and Mission file, Here is a video of the setup and bug occurring In addition, if you are able to get the troops to embark while you are in the F10 map, the troop icons do not disappear from the F10 map until you exit and re-enter the map. Thank you! Varial Embark bug.trk Embark bug.miz

A drag box select, allowing you to move and rotate multiple units at once would alleviate a huge headache when designing missions Secondly a undo and redo function would be great. also. being able to have troops loaded into vehicles at mission start would also help avoid alot of the buggyness that comes with embarking troops.

This is still an existing bug

As one of the people who helped proof read, None of the authors want to see the gazelle removed, nor do we want this to descend into insults (IE telling us to get a life). Let's please keep this a productive conversation as we would just like to see action or form of acknowledgement by Polychop that they are working to solve these issues.

A comprehensive bug report on Polychop’s Gazelle The linked document is a comprehensive view of multiple bugs plaguing the SA-342 Gazelle module for DCS: World, developed by Polychop Simulations. Many of these bugs have been brought to the attention of the developer and have either remain unaddressed or have been blown off. https://drive.google.com/file/d/1dNRsYAm4dgxsZbAyTxWHfw2v4yW_uk9-/view?usp=sharing This document was made with the support and hard work of members of the community: Written by: AveMe and Nightwolf Thanks to (in no particular order): FoxAlfa (Missile FM analysis and editing) Zhen (Code comment translation) Quaggles (Missile FM analysis, general assistance, and proofreading) Fragal (Missile comparisons, ED forum and Discord support over the past year) Krippz (Proofreading and editing) Varial (Proofreading and editing) Everyone who helped try to talk to Polychop and spread awareness of these bugs over the past year