skywalker22

The original cable I got inside the box was USB-C to USB-C, but was Oculus app did not recognize the headset, that's why I went and bought a new one, which seems to be fine. I just have 10fps in each game I start. The point being, When in DCS, GPU does not even starts working as it should (all temps are 55-60degC all the time), so it means there is some other thing which is a bottleneck in the chain. Something it holding my whole system (which is not bad by any means) back, so it cannot run as it should.

I tried Assetto Corsa and Assetto Corsa Competizione, the same thing, stutters as hell. Even less then 10fps. Is it really possible that is the fault in the cable? Although I got this message when I do the USB test in Oculus app.

1st of all, I got the Quest Pro yesterday, and today I wanted to tried it out if it works, that's why I went and bought this 20Gbps cable (the only one that I could get actually near around here), since no way I will get that original cable from Meta in any time short. But I will buy it if needed, of course.

With G2 from 60 to 90. With Quest PRO now 10 fps.

I have EVGA 3080Ti, Intel i7 10700K and MSI Z490 Gaming Edge motherboard, and I am having 10 fps with yesterday's bought Quest Pro!! WTF??? 10 fps in main menu of DCS!!! Previously I had (still have actually) Reverb G2, and fps were in 60-90 range at all times! What is going on with this crap of Meta? I tried everything, even went to buy a new 20Gbps USB-C cable (for additional 20€), and nothing - still 10fps! Windows Oculus app says the connection is established successfully with Quest Pro at cca 2Gbps of bandwidth, so this is OK. GPU does not ever start working at 10fps (temps are at 60degC). So GPU is not doing anything. There must be some bottleneck, but what? USB-C connector on motherboard is capable of 20Gbps, cable as well. I am sure there is some issue here, connection between GPU, motherboard, cable and VR. But what, is now the question for M$. Any tips, anyone experienced that as well?

I would, but my wifi here sucks - don't ask why is that so.

I wrote to Meta, and wrote all what was on my mind. Isn't a shame, that you have to buy a (f*cking) new cable to connect 1000+€ worth equipment? I would assume that cable comes with the box. I had exactly the same issue with I bought Reverb G2 - I had to buy a V2 cable additionally - but HP paid for it, after some ugly talk. Seems that the story repeats ones again. Just don't get it, how they cannot provide the right cable inside-the-box.

Thx. Am I right about the USB-C to USB-C cable which is in the box of Quest Pro, that is only meant for charging, and not for connectivity with Link cable to PC (with at 10Gpps)?

New to Quest Pro, got it today. No matter what I do, DCS does not want to start in VR. Read this and some other topics here, but no luck so far. I am connected over a cable successfully (in Oculus app and in VR headset), but not with the one which came in the box (what a shame, why they give it anyway), but I use one of my own. Anyway, I press Quest Link Rift from Quick settings, then I come to some black page with three dots blinking... and thats it. Don't even know how to come out of this. Then after few minutes I get a message "Quest Link isn't responding", And Close button. And then back to main lobby (image with a house and some waterfalls). --- PS: some progress, I am hearing sound now in DCS when it come to the main page - but no picture, only those 3 white dots are blinking (still). There is an issue with a cable, although I have connected it to USB 3.2 (10 Gbps), Oculus app says its connected to USB 2.0 (360 Mbps). Is this maybe the problem? Might be the cable issue as well.

I thought so, but I better asked. Sorry for a dumb question

Just got my new Quest Pro A question, I had Reverb G2, which requires Windows Mixed Reality. Quest Pro does not requite it, correct? So I can uninstall it?

Is the "Controller Charge Cable" which is inside the box, the same one as this?

Full light blocker?

Does this headset have a full enclosure, that blocks all outside light? As far as I have seen, it does not, it only has 2 side light blockers, but underneath there is still an opening. Does it bother?

Repair will not remove any additional content, CleanUp will.

Remove all the modes and do the dcs repair, then try again. It all works fine for me u know.

ED coded the RL possibility of random hardware error or malfunction. That's why these missies. @Aoi Kazefor more help, please paste your track here.

Read ones again, and again, ... u know Its all there.

2 more things to mention: It was mentioned not to look on the HUD, but what I do, is constantly looking at the air speed of the aircraft (on left side of the hud), and the fuel flow gage, which is just bellow the DED, to keep my aircraft at the same speed as the tanker (+as mentioned before, visual inspection of the tanker and positioning lights on the tanker). You have to be quite multitasking in refueling in DCS, since the boom it self still does not work as IRL, which actually hold you on to it.

You don't need to do or press anything, just position your self back to "center" position by looking at the positioning lights to turn green (up/down, and left/right). And btw, turn fuel state on your DED (press List and then 2 on ICP), so you will know how much fuel is in and how much is still left to fill into your aircraft.

Air refueling TAKES LOTS of time to master. It took me months of almost daily training to master it. Watching videos won't help you much, you need to get the feeling by your self, the feeling of the speed and the positioning of your self underneath the tanker. When you are there, make sure you observe the whole picture so you know if you are at the same speed as the tanker is, and keep an eye on the PDI (pilot director lights) to make sure you are in the sweet spot. Not easy to master, take lots of time. Just keep on practicing. At start try to do that in the straight line, after that you can start practicing also in the turn, which put air-refueling on another level (speciually flying through the clouds).

Sure it does, if you have rel.ang. set more then zero (lets say to default value of 45deg), the 1st release cue will be for tossing. And if you will be flying in level flight, bombs will not be dropped. But you can drop them when 2nd release cue appears after few more seconds of flying (depends of the speed and altitude).

Did you try to set Release Angle (REL ANG) parameter inside Controls (CNTL) menu to 0 degree? By default it is set to 45deg (for pull up).

OpenComposite is not required anymore in DCS?