Jump to content

jurinko

Members
  • Posts

    330
  • Joined

  • Last visited

Everything posted by jurinko

  1. Stsrt dcs from meta enviro and then confirm the launcher which appeared on monitor screen with mouse click.
  2. Here it looks like this: you need the nvpi 2423 and select it here.
  3. In the newest NVPI it looks like <CustomSettingValue> <UserfriendlyName>Preset K (v310+)</UserfriendlyName> <HexValue>0x0000000B</HexValue> but the best option is to download it with nvpi amd select it there. https://github.com/xHybred/NvidiaProfileInspectorRevamped/releases/tag/v3.0
  4. If i want avoid dlss swapper and do it manually, i need 1) the newest dlls and 2) do i need to alter the customnames.xml file to introduce the k preset? Edit, the newest nvpi is necessary. Preset K looks awesome and runs better than Preset J for me. DCS never looked and ran better.
  5. In the main menu under chapter 5. Common and select the middle of three DLSS options. To see J, you need to have this file in the same folder as inspector.exe. New driver works great. I tried preset F and ouch, everything was crawling like worms. Great improvement. CustomSettingNames.xml
  6. I got nvidiaprofileinspector crashing, this version is compatible: https://github.com/Orbmu2k/nvidiaProfileInspector/releases/tag/2.4.0.8
  7. Anyone tried the newest 572.16?
  8. Openxr toolkit is inevitable for many for switching turbo mode on to get smoooth performance. This can be alternatively done by the foveated rendering software.
  9. Im lucky I see none. Only if ASW kickes in, is the nearby passing airplane doubled. And new nvidia driver is due this week, promised to supply dlss 4 goodies without performance hit.
  10. I have finally reached VR nirvana with my Quest 3, cable link. 1. Use Meta quest link as openxr runtime and in openxr toolkit set Turbo mode on. Without Turbo it stutters. I ran dcs with SteamVR runtime before, it was acceptable but with PD of 1.2 max and ASW did not worked. With Meta/Turbo i can use 1.4 (Meta resolution 1.0/72Hz). 2. I had been using H265 codec at 150 bitrate from some reason (above 200 it gave me fps 1). With H264 and bitrate 500, the feeling is like ramping PD from 1.0 to 1.3. 3. New DLSS4/profile J further improved the visual quality. I put PD back one notch to 1.3 as I pay for it, but it looks good as never before. 4. Switch shadows off in dcs settings, it is broken and consumes plenty of power for nothing.
  11. Set shadows off. Are you using steamvr or openxr as runtime? When I had g2, my best performance was setting the max fps to 93 in the openxr toolkit and running it at native 90hz with steamvr. Openxr had poor quality. In dcs, set fps to 300 or whatever.
  12. New DLSS got rid of residual shimmering in F1 pit. Letters and gauges are much better visible. It is more taxing, but going back one step in PD fixed it.
  13. I put 2x mid springs paired with no center/linear force cams and added 2x soft springs no center/ progressive force cams. It feels just right with the extension. Two strongers springs were too much.
  14. I would like Caucasus made from scratch with Iraq map technology.
  15. You can set the frequency in Quest 3 to 72Hz and up the resolution (60 Hz with G2 is unbearable and 90Hz is demanding). I have 5600x, 4080, 64GB RAM and I am very satisfied going from G2 to Q3. I have most of the settings on high(est), DLSS Quality on and PD 1.5. For me, the most needed trick for totally smooth performance is to use Meta OpenXR runtime and Turbo ON in OpenXR Toolkit.
  16. I have just reached that meta - finding out one has to use Meta quest link as OpenXR runtime and switch the turbo in OpenXR tools on. I had been using SteamVR as OpenXR runtime since Meta Quest Link alone stutters, also reprojection with SteamVR looked better than with Meta. With SteamVR, I used PD 1.2 with DLSS to have smooth performance (72 Hz all the time) above Patagonia mountains and forests. With Meta link runtime+Turbo on, I can have either PD 1.3 with DLAA, or PD 1.5 with DLSS. Clouds, visibility on max, forest settings 80%, ground shadows off. Specs: 5800x, 4080, 64GB, latest Nvidia driver.
  17. Can we get hand adjusted famous peaks in the Falklands, like Two Sisters or Mount Longdon? Just to elevate few altitude points (I did maps for other sims so it is doable). Second, the rocks on Falkland peaks are now of brownish color and round shape, but in reality they are whiteish as the rocks on textures and sharp shape. Low polygon models would be more realistic. Thanks.
  18. I created maps for old IL-2 Sturmovik and for Condor gliding sim. The SRTM elevation data publicly available are quite good, but here in Iraq they are higher resolution. Combined with the texture and various bushes one gets a real feeling of altitude. Now excuse me, as I am off in F-5E quick start again
  19. Northern mountains are awesome. I need to switch the reprojection, but worth it. Finally a map with realistic terrain (South Atlantic is close behind). What prevented other maps to have such sharp cliffs and mountain ridges?
  20. One thing is sure, that SSD manufacturers will have good 2025.
  21. There is a part of falklands which has poor fps: looking west from port stanley, but it is not the stanley as when flying above in eastern direction, it is fine. The poor fps area extends to the mt longdon or those rocky mountains, some 10 km east of stanley, and then everything is ok. But if I turn back towards stanley from there, it starts again until i reach stanley. I thought those rocks on the mountain crests are the culprit, but they are everywhere and do not make issues further.
  22. Zdravey Andre, sorry for off topic but when will Simshaker be updated for Condor 3? Thanks!
  23. Quest 3 with steamvr as openxr runtime on cable. Much better performance and visuals than meta openxr runtime.
×
×
  • Create New...