Ready
-
Posts
649 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Ready
-
Set DCS's max FPS to Headset Refresh Rate When I set DCS's Max FPS above refresh rate my 1% and .02% are reduced. Setting Max FPS to 90 (Aero=90Hz) is the best setting for me.
-
Ah okay. Will test and post my results. Nice video!
-
Update the DLSS preset used by DCS to remove ghosting
Ready replied to sleighzy's topic in General Bugs
Yes if configured correctly it shows up in my VR and in the desktop mirror. Bottom left corner. I am not using the registry entry so can't help there. I am using DLSSTweaks to enable/disable. -
DLSS ON vs DLSS OFF? For me there is a huge difference between the two. I don't see a video when I click on the image.
-
What is it exactly you are comparing? I will run the same test just to compare if I see the same.
-
What are your MSI Afterburner settings for the 4090? I am currently on +100 Core Voltage, +50 Core clock and +700 Memory Clock. I sometimes run Core Clock on +120 and Memory Clock on +900, which also seems to be sweet and stable, but I had a few crashes a while ago and I think it was caused by this OC (but it was with my previous W10 install) so I could experiment with upping it again..
-
Nice! So with your setup you don't really see a difference between 35ppd and 39ppd? I will check the same now DLSS4 is here. Which Quad Views application do you refer to? I am using Mbuccia's QVFR and have OpenXRToolkit running for the performance overlay and some post processing effects sometimes. When I enable Turbo Mode inside OXRTK I don't see any difference in performance on way or the other. Why are you automatic vertical sync and motion smoothing? For me that costs a lot.
-
I don't think my system is horribly overloaded tbh. I believe I still have a lot of headroom in the 9800X3D, even though DCS tells me I am CPU-bound and it somehow has no way to make better use of the CPU's performance. My 4090 is not really doing much during the quick testruns (I start the stock A-10C Marianas take off mission and keep the Hog standing there). I keep my headset on my desk and I sometimes pick it up to look around and check visuals. But the measurements are always done with the headset on the desk and VR centered. During these measurements the VRAM is relatively low I think. I will check VRAM in future tests when I have removed a bunch of images from the various Tabs in OpenKneeboard. There is about 80% of images I guess I don't not really need or use. Unsure if it would help to clean them up, as you say it does not do anything else than consuming some VRAM and I do like having them at my fingertips, just in case I need something. I have done a clean Windows10 install a couple of weeks ago and stripped it to its underwear. I am still working on finding more ways to further calm down the OS, but it is pretty silent already. Besides DCS I am running the following applications; Process Lasso, WtabletServicePro+children, VoiceAttack, SRS, OBS, Varjo Process Server+children, Simhaptic+DCSRealistic and OpenKneeboard (in various profiles with one or two kneeboards visible). I am checking these apps one by one to measure what is their impact in this mix. With regards to the OpenXR runtime; I am still using Jabbah's since there hasn't been a better known way for me to get OpenKneeboard to appear in my recordings. I will check in with him to see if there is anything to look at. It is unclear if he is still active, our last contact was beginning of 2023 and his last release was about that time, I had his last beta. Unbelievable how time flies. I see our chats on OpenKneeboard date back to 2022 when it was version 0.1.2.180. Where does the time go.. I am also still using Mbuccia's QVFR. Have not tried Varjo's because it won't show OpenKneeboard and I can not manually adjust the peripheral settings for example to get the most out of the system. When I don't have OBS running and OpenKneeboard is loaded the difference between hidden and visible shows a difference of a couple of FPS. I will run more tests in various DCS performance settings and configuration states to get a better picture of my system. (I just noticed that when I close and reopen OpenKneeboard the desktop app does not open in the screen location where it was when I closed it. I also noticed that when I update OpenKneeboard somehow my VR settings like the size, position and orientation of the Virtual Kneeboard gets reset. I will check your help thread and put a few items up on your github if it is not already on there.)
-
Further optimizations I am playing around with a couple of things at the moment: DCS Object Shadows Flat <> Default. Nvidia DLSS 4.0 Profile J <> K. Combinations of DCS PD (1.0, 0.9 or 08) <> DLSS Performance, Balanced, or Quality <> QVFR Focus_Multiplier (1.0, 1.1 or 1.2) Combinations of Sharpness in DLSS (currently .3) <> Sharpen_Focus_View in QVFR (currently .5) OpenKneeboard Single <> Double Kneeboard. Check if there is a performance difference. Only opening the Kneeboard when I need it during flight and keeping it closed otherwise. Having it open costs about 3-4 FPS and a 5-15% hit on the 1% and 0.2% Reduce amount of images in the Kneeboard to reduce VRAM. (thanks Fred for the tip). Quad View Foveated Rendering Changing the dimensions of the focus section. Make them just large enough not to notice the focus section moving around. Currently both at .35 maybe reducing the vertical and increasing the horizontal. OBS I usually fly with OBS enabled. So I will start running tests again with OBS enabled. Disabling Desktop Preview. I always used to have the Preview enabled, will start disabling it after I checked that it is working. Adjusting bitrate. Currently possibly set too high.
-
Thanks yes I have gone that route a coupleof times. It seems easier for me to roll back a few versions and then upgrade with the nvidia installers. I then don't have to boot in safe modes etc and I guess the end result is the same?
-
Just try/compare it for yourself I would say. The opinions I read so far are mixed. I might also go back and forth for a while and settle.
-
Yes same here. I installed the new Nvidia driver (572.16) and Nvidia App after first having used the CUDA released driver (571.96). I checked Nvidia app but quickly uninstalled it. I got the feeling it will mess up my settings and is bloat and complications I don't need. There is also a question in the Nvidia app installer that asks 'do you want this app to optimize your stuff' or something like that. Do not do that, I read it can really mess up your settings. I also could not roll back to 571.96 so I tried rolling back to my previous best driver(566.14) and from there I installed 571.96. Performance-wise I did not notice much difference between 571.96 and 572.16. I will install the latest version again, but without the Nvidia app. With every driver I always go through the NVCP settings and the DLSSTweaks to make sure the settings I want are reconfigured. I also can not see the overlay inside the headset. It is perfectly readable on my Desktop mirror though. For me the easiest is using DLSSTweak to set 'HudOverlay'or something like that. I would Ditch the Nvidia app.
-
Thanks, yes the new radio could have something to do with it, not sure. I did check out that scripting thing, but could not get my head around it at the time. It was a bit too complicated or I did not have the patience, or both
-
DLSS Profile J and Profile K The difference between both profiles is very little in my case. I will probably fly with K until the next improvement is released. All so beautiful now! Will adjust/lower some QVFR and DLSS settings to trade some clarity for performance.
-
It is so tempting to switch it back on to try, but will probably instantly regret it when I CTD in the middle of a tense game..
-
It was one Taz's A-10C mod that somehow caused it. Very strange since it are only textures. But anyways, I found the issue and it is resolved. Thanks for the tips Thanks, never knew! Thanks it is resolved.
-
Yes thank you. It works now. Much appreciated.
-
Yes setting DLSSTweak to K ends up in J here as well. Agreed, still amazing. But would really like to see that ' improved temporal stability, reduced ghosting, and enhanced detail in motion
-
Mode J worked, but after installing 572.16 and the latest Nvidia App and today's DLSSTweaks, I somehow can not get it K profile to work. What also is confusing is that the HUD overlay says 'DLSSv3', shouldn't it state DLSSv4? It says v310.1.0, so I guess that is alright. It now defaults to C, even if I change it to J inside NVPI or to K inside DLSSTweaks. null
-
Recently my FM radio is acting up. I have no idea what is the cause. I usually startup and switch to a 30.* freq on the FM. Now when I start up the first dial on the FM is set to 13. When I rotate it, I get a loud tone on the single digit freqs. There is a rotary on the FM, which is by default on MAN. When I switch it to FM, the loud tone dissapears but others are still not able to reach me on FM. Using SRS and Mid and Front radio's function fine.
-
Update the DLSS preset used by DCS to remove ghosting
Ready replied to sleighzy's topic in General Bugs
Nice one! thanks. -
I have shadows at least set to medium. Really like the effects in the cockpit of Shadow High, but I can also live with Medium. I am seeing a strange effect though on treelines and fences/walls where a part of the shadows only renders when I am pretty close, like 1NM. Will see if I can catch it in a recording
-
I see it everywhere I look. Bloom and lens effect are disabled. But because I am using QVFR the effect might be amplified.
-
Nvidia 571.96 Updated to the newest Nvidia driver, which made a huge difference in combination with DLSS 4.0 Profile J. I was able to readjust my Quads Focus Multiplier back to 1.2 Inside DCS DLSS Performance and Sharpening 30, which probably can be dialed back a bit. Had to reduce some of the GPU overclock to keep it stable in my testcase. Amazingly crisp visuals at no real frame loss.
-
Same here on Varjo Aero, for me it also is visible without SSAO.
