Benom8

Hi, Being able to remove the mirrors completely is a neat feature, but I noticed that doing so gives the same FPS hit as having them rendering reflections. Brief track attached, sitting on the tarmac at Tinian, where mirrors seem to make a big FPS difference on my system. The only geometry behind the mirrors was the ground. With the mirrors on but not rendering reflections I got 60FPS (vsync limit), but with the reflections on, or mirrors removed it was down to around 40. Apologies if this is already known, I couldn't find a thread about it. Key system specs: i5-9600K, 32GB RAM, GTX 1660S. Mi24-Mirrors-FPS.trk

That's good news about the template! In the mean time, you can edit a copy of the dds file and include it in the same folder as your other livery textures. That way it doesn't affect any other liveries. Make sure you have the following line in your description.lua file (assumes the file you added to the livery is still called "mi-24p_evu.dds") : {"mi_24p_evu", DIFFUSE, "mi-24p_evu", false};

The IR suppressors are not part of the template last time I checked, but look for mi-24p_evu.dds. You don't have the various layers, but without too much effort you can approximately extract the dirt and non-paint colours to put over your livery.

I noticed that in this map there's currently a flagpole on one of the perimeter fences slightly to the right of centerline when landing on runway 29 at Ercan. This is a real hazard when flying a 2.5 degree glideslope to the threshold. Wanted to query this as it seems an unlikely setup in reality.

Just to link a very similar thread. Sorry I didn't see this one when I posted.

Hi, I think it would be handy to allow players to set the frequency presets for this and other airframes in some sensible way in-game. E.g. via an interactive kneeboard when landed at a friendly base. This would avoid relying on mission designers to set these presets/guess which ones would be useful - these can be hard to plan out e.g. if players want to use a particular frequency for their flight on SRS etc. Just a thought! Best wishes

I used Disk Cleanup for this (e.g. get to this via Right-click the drive -> Properties -> Disk Cleanup). There's a checkbox for deleting DirectX shaders.

Just to add to the folklore on this, I was getting this issue sporadically (and only one black poly at a time) on my 1660S. Incidentally I was using an AMD 280X on this system previously. I haven't noticed these for the last week or so after I: Updated the drivers, cleared NVidia shader cache, cleared the DCS shader caches, repaired DCS, and cleared the DirectX shader cache. Fingers crossed they're gone. I underline the last step because I don't see it mentioned here yet, and maybe there was something lurking there from my old card.

This may be a different issue, but I sometimes find that the mouse does not pan in the F2 view. Restarting DCS is the only thing that works for me. Interested to know if this is related.