Mr_sukebe

Hoping that a few of you might be able to assist with a query that I have. I've recently replaced my 3080Ti with a 5080, the 5080 having 16GB of VRAM. Whilst in game, if I open the DCS built in FPS monitoring, one of the lines in the detailed block mentions both reserved and used VRAM. I don't remember that being there before. Either way, I have been used to my VRAM all being reserved, and that's still the case with the 5080. However, I don't remember previously being able to see VRAM actively in use. What has surprised me is that it's not exceeded 8GB during the last few flights. Can both 5 series and older NVidia users please comment on what you're seeing in the VRAM actually being used. In short, I don't understand why I don't seem to have a VRAM issue anymore, despite only increasing the VRAM by 4GB as part of the GPU swap and that really confuses me. I'm wondering if the move to GDDR7 RAM has made the difference.

Just turn DLSS off. DLAA is anti-aliasing, and can be used without the upscaling of DLSS. I'd personally recommend that you disable DLSS and at least try DLAA. If you don't like it, THEN disable it.

It would help if we knew which part of DLSS you’re using. At the moment, it’s like saying that my Ford car is unreliable.

By DLSS, what do you mean by mean? DLSS now contains: - Upsampling - Anti-aliasing - frame gen - multi frame gen

Sorry, was meant as a joke

I probably have more hours in the Harrier than any other aircraft in DCS. It's a really good module. HOWEVER, I can't now overlook the fact that the Razbam could potentially kill the module (e.g. if Razbam didn't hand over source code and a future DCS update breaks the module). In place, you might want to look at the Mirage F1, which is also a great module.

Do we get two versions of the Shinano, i.e. the one without aircraft, and the other underwater with holes in it?

Just been for a meander around the Falklands in a harrier. Textures high. From the data displayed by DCS, it had reserved 15GB of VRAM, and was using under 7GB, that's promising, though being fair, it was a very simple scenario with not much there. Frame time was mostly 13, sometimes going into 14. Task manager showing GPU usage around 80% at a pretty much continuous 72fps. Have just updated my Encode Resolution. 3905 was NOT correct. Should have been 3840. Changing that has improved definition. Have also disabled DLSS upsampling, whilst using DLAA. Still getting a solid 72fps. OK, think I'm good at that.

Not completely equal CPU use across all cores, but none maxed out. VRAM varied. Whilst over Normandy in a 190A8, it was 12GB. In the Gulf, over Dubai it was full. To give me some breathing room on VRAM, I’m going to put textures back at medium. In VR, the visual hit is not huge. I’ll check frame times later today.

Have you watched the video? The guy in question is apparently using Vulkan with DCS right now. I've no idea how he did it.

Having played more this evening, I'll very happily take back my comment about OTT being redundant. I tried a variety of things tonight, and settled on using OTT to manage the Link Bandwidth, Encoding Res, and multiplier Had a meander about in Normandy and over Dubai, solid 72 frame rates on both, despite the GPU not being maxed out. For awareness, I'm still getting micro-stutters even with a solid 72fps. From a video I watched recently, my hope is that the move to Vulkan will assist.

As already mentioned, Textures. Lower them down. Other things to try: - Disable your "home" in Oculus. That eats a couple of GB of VRAM - Use the mod "Empty VR hangar", which also eliminates wasting a bunch of VRAM.

Thanks. I hadn't even realised, as I don't get shown my own sig.

OTT - I only really used it for upsampling. As this can be done in Quad views, for myself it was redundant. If you wish to use, that’s cool VRAM usage: You can see my settings. Maybe ours are different. Whilst checking they were reasonably complex missions, but I’d expect that to mainly affect CPU usage. Either way, if you’re using less, we’ll done

My settings (updated) are: Oculus Headset: Via USB3 data cable, Anker powered USB hub to PC OpenXR Oculus HomePage - disabled Oculus tray Tool: x1.3 supersampling Res: 3905 Link Bandwidth: 960 Quad Views: peripheral_multiplier=0.3 focus_multiplier=1 horizontal_focus_section=0.22 vertical_focus_section=0.22 DCS: Using Empty VR Hangar mod to save VRAM (see image attached)

If you have such a variance in fps, my recommendation is to lower the textures. Try setting Textures (i.e. your aircraft) to Medium and Textures for Ground to Low.

Sorry, can't remember offhand, but I'll check later. My assumption is that the default settings assume we'll be using fixed fov rendering. As we have eye tracking, I've been a lot more aggressive, so the periphery multiplier is pretty low. x1.5 is the upscaling for I assume the central area.

Currently running with .22 * .22 and x1.5

My 5080 arrived today and is now installed, having replaced a 3080Ti. The rest of the PC includes a 7800x3d, 64GB ram, PCIE5 SSD. My VR headset is an Oculus Pro, which does have eye tracking. As such, I'm using that rather awesome Quad Views from Mbuchia, which most certainly does help. My drivers are 572.16, using the latest DLSS (K?). The DLSS setting is for quality upsampling and DLAA AA. The hope was to achieve an FPS of 72, which is the native frame rate for the Oculus Pro, and in short, with the 5080, it nearly consistently hits it. Settings included: High Textures High scenery textures Ultra Clouds (lower settings look a real mess with DLSS upsampling) scenery detail, forests around 80% across Flat shadows In the Oculus, I have the "Home" disabled, and in DCS, I have the empty hangar, both of which save VRAM space. I tried a variety of aircraft including the Viggen, Harrier, F4, F18, Apache and Chinook (not the mod). For terrains, I used Kola, Afghanistan and Falklands. With most of the aircraft/terrain combinations, the GPU was running between 60-80% usage, even after upping the up-sampling in Quad Views to x1.5. The frame did visibly bounce around a little, but in most combos, it was very smooth. VRAM usage was around 14GB+, so not much headroom. The positive news was that with nearly every combo, once the shaders were built for all but the "odd" new texture, that the blips barely registered whilst it was loading. My guess is that maybe data bus all being at PCIE5 "might" helped. The caveats being: Add the Chinook showed up the implications of only 16GB of VRAM, which resulted in an absolute tanking of frame rate, whilst DCS was dragging in what are clearly "fairly large" textures for the aircraft. As that was the only aircraft that I experienced issues with (and that was on the SA map), that's fairly positive. Is it enough to justify the additional spondoolies for a 5090, well that's not for me to answer This was single player. Haven't tried multi-player, so these findings "might" not be fully representative In short, I'm pretty impressed. I wasn't sure that it was going to deliver the hoped for 72fps, but in the majority of my tests, it happily managed it. As for power consumption, turns out that it's very close to my old 3080Ti, meaning that I frankly don't really care. Hope that helps.

That’s an interesting video. it’ll be interesting to see how he did it and which terrains and modules are not as yet compatible

You’ve gotta love the ingenuity

Just checked, my install is 1TB, almost exactly, again, excluding the Saved Games folder.

Seaking, maybe a Ka27

The move from a 9700 to a 9900 is only really going to give you hyperthreading as the number of CPU cores won't change. To my knowledge, that's unlikely to help either of the sims that you mention. Personally I bought a new rig to replace my 9700 and went with a 7800x3d. That game me a good 50% improvement in frame rate, and is where I'd recommend you apply the cash.

See the above from Parrot, stating that his is 1.05TB currently. I'll check mine again later on and give a precise count. Do remember that I did state that this EXCLUDES my Saved Games folder, which I have on another drive.