Granny

I'm not using steam and tried a couple of the other suggestions but didn't have any luck. (I'm probably doing something wrong). I'm thinking of giving VD a try but I notice the requirements say you need an ethernet connection. Where my system is located I can't run an ethernet cable to my router without some painful construction projects. I do have pretty good wifi signal and good speed though. Is it even possible to use VD over wifi, and if it is would DCS play well that way?

Just discover I have this problem now, had updates on Automatic and now have V63 on both PC and Headset. How did you revert to V62?

Thanks again everyone for your help, I think I have found my happy place. Its not perfect but I'm in a much better, more playable state than I was a couple weeks ago. For anyone interested, the final changes I made was to go with 80Hz refresh rate on the Q2, then on Oculus Debug Tool reduced my field of view to 0.8. This was an effort to preserved some FPS for the next steps. I increased distortion curvature to High, to focus resolution towards the center. Then I started inching PD back up, but in the ODT this time, rather than in game. I don't now why but doing this in ODT seemed to be less of an FPS hit than using the in game slider. 1.3PD is my wall. With those setting I am getting perfectly smooth 80fps, and readable instruments. Not crystal clear, but readable. Still some ghosting and a bit of aliasing but nothing I can't live with. Considering the limitations of my system I am pretty happy. Thanks again. Granny out!

Thanks all for your suggestions and putting up with my lack of knowledge on this stuff. I was caught in this weird loop where I believe more FPS was the answer, and since FPS seem to always be half my refresh rate, I need to increase refresh rate, which drove me to try and run at 120hz just to get 60FPS. I didn't take account the demand my high PD setting had. As soon as I dropped my PD to 1.2, I got all my FPS back, and dropping the refresh rate to 90hz made it smooth, turbo mode made it all pretty stable as well. I'm getting 80 to 90 very playable FPS now, so that seems to be the sweet spot form my set up. So here's my next question. I got to 1.5PD by trying to find a setting the would make my cockpit instruments and such clear and readable. I have cockpit res at 1040, textures high, and sharpness at 0.9. But at 1.2PD all the text is pretty blurry, anything in my MFDs is unreadable without zooming. I suspect the problem is TAA but without TAA the aliasing is unbearable (I really hate aliasing). I had hoped Quadview would help, but I tried that and it gave me a few more FPS but didn't clear up the cockpit display. Is there anything else I can do to sharpen this up or is it something I'm going to have to live with until I can upgrade?

Bear with me, I am an amateur with a no budget for an upgrade. I have to live with what I have so I'm trying o max perform my system and I know (becasue I've seen) it can do better than it is right now. I thought I was onto something new when I discovered the overhead capacity stats yesterday, hence the new thread. Here are my current points of confusion: 1) You're saying what I'm seeing is Motion Reprojection caused by ASW. That makes sense except I've been using OpenXR Took Kit's Turbo Mode for a long time, which gives me a big red warning that it disables ASW. So, is Turbo also a form of motion reprojection or is something else going on? 2) Oculus display tools shows I have in the neighborhood of 97% overhead capacity even before my FPS is cut in half, and it stays there after the cut. In other games I see a cut in capacity but maintain FPS. If I have so much overhead, why is the FPS getting cut? It looks to me like my system has more resources and performance available but either Oculus or DCS just won't take advantage of it. Or do I just completely misunderstand what "overhead capacity" means?

120Hz is experimental but I do get 60FPS and the best overall results when its stable but becomes unstable sometimes in busy scenarios. 90hz is my sweet spot most of the time for multiplayer. 80hzworks but isn't as smooth. 72 is just annoying. I think its weird that I'm seeing the drop in while I'm just looking at loading screens and menus too.

I don't know how I never noticed this before but I found myself in cold FC3 jet yesterday, and feeling lazy I hit Lwin-Home to get the autostart sequence rolling. This works on my F-16 like a champ, but nothing happened on the FC3 A10-A Then I opened the Controls menu and did a search but could not find autostart. Same for the Mig-29, I assume same for all FC3 aircraft. Am I missing it or is there not an autostart feature in FC3?

I've been troubleshooting some issue in DCS on my Quest 2 and I think I may be on to something, but I don't know what to do about it. I have notice that the DCS FPS counter shows I am getting FPS equal to half of the refresh rate of the Quest 2 headset. I.e if set my Q2 at 120hz refresh rate I get a solid 60FPS on the counter. I have heard that's the result of the headset effectively being 2 displays, one for each eye, thus 120/2 = 60. I think that information is incorrect. I recently discovered the Oculus Debug Tool and its performance Hud did a little investigating. This is what I see, before I load DCS, FPS is green and maxed out, overhead is green and near 100%, very few dropped frames. As soon as the DCS load screen pops up (not even at the menu yet) FPS instantly drops by half, and the dropped frame counter begins to sky rocker, yet my overhead remains green and near 100%. It stays the way until I close DCS. I tried this same experiment on Star Wars Squadrons in VR and this did not happen. I maintained a smooth and steady 120FPS in game play, but overhead dropped to the low 60%s. Dropped frames were very minimal. This is what I would expect to see. So my problem seems to be a DCS issue specific issue. I saw a youtuber that had exactly this same problem on another game. On his system it seemed to be a bug connected with his audio Simply changing his audio output from the Q2 headset, to his monitor speakers fixed the issue instantly. I tried the same but it had no effect. If I have nearly 100% overhead available, i would think I should be able to max out the FPS. I'm pretty sure if I can fix this issue it will fix the other VR anomalies I'm having. Anyone have a clue what's happening??

Thanks, gave it a try. Moving the Oculus Resolution slider all the way to the right gives 5408x2252. I tried that with DCS PD at 1.0. The results were mixed. In cockpit detail improved a bit, text that was blurry before was easier to read. However my FPS dropped from 60 to 50 and the "vibrating" around the edges became full on stutter and all aircraft maneuvers were jerky. With my settings I was getting pretty smooth maneuvering even at 45FPS. I did not use quad view, I have tried it before and found it looks basically like setting distortion curvature to high and introduced as many issues as it fixed. I did change my distortion curvature to high, which made me feel like I needed to clean the lens and didn't really improve performance enough to help the stutter issue. It was a good idea, just didn't work in my situation. Thanks.

My understanding is you will always be "bound" by one component or another, either your CPU or GPU. Something has to be the limfac, there is no such thing as an unbound system. I have a Ryzen 5 5500, Radeon RT 6700 XT, 32GB DDR4 RAM, and 2TD WD Black NVMe drive. I do VR with a quest 2. I have found that FPS in DCS VR seems to lock at 1/2 the refresh rate in my headset. Not sure why. Q2 has refresh options of 72, 80, 90, and 120hz. My FPS in DCS with headset on will be CPU bound at 36, 40, 90, and 60 respectively. (Note, you have to go into the headset, setting, and enable 120hz there to get DCS above 45FPS). No idea why its bound like this. My CPU runs around 45-50% usage when I'm playing so it has plenty of headroom. This doesn't happen in 2D. Its not usual for me to see 100fps on my HD extra wide monitor even with pretty high settings. There are other issues in DCS VR that are frustrating me too, but those are in another thread.

I got the 2152 from some youtube video on optimizing your settings. I don't know what the magic is behind it, truth be told I really don't understand the numbers, but it works. I tried resetting to 3440, and also used "0" for default. Both made everything worse. Not only did the "vibration" get worse, but got flickering and stuttering and frame drops, and DCS even crashed. Returned to 2152 and back to smooth operations. No idea what that means, I would think if 3440 is native, that would be the ideal settings. SInce DCS 2.9 came out I've been using FSR, which I think is an AMD version of upscaling. It helps a lot reducing aliasing with out too much performance hit. Maybe I have an ODT/FSR conflict??

Yes I am using MT. So, good news. I found in the Q2 headset itself there is an experimental setting that allows 120hz refresh rate for games that ask for it. I turned this on and boom, FPS jumped up from45 to 60FPS. The vibrating is still there but its much less distracting than before. FPS still seem to be stuck at 1/2 the refresh rate no matter what. It rarely goes over 60. 60FPS was stable inflight, but a little glitchy in graphically intense environments (Multiplayer, Marianas Map, on the ground with other players around). I used ODT to shrink the FOV to 0.8, which helped that quite a bit. Still CPU bound mostly, once in a while I will see it flicker over to GPU bound in those graphically intense environments. I see this happen sometime when I try to max out the in-game graphic settings as well. Anyway, I have finally seen some improvement, but still working on more. As for the TAA ghosting, I think you're right, I will just have to live with that.

Thanks. Sounds like you see similar things as I do. So I've been playing around with Q2s refresh rate and monitoring FPS in the headset with the DTS overlay, and the OpenXR overlay. At 72, 80, and 90Hz my FPS is exactly half the refresh rate (36, 40, 45FPS) Its tight and stable. That's with Oculus's default resolution. For some reason at 120hz, it stays lock at 45fps, which I can't figure out. I have tried 120hz in the past and I got up to 60fps, but it was unstable. Today its locked at 45, and I don't have my FPS capped (I did increase the Max FPS all the way to max on the slider). 72Hz/36FPS was by far the worst, the others were all about the same. In all my runs the DTS overlays says I'm CPU bound "render thread" and OpenXR overlay reported "rdr CPU" in the 7-9ms range, "app GPU" 16.5-19.5,s range, and VRAM usage 6-9GB. What all that means I have no idea. Kinda thought 45fps in the headset was respectable but maybe not?

Thanks, tried. It reduced both issues a bit, but didn't make them go away. It also introduced some pretty gross aliasing, shimmery everywhere like flying through water. I turned on TAA after that and that helped the aliasing but pretty much undid the improvement made by turning off FSR. Then I swapped TAA for MSAA which just made everything worse and I got some actual stuttering.

Hello I am continuing to have two issues in DCS 2.9, in VR on my Quest 2. First, In straight and level flight everything is fine. When executing a rolling maneuver the scene has "vibration". I don't think its stutter, because the actual roll maneuver is smooth and the scene at the aircraft's 12 O'clock is smooth. The vibration is noticeable as you move outward from the nose of the airplane and is worst around the periphery. It is not associated with head movement, its fixed around the aircraft. I do not notice any tearing. Second, other aircraft in the scene ghost and smear, IOW the corners and edges of the model leave a visual trail behind them when they move fore or aft in the scene. When maneuvering laterally a ghost image will often appear (i/e an F-16 with its single vertical stab, will appear to have 2 vertical stabs). I have noticed that this problem reduces some if I get rid of upscaling and sharpening, but then I get significant aliasing in the middle distance. These issues do not occur in 2D on my monitor (LG HD WQHD 3440x1440) even with fairly high graphic settings. The issues do not occur in my Quest 2 in any other application or game. I have also reached out to Oculus and did significant troubleshooting with them, nothing is having an effect. It is not my GPU, I have used two different GPUs, (GTX 1080TI and RX 6700 RT) and get the same results. I have reload the drivers for Oculus and for my GPUs. I have overclocked and removed the overclocking. (overclocking the RX6700RT did help with performance some). It is not my USB cable, its transmitting at 2.6Gbps. I have removed all the unofficial mods, and emptied the Metashader folder and fxo folder and run DCS repair utility several times. I have adjusted setting for days, increasing Pixel Density does seem to help somewhat (seems to move the vibration farther outward, decreases the amplitude of the shaking) but anything above 1.5-1.6PD causes performance issues. The settings I have now seem to work best but it is still far from ideal. Also, I have Turbo mode ON in OpenZR tool kit. It does seem to help performance. Any help is appreciated. I have attached logs and images of my settings for your review. System Specs are below (OS is Windows 11) System Type x64-based PC System SKU SKU Processor AMD Ryzen 5 5500, 3600 Mhz, 6 Core(s), 12 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 3002, 2/23/2023 SMBIOS Version 3.3 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer ASUSTeK COMPUTER INC. BaseBoard Product TUF GAMING B550M-PLUS WIFI II BaseBoard Version Rev X.0x Platform Role Desktop Secure Boot State Off PCR7 Configuration Elevation Required to View Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume4 Locale United States Hardware Abstraction Layer Version = "10.0.22621.2506" User Name AlsGamingPC\allan Time Zone Central Standard Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.8 GB Available Physical Memory 25.8 GB Total Virtual Memory 45.3 GB Available Virtual Memory 35.9 GB Page File Space 13.5 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Windows Defender Application Control policy Enforced Windows Defender Application Control user mode policy Off Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware No Hyper-V - Data Execution Protection Yes dcs.log