Sporg

You're welcome, and thanks. ???? The biggest work I felt was finding my way, and optimizing the game to something I liked. Writing it down was just nice, so that others could use it. ???? I don't have your issues with text labels and green crosd. I get the usual text labels when pointing at something with the controllers, that's all.

That's normally what has been recommended, yes. But I tested it thoroughly, and the best result was what I described in the guide. I have tried 1.6 in game and 1.0 in the Tray Tool. Here the image is limited by Quest Link that does not pass the full quality to the headset. I've also tried 1.6 in Tray Tool and 1.0 in game. Here Windows is clear, but DCS seems to be not as sharp as it can be. I have also tried a slight difference ie. 1.2 in game and 1.3 in the headset, or the other way around. Again the image got worse and I hardly gained any performance, actually it felt slightly worse. I don't know if it is because that the identical setting is simply easier for the system to work with. I can only guess at that. But about sharpness I have come to realize, that using a small setting twice is in fact like using a sharpening filter twice. And that I have had good success with when working with image treatment for my work: Using a gentle filter twice gives a better result than using a harder filtering once. It could be a similar phenomenon going on here. But test it for yourself, preferably on the ground. I have tested both for image quality, but also tested for how far away I could see details and small objects. And the described setting was the one that let me see the clearest and the farthest. Edit: It can also be that it is simply just the best compromise between having a sharp game and good transfer of the image via Link to the headset. :)

Hi Emacs I have made a guide to my setup and optimization of the Quest in DCS. I have uploaded it here: https://forums.eagle.ru/showthread.php?t=276595 Maybe it can be of use or inspiration to you.

Hi all I've made a guide for setting the Oculus Quest up for use in Windows and DCS, and for optimizing the Oculus Link driver. I hope it can be of help to fellow Quest users. There's also tips on how to use the Oculus controllers in DCS instead of using mouse. DCS has some useful default key binds for them. I've been using Oculus Quest for a while in DCS, and succeeded optimizing it using Oculus Tray Tool to get a picture and performance in game that I'm satisfied with. You can optimize the video stream sent to the Quest over Link by adjusting Encode Resolution, Default Super Sampling (Pixel Density) and Distortion Curvature (which is a kind of sweet spot sharpness setting), provided you have a powerful GPU. I don't have the highest fps, but I can see everything pretty crisply, and can see objects pretty far, ie. Supercarrier from the air, and aircraft approaching. With an i7 9700K, GTX 1080TI OC and 32 GB 3000 MHz RAM I have around 36 fps in average, down to 30 fps on Supercarrier with Tomcat, or in MP with Gazelle, with quite high settings. I am using an Anker USB cable, the one recommended by Oculus. The most important thing I found is that it seems to look the best, with the best view of far away objects, with SS in Tray Tool and PD in DCS set to the same value. But feel free to experiment for yourself. My focus has been on graphical quality more than on fps, your priorities might of course differ. :) The guide can be downloaded below, and I add some screenshots to show the result of my settings in game. There's links to download of Oculus Tray Tool in the guide, and also a link to Oculus' page with their recommendations for Link resolution settings. Using the Oculus Quest for DCS_Rev2.pdf

Thanks for that video. It was very interesting. What I can say is just that it emphasizes exactly that the OLED displays in the Quest are better able to show black, so that fits with night flying looking good. Another thing is, I think that video may have been made before Oculus introduced overriding the default Oculus Link Resolution, which was done 12 days after this video. ;) https://forums.oculusvr.com/community/discussion/83561/oculus-link-resolution-with-v12 These tweaks greatly enhances Quest clarity, especially if you have a powerful GPU that can run it. I have made a guide on running Quest via Link, and getting high graphics quality in DCS (but not high frame rates), which I plan to post in here soon. The difference from standard Oculus settings is quite remarkable. About frame rates, you are in to something: Flight simulators are have traditionally been fine with relatively low frame rates, the more important thing here is that they are consistent, so that the game runs smoothly. Using my quite high settings I get very good details and scenery in DCS with Quest, and it runs smoothly at 30-36 fps most of the time, even on Supercarrier in the Tomcat, two fps eating entities in the game.In sim racing and first person shooters such a low frame rate would hardly be acceptable, but it works fine in DCS.

Thanks, I'll check that.

Ah yes. Then the canopy ejection happened earlier: I got so frustrated after finally having refueled and rearmed, and then the damn canopy jettisoned, that I drove over the side after that. :D

Galinette, that is simply not true. There must be a problem with your setup. I have used the Quest during night time and it looks fabulous.

I have a recurring problem with the canopy ejecting by itself when I enter the aircraft. I have experienced it when I start a mission, and now also when I entered the aircraft from checking key binds. I link to two tracks. In the first one, the canopy blows the second I start the mission (SC CASE I): https://www.dropbox.com/s/rmz45vgy3sv01os/F-14%20SC%20CASE%20I%20canopy%20blows%20entering.trk?dl=0 In the second one (SC Qual) I complete a launch and a landing, parking and refueling, then, after checking key binds, the canopy blows immediately when I click Cancel to return to the aircraft (time around 15:24:27 I think): https://www.dropbox.com/s/p0csnskdz94b90e/F-14%20SC%20qual%2C%20launch%2C%20land%2C%20AI%20parking%2C%20canopy%20blown%20on%20return%20from%20config.trk?dl=0 I link here to picture of the second mission debrief (I didn't manage to save it): https://www.dropbox.com/s/bx3vjeejh15oicg/Screen_200601_132837.png?dl=0

I have experienced weird AI behavior as well, in the F-14. After wingman landing on carrier, time 15:15:18, he proceeds to drive *through* the crane truck and the parked aircraft when taxiing to parking at the end of the carrier. No damage though, it just goes through everything. Track attached here: https://www.dropbox.com/s/p0csnskdz94b90e/F-14%20SC%20qual%2C%20launch%2C%20land%2C%20AI%20parking%2C%20canopy%20blown%20on%20return%20from%20config.trk?dl=0

A good summary of the Reverb from one with high IPD like me. https://www.reddit.com/r/WindowsMR/comments/bzeg9c/hp_reverb_initial_impressions_flight_sim_use_with/ To sum it up: He can use it when looking straight forward, but lose out on FOV and on seeing the edge of the display and getting blurriness on one eye when looking to the sides. The IPD range adjustment in the headset is simply not large enough. Additionally I've seen reports on some people getting eye strain when using it for longer periods. (and this makes it tricky: You can test it, and feel it's fine, but only discover problems when you really start using it.) These problems made me opt for the Quest, even if I would love a higher resolution headset. I hope they put better IPD adjustment in the next generation of headsets, and/or better resolution in the successor to the Quest.

Good summary. Add to that: - At high resolution (4K here), while you get a glorious view, everything is much smaller, and especially in helicopter it's difficult to judge the distance to objects. The result is, in VR I can fly at treetop level and below, following creeks and railroads running between and below the tress with ease. At 4K I am scared to fly so low, and so close. - At 4K you have the glorious view, but sometimes, amazingly, and counter-intuitively, you sometimes have *bigger* difficulty spotting objects (other aircraft etc.) than you have at lower resolutions. (This is an old and well known problem with DCS) Even if I don't have much problem flying with monitor plus TrackIR, even after starting with VR, I find myself doing it much less. It looks better, but the feeling of not being able to judge distance, and less 3D structure on the ground makes me fly VR more. See my reply above. While the lower resolution might give you problems with proper ID of the objects you spot, you actually see them much earlier. This is an old and well documented problem/dilemma in DCS. While high resolution makes you able to see the smallest objects far away, strangely some objects remain invisible until very close (so close that they are a great threat to you before you even see them). I tested it myself when I got a 4K monitor, and some modules were invisible well inside my normally visible range. It differs from object to object as well: Some works fine at high resolution, some not at all. - PS I'm using Quest with USB link cable due to having high IPD, but it works absolutely fine. I look forward to a new generation with better resolution, and hopefully still mechanical IPD adjustment, or different headsets/lenses for people with different IPD range.

I am using the Oculus Quest with USB cable link to PC. It has mechanical IPD adjustment up to 71-72 mm. That works well for me. I also needed mechanical IPD adjustment, since mine is 70 mm, and Quest seemed to be the cheapest option of this generation that had mechanical adjustment.

Bug in Gazelle Failure/Damage effect @f410 There's a bug in the Gazelle Failure/Damage effect. I tested yesterday with a new DCS/SimShaker beta setup on my new PC. There was a constant vibration when I entered the cockpit, by unchecking effects one by one, I found that the major culprit is the Failure/Damage effect, it's on constantly. Also, Main Rotor Whirl High does not seem to react to adjustment of Strength. Other modules reacts correctly to both. There also seem to be another vibration I can't find where comes from. It did not go away no matter which effects I switched off. I have switched off G-feeling, so it shouldn't be that. I am using JetSeat and SimShaker latest beta. DCS Open Beta, didn't test release version. But it's an old problem.

I can confirm that this works. I just set a new PC up with DCS and did this exact trick to all my controller key binding files. You need to do it separately to all the controllers you have, joystick, throttle, rudder pedals etc. It's tedious, but you get all of your old settings back.

Tic-Tac, GAMETRIX KW-908 only have 6 vibration zones, even if it has 8 motors. The 4 bottom ones are combined in 2xleft and 2xright. Then you have 4 individually controlled motors in the back.

As title states. In the (new?) landing mission, you're left on approach to a runway. I landed there, only to immediately being crashed into by two aircraft taking off in opposite direction.. Lol.

Hi all The project is not dead, but VH-Rock has gotten so much to do in his life, that he sadly rarely has time to do skin work anymore, if at all. I have some screenshots and a video of it in its current state, and VH-Rock has said that he might upload it as is, before finishing it at a later point. From older version of DCS: From video recorded yesterday, 08-11-2019: Video here:

Thanks BigNewy I'll test again and see if I can get it to work now. FWIW I have been very precise with the dial (I can turn mechanical clicks off on my mousewheel, so the wheel moves freely), but I'll give it a go again. Edit: Okay, I tested again, and it seems to work now. I don't know if something was done on your side, but at least it seems to finally work. Huey now picks up the 490 MHz beacon as it should, >300 feet over Batumi. Thanks for testing and guiding. :thumbup:

Thanks. What I mean is, I was very precise with the dial, and identified the right beacon, also from morse code. But its behavior in the Huey is different than in the other aircraft. It loses directional ability much closer to the beacon than in the other aircraft. As I described above. Also, should the needle jump when it doesn't have proper directional ability? Because that happens as well.

Well, does the Huey have a particularly weak ADF? Since the other aircraft I tried did not behave the same way? (Gazelle, L-39, C-101) Also, I tuned in to the beacon by flying close to it, then extended to Batumi without touching the ADF, to see where it actually cut out. To me it also does not make sense that over the sea, with line of sight to the beacon, I still needed to get over 1500 feet altitude to get direction? The other aircraft would catch it at a few hundred feet altitude, even while still over Batumi? Thanks for investigating by the way.

I believe you may have your brake axis set up wrong. If you don't invert the axis, it is on full brake when you don't touch the pedals, but is released when you press them. That could give the effect you describe. Check if the pedal in the aircraft follows your pedal when you press it.

It should be possible, but it will not be reversible like the other solution: The two detents consist of two rubber plugs on the throttle axis, If you cut the one of them off that represents idle detent, you should have it the way you want. I've shown them here in the orange circle:

Thanks BigNewy Let's hope they take notice and find a fix once and for all. :)

As title says: If Wake turbulence is on, performance may drop significantly (down to unplayable) if there are many big aircraft in the mission. I got the suggestion from another user when complaining about the "Bomber Intercept" mission that comes with FW 190 A-8. The FPS would drop to near single digits when the bomber formation came near. Switching off wake turbulence fixed the problem immediately. Since then I have seen the problem and the fix confirmed other places as well, also in other types of missions with many big aircraft. Thread here: https://forums.eagle.ru/showthread.php?t=242955 (It says "Can't Reproduce" but I think moderators/devs should test again, now that the culprit is found.)