Richrach

Rabies, First, love the callsign. I may be late to the game, but a few things I have found that can increase your frame rates. - Turn everything off in NVIDIA settings for the GPU. Your photo of the frame counter shows the CPU is the bottleneck. This is likely not the case. I saw the same thing on my computer and the information was bogus. Putting everything on the CPU's shoulders helped immensely for me (counter to things I have posted before... I was still searching for what really worked). - Turn off multi-thread if you have it on for your CPU. Again, from experience, this was a huge killer. - Have you tried playing offline? You can log in with the WiFi turned off so there is no link to the internet. Normally, I play around 55-60 FPS on my system. I have found turning off the links to the outside world my frame rate goes up 10-15 FPS just because my computer is not trying to talk to the outside world and run DCS. This makes sense and if you think about it you are not going to be playing in the multi-player world at 20 FPS. Just some ideas. I spent an incredible amount of time chasing tips and ideas to speed things up on my own system. There are a lot of opinions out there, many of which may be very specific to unique set-ups. The three above have been the most valuable items I learned in that time. Good luck and good hunting, Richrach

All, I found the solution. Names of files must not have spaces. If you name something "A B C" it must be "A-B-C" or "A_B_C", or just "ABC". The format does not support file names with spaces. Simple, but I did not know. I hope this is helpful to the other simple minds out there like mine.

Grubby, I flew the TA-4J in training with the US Navy. The flight model is excellent with one exception, landing. Regarding sensitivity of the flight controls in a sim, the original aircraft had a roll rate of 720 degrees a second, two complete revolutions in that second. Full stick deflections were limited to one roll of 360 degrees (one half second) due to the probability of entering a "coupled roll" where the aircraft could become unrecoverable. It was an insanely responsive platform! Regarding landing, the flight model is terrible. Response to power to control glideslope is not even close to the real aircraft, or any aircraft I have flown. Not sure how one would fix this as other sims have gotten it right in the past, most notably Janes F/A-18 from many years ago. A suggestion: Use the axis tuning tools to reduce the sensitivity in the areas you are struggling with. Here are my settings which may give you a place to start. Pitch - Deadzone = 8 / Saturation X = 100 / Saturation Y = 80 / Curvature = 30 Roll - Deadzone = 8 / Saturation X = 100 / Saturation Y = 70 / Curvature = 35 Elevator trim speed = 33 Aileron trim speed = 33 Rudder trim speed = 50 I am constantly trimming throughout a flight, which is/was normal for aircraft of this era. Modern fly-by-wire lawn darts are junk in my opinion because the pilot does not actually have a feel for what the plane is telling him through its trim. Trim is the original "force feedback" as it always told you what was happening aerodynamically with the airframe. Modern jets breed terrible pilots. This jet was a joy to fly, one of the best aircraft I have ever flown. Responsive, nimble, honest. A good pilot could spank the crap out of any jet out there in its day, F-4, F-14, F-15, F-16, Mirage, MiG (pick one) in a tight fight. The combat slats gave it control at low speed that was just amazing. All it lacked was a solid radar, which is also fairly well represented in the game. The cockpit was so small most pilots had to turn sideways (myself included) to bring the canopy down or it would pinch/catch the sleeves of your flight suit! It was like putting on a pair of jeans that are one size too tight. No kidding, you felt like you were not in a cockpit, but actually part of the plane. (Real useless trivia, the T-2C "Buckeye" was just the opposite. You could put three people in each seat in that jet. It was like sitting in an oversized bathtub. A jet made for really fat people!) That there is such a high quality model of this aircraft in DCS that is not a paid module is a testament to those like myself who flew this jet and loved it so much. What a joy it is to fly it again! I hope this helps, Richrach Combat Vet: Iraq, Kosovo, Afghanistan, Pakistan

Tried to add a couple audio clips to a mission. The files were built using both WAV and OGG. Neither type would play. Tried to trigger them via a time trigger (Time more than 30 seconds), Part of Coalition in Zone, and Unit Inside Zone. None worked. This is in 2.9.51704.

UPDATE with morebettergooder results (Changes/additions in BOLD) DCS 2.9.2.49940 Open Beta System: i5 12600KF OC 52/52/52/52/52/51P 41E, -0.050 Core Voltage offset, Hyperthread disabled (Note: I did use these settings in Intel XTU, but found them not stable. They are completely stable when set in BIOS. This is as fast as my CPU will run, period.) RTX 4070 OC edition NO additional overclocking 64GB DDR4@3600 Motherboard: MSI PRO-Z690-DDR4-WiFi Pimax 8KX - 72Hz, FOV Normal, Render quality 2.0 (max) (This is huge! UNBELIEVABLE the difference it makes!), Fixed foveated rendering - Balanced PimaxXR Runtime = Prefer framerate over latency - checked Enable Quad views (get it, it is amazing) - checked A-4E-C Combined Arms Sinai map Process Lasso Set DCS.exe Priority class to High Set CPU Affinity DISABLE on the two cores that were hitting 100% usage in the game (This makes stutter go away completely, wow). DCS-Beta-MT OFF UNLESS OTHERSWISE STATED Resolution - 1920x1080 Cockpit - 1024 Upscaling - DLSS Sharpening - 0.6 Textures - Med (In VR cannot tell the difference between med and high setting. I choose med) Terrain textures - High Shadows - Med (Looks better than high. No impact on frame rate.) Visib range - High Clouds - Standard Water - Med Heat blur - Low (If you are all about high textures and detail and have this off, you need help) Clutter/grass - 760 (personal preference for visuals in Sinai map. Does not seem to have an impact on FPS) Forrest visibility - 100 Forest details - .75 Scenery details - .75 Preload radius - 75000 Chimney smoke - 1 Max FPS - 50 Anisotropic filtering - OFF (High settings in terrain seem to take care of this, not needed) Terrain objects shadows - Flat (Looks better than in any other setting) VR pixel density - 1 Enable hot plug - off Use DCS system resolution - checked NVIDIA settings OFF/Auto UNLESS OTHERSWISE STATED: Anisotropic filtering - App controlled Power management - PREF MAX perf Texture filtering quality - Quality Texture filtering trilinear - On Virtual reality pre-rendered frames - 1 Vertical sync - Off Results: I set 50 FMS to smooth out the work being done by the CPU. Process Lasso helps immensely by moving the work off the most used core and distributing it throughout the CPU. No stutter. With these settings the game can vary between 43-70+ FPS before setting a limit. Rather than have the CPU beat itself to death trying to keep up, 50 FPS is a great tradeoff. I cannot see any difference between that and anything higher. Using Process Lasso seems to have increased the terrain rendering as well, much more detail in external views. ____ The only constant in DCS is change. As I am typing this, a new driver just came out for the Nvidia RTX-4070, 551.23. This driver adds support for Ultra Low Latency Mode, so who knows, my write-up may not be current even as I finish it. Be safe. Get up and get outside to breathe fresh air once in a while! - Richrach

All, I am a little amazed, irritated, and a few other choice words. Shortening the story, I just turned off Open XR tool kit, left Open Composite and Pimax XR on and jumped 15 FPS! So I went back into DCS and turned everything up to max and cranked out a crystal clear cockpit, outside views, everything. All the agonizing and suffering over all the settings was about useless. Up to now I have had what I thought was the best a VR headset could do. It was fuzzy, a bit blurry and mostly disappointing for all the work I had put in. All better. CRYSTAL CLEAR cockpit and externals, exquisite detail, I can see the eyes on the personnel standing outside the plane for the first time. AND all my settings are cranked up to high/max. I have met the enemy, and he is we. All the fighting for FPS on my system (see above) made it worse. Wow. NOW I am going to enjoy this game the way it was meant to be played in VR, with clarity and solid FPS. Your mileage may vary, but I hope not. - Richrach

Settings for i5 12600KF, RTX 4070 OC edition, 64GB DDR4@3600, Pimax 8KX. ***NOT A MAX DOLLAR OR MAX POWER SYSTEM. KEY SETTINGS THAT HAVE HAD THE MOST IMPACT. SOME OF US HAVE LIVES IN THE ANALOG WORLD, FLEW ACTUAL COMBAT MISSIONS, AND DO SPEND EVERY WAKING MOMENT IN A PLAYWORLD. YOUR EXPERIENCE MAY BE DIFFERENT. GOOD LUCK.*** All the following is based on the A-4E module (I actually flew the A-4), Sinai map, hundreds of vehicles and a dozen aircraft. These result in 43-50 FPS on deck, 62+ FPS in flight low altitude, 72 FPS in outside views. Very smooth, very enjoyable. Almost stutter-free (one happens once in a long while and appears to be GPU related.) Computer: CPU = Using Intel XTU - OC to 52P/41E, -0.050 voltage offset, runs at 118 watts in game, well within 125 watt limit of CPU GPU = STOCK, no changes (system is CPU limited, DO NOT MESS WITH OCing GPU) ***THIS SETUP IS CPU LIMITED. REPEAT CPU LIMITED. YOU CAN OC A 4090 WITH THIS CPU AND NOT GAIN A SINGLE FPS. BE SMART, USE YOUR TIME AND EFFORTS WHERE THEY CAN GET YOU AN ACTUAL BENEFIT. DID I MENTION THIS SYSTEM IS CPU LIMITED?*** BIOS = Hyperthread-off, all else stock (Hyperthread is a huge deal, probably 5-10 FPS impact in this single setting. WILL SLOW DOWN the processor in other tasks outside DCS) Pimax 8KX = Single lighthouse, 72Hz, FOV - Normal, Render quality - 1.70, Fixed foveated rendering - Balanced, all else unchecked PimaxXR Runtime = Prefer framerate over latency - checked, Enable Quad views (get it, it is amazing) - checked NVIDIA = Anisotropic filtering - App controlled, Power management - MAX perf, Texture filtering - Anisotropic filtering - On, Texture filtering quality - High performance, Texture filtering trilinear - On, Virtual reality pre-rendered frames - 1, Vertical sync - Fast (These are the settings I have tested and work for me) DCS: OFF UNLESS OTHERSWISE STATED Resolution - 1920-1080 Cockpit - 1024 Upscaling - DLSS Sharpening - 0.5 Textures - High Terrain textures - High Shadows - Med Visib range - Med (big one) Clouds - Standard Water - Low (This may or may not have a big impact. Testing ongoing) Heat blur - Low (If you do not have heat blur on, you clearly have never seen actual aircraft spinning up close. You do not even deserve to even be near simulated airplanes.) Clutter/grass - 760 (personal preference for visuals in Sinai map. Does not seem to have a great impact on FPS) Forrest visibility - 100 Forest details - 1 Scenery details - 1 Preload radius - 75000 Chimney smoke - 1 Max FPS - 300 (Let Pimax deal with this. Ignore it in Nvidia as well) Anisotropic filtering - OFF (High settings in terrain seem to take care of this, not needed) Terrain objects shadows - Default VR pixel density - 1 (You will set your increase in density in the Pimax controls. This is huge) Enable hot plug - off Use DCS system resolution - checked ____ I hope this helps someone out there. Good luck in the New Year. Be safe. Have fun. Get outside and breathe the fresh air once in awhile. - Richrach

The satellite setting in the F10 map in the Syrian campaign renders water, specifically lakes, as brown. Google earth shows satellites see water as blue, green, or shades thereof. Sure would be nice to be able to use satellite view to distinguish between water and the ground around it. - Richrach

WipeUout, you are exactly right. I have FFR off in Pimax. It was a previous set of testing I took the data from. Everything else was correct. Thank you for being so diligent! Magnum!

Darkman, I envy you the 4090. By the time I can afford one of those they will have brain implants and computers will be a thing of the past. With my CPU manually set to run all cores equally in power there are zero issues with CPU bottleneck. CPU max load across the chip is 73-75%. The GPU runs above 90% most of the time, usually at 98%. VRAM is maxed out (8GB) and I think this is the real culprit. How much of your VRAM is being used? Is it near 100%? I am going to hold out for a 3090 with 24GB RAM. This is probably the real solution for DCS at this juncture for me. Candygram!

Input on a moderate system that may help others without the big pockets needed for a RTX 4090 GPU. System: i5-12400F (Overclocked to base 4GHz, manually set to all cores, turbo mode off) RTX 3070 (Overclocked GPU 2115Mhz (+200MHz), VRAM overclocked to 8Ghz (+1000 MHz) 32GB DDR4 RAM Pimax 8K+ (No base stations, 9-axis) MSI Z690 Pro WiFi DDR4 Motherboard Results: Syria map, heavy mission with high load of aircraft, vehicles, and static objects Cockpit view (A-4 Skyhawk) - 43-51FPS (Lower values only momentary. Majority of time is 48-50FPS) External view (F2) - 36-51FPS (HIGHLY dependent on what one is looking at. Planes in flight upper numbers. Helos on ground or aircraft taxiing lower range FPS) Vehicle view (F7) - 35-53FPS (HIGHLY dependent on what is going on in the view. Simple vehicles/static objects, no problem. Combine moving vehicles, explosions, firing, flames, aircraft flying overhead and the frame rate hits the lower end occasionally.) NVidia Settings: Image scaling - Off Anisotropic filtering - App controlled (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Antialiasing - FXAA - Off Antialiasing mode - App controlled CUDA- GPUs - All Max frame rate - Off MFAA - Off Texture filters (in order) - Off/Allow/High performance/On Threaded optimization - On Triple buffering - Off Vertical sync - Off VR pre-rendered frames - 1 OpenComposite settings OpenXR OXRMR settings: Rendering custom scale - 115% (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Motion reprojection - Disabled Pimax settings: 72Hz FOV - Normal Render quality - Custom 1 Fixed foveated rendering - Balanced Parallel Projection selected OpenXR toolkit: Upscaling/sharpening - CAS Sharpening - 50% Fixed Foveated Rendering - Off (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Turbo mode - On Post processing - On DCS settings (off unless otherwise listed): Textures - Medium (cannot see more detail at high setting) Terrain - High Water - Med Visibility range - Med Shadows - Med Res cockpit - 1024 (really cannot tell difference between this and 512) MSAA - 4X (GREATLY reduces shimmering in headset. I have tried all combinations of rendering levels in DSC/Pimax/OpenXR, SSAA, MSAA. For whatever reason, this seems to work best on my system. ***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Clouds - Low Clutter/grass - 500 Forrest Vis - 50% (Syria map has WAY more trees that the Golan Heights has in reality. I turned this down just to make it more realistic. Higher settings do not seem to impact FPS. Literature indicates the trees are actually still there at lower settings but not rendered to the screen) Forrest details - 1 Scenery details - 1 Preload radius - 100 Chimney smoke - 1 Anisoptrophic filtering - 8x (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Terrain object shadows - Flat Rain droplets - On VR density - 1.0 Force IPD distance 40 (I flew the A-4 in real life. Setting this to 40 gives my eyes the same perspective I had in the actual cockpit. Your mileage may vary) I have spent many hours working all the settings. Much of what goes into making DCS perform at its best is FM (Freakin' Magic) and pure trial and error. Take my inputs with a grain of salt. I hope these give you at least a good place to start from. Good hunting, Richrach USN(ret) Actual aircraft flown: TA-4J, F/A-18, F-16, B-52, SH-60B, SH-3, E-2C, EA-6B (among many others)

Ejections for aircraft hit by anti-aircraft or missiles is almost instant in the game. This is not realistic at all. It takes time to recognize an aircraft is damaged beyond saving and make the decision to eject. A pilot will instinctively stay with an aircraft and try to save it as his (or her) initial reaction. Ejecting equates to failure in the mind of a military pilot, and is the last resort after the last resort. U.S. Navy manuals list a 1.2 second delay from the time the decision to eject is made and actually actuating the seat. This does not include the time leading up to that decision. A 3-5 second delay would be far more realistic in DTS for ejections from jet aircraft operated by the sim. - Richrach