Phantom711

Hast Du Deine Frage in dem anderen Thread gelöscht? Jetzt sehen meine Antworten etwas aus dem Zusammenhang gerissen aus. Also nochmal: Deine FPS sind irgendwie capped bei 60, Deine Karte könnte mehr. Das heisst aber nicht, dass Du etwas ändern solltest wenn Du bereits ein flüssiges Spielerlebnis hast. DCS ist ja kein Shooter. Du wirst nur so keine wirklich relevante Antwort auf Deine Frage bekommen, weil ja nicht alle headsets 60 oder 120Hz können. Dass ich nicht glaube, dass Du auch nur die 60 FPS in DCS in allen Spielsituationen mit dieser Auflösung hältst, steht auf einem anderen Blatt. Denn da sind wir nämlich bei den Variablen, die Du unerwähnt lässt: welches Flugzeug? Welche Karte? Welche Flughöhe?

Das spielt keine Rolle. Deine FPS sind definitiv irgendwie capped bei 60. Deine Karte könnte mehr, aber das heisst nicht, dass es im Sinne eines flüssigen Spielerlebnisses zielführend wäre, daran etwas zu ändern.

Da solltest Du hier vielleicht lieber ein extra Thema aufmachen, da das ganz sicher keine kurze Frage/kurze Antwort ist. Da gibt es einfach zu viele Variablen. Wenn Du konstant 60 FPS angezeigt bekommst, dann läuft Dein headset vmtl im 120Hz mode mit irgendeiner Form von Motion Reprojection. Ansonsten ist es unwahrscheinlich, dass man in DCS konstant 60 FPS hat. Oder Du hast Deine FPS irgendwo anderweitig absichtlich ausgebremst.

@Keith Briscoe Depends on your level of expectation. Let‘s be honest, this is not the best setup nowadays for DCS in VR. Do you already use a VR headset and just want to swap?

Don‘t worry, you will get this sorted out. I still stick to my point though, that your developer account is probably good to go already and the problem sits elsewhere.

Wait…what? I just googled the exchange rate to Euros. That‘s still 1600 Euros. WTF? Come over to Germany…costs 1200€ new from Meta. Besides you can actually pick them up relatively cheap on ebay (and the likes).

@72Stu Ok…I am curious: What makes you draw that conclusion?

See…just like yours. And I am 100% sure my eyetracking works in DCS.

No…I don‘t have that or at least I don‘t know where I would even find that page as in your last picture. Maybe because I was already verified with my FB account. But how about you just do the Admin Verification?

@Gunnergolly I just checked my Meta App. It looks the same like yours. There is nothing more that‘s gonna happen under the Developer Tab. You should be set. I use QVFR successfully with the link cable. I don‘t know how it would work with VD though.

@Gunnergolly As far as I recall, this is just how it looks and you should be good to go already. Just give QVFR a try now! But yeah…the account thing is very confusing and I wouldn‘t even know where to look for what now.

I know, that it wanted some 2-factor authentication which I apparently already had since I just used my FB account.

No such thing. you have to press the respective Buttons on the AMPCD (lower screen). of course you could bind buttons to those buttons, but be aware, that they could end up having a different function, if the buttons on that display say so. In general I would suggest to interact with the clickable cockpit as much as possible and bind the HOTAS as realistic as possible.

@sze5003 From all the reading, I was aware of that. I have it set to 0…so that it can just do it‘s thing.

@Squatch Could you provide a screenshot or just an photo via cellphone.?

@Gunnergolly Would you be son kind to provide some feedback here, once you have tried the QPro vs the Q3 in DCS? Specifically: Is the higher resolution of the Q3 noticably better when looking at MFDs in the cockpit?

No...don`t know what you mean. Try resetting your OXRTK to defaults. Well....as I said, I am already at "default" which is 200Mbps as far as I know.

@Gman109 First: Hope you get better soon. Sounds good, that you can get back into flightsims. I try to explain: Q3 and QPro can be run stand-alone. How well that works with DCS, I don`t know since I have not tried. It will also deplete the battery rather quick and you can not swap them. So alternatively you can run them with a USB-c to USB-C Link Cable. This is the only connection, unlike your G2, there is no displayport connection at all. I would think, that this is the most common way, thet the Q3 or QPro are used for DCS. Then there is Virtual Desktop (VD)...another wireless way via WLAN which has it`s benefits...but I leave it to others to elaborate further since I have not tried that either. Some other acronyms: OTT-Oculus Tray Tool: Lets you inker with some more settings, like supersampling resolution, framerate, encoding bitrate ODT-Oculus Debug tool: similar to the above. OXR-Open XR: The runtime that DCS uses now for the Multithreaded (MT) version and also for single thread if desired (instead of SteamVR) OXRTK-OpenXR Toolkit: in the context of the Quest referring to the "Open XR Toolkit companion", a tool with which you can also adjust some graphics settings QVFR-Quad view foveated rendering: 3rd party program which allows to make use of the eye-tracking of the QPro. Only renders area in high res, where your eyes are looking...saves some performance. (Note: Q3 does not have eye-tracking). EDIT: As for the cable: The safest way is to use the original Oculus Link cable. Costs 99€ though. There are people that have successfully used aftermarket cables.

@YoYo I play DCS pretty much exclusively...so for the "yeeeeee" of the engines, the "beep-beep" of the RWR and the "brrrrt" of the Vulcan they are good enough and I would rather not want an additional cable hang off of my head. EDIT: But thanks for your info...good to know, that there is an "escape".

Yes...using QVFR.

Yeah...that`s what I meant. 960 is an acoustic stutterfest. So what you are saying is, that using seperate headphones (or speakers) via the audiojack (on the PC) eliminates the problem? Also, since my system is not far below yours: Do you also still have microstutters even though framerate appears to be stable (@72 in my case).

Hi... Using the QPro for about 2 weeks now (with the original oculus link cable). I have tinkered with various settings but actually went back to default Encode bitrate/Dynamic bitrate and still get some audio cutouts. How people run it on 960 encode bitrate is absolutely surreal to me. Anything I could still try to get rid of that? My specs: Win10/13700K/4090 EDIT: To be clear...I don`t see a need to run at a higher bitrate, I simply want to get rid of the audio cutouts.

Ich denke, damit sind eher z.B. F-4B oder F-4J gemeint und nicht die „Feinheiten“ bei der E.

It‘s not like I would definitely know, that the following things would be related…just some stuff that pops up in my mind, that I would check: 1. Do you have „Easy comms“ selected? 2. Do you have a microphone assigned in the Audio options tab? 3. I have not revistited VOIP recently, but as far as I recall, it had to be set up initially somehow…

@BaronVonVaderham I just emailed them about the F/A-18 sticks 2 days ago and they said they would become available around X-mas. I don‘t know for the F-16 stick since I did not ask. I own the „basic“ F-16 stick and I have never „slipped“ off of it…so unless you really desperately need one, I would not go for the more expensive one. EDIT: That being said, I definitely recommend getting the RS stick. I tried it with a TM stick on the FSSB R3L initially, but it didn‘t feel like it was meant for those kind of forces. Also note though, that you need to add VAT to the pricetag on the RS website (as far as I recall).