101st Lonestar AUT

Would be interresting for me as well - especially in combination with the 5800X3D-CPU and in virtual reality! If anyone can could provide that info... :-)

the problem is, that you can enter the coordinates, but when hitting enter it does not save and shows the old ones...

UPDATE: It is not possible on some specific servers!!! Now, what is the setting we are searching for on the server? Thanks anyway.

Hello fellow Pilots! As @AlphaJuliet wrote in one of his Threads there has been a known Bug - Am I the only one not beeing able to edit existing waypoints or create new ones by LAT / LONG coordinates? My standard procedure (not working anymore): - EHSD-->DATA page - WYPT active - choose waypoint or create new one - edit POS by entering LAT/LONG (same way as in INS alignment) - press ENT - same for ELEV - (check setting again) - exit Data page To be honest, I have not been sitting in the Harrier for a few months. Is there a new procedure now? But the entered coordinates do not save anymore. Therefore I cannot fly my CAS... On Reddit you can read a lot of postings that this bug has still not been fixed: Tried a few solutions such as creating a MK1 or creating new TOO first and editing coordinates afterwards. --> Nothing seems to work for me! Your help will be apprecaited Thanks & best regards, LonestarR

For ST performance he can try my guide --> helped a lot of people in my squadron:

Did not help - just switches that 100% CPU-load to another core. TNX anyways

All I did was turning off "Hardware accelerated GPU-Scheduling" in Windows settings (as recommended for DCS). Nothing else...

Question is: Why should MT on AMD Ryzen be worse in performance than when in ST?? These CPUs are built for several threads running at the same time and not for ST performance...

This exactly seems to be the problem for me, too. When I start in ST-mode I do not see a major difference in between the core-loads compared with MT --> thats why I opened this thread with that title. (Means that only 1 core is maxed out - hope that ED can check my topic and maybe get rid of this problem in a future patch)

I have tried before with 16 threads and it was like a slideshow - something with MT is not optimized for my AMD-Processor. (8 physical cores work better for me, thats what I mean), GPU at 87-98%

Pagefile is off because of my 64GB RAM --> DCS uses 47-48GB of RAM and therefore I would not like to have a bottleneck through my SSD. My GPU-load is at 87-98% and on its limits

Unplayable in MT & Micro-Stuttering when in Multithreading. (though: ST works fine and stable @40fps!!) FPS-Counter displays CPU bound, but the game still only uses around 40% of my eight P-Cores! (even worse with 16 threads) Bug? I am messing around with this for a few weeks now. Repairs, Shader folders deleted, anything explained in the forum tried etc... no Improvements... SPECS: Amd Ryzen 7 3700X, 3060Ti, 64GB RAM, Quest 2 / OpenXR null #thanks for your help ;-) DxDiag.txt dcs.log

Dito. but in standalone

Thats exactly my standard configuration - running perfectly smooth in ST but stuttering in MT --> completely unplayable for me . ED please help! @NineLine Why dont we get improvements with MT? SPECS: AMD 3700X, 3060TI, 64GB RAM

For DCS 2.8 Multithreading Update try this in combination with my Guide: GamersByNight DCS VR Settings & Optimization Guide (as far as I can see, not all Information is accurate in there, so you have to combine and find the correct settings for your PC) I will update you as soon as I find time...

Mission load is one of the most problematic things in DCS VR. We cant do much against low framerates because of the current engine. --> two things that help here: get your ingame details on a lower value & edit the graphics.lua according my guideline! Choosing the best VR-USB should be described in your motherboards ducumentation. (normally: one of the onboard USB 3.x connects at the back of your mainboard). First time starting via desktop seems to register the App on your Quest HMD in the Link app... Repair is always a good choice, though. I did not try any other VR kits than QuestVR, yet. Thats mainly because I did manage to get a stable setup for MP as well (27-40 FPS on my 3060ti).

Sounds similar but we did not drop pairs (tandem). Just launched two single JSOWs. Also the Tread is from beginning of 2022 and still not fixed. (I mean JSOW is not the most important - I understand...) Thanks for the hint.

Happened in our squadron training: - Four f-16 dropping 8 JSOW similarly. (single realease, nearly same position, one bomb after the other) - Half of them hitting the target perfectly, the other half was behaving like brake chutes, soaring down and detonating in the mountains 10 miles before targets. Tacview: Reason found - Energy bleeding out because of vertical "wobbling" null BR

See this post & find my solution: https://forum.dcs.world/topic/309622-low-fps-in-vr-multiplayer-only/?do=findComment&comment=5107560

Did it help? O_O

*** V1.1 modified on 01.02.2023 *** Ok, will just summarize for you - as a kind of X-MAS present - this is for my WIN10 setup at least: (It took me about 6 weeks to get DCS running smooth and stable, so I do know the pain...) First of all: DCS-Settings have the biggest impact to your performance, so start on low settings and after all get higher step by step. (Texture Settings cannot be set to high, if you dont have a graphics card with 12GB or more!!) Before starting DCS restart your PC and be sure no other applications than needed are running in the background! (also check your autostart and disable any unnecessary apps in Windows-Taskmanager, than restart again and doublecheck). Be sure to use a VR-Ready USB-Port for your Link-cable, or at least the fastest one you can find on your PC. I am using an external powered USB3.1-Hub to really get safe in terms of voltage supply... Delete the two shader folders of DCS itself before first time starting in DCS-VR (wherever your game files are located e.g. C:\Games\Eagle Dynamics\DCS World OpenBeta\Config" --> "fxo" and "metashaders2" folders)! My Rig: - AMD Ryzen 3700X - Nvidia 3060ti - 64GB Ram - WIN10Pro Installed software: - MSI Gaming App (in my case: for VR-Ready USB support) - latest Nvidia Drivers - latest Oculus-HMD Update installed (WLAN needed) - latest WIN10-Updates - Oculus Tray Tool (or Debug Tool) - ProcessLasso (for managing your processes permanently) Configuration: 1. DCS ingame graphics settings (see screenshot below) 2. edit graphics.lua (can be found in C:\Users\username\Saved Games\DCS.openbeta\Config\) - search for following lines: maxfps = 40; Precaching = { around_camera = 42500; around_objects = 7500; } (40 maxfps comes from Oculus Home App --> e.g. 80Hz == 40fps for each eye, around_camera is my TGP max render distance and should be same as ingame. Due to 2.8 you can either write an autoexec.bat or change these settings manually after each update, tutorials can be found in DCS forums) 3. Nvidia settings --> I am using Anisotropic Filtering by Nvidia and turned it off ingame, skip FXAA and Antialiasing for the beginning (see screenshots below) 4. Oculus settings --> start with 1.0 resolution, you can get up to max resolution at 80Hz and even higher with small impacts to your performance (see screenshot) 5. Oculus Tray Tool OTT settings (see screenshot) 6. ProcessLasso settings (DCS needs 2-3 permanent cores, OVRServer needs at least 2 - try to get DCS and any other 3rd party app on different cores with this tool permanently or via taskmanager each time you start DCS) + set priority HIGH for DCS.exe and OVRServer_x64.exe or to real time 7. Windows Energy settings --> use optimum performance profile & check if USB-powersafe is deactivated (see screenshot) 8. Windows Graphics settings --> deactivate hardware based GPU scheduling 9. Windows System Properties, Performance --> use processor time scheduling FOR background apps (this is priority for OVR Server Link-App) 10. HINT: if you own a NVIDIA card you can AUTOTUNE your card via the Alt+Z (enable in game overlay first) menu and use this profile in afterburner to get some extra power Startup routine: 0. Be sure ProcessLasso is running in the background 1. Check if your USB is ready for using VR (in my case: in MSI Gaming APP it has to be activated) 2. Start Oculus Home 3. Start Oculus Tray Tool (minimize and do not close it) 4. Start your Quest2 (and define your Guaridian area - for me: desktop, fixed) 4.1 At the very first start: test USB-voltage & bandwith within the Oculus Home App (should be around 2.8 GBit/s on USB 3) 5. In the Q2 go to your Link-App (usually in the quick settings bar left) and connect with your PC 6. As soon as the Link is established and the App is running start DCS directly from your PC Desktop (first time seems to be important) For more Details I will post the Screenshots in saperate as following: ^^ Clouds can be left on "standard" after the new updates to AA. ^^ take ALL the values out of the () for your config and finally use "pre-rendered VR Frames Value: 1-2" ^^you can try lower Encode Bitrate and Resolution here as well - depends on your cable and USB-Device Screenshot out of Windows Energy-Management (edit your Power-Plan): Hope this helps a lot of you guys and safes your X-mas holidays! BR LSR

Wow @Quip, that was the missing preference - at least for for my setup. A very big "THANK YOU" for the hint, I was nearly giving up DCS & VR! I've tested the whole weekend and it now runs smooth and stable like neverelse before... I recognized that the load of my garphicscard (3060ti) is now somewhere between 86 and 98% (instead of perma 100%) and that seems to give extra headroom for the stream via link to render without any framedrops. (have some when I open the F-10 map still, but thats ok so far) For all those, who have the same struggles with these annoying framedrops: Watch the load of your graphics card and try to get your ingame detail settings bit down to gain some headroom. Rendering of streaming also uses your graphics card and cannot be changed to CPU, nor it can do any reservation for its process. Therefore it needs some extra power in case of framedrops. If you do not use 100% of your card permanently you should get rid of those jitters on the Q2 and maybe other HMDs, too. I will also bring a complete guide for setting up the Quest 2 in terms of performance and quality, will keep you informed. TNX to you all, fly safe & BR

After a complete Hardware-Upgrade of my PC (now: 64GB RAM, 3700X and all the Overclocking done) I still have the same Issue and even more Framedrops after the new DCS Update... Enclosed you find a screenshot of Oculus debug tool - so thats my Problem... Dunno what to do now... Spend over 50h to get this working and still no solution,yet... Please HELP!

I have also tried to assign specific cores to DCS only - no sucess... btw: boosted up my CPU by 28% - did not change a thing My FPS are still ulow on these specific servers - on others they run between 27-40fps. But what happens on good running servers is that from times to times suddenly huge framedrops appear. In that case I have to tab out of the VR-window or put the headset away. Anytime I return back into the VR the FPS are normal again... Can anyone explain whats happening there? Seems like VRAM getting stuck.

My guess: CPU is definately the reason why this happens - but as you can see it is only used by 21% while running DCS. Means that DCS doesn't get the full performance out of these AMD Processors. And on MP-Servers, where the CPU-workload seems to be significantly higher - this fact is making a huge impact to my fps-performance...