rob10

This is a long standing bug. Ignore the unable to clear and carry on.

If there is an enemy unit close/on the base it will turn it NEUTRAL or RED and that prevents you from rearming etc (because it's no longer a "friendly" airbase). In this case I'm guessing it's making it a RED airbase so you're not "allowed" to land there. Working as designed. That's why when you move the units farther out you get the airbase (because it's still considered a "blue" airbase).

Check that you're actually updated to the latest version of DCS: 2.9.7.58923

Short version is that that's atypical and for the majority MT is going to improve the experience significantly and allow ED to do more for less performance cost. Unfortunately they seem to have ran into some issues with certain newer processor combinations where MT isn't a better option.

I've used these commands for a while, but I hadn't thought about this part of it. Opens up even more possibilities! Thanks.

One would think GUI for GUI, but it has also reduced the size of radio menus too for some reason (which makes sense since it's a user interface too) . I don't change settings often, so I could live with that part, it's the tiny radio menus that hurt.

Set your GUI scaling to 1X

For comparison, here are screen shots of my settings menu at Scale 1 and Scale 1.5. Both have text set for 1.75 so it unfortunately doesn't help in this case. nullnull

Haven't had a chance to check your .miz files (thanks for posting them, makes checking things easier), but I'll bet the problem ones have a supercarrier in the mission and the OK ones don't. That's the reported difference and seems to be the case that I've seen so far.

How much physical RAM do you have? Seems to be a number of logs with crashes showing after the latest update where 16 GB RAM is a common denominator.

There seem to be a number of posts with similar logs to yours. The common denominators that I'm seeing is a Access Violation error and only having 16 GB physical RAM and using Steam. I'm wondering if 16 GB is no longer enough, but interesting that it only seems to be Steam users The mirror issue is a Single Thread (ST) issue. Switch to Multi-thread (MT) and you should fix that problem.

Set your GUI scaling to 1X and it will get around that issue.

Hmm. I've always had that set to 1.75 (higher resolution 2D) to get a decent size for menus and comm's text. When I set GUI to 1X it shrinks all that stuff down considerably even with text size set to 1.75. Likely depends if you're 2D/3D, what your res is, how far you sit from your monitor etc (and old eyes don't help ). Thanks for the suggestion though!

Set your GUI scaling to 1X.

Your log file looks very similar to the one I commented on here.

That's what that option did in game. How do you do it otherwise? I used 1.5X as well and I'd like to get my sizing back.

Set your GUI scaling to 1X in the settings. Apparently only an issue if you have the supercarrier in the mission.

Thanks. I knew I had flown a couple things yesterday afternoon and hadn't seen the issue, then flying last night I had it and I couldn't figure out why. But this would explain it!

Set your GUI scaling in setting to 1X and you'll get things back to normal.

Because for most people (obviously not all as evidenced in this thread, but most) they don't have the problem you're seeing. In a perfect world it would get caught but there are so many possible systems and configuration that there is no way to catch every possible issue. And if it does get caught but only effects 0.1% of users it might not be considered serious enough to stop a patch fully.

Couple of things: you really need to try and get more RAM. 16 GB physical and 20 GB pagefile is very marginal and it looks like you're using a bunch of mods which likely won't help. Personally I think DCS realistically wants a minimum of 64 GB between RAM and pagefile and obviously the more of that that comes from RAM the better (speed wise). Check your anti-virus. There is a Access Violation crash which another user found was due to antivirus quarantining a file. You can also check this thread (and I know there are a few more with same Access Violation crashes):

And check that your AV doesn't have the files quarantined. I would have thought reinstalling with AV off would replace it, but it might be causing issues if it's already quarantined. And if you're turning AV on before you run it, then it will still be nuking those files (it's generally detecting them, not really related to detection during installation).

Set your GUI scaling back to 1 and you should be back to normal.

Literally that the unit is tilted and by how much. The 2nd number in brackets is the MAX allowed angle and if either of the 1st numbers are higher than the 2nd numbers you'll get this. Mainly meant for SAM's etc that need to be relatively level to be able to function.

Check your anti-virus. Quite possible that a file or two has been quarantined so is unavailable to DCS. It may have removed them before you excluded DCS.