bernardv

Hello, Misson 2 completely falls apart. SEAD team is defeated by AA fire, you cannot do bombing runs because AA remains active. Sometimes even the F14s lose to the 29s ... has anyone tested this with the more recent DCS and FA18 updates?

Hi, I noticed the fix included in this last update, thx. The F-16 planes are at the scene now, but the rescue helicopter still arrives super early and then runs away without picking up Colt. Am I doing something wrong? What is the trigger for the rescue helicopter to approach?

Latest beta - 2.8.8.43704 (installer verson 2.16.3.18).

Hello, what's the trick with mission 6 (Everyone comes home)? The rescue helicopter gets shot at and runs away (without performing the rescue) as soon as I arrive at the scene. Doesn't matter if I take out all of the Russian forces after that, the helicopter is gone and Colt is left at the LZ. Is this a bug?

Mate, you're a fucking genius. You just saved me 2000€ (cost of RTX 4080/90 card, new power supply and case). You should be working for DCS, i.e. they should be paying you.

@gortex I'm having the same issue in VR, same graphics card with Quest 2 headset. I have to add that I don't have similar severe VRAM shortage issues with any other game (or sim), VR or regular. I've heard speculations that DCS texture handling is very sloppy with identical textures being stored in VRAM over and over, full resolution textures of distant planes being loaded even if that plane is just a dot in the sky ... As noted I'm not claiming this is a fact, just speculations by some more educated users. Are there any plans to optimize VRAM usage in the pipeline or not?

After some additional testing it looks like setting the right bitrate for air link seems to do the trick. Setting it too high (200) definitely makes it worse, but at 135 for example I can notice the audio and video quality is not optimal. For me 170 looks like the sweet spot - stable and looks good.

I tried the Virtual desktop and when compared to air link I find it to be a cluttered bloated instable mess. It can't even work with DCS without steamVR (which I'm not using), the controls are not mapped properly ... all in all definitely not the direction I want to go. fholgers - another factor that IMO just adds complexity and instability to the equation, thanks but no thanks. I'm looking for a tested and robust setup, not some untested combination of exotic software components. If/when something like hfolgers would actually work properly with DCS, it would get included in open beta at least.

Hi as described under a A-10-C2 bug thread; at high detail situations (e.g. a hi def plane like A10C2 on a cluttered airport scene like Nellis, also returning to Nellis from a mission) DCS tends to freeze (momentary drop in FPS to 0) for a moment, loading the textures I guess. This causes Quest 2 link tracking to go out of sync with DCS somehow. The result is terrible stuttering when looking around in VR. To resolve this one needs to pause the game and take off the headset for a second or two. This resets tracking and after that it's OK, well till the next drop in FPS. This workaround, once you figure it out, is not so terrible, but still I would wish for DCS and Quest 2 (via air link) to be able to cooperate better and not go into these stuttering at all. I guess the software could detect this state and resolve (resync tracking) automatically?

I think I figured this out. Looks like DCS is only able to run VR at 45 or 90 fps (I don't think it can even tell it's a Quest 2 headset, it just assumes it's Rift S). Quest 2 default for Air link is 72 Hz and that doesn't mix well with 45/90. After I switched to 90 Hz in Oculus settings the stuttering went away. Still I have no idea how this didn't affect F18 or any of the FC3 planes, just the A10C2. PS One explanation could be that this resynchronization from 45/90 to 72 takes an extra toll on the GPU. With simpler planes I was at the point where my GPU could still handle this, but with A10C2 it was just the last drop that pushed the GPU over the edge. PPS In the end it looks like it's simply a Quest 2 tracking issue, which occurs under high load of all components involved when using Air Link. If this stuttering starts to happen, the simplest way to resolve it is by just pausing the game and taking the headset off for a second to reset room-scale tracking on Quest level. With lower bit rates, simpler missions and planes, lower rendering resolution this is a non-issue, doesn't happen. With everything cranked up and when the mission starts in some cluttered environment in a more complex plane like A10C2...

I tried out some VR mods some time ago but I removed them soon, restored original bazar folders from backup. Refreshing these shader folders under saved games didn't make any difference. As I noted before; either this plane takes a higher toll on the main CPU thread or it's simply the quality of the textures and the level of detail in the cockpit that take a higher toll on the GPU. Perhaps more than 8 GB of VRAM would be optimal for a clear cockpit view of A10C in VR? Something like 6900 XT? Or can some upcoming Vulkan magic do the trick in the near future?

Here you go. I'm under the impression my settings are quite well optimized, but hey, I might be wrong dcs.log

I've got GTX 1080, Ryzen 5600X, 32 GB RAM, 1T NVMe disk. For VR I'm using Quest 2 (tried both Air and USB link), but it was similar on Rift S. My monitor is LG 32GN600-B with variable refresh rate up to 165Hz set to 120Hz for my Windows desktop. I use DCS in VR only. In an F-18 I get some degraded FPS flying over Dubai for example, otherwise it's fine. In an A10C2 I get low FPS/stuttering right away at any larger airport (Nellis, Dubai ...) when doing startup. On smaller airports and on most of Caucasus map It's much better, basically playable. Again, an F18 is playable everywhere for me.

Hi, I've noticed considerably worse FPS and stuttering when using A-10C2 compared to F-18 for example. This would be on the same map, same starting position on the runway, same settings... This is noticeable in VR in particular, when doing startup on some large airfield for example. Is there any reason for A-10C2 to take significantly more HW resources than F-18 and other planes or is it just implemented in a less optimal way? It is my impression that this module clogs the already clogged main DCS CPU thread even further, but it's just a hunch. Cheers

I mean sure, it's a war sim and war is what it is, but Isn't this title just a bit too cynical for good taste?