Jump to content

MHAce75

Members
  • Posts

    34
  • Joined

  • Last visited

About MHAce75

  • Birthday 10/10/1975

Personal Information

  • Flight Simulators
    DCS, MS Flight Simulator
  • Location
    Germany
  • Interests
    Travel, scuba diving, golf

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i meant from not using any preset (and staying on stock DLSS dll) to J or K... before doing any of this, I was CPU bound, now I am GPU bound by a great deal. I am not complaining, smoothness is still there, I was just wondering whether this is expected behavior BTW, does anybody of you dabble with VR pre-rendered frames in NVIDIA settings (e.g. 1, or 2?)
  2. plenty on DCS official site under "download/user files"
  3. is it expected that with swapping to DLAA 4 and choosing Preset J situation switches from CPU bound to GPU bound (by a great deal...)?... no super discernable performance degradation but neither huge visual improvements, but like to work with the latest stuff always.
  4. with a 4090 i am mostly CPU bound, i9-11900KF a bit dated already, sadly.
  5. how? going offline, i only see the frogfoot and unarmed Mustang variant... user-made/free-mods perhaps... Or am I missing something?
  6. The thread doesn't seem to be in the right section, as this section deals with VR issues. Staying in online mode, a reboot and restarting DCS should fix the issue, pending you have a working internet connection. Otherwise, try a slow repair with DCS Updater Utility. DCS offline play is limited to 2 planes that come with the initial installation.
  7. Interesting finding. I set OXRTK to safe mode, and after I installed Meta-Foveated I see the OXRTK in both eyes.
  8. DFR = meta-foveated from mbucchia?
  9. Yes that's why I asked. I try to have the least SS beyond Oculus settings as possible (such as in OTT etc). My primary purpose was to check whether people are rather using 72hz or 90hz in Oculus desktop settings and I got my answers. Thanks
  10. Ok. Maybe my bad, 10000 miles away from home ... so the max value for 72hz is 1.3 in Oculus desktop app? Then I stand corrected . Thanks
  11. Ok. Maybe I am thinking about something else. I only use Oculus desktop app (at 72hz 1.7, or at 90hz 1.5 (I may have reversed the values I am not near my PC these days) and started to leave OTT SS default. I actually do not know, what "in Meta" means :-)). I assumed you meant the Oculus desktop app, which at 72hz allows values higher than 1.3, or am I mistaken? I mean this 90hz max 1.5 72hz I think max 1.7 (I think) (Yes it shows Quest 2, I grabbed from the internet to show what I mean. The menu looks the same in Oculus desktop app for QP)
  12. Thanks I will try it out this weekend! One question back, you run 1.3 in Meta and 1.15 in OTT = 1.45. why not just run 1.5 in Meta and OTT default?
  13. Currently abroad can't test latest updates and meta-foveated until Saturday, so I am doing some pre-thinking. Rig with 11900kf, 5.1Ghz, 4090, 32 RAM. What has plagued me since the beginning of time, nevermind 72, 80, 90hz, that it is for me unplayable without AWS forced 45 + Turbo Mode, but then AWS forced introduces heavy ghosting, which is especially annoying when dogfighting. What are my best chances to remove ghosting? Going to 72hz (1.5), AWS off, if meta-foveating works for me, or staying at 90hz (1.7), AWS off, if meta-foveating works, and dialing down DCS graphics settings? 90hz looks and feels better, but is it too taxing for my CPU?
  14. Yes. If introduced heavy audio stuttering and more motion interruption here too. For audio I went back to other BT headset to alleviate the audio issues
×
×
  • Create New...