Spectre1986

Vulkan made a MASSIVE difference in my XP11 VR FPS and overall experience on day one, similar experiences were widely reported. I'm not sure what was wrong with your system if you're talking about the same sim...

Just FYI for anyone that's not aware, CPU and GPU utilization percentage tell you somewhere between "very little" and "nothing". You want frame times from the GPU and the frame times from the CPU+RAM, lower are better. You can get these times with a number of free tools like MSI Afterburner (enable it deep in the settings), with paid tools like fpsVR, or even built into DCS. I believe the default is RCTRL+Pause twice, it'll show a block of data. IIRC GPU frame time is just called "Frame Time" (shown in the first line or near it) and CPU+RAM frame time is near the center of the block of info and is labeled "Simulation". You will need a very complex single player mission or busy multiplayer server to realistically test CPU+RAM performance in DCS. Make sure you add things like MRLS, cluster munitions, and dozens (hundreds with Raptor Lake?) of ground units moving off-road to really tax CPU+RAM. Quick start or simple mission testing is pointless and will give bad results. Also, disabling hyperthreading and the little cores is always worth testing with DCS. Obviously, overclocking is always helpful too, but more limited with Raptor Lake. I'm very close to upgrading but need the data for VR. Thanks, in advance. i7-8086K@5.1Ghz 32GB@3.6GHz 3090@stock 2TB NVMe Reverb G2 Index

Just FYI everyone that's not aware, CPU and GPU utilization percentage tell you somewhere between "very little" and "nothing". You want frame times from the GPU and the frame times from the CPU+RAM, lower are better. You can get these times with a number of free tools like MSI Afterburner (enable it deep in the settings), with paid tools like fpsVR, or even built into DCS. I believe the default is RCTRL+Pause twice, it'll show a block of data. IIRC GPU frame time is just called "Frame Time" (shown in the first line or near it) and CPU+RAM frame time is near the center of the block of info and is labeled "Simulation". You will need a very complex single player mission or busy multiplayer server to realistically test CPU+RAM performance in DCS. Make sure you add things like MRLS, cluster munitions, and dozens (hundreds with Raptor Lake?) of ground units moving off-road really tax CPU+RAM. Quick start or simple mission testing is pointless and will give bad results. As usual with DCS World, disabling the little cores and disabling hyper-threading are definitely worth testing too. I'm very close to upgrading but need the data. Thanks guys. i7-8086K@5.1Ghz 32GB@3.6GHz 3090@stock 2TB NVMe Reverb G2 Index

Does anyone have a reference to how the 5800X3D compares with any Intel in DCS VR (G2 and Index)? I'm on a: i7-8086K@5.1Ghz 32Gb@3.6Ghz 3090 The i7-8086K is the same as the i5-10600K, so it is still pretty good. I'm planning on waiting for 13th gen\new Ryzen before doing a new build so I'm just curious where my rig lines up.

I had the same symptoms but not as often. For me it turned out to be my windows page/swap file was too small for the servers I fly in. DCS can use 55Gb+ depending on the server. My 32Gb@3.6Ghz wasn't cutting it. My CPU and GPU would flatline and everything would pause for a moment.

I'd just like to report that I am very pleased with this upgrade for my Virpil pedals (with toe-brakes). The install was easy and my helicopter flying instantly improved. The dial gives you the flexibility to quickly add\remove the damper effect at will and actually improves the strength of the pedals, so there isn't a downside with this mod. I highly recommend it for all VIrpil owners! During the install process I even found a couple Virpil screws that had started to back themselves out. It explains the rotational pedal slop I've started to experience. I cranked them down with a couple drops of threadlocker so I don't need to worry about them going forward. 10/10

Hello K-51, I am pleased with the collective I recently purchased from you and I already have the Virpil pedals. Please send the PM so I can submit payment for this mod.

Oh man, I hope it is soon. I just got my K-51 collective in and mounted today. This thing is amazing in the Huey, I can't wait to try it in the Apache! I didn't think it'd make much difference over using my Virpil CM3 throttle as a collective, but it is a HUGE difference!

Hello, Please put me on the list, I live in the USA. PM me with the details, I did not read all 25 pages of this thread but am willing to pay now.

Squadron Name: none Discord ID on MVP Discord: Specter#2182 Contact person Discord ID: Specter#2182 Aircraft Selection: F\A-18C Pilots: USA - Specter

Update issues Trojan Detected by Windows Defender I just installed the update to the Sound Module and the software would not start up anymore. When I clicked "details" on the error window it stated, "not installed". I downloaded the Sound Module beta fresh from the website and tried to install it. Windows Defender popped up and deleted what it claimed to be a trojan. I installed the standard non-beta and it seems to be working again.

How does the IFF without a lock work? I didn't see anything in the manual and I can't see any difference between the friend/foe symbology when I place the bracket over the radar contacts in a test...

I year later and I did a different, much better test just now; First I reset my 8086K to stock. I ran DCS in VR testing in the A-10C quick start - hard mission. I used Oculus Tray Tool to turn off ASW. I enabled the TGP then gunned the trucks and AAA at the first waypoint in one pass. Then I killed all four vehicles at the second waypoint, also in one, very low, gun pass. All keeping an eye on the FPS the entire time. After a few of these benchmark runs I was not satisfied with my performance, rarely dipping to 40FPS, even 35FPS once with smoke, explosions, fire, gunfire, units spawning, voiceover triggers, etc at my current settings. Note: Multiplayer is MUCH more demanding on the CPU than this. Next I overclocked my CPU to 4.7Ghz, all cores, and ran the same test a few times. MIN 45FPS, AVERAGE 75, going up to 90FPS every now and then (again, with ASW off). Finally I overclocked to 5.2Ghz and ran the same test a few times. Almost solid 90FPS, going down to 75FPS every now and then. This is with an i7-8086K, 32GB DDR4@3.7Ghz, and a 1080 founders. Task manager shows one core jumping up to 75-80%, and one sticking around 40%. All others are idle. *The max GPU utilization climbs with clock rate* DCS does need better optimization. I would probably be getting 90FPS all the time if all my cores were utilized and it wouldn't take 4.7Ghz to feed the 1080 fast enough for it to max out. 2D performance does not reflect VR performance. I'm no expert but I've read that every object costs the CPU double in DCS VR. The engine doesn't just render the same object from two different angles, it creates two different objects. I've read that flight sims are especially hard to multithread and I believe it. The best multithreaded flight sims are the worst flight sims (FSX, P3D) and the poorly threaded ones are the best (DCS, X-Plane 11). Hopefully someone figures it out or Vulkan does more than the experts expect it will.

I've done some further testing in regards to restarting a mission too quickly causing SSA to stop working. It doesn't always happen, but I have found that it is much more likely to fail if I use Left Ctrl + R to do an instant restart of the current single player mission. I only fly in the Rift so that may be a factor somehow, I just haven't tested in 2D. This happened on both my old i7-920 computer and on my new 8086K rig. I've also repaired DCS and reinstalled SSA on the new rig and it persists. It is easy to avoid, at the end of a mission I press Esc and wait 1-2 seconds for the vibes to stop before ending the mission. When I get to the debrief screen, I wait another 1-2 seconds before clicking "fly again". It would be nice to be able to use Ctrl+R to restart as it is about 20 seconds faster because it skips the debrief screen and the loading involved there.

I have noticed that mine will stop shaking if I restart a mission to quickly. It seems that as long as I give it 3 seconds or longer before clicking "fly again" the vibes keep working.