Special K

Help channel. Just ping me in there and we work from there.

This seems only to happen with the new modular DCS server. If anybody has a log that's not from it, please provide it in here.

Do you look in Mods or in CoreMods? CoreMods it always looked like it looks with yours.

Is there maybe any rules you need to accept? Check again, you should be able to chat over there. Would be easier honestly. Besides that, some export scripts might take so much CPU that they lock the FPS or make it look like that. Check that you can get into discord and ping me in the help channel. Then we'll analyse your log and system.

Overlay can be activated in the GForce Experience Overlay. You usually get that with pressing ALT+Z (might be Y depending on the language of your keyboard). And there are some things that can limit FPS. Disable any VSYNC in DCS and the Nvidia control panel, make sure you didn't limit the FPS in the control panel. If unsure, send your settings. I'm more responsive in discord, if you get to the help channel btw

That 1401 is definitely a miscalculation somewhere. If it displays 32 as your FPS then your FPS are at 32. You can use the Nvidia overlay, if you don't trust the ingame display.

Ok, you're talking about a VR issue. That might be, not a VR guy. For 2D, all I can say is that HT enabled gave me 20% more FPS than disabled.

It is not required, but as DCS can use up to 16 threads, why limit the possibilities. As this thread is about CPU bottlenecking, I would use all possible ways to counter that. One is enabling HT. Which missing labels are you talking about? Yes, DCS still uses DirectX11. It was not the plan to change the graphics API with MT. This is planned for a later change.

Just some ideas: - Make sure that HT/SMT is enabled (I see it is for you guys, but it should be checked, as we told a lot of people to disable it in the past as it was better back then). - If you see a lock at 60, that sounds like there is VSYNC active somewhere. - Make sure you deleted Saved Games\DCS(.openbeta)\fxo and metashaders2. - If no joy, try deleteing %LOCALAPPDATA%\TEMP\DCS.openbeta (or DCS for you steam users). - Check Saved Gamed\DCS(.openbeta)\Scripts\Exports.lua. I've seen winwing doubling and trippling their exports in there. If unsure, just rename the file to Exports.old and see if your issues vanish. Then we can work from there. - Disable Windows Game Mode. - In your Nvidia control panel: - Make sure that Threaded Optimization is turned on (not auto) for your DCS World profile. We've seen some suspects that auto is not fully working. - Enable the performance settings on the Power saving and Texture Quality values. - Set low latency mode to Ultra.

Ah damn, that's bad. Really thought we've got a step ahead. Any overclocking used? XMP profiles count as oc in that case.

Sorry, missed your dxdiag. What I see in there are 3 things: a) your windows is outdated. I would recommend updating your windows 11 with the latest update from Microsoft. b) your BIOS is very old and not Windows 11 compatible. This might cause all kind of issues already. Update your BIOS! c) DCS crashes in the visual c++ runtime. If the above mentioned updates don't help already, reinstall the visual C++ runtime.

Can you get me a dxdiag.txt? Maybe it's drivers related. I'll have a quick look then. Off to bed for today, you can hit me up in discord, too.

It's strange that it works with the 2080 TI without issues. And with the same drivers settings and options. It's very unlikely the GPU, but that sounds more or less like it..

Have you tried rolling back the driver yet? I have issues since anything newer than 522. Remove it with DDU, to make sure, everything is clean an shiny and try 522 or an even older one.

Can you send another log please?

Your pagefile is way too low. That can lead to all kind of issues. Decrease your preload radius to max 60000 and set your pagefile to at least 32 GB initial on your fastest SSD. Problems should vanish then.

As mentioned in discord already, that's not a DCS issue. Dxdiag showing 6 bluescreens, DCS, star citizen, photoshop and explorer crashing with RADAR_PRE_LEAK_64, which points to either too optimistic memory overclocking or bad chipset drivers. Or a faulty RAM stick.

And I removed the respective URL from it, so you guys should not see that any longer.

VAICOM pro had an autoupdate feature. Hollywood hosted the updates there. To see which version you need, your client asks this url: string URL = "http://www.awebsite.com/uploads/"; // <-- web URL of the hosted updates.json file string downloadfile = null; Log.Write("Checking for updates... ", Colors.Inline);

It seems to not be added to the serverSettings.lua by default. But yes, I would expect it to be still false then. It's just that setting that explicitely seemed to have fixed issues on 4YA, that's why Aunty suggested it. We're still trying to replicate it, no joy until now.

Did you roll back to a stable Win11 version or did you roll back to the IE before the current IE? I have a report from Microsoft where users claim this issue for other games on the last TWO IEs. For debug logging either edit or create a file named Saved Games\DCS(.OpenBeta)\Config\autoexec.cfg and insert this as a first line: log.set_output("dcs", "", log.ALL, log.FULL)

These are debug messages and absolutely normal. It scans different directories and in some it just does not find that lua. That is not the issue here, just a mapping that is not there (and not supposed to be there). If you switch to DEBUG logging, you'll see them, too.

@FlappieI just got pointed to this issue by another user, not sure if that is still a thing here. I checked that dcs.log that has been posted above. That user is using lots of mods and they have corruption in their Saved Games\MissionEditor files. Not surprising that it breaks their F10 view though.

With the BDA event, the unit type magically changes from UNIT to STATIC. That seems to be the issue here.

You are not using the standard export names (LEFT_MFCD, RIGHT_MFCD) and you are exporting stuff that is not exported in the standard game, which means, that you had amended the in-game luas to export these items. If you want it to work again, you must change the luas again, like you did in the past.