rob10

It might remove some bluriness, but the symbology is still too chunky/thick even when barely visible.

It's really helpful if you provide a new .log file after you make changes. It's possible you have multiple issues and after fixing the 1st issue the new one may show up in a new log.

Try updating or re-installing your Windows Visual C++ Redistributables. https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 That's what it seems to be choking on.

I wouldn't say it's blurry, so much as the letters have almost become bolded which makes them harder to read/ugly and agree that this changed just as of last update (wasn't like this previously, so different issue to the Dec '23 one for users currently starting to experience it). This seemed to be a fix for a problem some other users were having and I assume at higher resolution it looks better, but it's now degraded things for a different group of users. Seems like this needs to have options depending on resolution used.

It was added a couple of years ago, but never really announced and only gets mentioned occasionally, so I'd bet MOST people don't know about it.

You should be able to do a RIGHT click in binding for "close" and assign it to "off" to make it work (with "on" bound to "open").

ISSUE 2: you need to bind the MIP controls in you DCS bindings. Some may be automatically assigned (which is why some may work). ISSUE 3: not sure how this works in VR, but in 2D I would suggest making sure you select "WINWING" in your MONITORS selection in your SETTINGS/SYSTEM menu.

You haven't been around long based on your number of posts. After you've been here for a bit you'll realize how often MODS break things after DCS updates. Works fine before and breaks things (even seemingly unrelated things in some cases) after. Great example was the update where a number of different mod planes caused the supercarrier to not spawn when starting a mission (even if you didn't have the mod airplane in the mission). You would start a mission with say F-18 on the supercarrier and you would instantly plunge into the ocean and die because there was no carrier. Remove the mods and the carrier worked fine again.

See this for details on how to run a repair without running DCS. https://www.digitalcombatsimulator.com/en/support/faq/repair/

Start by deleting your FXO and METASHADERS 2 folders from your saved games. Then remove your mods. And it looks like DCS-BIOS is fighting with FC3 so that could be causing things to hang up too.

I suspect what you're seeing there is that it doesn't touch the old files until it has the new ones downloaded, so until the update is finished you can end up with 2 versions of the same files which bloats things up temporarily. If you search the forums you can find instructions on how to download the update to a non DCS drive but have it installed back onto your normal DCS drive. That will let you download the update on a larger HDD drive but have it install the update onto your space limited SSD for example.

3 suggestions: - remove your A-4 mod - check that your antivirus isn't blocking something. There is an error near the start where it can't find "Serializer.lua" file - do a repair of your DCS. Something might have gotten corrupted in the update.

You're running really slim on memory. Definitely drop your preload radius back a bunch (it's using a whole bunch of memory that you don't have a lot of -- you're currently at 60,000, drop it to at least 30,000). And I'd be bumping your pagefile. Currently you only have a total of 32 GB between RAM and pagefile.

From the first log it is showing a bunch of errors like this: Source c:/users/felipe/saved games/dcs.openbeta/mods/tech/static_objects/liveries/guardtower_flag/rus_summer is already mounted to the same mount /textures//liveries/guardtower_flag/RUS_summer. Which suggested mods, but actually looks like it was pulling things from 2 places or you had somehow gotten parts of the normal built inserted into your Saved Games/Mods folder.

It's usually almost all modules that are on sale during sales, so while I get where you're coming from, not sure it would be worth the effort. The announcement for the sale lists all the modules on sale and what level of sale they're at too.

You've only got a 4,096 MB pagefile with 32 GB RAM. I'd bump that to 32,768 MB fixed and see if that helps. You had C000005 error crash, but could just be you're running out of memory.

For the record, I'd start here: https://forum.dcs.world/forum/1340-quick-action-generator/

At this point it's reported and BigNewy has said the dev's have reproduced it, so not sure what purpose more pics will actually serve. It's an issue, for some, and ED is working on it.

Interesting. And good to know. I don't pay that much attention to my programs (I just assume they're doing what I want) so I probably wouldn't have noticed.

That sucks, but it's an issue for SOME users but I would argue not the majority. Why should everyone else have to downgrade (I have really crappy download speeds so that pretty much puts me out for a day)? It's been acknowledged and reproduced on their end, so hopefully ED can hotfix this quickly for those having the issue.

In fairness, the specs do not indicate needing a continuous connection. It says "internet connection required for activation". I think most people would interpret that to mean you need to authorize with internet, not that you need to have continuous internet (or maybe I'm just old and that's a holdover perception from when you had to go online once when you installed it and you were good after that). This requirement has changed somewhere over the last year or two and ED has never communicated that change or commented directly on it and that lack of communication bothers me (I haven't ran into the issue myself, so it's just the lack of communication that I'm having an issue with). The "offline" mode has been around forever, but I used to hook into my wifi when I booted DCS, then turn it off to save a tiny bit of load on my marginal computer and never had issues with it booting me.

Thanks for the better and more detailed response!

Been a long time since I flew this, but do you not have to drop practice bombs or something on the camp?

That seems to be the case. I played with it and updating the fuzes in the re-arm menu in the planner and had mixed results, but I didn't actually try fully replacing the bombs which is likely the best way to work around this.

Because there are a number of presets (think versions) of DLSS that the DLSS version now included can use. I'm not fully up to speed, but I think it defaults to something like preset "C" but the general consensus seems to be that preset "K" provides better results. But some prefer preset "J". And likely some prefer "C". So ED has to choose one to include by default and I guess they decided to go with an older one (for whatever their reasons are, maybe good, maybe inertia to leave it the same), so recommendation is to add that in the autoexec to get the one the "crowd" thinks is the better one.