Search the Community

All, I wonder if there is anyone out there who is experiencing the same - my Quest seems to loose tracking and my vision 'wobbles'. Problem - Upon starting i have buttery smooth vision, head tracking is fine. However over time, and it doesnt happen all the time, i might get a little 'glitch', or jerk and then it is as if my head is wobbling around. The current solution i have found is to cover the tracking cameras on the outside of my head set, move my head around untill i get the 'lost tracking' message. I can then uncover and it reverts back to normal. It will, however do the same again shortly after. Once its done it once it will do it again. Another solution is to minimise DCS on the comptuter and after a few seconds maximise again. This method doesn't always work. I have had this on my Quest 2 and thought it was just the hardware however I have recenlty got a Q3 and it does the same thing. When i exit out of DCS my desktop is also wobbly untill i quit out of Quest link and it resets. How i run DCS Using Standalone, i start up the Quest link using cable. I start up OTT and then start up DCS in Multithreading. Starting up OTT i have it so it reduces my resolution on the monitor to 1080 which gives me a noticable frame increase. Hardware I7 12700K, 3070Ti 8GB, 32GB Ram Any suggested solutions or thoughts on what is causign the issue would be very welcome Simon Mr Yeti

Sometimes, you have done everything possible to make your VR session very smooth and effective, but for obscure reasons after say 15mn of enjoying DCS, you suddenly get half of your current fps rate, sometimes worst, and in the better case, you have to wait for a while, in order to see your fps rate coming back ... or not, and have to restart the session. Hey dude, dont give up, you have to rescue some bastards alone in the Paradise Lost. Ok, for those like me that have already read all the literature and tricks to fix their stuttering trouble, I found out a very strange behavior and fixed it. You already have set your DCS/VR parameters the better you could, and: 1. Set Oculus parameters using Oculus Tray Tool - ASW mode if Off (it is MANDATORY !) - Adaptive GPU scaling is Off - OVR Server Priority is HIGH 2. Set Oculus Link parameters using Oculus Tray Tool - Encode Resolution: set as required by the limit of your GPU - Distortion Curvature: Low (according to the limit of your GPU like above) - Encode bitrate: 960 (ie max allowed by your link) - Sharpening: Disabled 3. Clean the D3D/GL/VK/whatever shader cache: => see script #1: cleanDXCache.ps1 4. Optionally use the powerful "NVidia Profile Inspector" and set: - "Enable DLSS-SR Override": 1 - "Override DLSS-SR Preset": 0x0000000B (ie Preset K) So now what to do ? The stuttering could appears because one or more of the 5 Oculus-Client.exe that run your session has a bad priority. Oculus-Client's are a set of 5 programs that run with the Oculus-Server, one at a time. I don't know what are their purposes, but sometimes, one of them is terminated and a new one is started. When I encountered stuttering, I found out that one of the oculus-client use a LOW priority. Using the registry, I tried to tell WIN/OS to set the priority of any instance "oculus-client.exe" to HIGH, but it didn't work for new instances, just when you start a new session. So, I wrote a brute-force script that monitor and set the priority of the oculus-client instances to HIGH, and until now, it really works. I never encounter stuttering anymore. ==> see script #2: setOVRPriority.ps1 Tips and tricks: 1. If you want to set a priority to any instance of a program, edit a file with a .reg extension, and put: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dcs.exe] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dcs.exe\PerfOptions] "CpuPriorityClass"=dword:00000003 2. If you want to launch the scripts attached to this post from the desktop, you have to create a shortcut like: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File "C:\pathToScript\cleanDXCache.ps1" Hope it helps, cleanDXCache.ps1 setOVRPriority.ps1

Bien le bonjour ! Je suis sur DCS depuis 7 ans maintenant, et j'ai une machine qui me permet de le faire tourner très bien sur mon écran 38 pouces. MSI B550 Gaming Plus RTX 3070 8Go Vram 64 Gb RAM 4000 Ryzen 7 5700X3D Depuis quelques mois, je possède le Quest 3. J'ai donc très logiquement testé DCS et je trouve le rendu globalement décevant. J'ai pu progressivement obtenir des performances correctes en jouant sur les paramètres du PC, les réglages graphiques NVIDIA et dans DCS, et le FOV avec Oculus Tray Tool. Mais je rencontre 2 soucis : le cockpit n'est pas très lisible (cadrans, chiffres assez flous, il faut que je rapproche pour voir bien), et l'extérieur du cockpit semble aussi peu clair. J'ai pourtant 72 FPS et en survolant une forêt par exemple, c'est bien. Ca baisse quand il y a du trafic et du détail au sol. Mais si je dois identifier des unités au sol par exemple, ou identifier un appareil en vol ami ou ennemi, c'est impossible tant c'est moche. J'ai parcouru en long et en large les tutos YT pour optimiser le Quest 3 et je crois que je m'en sors pas mal, mais : Ne serait-il pas opportun de procéder à un upgrade matériel ? Je pense à passer à une 3080Ti (une occasion se présente en ce moment chez qqn qui passe à la gamme 4000), ou à upgrader le CPU. Quel est selon vous le facteur limitant ? De mon côté, je dirais la CG parce que sur DCS elle est toujours à 100% (même sur écran où tout va très bien elle affiche 100% d'utilisation). Par contre, j'ai vu sur que j'aurais un bottleneck dû à mon CPU. Je lis aussi par ailleurs qu'il ne faut pas s'y fier... Donc je suis un peu perdu. Est-ce que maintient la config actuelle en essayant d'optimiser encore l'ensemble ? Est-ce que j'upgrade le CPU (si oui, pour lequel en AM4) ? Est-ce que passe à la 3080 Ti que j'ai vu en seconde main (pour 470€) ? Sachant que mon budget est grand max à ce montant de 470€. Merci d'avance !

Hello gusy after the chinook update i noticed less quality on VR in all modules, includes terrain and cockpits, image its blurry and not as good as before the update, i am the only one? I run 4090,i7 14000,64gb and quest 3 via Virtual desktop. Thanks a lot.

NOTE: I do not believe this is a DCS defect, however this behaviour commonly occurs when in DCS Problem At least twice a week (at times much more - i play DCS every evening) and within the first 15minutes of a SPlayer VR DCS session the following has been occurring over the last year - Black Screen, Fans 100 percent, hard-reset or power-cycle is the only option to restart (12VHPWR sense pin LED indicates normal signal) History I first encountered this issues last year with a new gaming rig however windows event viewer was reporting WHEA errors - in response i RMA'd the 4090 which turned out to have bad capacitors. About 3 months after installing the new 4090, i again started to encounter the same behaviour with similar frequency and symptoms. Just prior to black screen event, the Windows Event viewer reported the nebulous and useless Event ID 56 ACPI 2. I was able to eliminate this event from being reported by Windows by setting NVCPL to prefer max performance and restart (no fast start) PC prior to any DCS session. Over the last 10months i have tried many settings to resolve or at least minimize (see below). Currently the Windows Event Viewer reports (albeit with a timestamp nowhere near the black screen event) \Device\Video3 UCodeReset TDR occurred on GPID: 100. What i have tried to solve or at least mitigate Variations of this behaviour is littered en mass in forums across the internet (NVidia, Reddit, Overclock.net, etc.); as such and as expected with anything on the internet, the unstructured responses, recommendations, etc wildly vary from moronic, insulting, helpful. There is of course no systemic solution as influencing hardware, software, OS & BIOS configuration varies materially enough that a resolution for one particular person's ecosystem does not work for others. Removed all useless bloatware e.g. gamebars, overlays, RGB crap software, razer trash, armoury crate toiletware, ... NVCleanStall 552.44 driver; Disable Telemetry, disabled NVIDIA HD Audio Device sleep timer, enable Msg Sig Interrupts (default, High Priority) BIOS, Disable PCIe Native Power Management & ASPM, Enable Resizeable BAR, power limits set to Intel spec for 13700K Windows 10: Disabled hardware accelerated GPU scheduling, Disable PCIe link Power Management, TDR delay to 15seconds, no fast start on boot NVCPL: Neg Load Bias Allow, Prefer Max Performance NOTE: Have not tried the more controversial settings such as turning off C-State in BIOS Power Supply: MSI MPG A1000G PCIE5 (12VHPWR) GPU: ASUS TUF RTX 4090 GAMING w/ latest (23-2-22) VGA Bios. I use the anti-sag adjustable support brace (although a stupid design by asus) to help support the card and (hopefully) avoid slot contact issues that might lead to the behaviour i am experiencing. AC Power: I don't use my UPS as it is only 900Watt, instead using a high quality monster power surge protector. Not sure how sensitive the MSI power supply is to voltage variations (while under higher than normal load) in wall power? I do, of course, actively profile and log all relevant sensors via HWINFO and i use the Remi Mercier's FanControl (github) for all heat mgt. Nothing recorded is ever out of temp, voltage, etc bounds for any measured component when the black screen occurs At my wits end with this and truly hoping i don't have to RMA my 4090 again.

Hello, I've tried to solve this in as many ways as possible, but I can't so I'm going to post here. When attempting to fly the F1, the cockpit is full of flickering white dots that make it hard to look at anything. Hardware: VR Headset: Quest 3 CPU: Ryzen 9 7950X GPU: RX7900 XTX OS: Windows 11 In-Game Settings: Pixel Density: 1.2 Use DCS System Resolution: Yes Anti-aliasing: MSAA MSAA: 2x Upscaling: Off Sharpening: 1 Terrain Textures: High Shadows: Medium Flat Shadows Blur: On Secondary Shadows: Off SSS: Off Visible Range: Medium SSAO: OFf SSLR: Off Lens Effects: None Heat Blur: Off Motion Blur: Off Depth of Field: Off Anisotropic Filtering: 16x Terrain Objects Shadow: FLat Cockpit Global Illumination: Off Quest Link Settings: Render Resolution(Can't remember the proper name): Max Asynchronous Spacewarp: Disabled Please help me. I really like the Mirage F1 and I want to fly it but I can't see anything to fly!