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.

Well that is interesting. One of my extensions must bloc it as what I am writing this in there is no sig. I just opened this page in Chrome and I can see it now. I learn something new every day. Ok, your system looks good mate. My better half's machine is around that and it runs very nice with the Q2. I got an i9 9900k and a rtx2080ti + Rift S and I am envious of it. Something is absolutely wrong somewhere but I don't know anything else to suggest mate, sorry. That rig only got 30fps with a Rift S???

What are your specs out of curiosity? Are you running SteamVR with a Quest 2 or I am just unfamiliar with whatever you are using? I mention this as it says SteamVR SS is at 100% and Reprojection is at around 30%. If you are using SteamVR then there is half your problem I suspect but even if you are not and you are using something I don't know of to get those stats. "Reprojection" is sorta the same thing as ASW and is doing 30% of the work. Your average FPS is only around 60 so ASW is going to be needed but that tool you are using seems to indicate you are using SteamVR. .

BTW I just thought of something else. The Rift S just plugged into your PC and got the graphics signal straight from the card via a HDMI connection and powered through a seeperate USB connection. The Q2 software converts and compresses the image as I understand it and then send it to the actual Q2 hardware via WiFi or USB cable and then decompresses it and displays what you see. So unless I am wrong your hardware has that to deal with as well. What FPS are you actually pulling there? To me it looked like what I described above.

I am surprised mate as that FPS is absolutely horrible FPS for VR. Not trying to be a d*^k or anything but that is pretty much unacceptable FPS for 2d. For VR I don't see how you found it playable but each to their own. If that seems fine with you the screw what I say and enjoy it. Something to point out however is that if your Rift S only pulled 30fps the Quest 2 will really punish it. Rift S 1440 × 1280 px per eye or 2880x1280 for the panel. 80hz locked Quest 2 1832x1920 per eye or 3664x1920 for the panel, variable 72hz to 120hz. I suspect the rig you have pushing it all is being beaten to death by the Q2 and DCS is not known for being hardware friendly so to speak. Anyway bud, I hope you get it sorted.

I am not sure if "ghosting" is what I think it is but FPS in the 20's is not good for VR in any game, it is actually way below absolute minimum. On the quest 2 default the minimum stable rate (The FPS your PC must maintain) I is 36fps and ASW (Asynchronous Spacewarp) boosts that up to 72fps which is what the Quest 2 runs at default and as a minimum. ASW does a remarkable job but if I am right one of the downsides is "ghosting" which is being referred to in this thread. Sounds like it but I have never heard of it like that. It has always been "artifacts" in my head but ghosting seems to fit probably better. I can tell visually how much work ASW is doing by looking at the leading edge of my wing while stuff is speeding by, trees, houses etc. Say I have a nice stable 40 FPS indicated, I have Rift S on this system so it wants 80fps. It needs to pull 80fps but if it can't it locks it to 40fps to keep it smooth and takes and educated guess at what the next frame will be to get the Rift S display at 80fps nice and smoothly. If ASW is working I will then see a shimmer in front of the leading edge, how big a shimmer is an indicator of how much work ASW is doing. Another example I can think of is in a merge as the other plane goes by you sort of see two of them and the last is trees sort of doubling up/blurring when you turn in a chopper etc. Is this what you guys are calling ghosting? I suspect it is and this is how you get rid of it. Tune your rig and Quest 2 settings to pull a minimum of 72fps. Then no ghosting. That is probably not going to happen so this is what you can do to get the best you can. To minimize the ghosting tune your rig and Quest 2 to get as much as you can to get past 36fps. The more you get past that 36fps the less work ASW needs to do and the less ghosting you will get, below 36fps ASW just can't do it and you will get huge "ghosting" and judders etc. It is almost magic but not quite and in your case 36fps is the bottom line. FYI you can manually turn on and off ASW buy these hotkeys. ctrl+num1 disables it ctrl+num2 locks to 45 fps ctrl+num3 locks to 45 with asw on ctrl+num4 resets to auto I do believe the 45 is a relic from the Rift CV1 and 45 should say half. IE half of 72fps is 36fps and it seems to work on the misses Quest 2 and on my Rift S (80fps) that 45 is actually 40 but you can play around with them in game and see the difference... as long as you hit a minimum of 36fps stable. Apart from changing your setting in game and Quest 2 these tools can help. Oculus Tray Tool. It allows you to set individual profiles for each game. Super sampling, ASW mode, CPU priority and other stuff. I could not get by without this one. This video may also help but not sure as I didn't watch it through because I am only this much helpful today. I skipped through it and he explains what you need to do by the looks of it. The 300% is probably BS though. Hey it's a head start at least Oculus Debug Tool. You already have this installed. Usually "C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe" It has some monitors that let you help debug problems. And lastly not for DCS but for your American Truck Sim. It runs bad on Oculus as it is more for SteamVR unless something has changed. That means it will run but not very well but be amazed and stuff... I have some help for you there as well... possibly. OpenComposite. Not for use in any Oculus native game but some native SteamVR games don't work so well with Oculus and if I remember correctly American Truck Sim is one of them and it went from poor to awesome using that DLL replacement for me. If memory serves I only installed in ATS and I think it worked in IL2 as well. Take that with a grain of salt as it has been quite a while but pretty sure this will help with you ATS problem. I also recommend you only do the as needed installation (Copy and replace a DLL I think) and not the whole shebang install (The exe) as you don't need to fix what isn't broken. All the best mate.

There is every chance you may like it as much as I do. The way it is set up you can adjust the Halo band to suit your head and then independently adjust the actual Q2 in/out/up/down/tilt. In the image linked above the metal disk and the white disk on the side rotate as does the Q2 side mounts. The black thing on the side of the Q2 slides in and out and the black band on the side of the Halo Strap moves back and forwards via a dial at the back. It just fits my head but I seem to have a pretty large head. The dial seems very solid and man it can be turned up pretty tight with apparently no issues. Either to the head or the thing feeling like it is going to break. You can do it up very tight to your face (Though comfortable as all the real pressure is on your skull) but a bonus point is you can remove the face gasket/interface/lightkeeeperoutera or whatever it is called to bring it right up close to your eyes for a significant FoV increase, As the Halo is doing all the holding this is doable and also how I run my Rift S. There is a little bit of work needed there as there is something sharp that can bother my nose but that shouldn't be too hard to fix. It is the tilt thing I still have not gotten used to as I have had years of lifting VR headsets up to deal with but just tilting it up, doing what you need to do on the keyboard while still being able to view the VR is the all time winner for me.

Ok, interesting bit of information if you are running win 11 and a Quest 2. It ran like $$$$ and a bit of diagnosis showed that the ASW was not working properly. Like completely janked. The CTRL + 1,2,3 and 4 had some effect but it did not stick to the frames commanded (Say 40 for example, it would do everything but 40) and all and all it ran like a dog with 4 broken legs on her system. On mine it ran pretty sweet so I will be interested to try it on this rig but anyway to cut a very $$$$$$$ long story short, at this point in time, if you are having poor performance (apparently a completely broken ASW is "poor" performance) in Win 11 then do this. 1: Open the Oculus Debug Tool. 2: Under the "Service" dropdown select "Toggle Console Window Visibility". 3: Do not close or minimize the console. Leave it on you screen and run the game over the top of it. MY bloody forehead can now heel. FYI I am running a Rift S and I got to say the Quest 2 was a surprisingly good upgrade. Her Rift CV1 died so I bought her the Q2 to replace it. Now I want one. BTW the default headband is garbage. We spent 65au on an aftermarket one and I want one of them as well now. Even has the ability to flip the display up without removing the headset. Why don't they all do that out of the box? FYI it was this one... https://www.amazon.com.au/gp/product/B08YR8LFH3/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

Thanks mate.

Haha I suspect that won't buff out.