Flying Toaster

As the topic says, AI corsairs will not attack ships. I tried corsairs with Tiny Tims, bombs, and Tiny Tims + bombs. I tried a general 'anti ship' mission and waypoint, 'search and engage [ships] in zone', 'engage specific [ship] group', and 'engage specific [ship] unit'. In no case did an AI corsair attack any ships, they simply flew to their last waypoint (which had the attack command) and kept going into the sunset. When I switched out the corsairs for P-47s, P-51s, and Mosquitos, they would attack the ships. They attacked badly, but they still attacked.

There are some bridges missing, but that isn't the case for most of the disconnected roads that I saw. If you experiment with this and move the waypoints around tiny bits you'll find that there is usually one short segment of road that has no navmesh.

Some roads seem to be missing the road navmesh for vehicles. I gave a convoy a series of "on road" waypoints and they took rather strange directions. You can see in the screenshot that the main road is apparently not detected as a road by the AI: null

The DCS F10 map colours urban areas yellow. On the Germany map any areas with fields appear to be classified as urban, and therefore get coloured yellow. This makes navigating using the F10 map very very difficult, as it's hard to determine where towns are and therefore use them as landmarks. See the two screenshots - they are taken at the exact same place, just switching between 'alt' and 'sat' modes. nullnull

Repro: 1: Run attached mission 2: Wait until left A-10 is damaged by Shilkas 3: Go to F10 map 4: click on left A-10 Sadly it is an infinite freeze rather than proper CTD, so it doesn't generate a proper CTD report. dcs.log FogTest2.miz

Fog is flickering quite a bit at the end of its render distance. Apparently this is known, but more examples are useful, so here is one. This mission has some fog and a single GM slot. To repro, load mission, zoom in on the bullseye positions a bit, and use ctrl+F11 to go into free camera. Move the camera altitude to 20,000ft or so and look west (out to sea). You will see the flickering at the edge of the fog render distance. dcs.logFogTest1.miz

Dear Ugra media, why did you demand that this area be removed from the Sinai map? I can state with a high level of confidence that exactly zero people decided against buying the Syria map based on this area being present on the Sinai map. This demand will likely have the opposite effect of what you intend - as people will potentially avoid purchasing your products based on your newly acquired reputation for damaging other third party products. Northern Israel/Lebanon/Sea of Galilee area being present in the Sinai map in no way hurts the Syria map, and will not cause people to choose one or the other.

On the bright side, we got F-35 circles! Which I don't want, as I want this map for historical (or alternate history) engagements. Having Israel and the sea of galilee area made it possible to do missions to the North and South of Israel from one airbase.

The entire naval combat part of DCS needs a big overhaul. This would be a nice step towards it.

Why was this done? Airfields such as Ramat David are important even for missions involving the Sinai peninsula. For example aircraft based there took part in the opening raids for the 6 day war. Please put the detail back in.

It really needs a big explanation of the failure panel, instead of having the warnings all tucked away in individual sections.

Many controls (e.g. the armament panel buttons) have 2 keybinds - one for on, one for off. This makes it very hard to bind, taking twice as many keybinds as needed, therefore a 'toggle' keybind is essential.

Did you click the 'x' to get out of them? That could delete them

The bug does make it very tricky. I ripped a skid off on a tree before getting to the target point, then repaired it at NATO HQ. Landing on the Argo was "interesting" - and I hope they have a spare rotor on board.