sze5003

Yes I use the internal speakers. I think to get the best visual quality the Pro has to sit pretty high up on my head like a hat basically. I still have not figured out the correct way to wear it as each time it's adjusted and needs to be taken off I feel like I'm gonna break it if I don't loosen the wheel on the back to take it off. So I don't think wearing my arctis 7 wireless headset would be too comfortable.

I was under the same dilemma with a G2 and I'm glad I got a Pro. I did buy it new so I can get warranty and I will be keeping it assuming I can get over all the USB issues I've been having. I spent so much time trying third party cables and now using an official link cable and type C port on my motherboard but I have a bit of doubt with this port so I've also been looking at other alternatives. Obviously if I can't figure it out it will get returned sadly. I think once I figure out the correct order of settings to optimize it, will be awesome. Just alone on default settings it looked good in DCs and better than the G2 with the clarity all over. I also enjoy the build quality of the pro. I'm just a little upset that they didn't go with a native display port connection. Relying on USB where you have all sorts of motherboards out there with different varying results for connecting for PCVR feels like an oversight but I also understand it was developed for business and development use, probably not for titles like DCS.

This is what I found too. I think setting it back to 0 would be the right thing to do. Also didn't realize but each time a change is made in the debug tool you need to restart the oculus service. Encode resolution width is output resolution. It's the resolution of image that is actually output to the display. You can change it in debug tool. The default value is 0 (automatic), and the actual value is 3664 (Air Link may be 2880. And These are the max value in automatic setting, so may be lower depend on PC spec or bug). The max launchable value is around 4064 for both Link and Air Link. To apply the change, input value -> press enter -> click Service -> select Restart Oculus Service. Note: According to Aksoy (graphics programmer of Meta), render res 5408x2736 & encode res 3664 are required to achieve 1:1 ratio for Quest2 panel. It requires good PC. Encode res has a big impact on VRAM consumption as well as render res.

Sounds promising. I also have a 4090 and with Link for some reason an encode bitrate of 960 gave me lots of audio stutter. Some people with the same specs can run this but not sure why I cant.

Yea this must have been it for me too. While i was testing DCS out I was launching instant action missions, then exiting, then playing with the encode bitrate. So it was definitely not at 0. I think I need to lower the bitrate down still from 740. It seemed smooth but I swear I had some audio stutter, even if it was very slightly. What instant action mission is the best representation of a test? Also do we need to change encode resolution width ? I was following a video on YouTube and the guy had it set to 3905 but I'm not sure what this does or what it should be in regards to the other variables.

Airlink for me on the Pro was also completely lagging just to get into the oculus desktop environment and this is on dedicated 6e router. I've heard VD is actually supposed to be better in this regard but I guess it's weird to hear it's not.

Would be curious if anyone is trying VD with a dedicated 6e router. I have one but I don't have VD set up yet and I started troubleshooting USB issues after my setup.

I am going to look into a pcie type C card or maybe if I can find one with verticle ports instead of horizontal because my case chassis won't let me plug anything in to the current USB pcie card. The 4090 takes up too much space which only leaves me with one pcie slot free near the bottom of the case. I want to avoid using the type C port on my board so maybe I'll look for a pcie USB C card. (https://rog.asus.com/us/motherboards/rog-strix/rog-strix-z790-e-gaming-wifi-model/) I have two type C ports on there which should be available to do up to 20Gbps but even with the official link cable, only the first type C port reads 2.3Gbps. The second type C port for some reason reads as USB 2.0 and only shows 359Mbps in the oculus speed test.

I'm running 32gb ddr5, 4090 and 13900k. I have a Quest Pro that I got this weekend and spent a long time trying to get it to work optimally with DCS. I also came from a G2. First I would not try air link with this at all. Also if you touched the encode bitrate, airlink will have issues but avoid airlink for DCS. Virtual desktop supports openxr now so you could try that but I have not done so yet. Openxr is now native in DCS, you may still need the toolkit to get it configured. I am not at this step yet but will mess with it later. /topic/318004-dcs-now-supports-openxr-natively/ For the debug tool you will want to increase encode bitrate. I started with 960 and I worked down to 740 but I'm still getting random audio stutters. So I think I need to dial this down by 10 until they stop. In the oculus home PC app under settings I have 90hz selected and the resolution slider is 1.5. Not sure what the max is for your quest 3. Dcs settings are all maxed out except SSO and SSR. I'm using DLAA and no DLSS. Even with the official link cable I get some drop outs or connection issues. Not sure how to resolve this and a third party cable only gave me like 359Mbs in the speed test vs the official link cable attached to type C which gives 2.3Gps but I still had some freezes of link desktop, some disconnects and a bit of lag when you could tell the connection was going iffy.

Had some time to test out DCS last night, granted still had a bunch of random issues. I'm using all high settings in DCS, visibility extreme, civ traffic off, shadows I think are high, everything else besides SSO and SSR are set to high. I think clounds are also set to high or extreme. I'm using DLAA instead of MSAA and the PD in DCS settings is 1.0. In oculus home I have the Quest Pro set to 90hz, resolution all the way to the right at 1.5. Even with no encode bitrate modification I think it looked good, cockpit dials are visible, edge to edge clarity is there unlike my G2, colors really pop too. I made things a little clearer by setting encode bitrate to 740. I have the encode resolution width at 3905 too. 960 bitrate was giving me audio stutters consistently so I tried 800 and it was the same. Even at 740 I think I get some audio stutter but not as much as I got with the previous attempts so maybe I will dial it back by 10 and see if they stop. Can't see what fps I'm getting because I was too busy worrying about the quest pro maintening a proper connection to my PC. A bunch of times between my tests I had Link desktop freeze, I had to restart the oculus service. Sometimes the link cable would lose connection mid flight. I'm using the official meta link cable and from 100% after 2 hours of messing around in DCS the headset was at 88%. I think with some more tweaking I could get the picture i want and a smooth experience. But I'm really concerned about maintaining a proper connection with the cable. It still seems very messy. I don't want to be in a 1.5hr mission and then suddenly get disconnected from Link. Does anyone have a pcie USB C card or is that done that is supposed to be stable? Would that help here not relying on the type C port on the back of my motherboard?

Ok so I went out and bought an official meta link cable. I have at least one USB type C port on my motherboard and this time I get a green circle connection in occulus home and the speed test registers 2.3Gbps. Feeling a little better now I guess I'll return the Kuject cable but i have not tried DCS yealt so no clue if it will keep the headset charged while I'm flying. I'm not sure what to do really, this cable is highly recommended by everyone so I don't have a clue what alternatives will work with all the iffy USB test results I got.

I ordered an official meta link cable and I'll be picking it up soon. That one is USB C to USB C and I have 2 type C ports on the back of the motherboard. I also just updated my bios and will install the USB drivers again. Does the Kuject cable require you to use the Pro's USB C charging cable or can I use any charging cable to connect to the little chipset box on the Kuject? I don't think it should matter. After all the time it took last night to get the pro up and running, because initially it would not find my 6ghz router until I connected to my 5ghz network and let it update the firmware. I figured I could try DCS out but I won't bother if the oculus app is telling me it's connected via link but it's an orange circle not green and recommending I use USB 3 even though I am. If I can't figure it out I guess I'm returning the headset.

So I've got my pro last night and just finished setting it up. I'm using the Kuject connect cable and I can get link to work about half the time. I can't tell if it's the cable or not but the oculus PC app is telling me I should use USB 3.0 whenever it finally connects. The testing speed often says it can not run the test, try again later or when it does work it shows a speed of like 380mb? The ports on the back of my Asus Z790e board are USB 3.0. I also tried a USB 3.1 gen 2 port (red) and it doesn't seem to want to connect either. Are there known boards that the headset doesn't play nice with or should I ask Amazon for a replacement cable?

Perfect because this gives me a starting point to mess around with tomorrow when I get any headset. After all the DLSS testing results my plan was to use DLAA with DFR anyway, probably at 72hz since my DCS settings are almost all maxed out.

The quest 3 does not have the same color pallete as the quest pro so colors will be more muted. You definitely will need to change settings in the oculus debug tool. Increase the encode bitrate depending on your specs, enable link sharpening to see if it helps with the colors..this is for when connected to link cable. Try different encode bitrate and increase the resolution all the way to the max in oculus home. It will be a trial and error until it looks and performs the way you want.

Around the 8:05 mark this guy talks about the bitrate settings and mentions if you have audio issues then you may want to try different values for encode resolution and encode bitrate. He's using occulus tray tool which I dunno if that is still considered the proper thing to use or not. Audio in Spanish with subtitles but it's the only tutorial I found that went into detail.

I've been reading about it but haven't seen any solution that works for everyone. What's the lowest encode bitrate you've tried where you have not had audio stutter? Perhaps it's software related? Is it occurring in other games over link cable too? If not, maybe related to DCS only?

I'm about to get one this weekend and sad to hear that it's still an issue. I wonder if it is related to USB cable and throughput. Has anyone tried for example a USB hub or different ports? People have been saying there's not much difference in 960 bitrate vs 500. I don't think my Arctis 7 wireless will be comfortable with the headset on.

Same I always had to take off the G2 and keep a microfiber cloth near by to clean the lenses and these were prescription lenses too that would still get fogged up. I'll have to order them for the pro as well so I'll start researching which ones are a good fit.

I believe they are different implementations so you could use whichever one you prefer.

Yea the 3 does not have local dimming. I have heard that the dimming helps make night more realistic and I also haven't seen any direct comparison.

Thanks for confirming. I'm still undecided between the quest pro and quest 3 but I figure with the Pro I'll be able to not use DLSS if i dont like how it looks and still get performance from DFR with DLAA instead of mssa.

Others mentioned blurriness with DLSS and QVFR. Do you have it on quality mode or performance?

In fixed mode it does not need eye tracking. It sets it to a static section of the view which you can configue values for.

I ordered the white one to use when I get the quest pro because I was told that it works for that headset without issues. It seems the 3 is more power hungry. I'm assuming you did follow the instructions on the sequence for connecting the cable.