Gunnergolly

In VR it crashes everytime for me. Starting a quick action mission it half loads the cockpit before it crashes, loading from the mission editor it crashes four seconds later after pressing the "fly" button. In 2D it works fine.

Where's that five years gone !!!!!. No wonder all my original control bindings don't work anymore.. Still a great airrcraft to fly..... at least that hasn't changed ...

Thanks for your replies guys. It was due to using an old mission file, deleting the aircraft and adding a new M2000C fixed it.... It's been a very long time since i last time i played this aircraft, there's been a lot of changes in that time... i'm sure the countermeasures panel used to be on the left side of the glareshield !!!. Thanks again ..

I've been messing around with the M2000C and In the ME i pick one of the Eclair_M configurations to add more chaff/flares to the M2000C. The in game the kneepad says that i have those addtional flare/chaff quantities loaded but in reality i am only ever able to fire off a maximum of 16 flares no matter which pod configuration i choose in the ME. If for instance i choose to have an additional 16 flares in the Eclair-M pod, those 16 flares are fired off ok but the aircrafts internal flare dispencers have been disabled. The additional chaff quantities seem to working ok as it first empties the Eclair-M pod and then switches over to the internal chaff dispencers. I have disabled all mods and cleaned/repaired my DCS installation.... made no difference. Is this a known problem with the eclair pod or are am i doing something wrong ??....... i've read the manual but still non the wiser..

I didn't know that about the two different codecs. That would explain when testing my QPro using AIrlink it ran smooth.... because it's using the H.265 codec I've no idea why it's so stuttery when using the link cable with the H.264 codec .... bearing in mind that i have tested it with three different link cables, two powered ones and the expensive Oculus one..... so it's not the cable. Ive also tested the three link cables with the link speed tester and the results were all similar. Yeah i can only turn my bitrate up to a maximum of about 230Mb before the video breaks down using the H.265 codec over link. On the Q3 i've had my bitrate up to 940Mb, the sound stutters but it works, so my Q3 is happily using the H.264 codec. It get's me wondering that i must have a setting wrong somewhere because i'm able to reach whatever refresh rate i set in the Oculus PC app, but it's just not quiet syncing/locking in.... almost like i have two ASW's fighting each other causing a slight stutter and fluctuation in frames. It's a mystery with the QPro ???...

The Q3 has been the easier headset to get up and running.... it always just worked for me straight away with very little tinkering required. Initially the problem that i found with the QPro when using Oculus link is that it was constantly stuttering, even through it was achieving the required refresh rate. Eventually i figured out after playing around with the Oculus Debug tool settings that when i changed the Video codec from default to H.265 it started running smooth. Tomorrow when i have a bit of time, just out of curiosity i'll connect the Q3 up to Oculus link and try both codecs and see which one of the two run's better with that headset. I'm also finding that when i use OTT to try and force 1/2 refresh rate it stutters like crazy with the QPro. At the moment when using Oculus link i'm just ramping up the settings/resolution so that my system is forced into using ASW ... it looks good and is pretty smooth when flying the Apache... my RTX 4090 is certainly getting a good workout. Within Oculus Debug tool, i've also tried changing the (PC) Asynchronous Spacewarp to "Force 45fps" ASW enabled/disabled but they have no effect in game and they just change's back to disabled in ODT. I've done quiet a bit of googling and i can't find anything with regards to connecting the QPro to a cable for internet via a ethernet to usb C adapter.... i'm thinking that it maybe can't be done ??... I've had my QPRo for a week now, it's been a challenge (some of it down to my own ignorance i have to admit), but i'm getting there with it now, the eye tracking is working well and it's certainly a nice headset for flight simming..

My preference is to use Virtual Desktop with the new VDXR runtime and it runs well on the Quest Pro wirelessly and looks really good.... However i'd much prefer to use a cable if i could. As good as VIrtual Desktop is it falls down when my system is unable to maintain the headsets set refresh rate (72 in my case) and the ASW method on Virtual desktop is ugly..... not to be used... There is a work around that achieves a smooth 1/2 refresh rate experience with VD, but if what your flying has either a set of rotors or a propeller it's horrible. I've been experimenting with Oculus link for a couple of days now using the above link cable and it's working well now...... however Oculus link is my second choice.... I only use Oculus link when i know that i can't achieve full frame rate reliably, i'e flying Apache over certain parts of Syria. My initial Oculus link experience with the Quest Pro was not good, i was achieving the frames but it was jerky/ghosting effect with choppy sound. I've since discovered in the Oculus Debug software that if i select the H.265 video codec than it's smooth. When using my old PICO 4 or current Quest 3, both headsets allow(ed) me to turn the headsets wifi off and use a cable that supplies both power and internet via a ethernet/USB hub instead... it works really well..... compared to wireless it boosted my connection by about 50%. Is it possible to connect my Quest Pro directly to my router via an ethernet to usb C convertor ??. I'm using the one below which has proven to be very reliable. https://www.amazon.co.uk/dp/B08NXS46DN?psc=1&ref=ppx_yo2ov_dt_b_product_details

The Quest 3 allows me to turn off the headset's WIfi and instead use an ethernet to USB C adapter via a long cable to supply power/internet to the headset. I've tried doing the same with the Quest Pro, the power side is working, but it's not recognising the internet connection..... is it possible to supply the internet to the Quest Pro in this way ??.

I've not had a lot of playtime on the Quest Pro at the moment. However my initial thoughts are that in terms of reading the Hornet's MFD's, cockpit labels, etc etc the Quest 3 has the slight edge but that said .... barely. Where the Quest Pro has the advantage is that the view through it's lenses just seems more "panoramic", more natural feeling and has better vertical FOV..... i oversample using XR Toolkit and i'm having no problem reading the MFD's.... even if i turn DLSS on. The view through the Quest 3 lenses is equally beautiful, especially if you have the horse power to drive it, nice contrast and colours but i don't know how to explain it, kind of feels like your view is slightly squashed together ... To be fair i think once a comfortable aftermarket soft facial interface becomes available it will make a world of difference. ... out of the box comfort of the Quest 3 is awful.... i have an elite strap, but still using the original face gasket at the moment. Performance wise, i can't offer you numbers but the Quest 3 on my system performs better than the Quest Pro when using Qculus link, with less audio/graphical stuttering ... however to be fair i need to spend time with the Quest Pro tuning it on link, it's still very early days yet as i have been to busy trying to get the damn thing to work !!!. The Quest 3 on Virtual Desktop with the new VDXR runtime runs beautifully with a wired USB C internet connection, the Quest Pro running on VIrtual Desktop wirelessly also appears to be running well too.... i'd prefer a hard wired internet connection.... but it is what it is at the moment.. On the Quest 3 using Fixed QVFR my system is rendering 57% less pixels, this compared to if i were using the same resolution over the whole view without QVFR installed. With the Quest Pro my system is reducing both the "horizontal and vertical focus sections" parameters from 0.5 to 0.15 in the QVFR user settings.cfg file my system is having to generate 73% less pixels. I can't give you performance figures for comparison between the two headsets, but in terms of how smooth they feel when flying.... it's hard to discount either of them...their both excellent headsets... and i'll be keeping both .. If my interest was purely PCVR flight simming ... then personally i would choose the Quest Pro, the view through it's lenses in DCS world is beautiful and just has the feeling of depth.. Hope that helps...

Sorry for the long post, but i wanted to provide details on how I managed to finally get eye tracking working on my Quest Pro up and hopefully I might just save somebody else hours of frustration in the future. The fact that i was expecting to see a "Developer mode" toggle switch in the mobile Oculus app headset settings menu after successfully creating a developers account threw me. We’ll I’m happy to say that I finally have eye tracking up and running on both Virtual desktop and Oculus link. My previous post with it’s choreographed steps didn’t quiet go according to plan as I could not create a new user account when doing the initial headset setup after factory resetting it. Instead, I had to create a new Meta account online and then assign my Quest Pro to that new account…. Which wasn’t easy as I had to jump through a few Meta hoops to get there… However, the new account didn’t work either so Phantom711 was right when he said in his post that he thought that my original developer account was ok and I ought to maybe look elsewhere….. However at least I had proven it beyond doubt now that it wasn’t my original developer account at fault…. So I deleted my second account, paired my Quest Pro to the original account and started looking elsewhere. Concentrating on Virtual desktop first, previously I was unable to tick the “Forward face/eye tracking to PC” checkbox to enable eye tracking in VD. Following mbucchia VD OpenXT eye tracker setting up instructions I had only enabled eye tracking in the Quest Pro’s settings -> Movement tracking menu. I eventually realised that in order to allow me to enable the "Forward face/eye tracking to PC" checkbox I also had to enable Natural Facial Expressions in the same Oculus movement settings menu as well. Ticked Virtual Desktops “Forward face/eye tracking to PC” and it stayed on, tested eye tracking using mbuccia’s OpenXR Eye tracker app and it was working perfectly. Moving on to Oculus link next, so I turned on the “Developer Runtime Features” and “Eyetracking over Oculus link” switches on the Oculus PC app in the settings -> Beta menu…. but the eye tracking was not working when tested. Did a bit of googling and it said that on the phone app the under headset settings the “Developer mode” also had to be turned on. I still don’t have the “Developer mode” option available on my phone app under the Quest Pro's "headset settings", I only have “Debug mode” available, so I turned that option on and the Oculus link eye tracking started working. When I tested Oculus link a couple of days ago, I wrote that the performance was awful, so yesterday, I uninstalled the Oculus app deleted anything Oculus related in the Local, LocalAppData, LocalLow, Roaming folders located in C:\username\AppData. Used CCleaner to clean the Registry and then went in to the registry using Regedit and manually deleted anything remaining that said Oculus…… Reinstalled the PC Oculus app, tested again and now have good Oculus link performance…. Still needs tuning but at least it’s running smooth now. My next challenge with this headset is to find out if I can run it use a wired internet connection like I can on my Quest 3 using my ethernet to usb C adapter which also supplies power to the headset when using Virtual Desktop….. however that's for another day…. I’m just going to enjoy playing with my new Quest Pro now…..

I'm probably making a complete meal of it as i'm just guessing here, but i have to do something as it's not working.... the whole point of me buying the Quest Pro was to use Dynamic QVFR .... and i can't at the moment !!!. Originally in the good old days a few years back i imagine that i would have created a developers account using just my Oculus account ..... unfortunately it's grown arms and legs since then now that Meta and facebook have got themselves involved..... What could possibly go wrong ........ We'll see what happens ....

Thanks for your settings, i'll give them a try later... I normally use Virtual desktop which works really well for me providing i can maintain the headsets refresh rate..... only time i use link is for the Apache when playing on either the Syrian or Marianas map when i need to use ASW. My first challange is to get eye tracking working, i need to get the toggle switch in "developer" mode in the mobile app to appear. I've hit a brick wall at the moment with my current Meta account not playing ball, so will try markturner1960 advice and create a new account from scratch. Not exactly sure how he did it but i am going to dedicate my Quest Pro purely as a flight sim PCVR headset with only Virtual desktop installed. So my plan of attack tomorrow is :- 1) Factory reset my headset. 2) When i power up the headset i'll set up a new account as a first time Meta user using a different email address. 3) Try and avoid tying in my new user account with facebook if i can.... my current Meta account is already associated with facebook, not sure how that might effect my new account. 4) Pair my headset with the mobile app. 5) Sign in as a developer (https://developer.oculus.com/manage/organizations/create/) using my new email address and password. 6) Create a new developer organisation using the method in the Youtube video below and verify it by whatever means. 7) Go to the headset settings tab on the Meta mobile app and hopefully the "developer mode" toggle switch will have magically appeared..... i hope. It's been confirmed by Phantom711 that my current Developer account looks like his and should be good to go. Hopefully doing the above will help to establish were the problem lies with not been able to enable developer mode on my mobile app. If createing a totally new account dosen't resolve the issue than i'll have start looking elsewhere.. That's my plan anyway.... any suggestions are always welcome...

Yeah i really want the Quest Pro to work out, but we're just not getting on very well together at the moment :)... I've posted my link settings, i have a dcs profile dedicated for the Apache which is locked at 45 so that i can achieve smooth frames when i'm flying on the Syrian map. They work well for the Quest 3...

Yeah i could maybe do a factory reset of the headset and create a new account as a totally new user totally dedicated to this headset . Obviously i would lose all my games and content, but as i only intend to use this headset for DCS i would only have to repurchase Virtual Desktop once i have know that i can turn developer mode on ..... i would still be able to use all my other Meta content/games using my current account on my Quest 3... I tested the Quest Pro on link this morning, i'm not impressed.... F18C free flight quick start mission is awlful, flying over the buildings at high speed i'm getting a lot of ghosting and stuttering..... the sound is chopping in and out and my bitrate is only set at 300. Tested the Quest 3 using the same settings/link cable and it's super smooth and i can turn the bit rate up to arounf 750 before the sound starts stuttering. Virtual desktop is running really good, but another problem with this headset is that i can only use it wirelessly with VD, the Quest 3 and PICO 4 allowed me to turn off wireless and use a ethernet to usb C hub and feed the internet via the cable into the headsets usb port. When i get the time i will try and create a new account..

Guy's just want to say thanks for you help and interest, i'm just going to forget about it tonight. I've spent to much time on it today already....just going play some DCS with it and see how it compares to the Quest 3 :)...... Tomorrows another day...