-
Posts
268 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by minimi66
-
Used both, one didn't connect to headset and the other connected but said incompatible hardware. I can't get the exact one you have in UK as far as i know? Am thinking of switching GPU's back to my RTX 3080Ti which i luckily still have and selling the 4090. I had better results with 3080Ti to be honest. Thanks for the info though. It was def worth a try.
-
Hi, sorry i wasn't very specific on my post. I bought this: https://www.amazon.co.uk/dp/B0BGHVQNCH?psc=1&ref=ppx_yo2ov_dt_b_product_details on the advice of @DirtyMike0330 In a post he made earlier in this thread. Just to see if it made any difference to Link Cable connection etc. Maybe it aint the same model he has but it was the closest i could get on Amazon UK. Not his fault at all it was my decision alone to try it. Maybe i got a different model and that's why and maybe it wouldn't have made a difference on my system anyway? I tried 72 Hz Oculus refresh rate and 1.0 rendering res but again zero difference. What is the best DCS executable to use in this situation? I've been using "F:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR" Also, am i supposed to apply ODT settings prior to attaching Link Cable or after and do i close ODT before starting DCS or leave it open. I have the ODT console open as well but have tried it off with no difference in results.
-
Hi, I tried the settings that you recommended but sadly they made no difference at all. The ground stuttering is still there to the same extent. Tried with Virtualisation and Hyper Threading on and off but neither made any difference either. Tried ODT with all settings as per previous OTT ones before but trying both the 45Hz ASW enabled and 45Hz ASW disabled. Neither made any difference. The powered USB-C hub i bought didn't even work, there was no connection at all to the Quest Pro. Quest client said hardware incompatible. I'm now convinced this is some sort of other hardware issue. Not sure what but i'm losing the will to live with this? I'd love to know what my ratio of flying to fiddling is as of now!
-
Hey there, Thanks v much for what sounds like some really solid advice. I will definitely give those steps a try. I’ll have a go with ODT which I used a LOT with my Quest 2. Yes I was v happy with the benchmark results. I have XMP enabled and RAM is running at 3600 MHz. I’ve actually got another 32GB of identical DIMMs that I could install but not sure what the Channel 1 & 2 technology will do to the performance in that situation. Doubt it’s needed either? My PCIE bus was set at Auto but I changed it to 4 as you suggested and it raised the data rate through my USB-C cable from 2 Gbps to 2.5 I’m reasonably sure that the PC-Link USB C Cable-Quest Pro chain is bottlenecked to some degree in my case. I’ve got some new hardware arriving that might help there, maybe not. I’ll try those changes in refresh rate and rendering resolution and report back. Thanks.
-
-
See this thread from yesterday to answer some of your questions. Still have same problem after an entire day of trying to solve? Any new suggestions very welcome? Skip to the last few posts to see where we ended up. Also my current settings are listed there too. Thanks.
-
Does anyone with Quest Pro or Quest 2 know what the maximum bandwidth/data rate etc (whatever the correct term is?) that these headsets can take via Link Cable (a good link cable as in closer to the max rate of the USB-C port it is connected to). Also, do powered USB-C hubs with a top end USB-C cable add any value at all in terms of improving performance/quality in the headset? Again, when connected to the best possible port on your motherboard? Thanks.
-
No i uninstalled VD earlier today so it would not interfere with the testing etc. I'm done for today and not sure to be honest if i can devote much more time to this. It's still far from perfect and ground stutter is still there quite bad in Syria map particularly. Tried a few more tweaks with Oculus app and in-game but its not in a state i really want to play in at the moment. Maybe in a few updates time things will improve and i'll try again. In the mean time i'm going to fly non-VR only for now i think. Not as if i can upgrade my hardware either!! Lol! Thanks so much for all your help mate, i really appreciate it. I'm heading back to 2D 180 FPS Heaven!!! Fully maxed!! Good night and have a great weekend.
-
Ok, so i disabled Hyper-Threading and Virtualisation in BIOS and the ground stutter is MUCH reduced!! Its pretty much un-noticeable 95% of the time. The slight issue now is ghosting of buildings/trees/objects etc. That sensation of the object stretching very slightly as you look at it passing over it. I've had this before a while back and i think i fixed it with either an in-game setting adjustment or possibly a change of encode resolution width in OTT/ODT or a change of rendering resolution in Oculus app? Point is this is the most progress made so far! I'm a happy camper right now! Still work to be done though! Thanks again.
-
Thanks, so i've tried the OTT Profile on the MT Build and the frame rate is absolutely locked down at 45 Hz the entire time. Unfortunately the ground stuttering/jerking is still there. The image quality is fantastic though, best yet. Am now going to try the same profile on the Non-MT Build. Thanks again.
-
Hi, and thanks v much for your advice. Sadly, i had already read that previous post by Tenpox. I followed his settings to the letter other than your advice to enable ASW to 45 Forced in OTT. Just to be sure i just tried your settings with the 45 Forced option but no real improvement. The frame rate is stable when straight and level but as soon as i manoeuvre much it goes crazy and there is micro-pauses and stutters when looking even slightly off centre in cockpit view. It gets worse as the speed or manoeuvre become more violent. Nothing wrong with the image quality, its really great. As long as i'm stationary in mid air!! Lol!! I've not been using Virtual Desktop since reading BIGNEWY's post ref DCS native OpenXR compatibility. Bizarrely though on my old PC DCS worked pretty well in VR using VD? I have to say that most of the time when using OTT/ODT i feel like the changes in settings have zero effect in-game? They seldom seem to do what they seem supposed to? I have ordered the Powered USB-C Hub you suggested, will be here tomorrow. I also have a better Link Cable in-bound early next week from VRCover. Maybe those additions will fix the stuttering? Hope so as i really feel like i've tried pretty much everything else. It's been 10 days so far since installing DCS on the new rig. Thanks v much indeed for your advice, it is very much appreciated.