Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Spetz

  1. I got the forced Quest 2 ver38 update, and now my link cable/airlink ability is completely gone.. I select the option to use link cable (or airlink, doesn't matter), I get the black screen and three white dots as it used to to while loading my PC's desktop, then it dumps me back into home. Nothing I've done has fixed this.. Reinstall Oculus home, multiple restarts, that crappy automated Oculus help chat, swapped cables.. Nothing.. So obviously no ability to get into and do any flying with DCS as I can't get to virtual desktop anymore. I'm not running anything through steam. Anyone else have this issue? Ran absolutely perfect the day before the update. pissing me off... *** edit. Fixed. reinstalled PC app again (three times), but then lost audio for the headset. Used the OculusCodec.exe or something like that in the diagnosis folder and sorted that out. Never had an issue with their updates before, weird..
  2. It’s happens to me too. On Syria map, no mods, in VR, start in the Hornet with 45 FPS, switch slot to Viper, FPS down to 24ish, then switch to anything else, FPS tanks to about 8. Sometimes exiting that mission and loading up something in the Caucasus brings it back, but more often than not, have to fully exit the game and get back in.
  3. Thanks, but as soon as I change any field, I get field errors. using it with MS Excel. Changed the temp to 25 in this instance..
  4. OK, so finally figured out the combination to defeat the night issues since last OB update, this mod and Kegetys. Install went fine, can open using LSHFT+F7, cycle all the menus and save/close.. But I don't see any change in game .. Been trying out using the AV-8B and F18 specifically. The AV-8B NVG are now the single monocle, so I guess that is a change, but I can't adjust size, convergence or anything, and no other menu seems to affect anything in game.. No other effects are seen either when adjusting any of the menu's. All options in settings are as required per install instructions, and flying VR exclusively. Using Kegetys Clear water and your newest file. Am I missing something?
  5. I'm getting errors now too with the hotfix on the new build. Install was de-modded, cleaned, slow repaired and now I'm getting this. Loads just fine without VR Shaders installed via OvGME. Really too bad as this mod was what brought me back into flying after a couple year absence..
  6. Sorry, should have mentioned. Yes, I have done that already. GPU drivers are 471.11, installed via DDU in safe mode. I’m going to remove the Hind from my products and see if it changes anything with Syria. EDIT** So brain farted.. I didn't rename/delete my saved games folder as one of the potential fixes. Did that and added my Input folder back in and everything is buttery smooth again. I reinstalled the Hind as well. Still a few instances of tearing with the Hind, but for the most part I would say 95% better. I'll chalk that up to a WIP module. Zero issues with any other aircraft. So what ever was the issue, seems to have been dealt with. Thanks for your initial investigations.
  7. Regardless of how the above is set up (had some issues swapping SSD's over to new computer), this had never affected DCS or any other games/programs before the Cyprus update or Hind release.
  8. Here you go.. AllocatedBaseSize=32768 CurrentUsage=0 Description=C:\pagefile.sys InstallDate=20210331221535.490123-240 Name=C:\pagefile.sys PeakUsage=1 Status= TempPageFile=FALSE My W10 is on C (SSD), D is random programs (HDD), E is other games (SSD), and F is my dedicated DCS drive..
  9. Just going to report this lol.. Went to land on a cliff with a Gazelle and right through. Then fly through it in a Hornet to verify.. Kept on going.
  10. Carried from another thread. Since updating (now 2.7.3) Syria has been almost unplayable with the Hind with heavy stuttering and tearing. With other aircraft (tried all the modules I own) it is very much reduced, but still happens every so often. With other maps, everything is perfect with a solid 36 FPS per eye with my Quest 2 set at 72Hz (2070 Super) with any aircraft, including the Hind. I've done everything as suggested in other threads (pagefile, FXO/metashaders2, xBox DVR etc..) I was having sound stutters too, but did a factory reset on my headset and that solved those, but unfortunately not the tearing. I had zero issues before the last update (Cyprus release) and 2.7.3 today. Running resource manager shows nothing that I can see out of the ordinary.. Any ideas? Syria.miz dcs.log DxDiag.txt
  11. I checked out my DCS log and had lots of errors regarding the shader folder folder from what I can assume is remnants from the VR Shader mod. Deleted the shaders folder, FXO and metashaders2, then rebuilt the install. Gonna fire up and see how things work now before posting logs.
  12. I’m experiencing it too.. I’ll attach logs files tomorrow after work to this post.
  13. Oops.. Just realized this is in the wrong section.. Maybe a Mod can move it..? So retested the cable. 2.5 Ghz.. Nothing out of the ordinary. I think I've narrowed it down to a combination of the Hind and the Syria map. Hind on any map but Syria, works fine, nice and smooth. Any A/C on Syria and the tearing starts, but much much less that with the hind. So I deleted Syria, cleaned DCS, reinstalled Syria and repaired DCS. Much less tearing, but still there. Watched my memory use as well.. I have 32Gb and with both the Hind and Syria up and running, 15Gb of memory used. Syria and other A/C, between 9 an 12 Gb. Any other map, less than 8Gb with any A/C combination. Redid my pagefile as well, for some reason it was set at 4000mb.. Regardless, I guess I'll just wait until the Hind is more optimized before I commit to it unless someone else has ideas..
  14. I'm getting massive screen tearing all of a sudden with DCS, current Beta. I recently moved, and once settled, fired up DCS, updated, and got the Hind on free trial. For the update, I used DCS with a full repair first, then the update to current version. Then I updated my 2070 Super to nVidia 471.11 as people were saying it was much smoother. Did this using the proper safe-mode DDU way. Clean profile on driver install, nothing set in nVidia control panel. Also tried with two previous version drivers. Prior to this I was using 469.77 (I believe). IT ran great for like 3 minutes, super smooth and then it seemed to just $hit the bed.. Quest 2 is fully updated, using link cable, 72Hz at 1.0 resolution. I have Oculus Tray Tool set up as well, but issue doesn't change if it's running or not. Zero mods, Link cable swapped with spare. Deleted FXO and the other folder (forgot name). In game setting are rather mild. MSAA x 2 (no issue before) AF x 4. So basically I am for some reason I am getting massive screen tearing when I rotate my head. Any map, any aircraft. This never happened before and previously with my set up (and old GPU), I was getting a constant 32-36 FPS with OTT setting (SS at 1.4 BTW). I've got 32 Gb ram, and have never seen DCS use over 12Gb (building new VR Shaders), and typically maxes at 8Gb on Syria map. Is anyone else getting this or have any suggestions to try?
  15. Spetz


    Weird.. installed 471.11 via a full DDU removal, restart and then install, took the Hind out on Cyprus, and while it was much smoother overall, I’m getting what I can only describe as a combination between screen tearing and projecting a 2nd frame when move my head fast in VR. Like a extremely fast flash of another frame when turning my head. Very minor stuttering at that point. I have only Max Performance set on nVidia control panel. No other settings have changed since last GPU update. No change between having OTT running or not. ideas? Edit** redid the drivers a few times (DDU in safe mode), deleted FXO and metashaders2. Ran with VR Shaders mod on and off.. nothing changed. Pretty bad screen tearing. Went back to 466.79 (hotfix driver) and tearing gone. Must be something with my 2070 Super and that driver. They just don’t like each other.. weird..
  16. FYI, one of the latest nVidia GPU drivers was crap. 466.51 maybe? They actually released a hot fix for it. I installed the bad one, had massive screen tearing, crap performance etc.. used DDU in safe mode, removed and redid the new hotfix version and sorted it all out. I believe 466.55 is the new, good one.
  17. Same. no TacView though.. Joining a server with about a 16 ping rate, starts out fine (VR), with my usual 45+ FPS, then begins to progressively go down after about 20 minutes. I usually exit when it gets to about 12 FPS and completely unflyable.
  18. Ha! Just jumped back in the Harrier after flying the Hornet for ages, relearning the first module I truly enjoyed getting in to.. Burst out laughing after Training Mission 02 (start Up), after you complete the lesson but don't quit... Never stayed that long before in cockpit afterwards.. "...study sim.." Thanks for the laugh!
  19. Thanks for the heads up. Just checked my beta tab and that air link option isn't there yet, so I guess it hasn't been released yet. I think I'll wait for that instead of dropping $$ on the app.. Cheers
  20. Mind letting us know how you got it to work wirelessly? Any bandwidth lagging at all? I love the Quest 2, but that wire...jeebus...
  21. 84Gb...I think you're right. I likely read it wrong That does seem big eh?
  22. Just noticed it too.. had my Quest 2 at 1.0 in graphics settings in device setup since the update but had to bump it up to 1.4 just to get some clarity back again, costing a few FPS.
  • Create New...