HoBGoBLiNzx3

Any idea which NVCP settings may screw with DLSS/DLAA? Like low latency mode, Clamping LOD bias etc.? I'm gonna assume it's best to start off with everything on default.

Yeah I have issues here and there with express. It's worth a shot doing a clean install and if you still have issues, then you know it's the update itself. I've had issues where the install will freeze and then won't install even after a DDU cleaning. Luckily haven't had that issue in a while but I've gotten some random artifacting with the version you're currently on and the one before it. Take that for what it's worth haha.

Did you try and custom fresh install or just express?

Well yeah no doubt, I meant more so that you could have one guy focusing on SA, lasing, comms, etc. Even if the pilot can do it, it's nice to split some tasks up and work together. You wouldn't happen to have a link for their development page in the forums would you? I'm guessing a lot of it is just in the development thread?

I just want the ability to have a wso in the back and do multi role.

It would be extremely helpful if you could add a kneeboard page that is automatically updated every respawn with a list of users/flight group/aircraft and isn't needed to be added in the editor, just a basic function. While in SP this might not be as useful it is huge for MP. This would be extremely useful for MP comms. Most people don't know their flight group identification and being that the aircraft doesn't tell you who they are unless you have on labels (which most servers don't use and shouldn't) you have to go to the role page to find out who is who. A simple list of who is flying what in respect to the flight group is necessary for comms. For example Mav 1-2 - BO11 - F-18 User33 - BO12 - F-18 Pilot88 - BO13 - F-18 Check33 - EO11 - F-16 Delta3 - E012 - F-16 etc.. Separated by flight groups and aircraft.

That's smart imo, then it becomes card dependent, so everyone from high end to lower end RTX cards will be rewarded. Thanks BIGNEWY.

Two weeks bro

Yeah, you should read the newsletters... It literally says they will be adding FSR support AFTER DLSS..

Thanks Mbucchia. I meant when it's on. I was able to lock it to 45 but I had to drop resolution down to 80 and use FSR at 80% as well. My gpu frame times went down to 13-15ms which was much more stable but I was getting pretty bad artifacting and ghosting. So I decided to just leave it off. It's been something I've tried experimenting with and TBH the best I can do without MR is either 100% res with no AA and then the headset starts lagging even though the FPS are 40+ or drop the res down to 80% and add 2xMSAA and it is much smoother with frame times around 16-18ms (hardly ever going over 20). What I meant earlier was I can't seem to get the FPS I'm getting with MR on that I do when I have it off. Which would give me a good 10-15fps over 45. However when I enable MR that headroom vanishes.

I said in the op that is with and without limiting. I was able to lock reprojection in openxr toolkit and it stabilized but the artifacting went through the roof. Guess I'll just keep it off for now.

Well a MT performance update would have been nice.. or Vulkan.. or DLSS.. Will have to check out Syria though, should look a lot better. Surprised there was no Sinai update either. Thanks for the update never the less.

So I've always ran MR off with my G2 but recently started using it as the OpenXR tool update really helped with projection. I'm running into an issue hopefully I can get some insight on. I can obtain a stable 45 locked on rivatuner if I limit or I can produce 60fps uncapped with MR off. However, If I turn on MR (with riva tuner frame limited on and off doesn't matter) It always pushes me under 45 to mid 30's.. I know there is some overhead with MR but I don't think it should be costing 30fps. I've tried frames over latency and 3 on NVCP pre renders. Nothing seems to help it. I have a 3080 and i7-9700k with IEST on 5ghz. XMP on 32gb Reverb G2 (all drivers and updates current) I'm running 80% on XR tools with CAS and Fovated on quality. Any help would be greatly appriciated. Cpu frame times are around 6-8ms GPU frame times around 18-21ms <--- I can't seem to get that down regardless of my resolution or settings by much... I would really like to get MR to be stable at 45.... a few dips wouldn't be terrible but not constantly jumping between the two.

Yeah but as real pilots have said. It's much easier IRL as the jet pretty much feels locked into place and doesn't deviate massively by slight movements. I think Mover said that once under the wing you don't really need to do much in terms of stability. Which isn't the case in DCS as far as I can tell.

Is that an assumption or insider information?

Can't wait for DLSS.. Hopefully soon..

Same here on the Reverb G2.

["shadowTree"] = false, I don't see anything in the game that resembles it, and changing it doesn't seem to do anything that I can tell.

Edit: Benchmarks change quite a bit depending on game, and hardware. While this is obvious and why I edited my comment, only you will be able to see if it helps your hardware..

I have that version as well. This option won't effect everyone equally. It is hardware and game dependent but that doesn't mean it's not enabled. It's a driver level option for hardware and what it does is uncap memory size transfers for textures... DCS texture sizes might not be large enough for it to matter but that doesn't mean it wont in the future and it takes stress off the CPU. Make no mistake, if you enabled it, and turned it on in NPI, it IS running... You just might not see any gains... currently. Check below. " Resizable Base Address Register (or Resizable BAR, as it’s known colloquially) is a new feature that improves communication between your processor and graphics card. It’s actually been part of the PCI Express specification for some time, but only now have manufacturers actually enabled it for use on the latest graphics cards, motherboards, and processors. When you play a game, your GPU requests textures, shaders, and other assets from your CPU. These get stored in the graphics card’s video RAM, or VRAM, before getting drawn into an image and sent to your eager eyeballs. However, the CPU has historically been limited to accessing 256MB chunks of the graphics card’s VRAM at a time—which, with cards that have multiple gigs of VRAM, means making lots of little transfers one after the other. This creates a bottleneck that has only gotten worse as games have gotten bigger and more complicated." https://www.pcworld.com/article/394720/faster-gaming-frame-rates-for-free-resizable-bar-explained.html

I do not believe that is correct.. I'm looking right above it with all the other settings in my NCP like the power mode, shader cache size, etc and they all have a blue icon. You should be able to force it on ANY game.

I just turned it on yesterday in the newest NPI version? I saw improvements for sure. I also changed a few stereoscopic settings and the game looks and feels better than I've ever had it. I don't think people really understand what this does. It just uncaps the transfer size for textures, AMD has a version of it too. It really takes stain off your CPU more than anything. If you're going to test, it will be interesting to see the CPU frame times in VR.. I also have HAGS on. As we've learned with VR frames rate isn't everything... Many people have 60fps and still get stutters, hit VRAM and RAM limits etc. If you have a top of the line system, you might not notice it until texture sizes increase in the future and 4k becomes more of a standard, still with DCS constantly pushing it's VRAM limitations it can't hurt to force on even if it isn't officially supported. It's doesn't need to be in the first place but it would obviously be more beneficial if it was.

Yeah but without enabling AACQ or TDC depressing a bugged contact? That doesn't happen normally? You should be able to look at the radar without having any contacts soft locked once they populate track files...

For some reason when when I switch the TWS, without enabling sensor control switch right for AACQ the hornet is auto locking anything and everything, even things that aren't in the radars scope. I have to undesignated to cycle TWS/LTWS locked targets. I've been flying it for the past year and a half or so and I haven't ever really run into this problem. It's even locking targets with the TDC cursor over them without AACQ engaged. Any ideas?

I wasn't sure if the clouds were a transparent texture or not. It would be nice if the VR preset greyed out features that don't work. I guess there really isn't that much. The tooltips are a nice addition maybe just adding some more details for VR users may help in the future.