rob10

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.

ST is not fully unsupported yet, but it is being phased out (ED has indicated this for >6 months now) so support is more limited. Honestly I think ED were planning to have it gone by now but they're having issues with some newer systems choking on MT so they haven't fully depreciated ST yet while they continue to work on that issue. Unfortunately I doubt there is anything you can do to fix it on your end short of running MT (this is a known and reported issue in ST). Otherwise your hoping for ED to decide it's worth the effort to fix it in ST.

While the rest of your points may hold, it clearly was intentional to remove it currently. To quote directly from ORT's post: "Yes, this part of the map was removed from the build intentionally."

Just to point out that NineLine has clarified that it was SPECULATION on his behalf that this was the reason for removal. So don't use that post in your consideration of why. If it was Urga, then a pox on them along with ORT and Urga should announce that fact it they weren't involved because they're getting mud on their reputation by default currently. Since ORT didn't name or imply who the 3rd party was, it's possible (as was suggested by another poster) that this is a licensing issue with ORT and wherever they got their base data from. Either way doesn't matter because ORT is deservedly taking a hit for the way they've handled this, but I'm holding off judgement on Urga until we know the details.

In fairness, we don't know Urga has anything to do with this. NineLine speculated that it was about stepping on a third parties toes (i.e. Urga), but the ORT post doesn't imply that. As another poster suggested, this could be about licensing with wherever ORT got their base data from. That's very plausible since the chopped area follows a major lat/long grid line (logical spot for licensing to stop) and apparently doesn't really match up with where Syria goes to. Either way, the end result looks bad on ORT and more so that it wasn't announced ahead of time or even in the changelog.

When I finally got done downloading the update I did get the prompt to restart system or cancel.