Nadel

I confirmed what another poster suggested, if you enable unknown, the SA13 does show up as an unknown radar. I'm not sure if that's intended or not. Attaching a test mission with an F4, F5, and F14. Both the F5 and F14 will get a 13 RWR spike right before launch, the F4 only indicates unknown, and only if you have unknown on. SA13-RWR-test.miz -- sample mission to see F4, F5, or F14 get shot at by an SA13 f4_rwr_vs_sa13.trk -- F4 getting shot down with "unknown off", and no RWR mark (screenshot annotated with blue) f4_rwr_vs_sa13_unknown_on.trk -- F4 getting shot down with "unknown on", and RWR "U" (screenshot annotated with red) f5_f4_f14_rwr_vs_sa13.trk -- comparison of F5, F4, and F14 RWRs when flying into the SA13 SA13-RWR-test.miz f4_rwr_vs_sa13_unknown_on.trkf4_rwr_vs_sa13.trkf5_f4_f14_rwr_vs_sa13.trk null

(it's possible I misunderstand) but I believe the SA13 should spike you with the ranging radar when it fires. Fly an airplane directly at an SA13 at 4000 AGL F18 RWR: spike as the launcher fires F14 RWR: spike as the launcher fires F4 RWR: no spike/nails Is this a limitation of the F4 RWR? Or a bug?

"part of group in zone" does not behave as expected when used with an OR statement and two groups with only client slots. Given: Zone named "zone" Client aircraft: "plane1" and "plane2" "plane1" and "plane2" are flying from outside of zone to the inside of zone Bug1: Trigger Unexpectedly Activates Immediately: ONCE > PART OF GROUP IN ZONE(plane1, zone) OR PART OF GROUP IN ZONE(plane2, zone) > [[action]] Bug2: Trigger Unexpectedly Never Activates: SWITCHED CONDITION > PART OF GROUP IN ZONE(plane1, zone) OR PART OF GROUP IN ZONE(plane2, zone) > [[action]] Debriefing log also seems to have some unexpected events: bug.trk If plane2 is set to be an AI, both triggers work as expected. bug-group-in-zone-or-missing.miz

I figured it out, the free polygon tool essentially has two modes: 1. click to designate points of the shape (ie, 1 click = 1 vertex) 2. click-and-hold to draw a curve (ie, 1 vertex placed for every N pixels the mouse moves) In mode 1, as far as I can tell, you stop drawing by pressing escape (which also closes the draw tool, weird choice but ok) In mode 2, as soon as you release left click, you are done editing that polygon. BUT, you can go from mode 1 to mode 2. For example you can draw a squad with a single rounded corner. However, you must draw the rounded edge last because as soon as you draw the rounded edge in mode 2, you're done editing that polygon. The bug: While placing a point in mode 1, if the mouse moves a few pixels *while the left mouse button is depressed*, you enter mode 2 (but typically don't draw far enough to place additional points) then exit mode 2, finishing the polygon. For people with relatively high mouse sensitivity or not especially steady hands, this means that it is exceedingly frustrating to use the free polygon tool. It would be great to see: 1. Mode 2 not immediately end drawing the polygon on mouse button release 2. Escape 1x to stop drawing, and 2x to stop drawing and close the drawing tool 3. Way to edit an existing polygon after it's initially created (ex: click the midpoint between two vertices to add a new vertex). This would be especially useful for drawing contested areas or control zones in campaigns, as right now I have to redraw the full shape every time there's a change.

Definitely not the issue, don't have any issues with double clicks in any other software. Tried https://mousetester.com for 100 clicks, no double clicks.

How does anyone get the polygon free shape to work? I click to put down a couple of points, then it automatically stops creating the shape. I have to attempt to create the same simple shape with ~10 points at least 10 times before I'm able to complete the full shape.

Maybe the DDOS component is most commonly an issue for you, but this would be a great quality of life feature for people who regularly play with friends. There's plenty of times on the weekend where servers fill up and if you're trying to fly with a few friends, a queue would be very helpful! I've definitely resorted to attempting to join every 30-60s before, rather than waiting for the god awful refresh rate of the server browser. Good to know that causes performance issues at the server end though.

Since 2.8 the mission editor will frequently hang. It seems to happen the most when saving a mission, but once the mission file gets in a "bad state" this seems to happen frequently even when trying to make any change to the file. After crashing and relaunching DCS then opening the mission the mission, the map will stay all blue for an unusually long time as if it is failing to load the map at all. Attempting to save, make changes, or fly once this happens has a high chance of crashing. I've had moderate success with restoring previous versions of the mission, but it seems to reproduce again after some more mission editing. dcs.log TT_M03_crashing.miz

+1

If you're hitting the same issue I'm hitting, it seems like you can't select units that are under or next-to sensor/weapon range circles. In the example image below, the ship next to the red arrow is very difficult to select without zooming in. If you disable the sensor/weapon range visualizations (green arrow) it should be much easier to select the units.

While editing night missions in the mission editor and test flying them, it seems that sometimes the lighting does not load correctly. The most blatant example is when *everything* including lights inside the cockpit are obviously too dark. I've attached two images one before/after alt tabbing, which seemed to resolve the issue. However, I've also seen instances where changes to the time of day don't seem to be loaded correctly, and moving the time forward/backward by one hour doesn't change the lighting, but if you relaunch DCS and load the same miz the lighting is suddenly very different. dcs.log null nullnullnull

Mariana Trench Run_bug.miz Hit again while editing a different mission. Added some boats and modified some triggers, flew the mission to test, came back out and the ships/trigger changes were gone. This is the miz file after hitting the bug. dcs.log

dcs.log Hit the issue again after making some drawing changes and changing some units. It took me a few minutes to notice, so the error should have occurred in the last 10 minutes of the log. A blue UH-1 I deleted reappeared, and several circles I drew disappeared.

Hi dark_wood, Thanks for taking the time to respond. As I mentioned in the original post, I've encountered this issue both with and without autosave enabled. I'd actually enabled autosave in the hopes that it would limit the amount of work that I could lose because (presumably) the mission would not be reverted to content older than than the most recent autosave. However, this does not appear to be the case, and my work can be lost at any time back to some previous state, unrelated to autosave.

I don't have exact steps to reproduce this issue, but I make content weekly for a group and I hit this multiple times per month: Sometimes, some changes are not saved when selecting "fly mission" from the mission editor, even if you choose yes to save at the prompt. These changes are then missing from the editor after the test flight. I seem to hit this most often when editing triggers, but it's possible that's just where I end up testing the most. I hit this issue with autosave disabled. I enabled autosave, and still hit the issue, where I have lost progress that definitely should have been autosaved. What do you need from me the next time I hit this to make the bug actionable? I can work around the fact that it's 2022 and there's no undo function or box select. I can work around the fact that groups containing supply trucks have them changed to flak 18's if you change the group's coalition, even if the new coalition is joint task force red/blue. I can work around that units placed on a radar's search radius cannot be selected without zooming in because the radar circle "captures" the click. I can work around that sometimes when selecting a unit, it is immediately moved to the left by a fixed amount on the screen. But randomly undoing 30 minutes or more of my work is unacceptable. When this happens, I stop mission editing, and reconsider if this is a good use of my time. Please expand your testing for the mission editor, and add the features we need to efficiently create content for your customers.