Granny

Can't get the debug tool to work. I put the command in terminal and its doesn't recognize it. Does my 1080Ti predate the debug tool?

I have OC my CPU using Ryzen Master, it just the basic Precision Boost Overdrive setting in gaming mode, and stress tested with Ryzen Master itself. I OC my GPU using MSI afterburner using the curve it calculated for core clock and +200mhz boost on the memory clock. I did not stress test this but found things to get unstable at about +300mhz OC so I backed it down to 200 it worked fine. I've been using these setting for at least 6 months and DCS ran completely stable in 2.7, and 2.8 (MT). After v2.9 came out I went from v2.8 stable to 2.9 Openbeta. That's when the crashes started happening.

I updated from v2.8 stable to v2.9 open beta about a month ago and have since started getting regular crashes. Screen just locks up, visual tears, hour glass timer shows up, and I have to Control/Alt/Delete to bring up task manager and quit DCS. There is no particular pattern but seems to happen roughly an hour into game play. Happens in standalone and Multiplayer. I'm using DCS MT in VR with Oculus Q2. . Haven't experimented with 2D. I've been doing a lot of F-16 Air to Ground, using TGP and Mavericks...maybe two video feeds is taxing my system? My system in on the lower end for VR, but I keep my graphics setting low and it seems to handle it pretty well. At least it did with v2.8 stable. Crashes generally occur with no prior warning, like studder or tearing. It just stops. System Specs, Asus Tuff Gaming 2 B550 Mother Board, Ryzen 5 5500 CPU (slightly over clocked), MSI GTX 1080TI GPU (also slightly overclocked). Most recent log is attached. dcs.log

Thanks for that, the companion app made it much easier to work with and I have been testing it extensively for several days. I tried using foviation settings with Side Quest before and that seemed to have very little effect. Quadview definately made some significant changes, unfortunately at the end of three days I could not expand the clear center of the FOV large enough to keep the peripherial areas from being a distraction without introducing significant stuttering and tearing. It was worth a try though. Thanks again.

I have not been able to get it to work. Not sure if my system is not compatible or if I'm doing something wrong. I have OpenXR Tool kit, and I reset that to default in safe mode as per the instrutions. I re-enabled it, then installed Quad View. When I open the OpenXR menu, again there are no options related to Foveation. There are specific instructions on the wiki about various headsets, but the Quest 2 is not one of them. Any suggestions?

Yes, I have a 1080ti, Ryzen 5 5500, combo with Quest2 headset. Just made the move from 2.8 to 2.9 and experimenting with the new settings. What map you're on makes a big difference. I can get much better performance and quality on the Caucus maps than the Mariannas Map. In 2.8, on the Marianna map I set MSAA at X2 (gotta have it or aliasing and shimmering are unbearable), textures low, shadows off, cockpit res at 1024, clouds low, pix density to 1.1, with headsets refresh rate at 80hz. That keeps the stuttering and aliasing to a minimum, cockpit is still a bit blurry but not bad. I'm still working with 2.9 but so far the settings are basically the same, except I tried switching from MSAA to TAA. That deduce the aliasing and shimmering a lot, but more ghosting and microstutters, particularly over the congested parts of the islands, and the cockpit res is pretty bad. Jumping over tto he Caucus map, I can bring a lot of my settings up to medium (keep texture and clouds low, shadows flat or off) TAA or MSAA 2x both seem to work fine. I can increase pixel density to 1.3-1.4 which helps alot, and up my headset's refresh rate to 90hz. I'm still experimenting with upscaling and sharpness features of 2.9. So far I can't see the sharpness doing much. A few other things things that seem to have helped, I use Oculus tray tool and reduce my FOV to 0.7ish. Also, in the Nvidia control panel, I set a cap on my max framerate at 45fps (basically half the refresh rate of the headset). Saw that on a youtube video somewhere, not sure why it helps, but it got rid of a lot of stuttering and tearing. Runs much smoother now. I overclock my CPU using Ryzen Master and apply its generic Gaming settings. I also overclock my 1080ti with MSI afterburner a little bit. Its still not super awesome but its playable. I think I'm pretty much squeezing all the juice out of my system that I can. Hoping to upgrade in the future, probably a Ryzen 7 5000X3D, but not sure what GPU to go with. Anyway, hope that helps.

Thanks all, there are several tips in this thread that I had not tried. I've got things much better now. Still not perfect, but it will never be with until I get around to upgrading. But DCS is playable now.

Can anyone help me with DCS VR? I'm playing DCS MT 2.8 (non-Steam). Looks great on my monitor by when I strap on my Quest 2 (128) and go VR its pretty terrible. Even with pretty modest graphics settings I get lots of aliasing on straight edges and some qantization (especially in clouds and building in the middle distance) and some dithering. In general the entire scene looks like its in a fishbowl filled with water, very shimmery. I watched about 30hours of youtube videos and read a dozen articles over the the last 2 weeks telling me how to tweak every graphic setting in-game and in the Nvida Control panel. I have tried adjusting resolution, refresh rate, pixel density and a variety of other settings in the Oculus App, SideQuest, Oculus Debug Tool, Oculus Tray Tool, even the OpenXR tool kit. Most of these had no noticeable effect or in some cases degraded my performance with no improvment in quality. I slightly overclocked both my CPU (with Ryzen Master) and GPU (with Afterburner) to try to improve performance. Still no luck. So far only increasing the MSAA or the Pixel Density in-game slightly improves the image, but doesn't fix it and it immediately introduces stutter and cuts my FPS from 72ish to some times as low as 35. In-headset apps do seem much clearer than PC stuff over Quest Link. I have tried multiple USB cables and ports, but I'm getting 2.2Gb across them according to the Oculus App, and I have USB power power management disable, so that doesn't seem to be the issue. I'm running a Win11 PC with a Ryzen 5 5500 CPU and MSI 1080TI GPU. I know its not top end, but I've seen videos of players getting much better VR on similar systems. I am as a loss as to what to do. I also use the Quest to play Star Wars Squadrons (with Steam). My its not awesome, but its acceptable for the mid-to-lower tier hardware I have. Much better than what I see in DCS. So, iss my hardware the limfac, or is there key thing I'm missing. Please Help! Here's my specs are: OS Name Microsoft Windows 11 Home Version 10.0.22631 Build 22631 System Type x64-based PC Processor AMD Ryzen 5 5500, 3600 Mhz, 6 Core(s), 12 Logical Processor(s) BaseBoard Manufacturer ASUSTeK COMPUTER INC. BaseBoard Product TUF GAMING B550M-PLUS WIFI II BaseBoard Version Rev X.0x Installed Physical Memory (RAM) Silicon Power Turbine 3200MHz CL-16 1.35V DDR 4 (2x16) = 32.0 GB Total Physical Memory 31.8 GB Available Physical Memory 27.4 GB Total Virtual Memory 33.8 GB Available Virtual Memory 27.5 GB Page File Space 2.00 GB NVMe SSD Western Digitall Black 2TB Gen4 PCIe, M.2 2280 up to 5150MB/s GPU Nvidia Geforce GTX 1080TI Headset Quest 2 128 My in-game settings are: Textures - High Terrain Texture - High Civ Trafc - off Water - Low Vis Range - Low Heat Blur - off Shadows - Flat Flat shadow blur off Sec Shad - off Res 1280x768 Monitor - 1 scrn Res of Cockpt Dis = 512 MSAA 2x Depth of Fid off Lens Eft - off clouds - low Moton Blur 1 SSAA, SSLR, SSAO, all off Frst Vs 60% Forst Detail - 0.7 Scen Detail - 0.7 Preload rad 150000 Chimney Smk 1 Gamma 1.4 External FOV 78 Anisotrop Flit - 8 Terrain Obj Shad - off Cockpit Glb Ill - off Msge font - 1 Scale GUI 1.5 Rain Drop - off Vysnc off VR Pix Density 1.0 Forced IPD 68 MSAA Mask 1.00 Nvidia Control panel setting all restored to default settings. Oculus Head set refresh rate set to 72, pixel density at 1.0.

I have zoom function bound to a rocker on my HOTAS. Whenever I zoom in or out, upon releasing the rocker switch back to center, it does not return back to the original head position. It defaults to a position that is part way zoomed in, putting me a little too close to the cockpit console. This leaves lower portions of the instrument panel out of view that I can see from the original starting position. Doesn't matter what airplane I'm using or what HOTAS, same always happens. I'm using FaceTracknoIR V2 as my head tracker. That seems to establish my original head position but if I want to keep that original position I can't use the zoom. Any ideas why this is happening?

Looks Great, really excited about the C-130J. How long do we have to wait?