Moezilla

@BIGNEWY has the investigation come up with any findings on this issue yet?

The error message seems to refer to an issue relating to temporary files. If you have plenty of space on your drive(s) then another possible cause would be a permissions issue. Is it possible that you installed DCS, or parts of it, as administrator and are running it as a regular user now? This can lead to some weird behaviours.

@BIGNEWY has there been any update on the internal investigation into this issue?

@Oberst Struppi there may be an issue with AI pathfinding on the GermanyCW map.

@Flappie I did a quick test with the miz files I had attached above in the thread and the issue I had seen seems to be fixed. Thanks.

With Optiscaler you can re-route DLSS calls to FSR 2 or 3 on non-nvidia GPUs (I have an AMD card) even in DX11. I haven't tested it in every scenario but it works as a proof-of-concept.

Thanks for taking the time to nail down the conditions to reproduce the dot limit. I hope ED will take steps in the very near future to address this issue, which has been raised before, but now, thanks to @MoleUK, has tracks and a solid set of conditions to show it in action.

Yeah, the OF412 is too weak, and too fast. The L118, as a howitzer, needs a dual purpose direct/indirect round, so currently, the 122mm ammunition from the 2S1 is probably the best compromise, even though it's slightly too powerful. Ideally, ED would add the UK L31A1 105mm shell, and the US M1 105mm to their arsenal, so that the ranks of NATO artillery pieces could be filled out to cover the Cold War period. M101, M102 and M119 would bridge the gap from WW2-early 2010s for the US and other operators.

Just noticed that I had client tracks turned off. Here's another run with the same miz. dcs._client.log dcs.log server-20241008-130454.trk swg_caucasus_dynspawntest-20241008-130625.trk

@Flappie @BIGNEWY Here's the mission, logs, and tracks from both client, and dedicated server. This track features the Seawise Giant tanker, but it also affects carriers and the Oil Rig with helipad. Using these objects as dynamic spawns results in the parking spot not releasing properly if the aircraft is destroyed, preventing further spawns until the mission is restarted. dcs_client.log dcs_server.log server-20241008-124632.trk swg_caucasus_dynspawntest-20241008-124732.trk swg_caucasus_dynspawntest.miz

You are right. Sorry for getting your hopes up. In my first test I took off with the Huey and landed on land, then it allowed me to respawn on the SWG. But this time I threw the Huey in the sea and it would not let me respawn. I'll make a track and grab a log.

@Chesster @shaji I checked the SWG and CVN-71 in 2.9.8.1214 and they seem to be working as expected now. Can you confirm? @Flappie the ARA Veinticinco de Mayo seems to still be showing this bug when placed as a dynamic spawn. You can spawn 3 times in a dedicated server (4 times in a local server for some reason) and then you get a "YOUR FLIGHT IS DELAYED TO START, PLEASE WAIT" message in the top right of the screen, after that if you try to select role again the spawn/parking slots message comes up, then you can no longer spawn there until mission restart. Test mission attached. vdm_caucasus_dynspawntest.miz

OP's track still showing the same events in the debrief. Do tracks store and replay the previously fired events, or do they fire fresh events based on the stored actions in the .trk?

Since DCS version 2.9.8.1107 both executables should be the same, just on different paths. Maybe something is profiling the executables differently? Some people put the entire DCS installation folder and the folder in Saved Games into the exclusion list for Windows Defender (and any other AV solution) to prevent real-time scanning from eating CPU cycles. Also you could go to Settings -> System -> Display -> Graphics and add both DCS paths to the custom app settings with high performance ON. I see you are also running borderless fullscreen, so it could also be worth trying the Optimisations for windowed games setting in Settings -> System -> Display -> Graphics -> Default graphics settings to see if it helps improve any input lag. With Vsync ON it might be worth trying fullscreen mode in DCS, just as a test, and also using the nvidia CP to experiment with the low-latency mode there. Good luck, getting DCS into a sweet spot can take some tweaking, but it can run well.

Some things you could try: - disable hotplug devices in control settings, there are hotplug events in your log, including from your audio devices. - google how to turn off the power-saving features on your USB ports to prevent windows power management from putting them into low-power mode. - you have parked cores according to the log, you could try unparking them. there are free tools available online like Parkcontrol that can do this. I understand that DCS ran well before this time but it could be that some normal Windows/Dell updates have made some changes that may also have impacted how well DCS runs.

One thing that sticks out is that your motherboard BIOS is 5 years old and there have been 15 full releases, and a beta from less than a month ago, since your installed version. Apart from CPU microcode optimisations, power management improvements, and better device compatibility, there have been 5 security issues patched that may or may not fall inside your use cases. In Windows, it's probably worth doing some standard stuff if you haven't checked on them in a while: Windows Update, install latest AMD chipset drivers, ensure game mode and game bar are disabled.

Tested @tmz's scenic-bench in 2.9.8.1107 and it shows performance has returned to around 2.9.5 levels. I'm capped at 95fps on the carrier in the Hornet, or looking at the F-15 in the screenshot. I waited for, and watched, the scud strike on Khasab, and performance held up well for me. Hopefully it's the same for others. 2.9.8.1107

You are right that if you ask the CPU and GPU to work flat-out to deliver as many frames as possible there can be moments where the CPU gets a spike in demand that causes the GPU to wait, and then the GPU load drops, and FPS follows. It is better in general to cap the FPS at a level where your CPU has a small amount of headroom to absorb the smaller load spikes. There's nothing much that can be done if the mission spawns 10 moving columns right under you or a huge cruise missile strike lands. But something to check since you mentioned you haven't played DCS for 10 months, there is an issue with high-polling rate setting in mouse software. Until the issue is fixed the polling rate should be set to 500Hz or lower. The symptom of the issue is, as you described, looking around causing hitching.

It is a reported issue that I'm told has been fixed in an internal build, so it should make it into the next patch.

I'm not sure. I tried the FSR option when it first released and didn't like the TAA, so went back to MSAA.

If you are using the FSR upscaling option it will force TAA on.

Your autoupdate.log shows that the change to 2.9.5 failed because: 06493.957 ERROR: Can't delete F:\DCS World OpenBeta\Bazar/shaders/metashaders.edce: (32) The process cannot access the file because it is being used by another process. Possibly the DCS.exe process was non-responsive in the background and prevented the 2.9.5 update from happening, or if you have ever run DCS as admin it could result in a permissions issue with certain files. If it's the second option then things get a little more complicated, hopefully it's the first one. Reboot the computer and try .\DCS_updater.exe update 2.9.5.55918@release again, it should be able to use the downloaded files from before if they are still in the _downloads directory so it should be faster.

No, bin-mt is the correct directory. Use Skatezilla's tool to verify that DCS is detected as 2.9.5.55918, with the correct Sim Path and Saved Games Path. Then use the repair button on the left and run a slow repair. Then delete the contents of the Saved Games\DCS\fxo and Saved Games\DCS\metashaders2 directories, and try to launch DCS again. If that fails, then post your dcs.log.

Hold down shift before you right-click and choose Open Command Window here or whatever is closest to that. and do it on the bin folder not bin-mt

Find your DCS install directory (not the one in Saved Games) through explorer and double-click it so you see the API, Bazar, bin, bin-mt directories Right-click on the bin folder and choose Open in Terminal In the window that pops up enter .\DCS_updater.exe update 2.9.5.55918@release I just tested this and it worked. It looks like the text box in Skatezilla's tool doesn't allow non-numeric characters in the custom version box, so it can't give the updater a version string in the form it's expecting.