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.

This bug appears to have been fixed! Finally, over a year later... Can anyone else confirm?

I am unable to reproduce the missing tone bug I spoke of. The volume is up by default so IDK what was going on, maybe the PC restart fixed it... I am still able to reproduce the "gun firing instead of SA" bug 100% of the time. On a positive note, it looks like restarting the mission is all it takes to get it working again (until you select the AA gun anyway). That took a full DCS restart in the past. :thumbup:

Thanks for pointing that out Ramsay. It is odd that it worked without turning it up the first time I launched the game after the update. The update seemed to apply otherwise, I was able to fire both Sidearms without fiddling around between shots. I'll try to test again later. Can you confirm the "gun fires instead of SA if you select the AA gun before switching to the SA" bug still exists for you too? The exact process to reproduce can be found in this thread.

Bug persists, is worse after latest updates After the latest updates, I ran my the same test from the track I linked above. The first try I didn't select the gun at all and I was able to fire both Sidearms without switching or reselecting between. Well that looks like an improvement. I reloaded the mission and tried selecting the air to air gun, then cycled to the sidearm, got a lock, and... fired the gun... Now, every time I load up the Harrier, even after a full DCS restart, the Sidearm has no tone. It will get a lock and fire (as long as I didn't select the A2A gun yet) but it doesn't make any noise at all. I am glad to see that there was actually work done on the Harrier again, keep it up and good luck.

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.

Hi Decoy, here is a link with two tracks showing the bug; https://1drv.ms/f/s!AkI_kvIv4eiMghyLi5CtlD7SB4sh In both tracks I show that the sidearm is able to fire BEFORE I select the A2A gun, and it fails to fire after selecting it. The only reason the first sidearm fires is because I have not selected A2A guns yet. In the first track I fire the A2A gun to make it obvious I selected it before trying the sidearm again. In the second track I simply select the gun (without firing) and then try to fire the sidearm. It is easy to reproduce. Select the A2A gun, switch to A2G sidearm, get a lock, and try to fire. Are you not able to reproduce this critical bug like everyone else?

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.

This bug still persists Would another track showing the bug help? It has been almost a year now and steps to reproduce have been provided. I'm learning not to take a chance on any future Razbam aircraft after this. This is a critical bug that harms the aircrafts capabilities. Please stop future aircraft development until this critical bug is fixed.

Same problem on several rigs. From an old i7 920 OCed to 3.6 Ghz to my new i7 8086K OCed to 5.0 Ghz with a GTX 1080. Solutions are going to map view and looking around the hangar until it goes away. That does it 9 out of 10 times. If it doesn't work, go to the map view and then take your headset off far enough for it to go black, and put it back on. A final option is taking the headset off, in map view, and alt+enter to toggle full screen.

I have noticed a strange bug with the Hornet bringing me "feet wet" so often now in VR. If I line up the center of my vision with a mirror in VR while flying over the sea, the water vanishes. I am left with a brownish low resolution texture of the ocean floor in the eye looking at the mirror. All water in view vanishes, the other eye still sees water, it is very distracting. It does this one eye at a time and I am sure it is caused by mirrors, I can trace around them by aiming with my head and not see the issue until I look at the mirror. If I close the mirrors, the issue goes away. I fly with the Oculus Rift and had this bug on two different computer builds, although it was an upgrade using the same SSD image, I just installed the new drivers and swapped the hardware. This means it is the same install and corruption or errors would carry over. Although, I am pretty sure this issue has persisted through a windows reinstall but not positive on that. I've adjusted my graphics settings and it seems to persist. This bug appears with any mirror in any craft. DCS World 2.5 Beta standalone. Dinosaur VR Rig: i7-920 @ 3.6Ghz, 12GB DDR3 1600, GTX 1060 6GB New VR Rig: i7-8086K @ 5.0Ghz, 16GB DDR4 3600, GTX 1080 Has anyone else seen this and\or know a solution before I start running the repair?

Are you talking about a simshaker vibration bug or something? If you are you talking about the shockwave dancing over the canopy when going supersonic, that seems realistic, details probably provided by Boeing. Speaking of which, I bet that shockwave comes with some vibrations in real life... I wonder what sim data you can use for that f4l0, the speed would change with altitude and atmospheric conditions...

The solution is start the program from somewhere within your appdata folder. It is probably randomly generated so search for "SimShaker for Aviators beta.exe" in your appdata folder. After you run it once from there, the shortcut will start to work. You could also create a new one from there. For anyone reading this.