Jump to content

WipeUout

Members
  • Posts

    436
  • Joined

  • Last visited

Everything posted by WipeUout

  1. The only possible advantage would be if you move from a 4 stick config to a 2 stick config. Using 4 stick can be very demanding for the mobo memory controller and can cause crashes in DCS, always more safe to use only two sticks. If your firend is proposing 2 sticks of 16GB and you are using 4 sticks of 8BG, then it might be a good move.
  2. My Pimax 8KX runs pretty acceptable at 60 or 75hz but so much better at 90hz. What made a big difference was also to use Quadviews which seems to process frames in a more stable way. Using Quadviews made 60hz and 75hz much better than before. Seems that with Quadviews, the spacing between frames is more uniform creating a much better experience. I must also admit that simming at 60 or 75hz during long period of time is difficult compared to 90hz. With a 3080, you will not be able to sustain 90hz in all scenarios and at one point, have to compromize too much on quality. Personal taste and tolerance play a big role here also.
  3. 8KX, 4090, i9-13900K, 64GB RAM DCS MT Textures High/Terrain texture High for Caucasus, Nevada and Middle-east Textures High/Terrain Low for other maps DLAA + DLSS Performance Shadow low or med for Caucasus, Nevada and Middle-east, else flat Water Med Clouds Ultra for Caucasus, Nevada and Middle-east, else standard. Keep off: Traffic, Heat blur, Lens flare, Secondary blur/shadows, SSAA, SSLR, SSAO, Aniso Filt., Cockpit Global Illumi., V-synch Forest visibility 100%, detail factor at 1.0 in Caucasus, Nevada and Middle-east, else 0.1 Scenery detail at 1 in Caucasus, Nevada and Middle-east, else 0.5 Preload at max LOD keep at 1 Gamma 1.3 (To reduce haze, must be used in conjunction with max backlit in pimax client) but for night mission, crank up. PD =1.0 Pimax Client Refresh 90hz Backlit 100% FOV Normal Render Quality 1.0 FFR off OpenXR Sharpen at 100% Everything else at off/default PimaxXR Enable quadviews Quadview I use the following config file: # These settings are for all headsets and applications smoothen_focus_view_edges=0.3 sharpen_focus_view=0.8 [app:DCS World] # The settings are specific to the app "DCS World". turbo_mode=1 peripheral_multiplier=0.4 focus_multiplier=1.6 horizontal_focus_section=0.30 vertical_focus_section=0.45 Process Lasso For DCS, only use P-Cores + High priority class Pi_server, High priority class Additional tips and notes: Setup two saved settings in DCS: "Setting 1" for low demand maps, "Setting 2" for high demand maps. Acceptable AA option varies quite a lot from person to person. For me, using DLAA/DLSS combination is great and I do not mind the small smearing. Shadows can be improved a lot with mod "https://www.digitalcombatsimulator.com/en/files/3329503/". Quadviews high res box (30% x 45%) may seems small but with the wide FOV of the 8KX, this will give you a resonable size with tremendous uplift in performance. In VR, clouds are a significant performance hit and horrible at any setting except tolerable at ultra setting. If you play a mission that has lots of clouds, you must keep ultra setting compromise elsewhere such as the "focus_multiplier" down to 1.4. in quadviews or lower HMD refresh rate. You always have to option to lower the HMD refresh rate to 75hz or 60hz and keep same settings on any scenario but for me, 75hz and 60hz cause some flickering sometimes. With these settings, you should get a super smooth experience with excellent clarity. If not, then your windows/BIOS/NVCP maybe the issue. A windows fresh install, though requiring lots of work, can cure a lot of performance problems. If you use 4 x memory sticks on an MSI mobo, make sure your BIOS is up to date as it can cause crashes because of the stress imposed by DCS on the memory controller. Keep overclocking low, the i9 13th gen will not be the bottleneck in your system.
  4. Since 2.9.3, I also had crashes and occasional stutters lasting about a minute. Crashes were resolved by a BIOS update (MSI MPG Carbon). Memory management was not optimal and DCS is quite demanding from your memory controler specifically if you use the four memory slots (4 x stick of RAM). Stutters were resolved by using process lasso, removing use of e-cores for DCS, pi_server, and setting high priority for those two. The sim has never been so smooth and stable.
  5. Try VR-ROCK, nice fit and relatively cheap. Go for the 15mm foam also, much more confortable. DLAA+DLSS still my favorite but there are some smearing even at 90hz.
  6. I used to set DLSS/DLAA at Perfromance but with the latest 2.9.3, I am using DLSS/DLAA at quality with very sharp results and practicaly no more smearing. Big advantage with the combination DLSS/DLAA is the improved framerate instead of a big hit with MSAA and still some shimering. I run my 8kX at 75hz. I need to try again TAA with 2.9.3.
  7. My test track (FA-18C over Caucasus) is 10 FPS better. Only thing is that for all my tracks with FA-18, there is a horrible shaking of the airplane, because of the new flight model I guess. Other than that, also seeing reduction in CPU frame time of about 0.26 ms, which is not negligible. Welcomed improvement, thanks ED!
  8. I use the DLSS/DLAA combination only. The MFDs are the main issue for me but tolerable, the smearing is not a problem (very much personal tolerance here). DLAA alone without DLSS is a 2ms hit on my GPU frame time, not good. As for TAA I have two issues. It does look nice with a bit of sharpening but air targets disapearing is a problem. Second issue is with movement in general, it makes the image a bit blurry.
  9. What would be realy nice is the ability to switch off the changing/fading high altitude clouds. As an example, being able to have a clear sky that does not change would be great as this is often the case in the middle-east.
  10. @bandit648, first many thanks for this outstanding mod! Second, is it possible to change the transition time to even greater value such as 60 minutes?
  11. I use only one lighthouse and only on channel B. The behaviour and sensitivity of the tracking varies quite a bit and finding the best location for the lighthouse takes a lot of trial and error. I have my lighthouse on a tripod at about 2.5m from the ground and about 3.5m away from my head. When I start Pimax client, everything is grayed out and it goes into connect / disconnect about three times before I start seeing the lighthouse flashing green. Once it is flashing, while seated in my sim pit, I do the "Pimax Dance", or rotate the HMD 180 degrees from the lighthouse and out of sight and then back facing the lighthouse and the tracking starts. After that, I have to be very carefull not to grab the HMD from the side as I loose tracking easily. Other than that, it is very precise and creates quite well the illusion of being physically in the cockpit. As you said, oncer it's all fine, there is nothing like an 8KX to provide this intense level of immersion. Give it another try...
  12. Sound like something is filling up over time. Did you tried various setting for the terrain preload slider? Also consider checking if your GPU is in MSI mode. You may want to check also if you have the same issues with any of the texture settings. Also, where is your DCS installed? having DCS on a separate M2 drive from your Windows could help.
  13. Do not mix QVFR settings and pixel density, or ''render quality'' in Pimax client, these are two different things. Go back to the video and read the bottom comment, you will see that with the 2060, they lower render quality to 0.5 which means 25% of the native resolution. QVFR default settings will keep the focus area to 100% of the set resolution and the peripheral area at 50% of the resolution, that resolution is defined by other settings such as render quality in pimax client and/or pixel density in DCS. There is not doubt that QVFR does a superb job at incresing FPS but reducing the rendering resolution with a 2060 is probably the only way to reach 60 FPS!
  14. If you take into account the rendering resolution drop to 0.5, this is a reduction of 75% of the pixel count. I think it looks plausible but the image quality must suffer a lot.
  15. When a mission has no clouds or preset selected, there are high altitude clouds showing on and off. Whenever I switch from external to cockpit view, the high altitude clouds paterns change and sometimes they go away leaving a perfectly clear sky. Is there a way to stop this random ''high clouds on/off'' behaviour? Is it possible to have a clear sky throughout the mission?
  16. If you mean that you see a border between the inner high resolution portion of the image, and the outer low resolution portion of the image, then yes this is a reported issue. It is more apparent in some modules such as the F-16 (for me) and even sometimes more visible on the left side than the right side. Unfortunately, this is a problem related to DCS, not OXRTK or QVFR.
  17. +1 QVFR is providing even more performance than OXRTK's FFR. Given that VR is demanding so much, this tool should be part of the baseline!
  18. I would like to share my optimization journey for my 8KX. Although not able to use DFR, FFR works quite well with this HMD. I have been using OXRTK FFR and was getting about 1.5ms shredded from my average GPU frametime consistently. First time I tried QVFR, I did not get such a great result with default settings and never thought about playing with settings. I revisited using QVFR a couple of days ago and got incredible results of over 2.5ms improvement with an even better image quality. I have tweeked settings as follow: For the HMD smoothen_focus_view_edges=0.2 sharpen_focus_view=0.8 For DCS turbo_mode=0 peripheral_multiplier=0.4 focus_multiplier=1.4 horizontal_focus_section=0.35 vertical_focus_section=0.45 Horizontal focus may seem small but with the 8KX wide FOV (normal at 140 deg.), I barely notice the blur on the sides and get tremendous performance uplift. Image has never been so clear and crisp and I believe that the 8KX is still not at the limit of what it can do. I use DLSS balanced and the result is amazing. Still some issues with MFDs but overall excellent. Thanks @mbucchia!!
  19. Had awfull stutters and even crashes until I found out that my overclocking software was the cause (intel Xtreme on auto-OC). If you use such OC application, try to suspend/remove and see if it is the cause.
  20. I see similar results when comparing Caucasus and Persian Gulf. DLSS seems to provide a bigger performance boost on busy maps such as flying over Dubai in the Gulf map but also with increased smearing. Flying over Caucasus with DLSS provides very limited performance gain in contrast, but also much less smearing.
  21. I can speak to this coming from a Pimax 5kS up to the 8kX. The increased resolution brings down shimmering to a tolerable level on the 8kX with less impact than using MSAA, at least that was the case for DCS 2.8 and previous. There is still a long ways to go to get to a point where resolution is enough to counter shimmering, which I guess would be around 60 to 70 PPD. Nervetheless, image quality is very personnal. I find that using DLSS is an acceptable compromise to trade some sharpness for an increased performance and almost no shimmering on busy maps.
  22. I have been experiencing major stutters and the sim crashing as soon as I would try to engage DLSS / DLAA / TAA after a few seconds. I tried various combination of PimaxXR/Pimax Client / Quad views on/off etc... Sometimes, the stutters would go away butg after a few minutes woudl intesify. Until I started to stop all overclocking and found out that the Intel Extreme Tuning Utility was the culprit. It was set to automatic OC and it does not play well with DCS 2.9. I have not checked if the OC is set to specific values it would work, but for sure when in auto OC, it does not. Now I am experiencing the most fluid and smooth siming ever. DLSS is a bit blurry but so much smooth that it is worth the compromize for me.
  23. You can also reduce DCS setting gamma to 1.3 and boost your HMD backlit or brightness or both (if applicable). Using also the sunglasses in OXRTK will reduce haze a bit.
  24. @Sr. This looks like a corrupted config file in your "Saved Games\DCS" folder.
  25. The Crystal has two tracking options, internal or lighthouse. Controllers are not required in DCS.
×
×
  • Create New...