Mr_sukebe

From a WW2 perspective: Just looking at that map, phase 3 looks like it'll include Arnhem and Nijmegen. Also has enough on the western side to include Boddenplatte, the bulge etc, with us able to use allied bases in northern France. Plenty of cities in the middle to conduct bomber intercepts. We'll finally have a genuine location to use the K4 and D9 Awesome stuff.

Doesn’t seem to be an outrageous price, which is good. The real question will be how it compares from a quality perspective to other existing solutions. For example, does the build lock the components in place? If not, is there a degree of wobble on each component. That would annoy me

Do you mean in DCS, or reality? My assumption is that it would be faster on the ground, as it's a safer environment to conduct fueling. It's worth remembering that drogue and probe is (as I understand it), significantly slower than boom, as used by Air Force aircraft.

It's well deserved. Please pass my thanks along the your whole team. As an ex-programmer, it's rare that we get thanked, so it's nice to return the compliment when the opportunity arises.

I believe that someone tested the Beta of 1.1.1.36 and was still getting Ghost presses, at least that was the comment on their Discord.

The benchmarks I saw yesterday showed the 9950x3d not having any real benefit within gaming. That "might" be slightly different within DCS, not with DCS running on the primary CCD, but with the number of other background Apps that some of us use (e.g. Simshaker, Discord, SRS etc).

No mention of a fix for Virpil Alpha "ghost" button presses.

Interesting. I wonder which one is correct? Maybe neither are.

+1. One of my favourite modules. Very "hands on". The most amusing thing being that I still can't hit anything.

Thanks, not just me taken by surprise.

Have you tried the updated options in DLSS, eg preset K? if not, there’s a thread on how to configure it.

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