Shrubbo

Tried it for a while, smooth with lots of graphics but the artifacts where way to harsh for me in a lot of situations. It is however perfect in ATS so thanks for that. Max everything at 2.0... nice. I never would have tried without this thread. Thanks for the offer as well but at this point it is doubtful as I have a bit of a medical condition that can be, lets say problematic, to be nice haha.

FPS is always FPS and your eyes are seeing 72fps, not 24 because ASW is doing the work. But still you are right, you can get smooth game play from that crappy FPS so thanks for the learning experience. I just went and tested that on my rig and the 30Hz in OTT seems to actually mean around 33%. Something I did not think the rift S could work with. Also if I use the Oculus Hotkeys they actually equate to Auto, half, half locked with no ASW and off. There is no 1/3 option so if I hit those hotkeys in game I will wipe out the 33% OTT can do and it goes back to 50% which is the lowest those hotkeys will do. It also appears I need to restart the game to get back to the "30hz" or the real value 33% and that on mine means that if DCS can spit out 27FPS solid I will get a nice smooth game play at an apparent 80fps in my HMD. So thanks for the heads up. A lot of artifacts (What I thought your were calling ghosts) but it is smooth as with a lot more stuff dialed up so maybe I can get used to it. All the screwing around I did trying to help you (Though I clearly didn't understand) did show me an 80FPS flyby on my rig was something I wish it could pull at these settings all the time. Glorious.

I am totally at a loss at understanding what you are seeing but FPS is FPS and ASW needs a specific minimum and you are honestly the first person I have ever seen that thinks 24fps is good for VR. I know find 40fps barely tolerable with ASW. But hey who cares as long as you are happy with it and am glad you have found something that suits you.

Myself and the better half's TM Warthog sticks had a bit a movement in the actual handles. Turns out I found a real quick 1 dollar fix. A hose clamp and now they are both rock solid and it is only a PITA if I am taking the handle off regularly... which we are not.

I am also curious to know what the issue was and how you fixed it.

Went to win 11 on two rigs and 2 VR sets. No problems at all with the Rift S. BTW I also prefer 11 over 10 by a lot now for various reasons. YMMV. The Quest 2 was unplayable (ASW did not work) until I found the workaround for it on a youtube channel or page or something. What the hell it works. Apparently the bug has been known about since at least October. The Workaround. Open Oculus Tray Tool. Usually "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe" Click the service drop down and select "Toggle Console Window Viability" Do not close or minimize the console window, just let it keep on scrolling info. Run the game over the top of it. Do the reverse when finished if you want to get rid of the window. I do not know why, but it works.

FYI I through on of these in the misses PC and have had no issues with the quest 2. https://www.ebay.com.au/itm/124974649593

I hope so, that sucks. This has actually been a learning experience for me as well. I am starting to lean more toward a greater FPS speed then lower and really nice graphics with all the playing around I have done once I got into this thread. so thanks to you guys for bringing it up. There is something to be said for an 80fps fly bye with no ASW running. The cockpit FPS limit is crazy with your rig so something is definitely wrong. I found this on the cockpit thing though. May be of help. Anyway hope you get it sorted mate.

I went through that list of links I posted for you above and did some of the optimization mods myself, played with setting etc as suggest and I got a boost which I am pretty happy with but for the hell of it I checked and I can tell you that I am pretty sure I know what your problem is. It is your PD. I believe you are asking too much. Way to much. If anyone knows how to get a good FPS and have it look half decent with that PD please let me know how. Like I said I can't see sigs on the browser. Some extension is blocking it so I just updated mine to what I am running. It is a little more powerful then yours but I am running the rift S so I am not needing to push the pixels you have to. With that in mind these are roughly the FPS numbers I was getting in my test map with my preferred graphics settings. PD 2.5 FPS mid 20's. ASW on or off, didn't matter. Unplayable. PD 2.0 Low to mid 30's. ASW on or off didn't matter as it needs to min of 40 fps with my Rift S. Crappy. Horrible. PD 1.5 Could pull 40 up to 60's but would sometimes duck below 40. ASW helped smooth things out a bit but it would stutter sometimes because of the sub 40's. Not working for me. PD 1.2 Up to 80fps and ducked to the 60's with ASW off. Some jitters as the FPS was not stable. Sure was pretty on the fly byes though when it was. I could lock it at 40fps with no ASW (CTRL +num2) and it would stay there rock stable. Still at 40 fps I can see those frames. No ghosting tho. Acceptable sort of for me. I could lock it to 40fps with ASW on (CTRL+Num3) and it was butter smooth. Some ghosting on the fly byes but this is the sweet spot for me. There is no way I can think of to get good FPS at the PD's you are running at, with a Rift S and my rig and my preferred graphics settings which suit me. If I run the default low setting in DCS and a PD of 2.0 I can get a stable 80fps on my test map but it looks horrible. Clear, but I can clearly see the horrible. On another test map I have that has a lot of combat units doing their thing it can jump from 80 to high 30's so I get the worst of both haha. TL/DR. I think your PD is way to high. I suggest yo try DCS on the default low settings with that PD and see what you get. If you get great FPS then that is for sure your problem and then you have to work out what you want to trade and see if you can find a balance you can be happy with. For reference this is my preferred setting ATM though I am sure that will change in the next 10 minutes. Having fun seeing what I can actually get out of it.

PD 2.00. My god man. Diminishing returns past 1.5 and I think I run mine at 1.2/ I think you are asking too much

This may or may not help but this guys had FPS in the 20's in multiplayer and seemed to have derived some benefit from links provided. So maybe worth a look?

If I didn't know you had windows 10 I would say I know your problem. That win 11 thing was doing my head in as well for an extended period. Anyway I hope you get it going mate, your rig should do much better. All the best.

It needs to actually be much faster to help stop you puking but more so for immersive gameplay. The Q2 default is 72fps which is the lowest I know of. They originally thought 90fps was bare minimum. The Q2 is going to run at 72fps anyway no matter what you throw at it but if you can't supply the FPS that is when things start to happen just as with a monitor on a 2d game. As far as DCS + Q2 goes at default anything under 72fps (default for q2) forces ASW to turn on to try and maintain that 72fps. So CTRL + Pause should show in your case a steady 36fps minimum for smooth game play. It should only jump between 2 numbers, 36 and 72, Best case 72. Outside of that it is struggling. The amount of ghosting depends on how much lower then 72 fps ASW has to deak with. If you then press L Ctrl + numpad 1 that will turn off ASW and you will see the FPS jumping around, no ghost but a crap experience. L Ctrl + numpad 4 turns it back on. If cntrl + pause shows anything under 36ps you will not get smooth a smooth fps. Under 36fps you will see no difference in FPS as ASW can't cope. If you can run 72 or higher it will stay at 72 unless you turn it off but it will be smooth as butter. The Q2 can go to 120hz but I think the game code has to call for that (?) and I would like to own the PC that could do that with DCS and look great at the same time. In VFGIP's example below he appears to be running at around 58fps, his GPU at 98% and reprojection at around 32%. I say appears as that seems to be running SteamVR instead of Oculus Vr software. The point being that there is no way you are going to be able to see a plane fly by at 90 degrees and those closing speeds even at 60fps. He doesn't appear to have what I now call ghosting but he sure doesn't have enough FPS to fill the gaps. I was going to say I can't understand how you could find 30fps acceptable but I just remembered a mate of mine has the same rig as me an runs his settings in DCS on high. No way we can maintain above 40fps (In combat or say Dubai) at those setting but he doesn't seem to notice and he is happy with that. For me it is unplayable. ghosting and jittering all over the place. Similar to trying to run DCS on a 4k monitor with a budget machine, it just isn't going to be smooth but hey you may be happy with it so more power to you if that works for you. It is also possible I have no idea of what I am talking about but I think I am in the ball park and just trying to help out so a merry Christmas to you all as well

Look up one post, I just edited it with everything I have atm. Or click this link to take you back....

No but I know your FPS should be way past what you have. I thought you has some old POS by what you are describing. Try using the monitors is in Oculus Debug Tool. Usually "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe" I attached an image to show you where they are if you are unfamiliar with it. You might be able to figure something out with it. EDIT: BTW I will go fire her rig up and see what I can see. Edit Edit: Ok I have done so. The following give her a solid 36FPS (Racked up to 72FPS by ASW) and without ASW running around 56FPS. Benchmark is loading up the instant action mission TF51D and the Hot Start mission at Caucasus. Also flying around gives a solid 36 as well so nice and smooth. Note not optimized for heavy combat. She just likes to fly around and I could do better if I spent more time on it.