arparso

No, sadly not. I used MSI afterburner's benchmarking mode to get the numbers and plugged these into LibreOffice Calc to create the graph.

Thank you for the benchmark. Because I'm trying to figure out if switching to Ryzen 3000-series is worth it, I tried it out on my current machine and these were the results: CPU: i7 4790K @ 4.4GHz RAM: 16GB DDR3-2400 (CL 11-13-13-31) GPU: Gainward GTX 1080 GLH Average FPS in low and medium presets did not differ much from yours, despite the slower GPU (my 1080 vs your 1080 Ti). Maybe that's hitting a CPU bottleneck here? In high preset, the slower GPU falls back a bit and in VR it finally gets crushed. You did not specify your pixel density used in DCS VR settings - I had mine set up to 1.3, which is my usual setting in VR gameplay.

Thanks for doing this and providing the track. I'm thinking about going Ryzen, too, so I am always eager to see other people's results in DCS. For comparison's sake, I ran your track file with the same settings on my PC: CPU: i7 4790K @ 4.4GHz RAM: 16GB DDR3-2400 (CL 11-13-13-31) GPU: Gainward GTX 1080 GLH Average FPS is obviously very different (mostly due to GPU, I guess: 1080 vs 1060). Interesting to see how your 0.1% on the Ryzen is quite a bit better despite the weaker GPU.

Just started getting into the Mirage and now attempting to play the campaign. First mission went fine, but second one did not. I got to the "show of force" part and took a few minutes to figure out the countermeasures and locate the ground battle I am supposed to fly over. While on my way to do the "show of force" I already got a message about Hueys arriving shortly, then still dropped some flares over the battle and only got radio silence afterwards. I continued to my current waypoint (4) and then followed the next waypoints until eventually landing at home base again. This "won" the mission, but I had no further contact with Colt and received no TACAN, HSI or ILS training that is mentioned in the briefing. Not sure what I did wrong, but I clearly missed some trigger here!? Also had no F10 radio menu available at that point. ----- And a few more questions/comments: - So far, the kneeboard only shows me the first page with ground setup and countermeasure programs and none of the other pages (e.g. airfield charts). This is annoying for startup, as I have to look up the initial coordinates on the F10 map now (they are not included in the briefing and the corresponding kneeboard page is missing). Is this normal or should the kneeboard actually show more pages? - I found it difficult to locate the ground battle at all (only due to the tracer fire). Some coordinates were given over radio, but they disappeared so quickly, I could not enter them in my INS in time. Since I'm flying in VR, I also could not write them down on paper either. - Countermeasures were not covered in the training missions, I think - so I had to pause and read up on their use first, which took me a bit out of the mission. Other than these issues I had a lot of fun so far. Scenario seems interesting and the voiceover and atmosphere are pretty good :)

"Depth information" means information about the actual position of each pixel in the 3D world. Usually you only have the final 2D image to be displayed on the monitor (or one for each eye in the HMD) and only know each pixel's color. However, you actually don't know the location of the pixel in the 3-dimensional scene that is being rendered. Is the pixel very close to the camera or is it far away? Does this pixel belong to the cockpit right in front of you or is it part of the mountain range dozens of miles away? This information is usually stored in a "depth buffer". It stores the "depth" of each pixel or in other words: The distance between the camera and the pixel in the 3D scene. ASW 2.0 requires the game developers to supply this depth buffer to the Oculus runtime, because the "depth" is required for some of their calculations. Some games or game engines already supply their depth buffer (Unreal/Unity) and will automatically benefit from ASW 2.0. Not sure if DCS does or doesn't at the moment.

Completely agree. Especially everything on the left side console and the right side console is unreadable, even with maximum VR zoom and leaning way down (using a Rift here). This was not an issue in any other jet so far. I can't for the life of me make out the text next to the ICS switch or the master test switch, the hydraulic switches on the right or any of the radio controls on the left. I basically have to memorize all of these for now. I'm just glad that most of them are only needed for startup and not actual flight. The front panels and instruments are much better. This was not really an issue in the F/A-18C, A-10C or any of my other modules, at least not to that extreme extent.

I can't get TacView to record in multiplayer (even when I'm the host) or when playing back the .trk file in DCS. So far it only worked in singleplayer missions. All the export options are checked when creating the MP server. Is there anything else I need to do? And shouldn't it always record at least the .trk replay, when I play that in DCS? Here are the .trk file and dcs log (from letting the .trk play for ~10 minutes): https://www.dropbox.com/sh/794lhsdcaf4y9ga/AABwFZaMRnxvgsAi9nj2dTNHa?dl=0

Can't get this mission to work and I don't know why. The game just gets stuck on the loading screen (after displaying the briefing) and never continues. When trying the Persian Gulf version, the game even outright crashes / closes itself and returns to desktop. Are there any specific requirements I'm missing? Does it not work on current release branch? Content of DCS.log: