DirtyMike0330
-
Posts
232 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by DirtyMike0330
-
-
29 minutes ago, Blue73 said:
Hi Skywalker, you need to disable the sliced encoder setting in ODT. Then you can chose what gfx setting you like. Very minor impact on latency, in the ms.
What does the enabling/disabling sliced encoding (as opposed to leaving it at default) do? I just did a cursory google, but I'm not seeing much on what the function of sliced encoding. I've just had mine on default since having the QP.
-
19 minutes ago, Levi_T said:
Hello Everyone!
I tried VRNS with SteamVR and XRNS with OpenXR in DCS, but unfortunately it didn't work. I went through everything step by step that is on this website https://gitlab.com/NobiWan/xrnecksafer, but unfortunately nothing helps. It is interesting that VRNS works without errors in IL2, I only have problems with DCS. What am I messing up?
IWhich headset are you using? If you are using the G2, it currently doesn't work in DCS with xrnecksafer.
-
3 hours ago, slughead said:
What's the lowest FOV that people are running at? I'm currently at 0.75. I can see the top edge of the image when looking straight up (head up, eyes up) so this will be noticeable in turning fights. At 0.6 the edge is visible all the time. I can see the top edge at most FOV reduction values so it's a tradeoff of fps vs some loss of realism in certain head positions.
The fps improvement is significant though, so much so that I've also enabled turbo mode in the OpenXR Toolkit and have a good 18% GPU headroom with all settings maxed out in DCS. (4090, 13900k). In Caucus I'm maintaining 72fps and rarely dipped into ASW flying fast, low and turning over cities. Yet to test on other theatres which we know will zap the fps.
I’ve only tried .87 so far and only on Enigma’s Cold War, where I’m able to maintain 90fps with all high+ settings. I need to see how it fares on other maps and maybe something like the Hoggit server as well. We both have 4090s and comparable CPUs, I’m surprised you’re not easily hitting 90 on Caucasus
-
11 minutes ago, markturner1960 said:
OK< thanks...one last query regarding power off on the main headset. Long press turns it off, yes? I do remember seeing power options in a menu from within the headset while turning it off as well. The confusing thing is I have used the long press, the headset makes a noise and then you get the LED white for a bit, then it goes amber...... if its still got lights on it, of any colour, to me that says it's not off completely....
Can it be powered off, yet charging and showing an amber ( charging) / green (charged) or red ( trickle) ? And if the answer to that is yes, how can you tell its powered off properly ?
Sorry for the basic questions, again, I cant believe there is not instructions for all this included !
When you long press, you should have the headset on because you need to then click the power off button inside the headset.
-
6 minutes ago, markturner1960 said:
OK, thanks - what would the advantage of that be, given that the ASW works so well on this headset?
I don’t see any point in locking to a low frame rate and not using ASW, especially if your PC is beefy enough to push the QP. Or reducing from 90fps.
-
1 hour ago, markturner1960 said:
OK< so I have some issue regarding charging with mine? Twice now, I have started using it, after carefully setting it in the cradle and then discovered halfway through my session ( so about 30 minutes) that its about to run out of charge........so right now, mine is sitting in the charging dock, the amber light is on? Signifying charging as I understand, yet its still at 3% charge after an hour which is what it was when I put it on there.
I have ordered one of these: https://www.amazon.com/dp/B0BS9C9RBZ?ref=ppx_pop_mob_ap_share on Dirty Mikes recommendation so hopefully will solve the issue.
How can you tell for 100% sure its charging when sitting in the dock and is there a way to get battery levels displayed when the link cable is not plugged in? How do you tell power status when in the dock and do you guys power down completely before docking it? Should it be off when charging and only turned on in use?
Here is the chart for the LEDs.
If you're seeing amber, it should be charging, but should be nearly full charge after an hour or so. You are using the charging cable that came with the QP, correct? And are you putting it on the dock to charge while it is still on?
I always fully power off the device after use. I rarely use the dock, since the usb-c hub keeps it almost fully charged while I am playing, but the couple times I have used it I made sure the QP was off first.
I'm pretty sure you can check the battery status by short pressing the power button while the QP is off, just a quick tap should pop up the battery level IIRC. null
-
2 hours ago, slughead said:
As for your blurriness.... you've answered your own question. You said it doesn't happen with default settings. That means something you've changed has caused this. Go back to default, and make one change at a time to isolate what has caused it.
Interesting comment on link sharpening and the encode resolution here:
I’ll have to try enabling/disabling the link sharpening while in headset today and see how it actually affects anything on the horizon. The 3600 vs 3905 debate is also interesting.
-
1
-
-
2 hours ago, YoYo said:
Thx, I have to install OTT, Im using only ODT but I noticed that it doesnt remember settings (not always).
I'm on Link cable of course. One more thing puzzles me, but I honestly haven't had time to test it. Perhaps you know the answer?
It's about the ground textures, the ones further away, which at these settings (as in the screenshot below) seem more blurred. While it is not so visible in DCS (but this effect is present as well), it is more visible in IL-2 BoX, e.g. However, interestingly, the Default settings of QPro hasnt this effect. The textures on the horizon are not that blurry. Theoretically, it should be the other way around
. There's probably some culprit for that, but I don't know what.
It's not a big problem, but the fact that with the HP G2 the textures were sharper.
I'm interested in your findings here if you decide to try to figure out what specific setting is causing the blurriness for you.
-
1
-
-
Just want to chime again on the whole FOV multiplier thing (I've been using .87) and report that I was still able to maintain a rock solid 90 fps on Enigma's CW server today, this time with 50+ people online and engaged in several dogfights, near active SAM sites, etc. I didn't think I'd be able to play DCS without 45 locked ASW anytime soon (while maintaining all high game settings and MSAA x2), so this is pretty exciting!!
-
2
-
-
6 hours ago, markturner1960 said:
Not sure, still feeling my way....if I shut DCS, it does return to the grey grid room......
however, i am now using it controllers free, but do still have a persistent small floating box warning about the controllers not being on.....which i would dearly love to get rid of! Any ideas?
This only happens to me very intermittently, and generally I just restart the headset and it goes away on the next attempt. I still prefer to just use one controller initially, so I can hit the desktop button in the grey quest link area, and then use my mouse to turn on all my apps on the PC via the virtual desktop prior to launching my game. You just have to remember to long press and turn the controller off before you launch the game itself.
If this is happening to you every time (it def shouldn't be), maybe just make sure your software is up to date in BOTH the Oculus headset (settings > system> software) without the link cable and then also via the Oculus software on the PC, from the devices tab with your link connected.
-
1 hour ago, markturner1960 said:
On investigation, the OTT setting is for the 2D monitor, so it needs to be set in ODT. I changed it from 0; 0 to 0; 0.85 ( I have no idea what the first zero and semi colon are? ) Is this correct?
I did the same number for both, assuming that is correct. It is "Horizontal; Vertical" (or the other way around, but you get the point lol)
-
9 hours ago, diamond26 said:
This is not what you want to see when you test the link cable. You should see USB3 and speed above 1.9 gbps. Also when you see these 3 dots, try: disconnect Oculus, power off both PC and oculus and start up again. Sometimes you need to reconnect the Oculus cable on the fly to get rid of this problem. Most times I’ve seen this behavior was when I was switching between different Hz settings (72,80,90)
It renders a smaller area on your headset and thus increasing FPS performance. Usually you don’t see the black bars around the image until you hit 0.75 but each individual sees it differently. As with most settings in ODT, you need to put it before you start DCS. To get a feeling what it is just try an extreme figure first like 0.5 (it should look like a tunnel view)
45 minutes ago, Festom said:Reduce the image size. With 0.85 you see the same, but dont lose gpu power generating things that you cant see.
0.85 its perfect for me. For example, with 0.7 , can see black if i look at the edges.
Sorry for my english
Very surprised (with only preliminary testing) but using .087, I was actually able to maintain 90fps on Enigma's Cold War server, even while in the area of a 3-4 plane dogfight, at high altitude and also screaming around on the deck. Now, there were only like 20 people online in the server at the time, and who knows what other factors would play into that, but honestly very surprising on the initial test. I'll have to try it on a few more MP servers and see if it stays consistent. Thanks for the suggestion!
-
1
-
-
12 hours ago, Festom said:
Nobody use fov multiplier? 0.85 and free fps
Can you elaborate a little on what it does?
-
1
-
-
3 hours ago, markturner1960 said:
OK, so my next question relates to the openXR performance toolkit..... there are some things in there which it says dont play nice with ASW, so turned them off......
Whats peoples thouights on the various other settings in there? Such as resolution overide, sharpening etc? Currently, I have everything prertty much turned off.....
@mike, will this do the same job as your linked charger hub? https://www.amazon.co.uk/Minisopuru-Hub-USB-Adaptateur-Ordinateur-Grey/dp/B0BGHVQNCH/ref=sr_1_4?keywords=miniso%2Bpuru&qid=1685692090&sr=8-4&th=1
I cant find your exact model on amazon uk
I mostly just use the toolkit to check fps/cpu/gpu stats, but I'm sure some other folks will be able to help out with that one. It does have a nice sunglasses feature that I will toggle on in certain environments or time of day. I also use CAS sharpening in DCS (I think I am at like 70% right now) but it is pretty subjective on what you'll like the look of. I think it has more usage when trying to eek all the performance/quality out of MSFS, but I don't fly that often enough to provide any setting suggestions.
The hub you're looking at is from the same manufacturer and does seem to have the single usb-c connection at the end that shares the data + charging functionality, so my guess is that it would likely work. Worst case, if it doesn't work for some reason, you can try https://www.amazon.co.uk/Kuject-Separate-Charging-Ultra-Durable-Accessories/dp/B09TN25765/ref=sr_1_2?crid=6E0C1YWW1E9O&keywords=kuject+quest+pro&qid=1685702971&sprefix=kuject+quest+pro%2Caps%2C126&sr=8-2 as a second option. It seems to work for some folks, I personally didn't have the best experience with it and the hub option is cheaper, less bulky, and is providing the charging directly to your QP, as opposed to the cable system.
Glad you're making progress with the headset!
-
1
-
-
55 minutes ago, markturner1960 said:
OK, I have uninstalled WMRP and mixed reality for steamVR. I also removed the hand controllers, to re pair. However, they did not show in the device list to re pair? They just seemed to pair automatically. Did you have to pair yours like the headset? They work though so I guess thats all that matters.
Cant believe there is no instructions from Meta regarding all this, you get sent the complex expensive device and are basically just expected to figure it all out yourself....not impressed!
For example, there is a power button on the headset....so when and how should this be used?
Anyway, I have managed to get it starting in the same way fairly reliably. When I put on the headset, I am in the VR home. The controllers let me click on the menu bar to turn on quest link, the room dissapears and I am in the grid, from there I can pick DCS from the left hand window of recent apps to run again. This works well now. No idea why I could not get it going before!
That leaves the tweaking. I am after the best possible image at the lowest acceptable frame rate. I have put ASW on auto, set 72hz and 1.3% IE all the way to the right on resolution and 1.15 in OTT and it seems to run at 36 FPS pretty nicely, very smooth and teh resolution is insane....never knew DCS could look this good......
But there is bad.......how can I stop the really annoying messages about light levels for controller tracking etc popping up? They seem persistent as well, and are not opaque so they obscure stuff in the cockpit.....
Also, it does seem a little flaky..a few times, it has frozen on me and I have had to kill DCS with task manager - usually when I remove teh headset to look at something, then there can be issues....
Thanks again for the help!
Instead of clicking the DCS app on the left, do you see a button on the bottom that says DESKTOP? If so, click that and you should be on your desktop. Once you're there, use your mouse to open up whatever apps you need. Then, long press the controller to turn it off. You'll get a big pop-up on the bottom of the screen that says controller not connected and it will be persistent. This is fine. Then, as your last step, start DCS from your desktop. You should have no controller-related popup messages going this route.
As far as settings, I don't have experience with the 72hz range of anything. What I would try, in your case with a 3090, is 90hz, slider full right to 1.3 or 1.5, whatever the max is. In OTT, leave the 1.15 at 0, since you're already super sampling a bit in the aforementioned 90hz slider area. I like to set the ASW to 45 ASW as opposed to auto, because with auto there is a delay and jerk transition, and it is unlikely that I am hitting any sustained high FPS at any time in multiplayer or busy single player play. But a solid 45 should be doable with this configuration for you.
You can short press the power button to put the headset in standby and short press to turn it back on. Long pressing it gives you the options to power down or restart (I use it for powering down the QP).
-
10 minutes ago, Slippa said:
“Not interested that much”.
If I were completely disinterested I wouldn’t have looked in, did you consider that? Also interesting to see others using a similar set up to me starting a thread discussing it.
I missed your appointment as, well, anything constructive really but always a pleasure sweetheart, opinions are like arses, we’ve all got em. Don’t be upset, buy yourself a headset or something, maybe one of these. You’d be well placed to give everyone your judgement then and better inform everybody.
Nope, I just stopped considering once I determined that you are a douchebag.
Buy myself a headset
I won't dive into how uninformed you are, since a cursory glance at my signature and forum contributions would easily highlight how absolutely stupid that comment was, but, hey, keep using cute quotes and your 6 year old mac to make yourself feel fancy.
-
4 hours ago, Slippa said:
I’m not interested in VR that much
Yet, you feel the need to throw your two cents in the VR forum. Thanks for the input that nobody asked for (or cares about)
-
1 hour ago, markturner1960 said:
I dont really understand whats going on.....the battery seems to be running down in the headset, so maybe some issue with the quest link? How can I check if quest link is correctly installed? It does not appear in the apps on the start menu.....
Finally, I have read so many threads and so many discussions on the settings, I think I have fried my brain...I cant decide what is the best setting from what people are saying....
Honestly, all I did was follow the exact settings in the first link I reference in my review post and not tinker with it after that. Those settings worked for me without any issues. I think even with a 3090 you can push those. Maybe just don't do the 1.15 in OTT/ODT but everything else should be fine. You can adjust the render down from 1.3 to 1.0 if needed, but leave the 90hz refresh rate because you can def run IL2 at 90fps, you'll just have to use ASW for DCS and MSFS, it is basically unavoidable unless you love stuttery scenery lol
The link cable is not sufficient to keep your QP charged, you will need this: https://www.amazon.com/dp/B0BS9C9RBZ?psc=1&ref=ppx_yo2ov_dt_b_product_details
My QP has not dipped below 90% using that, regardless of how many hours I am flying.
Just now, markturner1960 said:Thanks, I am letting the headset charge up ( I got the link cable to make sure it did not run down, so am confused as to how it has run down to 16% after only around 3 hours use today and all the while plugged in via the cable) The cable test ran OK during set up, so there should not be any issues there...? so will try and answer quickly for now:
OK, I did not uninstall WMR as I wanted to assess the QP before I decided to keep or not. Whatever happens, though, I am decided to switch to the QP, its too good! So will uninstall now. Do you think maybe I should start from scratch again after uninstalling the WMR <profanity>?
Dont remeber pairing the controllers, defintely the headset. But the controllers work OK. However I dont see any menu in the grey grid.
You are being super helpful, cant thank you and everyone else who is answering enough! Going to pop out now while the headset charges for 30 minutes or so and get back into this then.
No problem, you'll get it sorted out! Make sure at least one of the controllers is on for starters and yeah, when you select enable quest link from the headset and that grey thing pops up, you should definitely be seeing big buttons on the bottom of that. I still think demo mode might be playing a part in this, if that is something you clicked "start" on or activated.
I think if you just uninstall anything related to WMR from the Windows Store and from Steam, that will probably be sufficient. As a nuclear option, if you get fed up, uninstall absolutely everything, including the Oculus software, do a factory reset on the headset, and then just start clean, with some form of those settings I posted above. Good luck!
-
1 hour ago, markturner1960 said:
Thank you, its slowly becoming clearer. It did do an update yesterday, however, in my settings, under Beta, I only see 3 options....in your screen grab further up, you have several, I have turned on public test channel & demo mode, but dont see what you show.....
Can you clarify what ODT is? OTT is obviously oculus tray tool. And to be clear, no edited shortcut is required, you simply use the MT .exe shortcut, with "Enable VR headset" checked in DCS. This will run DCS in open XR, via the oculus runtime, is that correct?
Thanks again for your patient help!
Debug tool can be found in your version of D:\Oculus\Support\oculus-diagnostics. It is just the native version of Oculus Tool Tray, with less custom features. It looks like the attached screen.
And yes, I can confirm that my DCS MT shortcut has no arguments at all. As long as your Oculus Home runtime is set to OpenXR and you have vr headset checked in the DCS settings, you should be able to just launch and get into VR. I responded in your other thread about the whole Demo mode thing... if you clicked Start on that, that might be causing some headache for you. I'm not sure what the functionality of it is, but I don't use it and just by the naming, I would assume it would limit certain things in your QP experience. nullnull
nullAs far as the public test channel goes, I haven't personally had any issues, so that is up to you in general.
Here is another general link for you to explore, if you haven't already, regarding all the OpenXR/eye tracking stuff:
https://mbucchia.github.io/OpenXR-Toolkit/et.html#considerations-for-quest-pro
-
48 minutes ago, markturner1960 said:
Sorry Mike, this is really helpful, but in my windows settings, there is nothing referencing quest link? I have display, sound, notifications, focus assist, power & sleep, Storage, Tablet, Multitasking, Projecting to this PC, Shared experiences, Clipboard, Remote desktop......
If I put on the headset, I get the VR home room, with a window asking if I want to enable quest link. If I choose yes, the home is replaced by the grey grid and I cant access any menus etc using the controllers...is this how it should be?
DCS only seems to launch when I use the old shortcut with the force openXR line appended to it. If I use a shortcut to teh .exe, it starts DCS, but not in VR....
When i turned DCS off, I get a black screen on my monitor, in the tool tray there are 3 windows open showing oculus mirror. If I turn these off using the X in top corner, the main desktop screen becomes visible again.....
I dont really understand whats going on.....the barrery seems to be running down in the headset, so maybe some issue with the quest link?
Yup, I was referring to getting to the grey grid when I mentioned system settings, so disregard that part
In that grey grid, you should absolutely be able to click one of the icons on the bottom that says DESKTOP with your controller. Just to confirm, did you pair your controllers during the initial setup and can use them prior to turning on quest link?
I'm going to answer you in the other thread as well, but are you saying you turned on Demo mode? Like, you hit the start button on that? I have never used that function, but if I had to make a wild guess, if you turned it on it could be limiting your options, which would explain why you don't see any other options underneath it. If it is on, turn it off and see what happens. That could also be causing your other issues with apps not launching in VR.
When you can click things in the grey grid area, there is an additional settings menu there that you can use to I believe turn off any extra mirrors. I'll post my Oculus Home settings here again. By the way, when you did the initial Oculus setup, did you decide to leave all your WMR stuff or do a clean setup?nullnull
-
5 hours ago, markturner1960 said:
Hi, I have some queries regarding this and started this thread to avoid cluttering the Pro /G2 thread. I had my G2 running superbly with open XR and want to make sure I get the best experience with the Pro. So…….
What is the best runtime to use? Reading various threads it looks like people are using open vr and open xr……
How best to launch the sim? Via a shortcut like I was doing with the G2? I want to use MT ( unless recommended not to…?)
Should I have the “enable VR headset” option checked in game?
any 3090 users got some tips on optimum settings? Most threads with these discussed seem to involve a 4090…….which I may look at but for now I want to see what I can wring out of the 3090
many thanks
Edit: So, this morning, after a while spent reading various threads, I tried launching DCS again, via the old shortcut I used for the G2, with the --force_enable_VR --force_OpenXR text appended. DCS launched, but nothing in the headset and this time, no VR room, just a grey grid . i was unable to get the menus up for apps and settings etc....not sure whats going on, everytime I try and start, something diferent happens! It does launch DCS if I use the .exe shortcut in the mt bin folder, but I dont get the oculus home appearing.
I installed VR explorer, it says xr create session error: reload with session enabled? Runtime is Oculus 1.86.0. It still says this when DCS runs via the .exe.
Just for your reference: my desktop shortcut for DCS MT has no arguments in it and I just have the enable VR option checked in game. It launches in VR without any issue with the QP.
My order of operations:
1. Turn on QP
2. Settings > System > Turn on Quest Link
3. At this point, I can either:
a. look at my monitor and turn on my apps (Vaicom, NeckSafer, etc) and then double click the DCS shortcut to start the game in VR
b. If I turn on one of the controllers, I can click the DESKTOP button from the quest link screen inside the headset and access the virtual desktop, in which case I will just use my mouse for everything in the headset. I then power off the controller before I launch the game.
-
13 hours ago, markturner1960 said:
Thank you Mike, so much! I finally have it working and need to do some tweaking but WOW! Utterly amazing first impression. One big issue I have is that there is a line about three quarters of teh way down the FOV, above which, everything looks great and below, its lighter? I tried taking a screen grab, but it does not show in the picture.....any ideas? Hope I described it OK! Also, on beta, I only have the first 3 options showing, down to demo mode.....why is that do you know?
Edit...on tweaking, I do have an issue - I changed the refresh to 72 and since then, DCS starts but no DCS in the headset, just the VR home. I changed the refresh back to 80 where it was when i first fired it up and it worked, but it still wont start in VR.......
Another query regarding the audio...its crap, but my cans do not fit over the headband properly.....any recommendations? You said you were using arctis headphones, they look pretty identical to mine, how do you get yours to fit?
I haven't personally experienced the FOV issue, so I'm not 100% sure. Maybe something with the refresh rate selection you made? I have never used any other settings than what is in my OP. As far as not seeing the options I see, my guess would be the headset hasn't updated or maybe you're not on the public test channel I mentioned. That could potentially open up more options in the software. I'd just suggest making sure everything is fully updated for starters!
For point 2, did you make sure the VR option is checked on in your DCS game settings? That should start it in VR every time you boot it up after you Quest is connected and on.
The on-board audio is my least favorite part of the QP lol I have the Arctis 7 Wireless headphones and when I extend the arms (or whatever you call them) fully, they fit perfectly over the QP and then I can tighten the fit a little bit.
2 minutes ago, slughead said:It's in the v53 normal release. It's enabled by default so no need to use ODT unless you want to turn it off.
Ah ok, so maybe the PTC requirement was for the initial release of local dimming. Or maybe it was for something related to OpenXR toolkit and eye tracking. Its hard to keep track nowadays lol
-
14 hours ago, TZeer said:
You need that to get localdimming to work?
Someone can correct me if I'm wrong, but I'm pretty sure you needed the public test channel to get local dimming, unless they have pushed a recent regular update that has also included it. You can confirm if local dimming is in via the oculus debug tool in one of the diagnostics folders in your Oculus PC installation.
-
41 minutes ago, diamond26 said:
I'm using OTT longtime now but I haven't seen this feature. Where exactly is it?
29 minutes ago, markturner1960 said:Sorry for more dumb questions.....I have installed the occulus software and OTT . However, I dont see the any options for graphics in the Oculus GUI, under "settings" it has options for account, privacy, payment, general and Beta. On the left there are options for Home, Store, Library, Events, Devices & settings. Cant see any graphics settings options anywhere......?
I would also recommend you join the public test channel, enable dev features, and also eye tracking (once you configure eye tracking in the headset itself). This will get your local dimming activated as well.
-
1
-
1
-
Meta Quest Pro Settings
in Virtual Reality
Posted
Thanks!