sze5003
-
Posts
1918 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by sze5003
-
-
Can't wait to have something like iron flag for the F18. I haven't been in DCS in what feels like over a year so getting back into it now with the provided in game tutorials isn't going to be pleasing.
Looking forward to the wingman campaign but I'll definitely check out the linked missions above. -
I heard that boresight on the ground will not matter now due to the parallax errors that have been introduced in a previous DCS update.
Mission 7 which I just finished you did have about 5 minutes or less to lock two targets or 1, fire a Mav and then turn back and go low and come back quick to get the SA6.
Nonetheless I'll try once in mission 8 to boresight on the ground before heading out. -
Thanks zooming out does help a little bit. I was able to boresight this way and didn't bother with the hand off modes. I still ended up hitting a light pole instead. I don't think I was able to see the pole before firing.
-
I'm stuck on mission 4 for some time now. I'm not sure what the proper approach should be. Should I let Bug get the triple A at waypoint 4 and then I attempt to use Mavericks in the pop up targets later?
Do I lose points letting Bug take them out?
I just can't ever seem to get the Mavericks to hit my targets. Auto hand off barely works. It locks on and says hand off in progress then I see the blinking cross hairs on the WPN page so I fire, mav looks like it's heading in towards the target but then misses.
They seem to mistakenly lock on to near by buildings or other objects.
Boresighting them is tough because I can't see anything properly on the WPN page. Im flying in VR and even with my quad views focus resolution set to 2.0 it's hard to make out anything on the weapons page.
I tend to set the tgp on a target then use the HUD to slew the Mavericks on or near the tgp box, then try to view what I'm locking up on the WPN page, seems to work and I get blinking cross hairs but I fire and of course I miss again.
I feel like I'm missing something here but I love the campaign so I'll keep trying as I'm learning a lot. -
2 hours ago, Hobel said:
what kind of distances are we talking about here?
I’m about to fly the mission once more in a few minutes but I’m going to say it was between 8-10 miles. I’m able to lock up the SA-8 on the targeting pod well before that distance. But it’s super hard to see on the WPN screen when trying to boresight (specifically in VR). I will probably use the GBU-38’s instead on the first target and try the Mavericks on subsequent targets. I’ll save the track if I fail again which I probably will
but I like the practice.
-
On 7/1/2024 at 7:47 AM, Hyperlynx said:
Actually, I was starting to come to the conclusion that mavs are only any good for picking off tanks out in the open. This thread was to see if I was missing something
The actual scenario is some of the Wild Weasels SEAD campaign missions, where they keep giving me two AGM-65Ds and two JDAMs/LGBUs. The bombs are just fine, but I'm having a hell of a time accurately picking off AAA or a Gecko or whatever that's been parked next to a building.
I thought maybe the solution is "yes, you need to boresight the missiles, then you can accurately pick out the target with the TGP and do a handoff". The bus scenario was just to test that out. The distances are pretty similar to the Gecko being parked next to a building. The conclusion I was coming to was that yeah, Mavs really aren't suited for this sort of thing, and the TGP isn't going to help much.
In the context of the SEAD campaign, I'm thinking only try to use the Mavericks on things I can clearly identify, and for cleaning up TELs after the radars are destroyed, and to use guided bombs for everything else.
e: I wish we got the laser guided mavs, (ersatz Hellfires?) because they'd probably work a lot better. Or, even better, APKWS
I’m currently stuck in the Weasels campaign on mission 3 trying to use Mavs. What did you to do achieve a better lock? For me the auto hand off only worked in the tutorial missions and never seems to happen if I set point track on an SA-8 with TGP and then try to hand off when Mav is in PRE and TGP is on Auto.
-
6 minutes ago, FupDuck said:
I think the issue is mainly with the desktop app, not the headset firmware. You need to block the link software from updating. There are instructions on the 3rd page of this thread
Yea I found the blog post and followed the instructions to replace the v68 updated desktop app files with v67 ones. Now if I want to try the PTC update I need the desktop app to update again back to v68. But it is not triggering an update so I will need to uninstall it and reinstall I suppose.
-
I can try it tonight but I'm skeptical. I just went through the process to roll back desktop oculus app to v67 files since it updated a while ago.Thanks...anyone test this yet?
I also did the os update disabling on the headset. So if I go into PTC and it doesn't work I'll be screwed lol. -
5 minutes ago, mbucchia said:
I have received signals that Meta is going to release a hotfix in PTC. Will still be v68<something>, but should have the particular fix to the issue.
Funny I just set up sidequest today, loaded filemanager+ and disabled oculus OS updater app. Thanks for the info, once the update is out at least it will be an easy revert.
-
One thing I don't like about link cable is how inconsistent it can be. A day ago I flew a mission in weasels over Syria, no stutters, no hourglass loading while flying randomly, it was great.
Last night I hook it up to do the same thing because I failed that mission and this time I had instances of the loading hourglass 2-3 times.
Usually it's oculus services so I force close all of them and usually this helps but I can't say this is 100% the solution.
I'm running 1.0 resolution in oculus home app, 90hz, quad views, in oculus debug tool 2.0 super sample and 500 bit rate.
It's very inconsistent when I end up with the hourglass pauses. There's days where it does not occur at all. -
Not so much the speed, the point of a separate 6ghz router is to create a stable and quick connection that's isolated from other wireless traffic.Hmm, downside is a wireless router with those speeds is quite expensive.
What is commonly recommended by the Virtual desktop discord is TP Link Axe5400. I got mine for $150.
I have a separate mesh system at home since I can't drill through walls to wire stuff as we are renting, so I have the tp link wired to a satellite in the office and then an Ethernet cable form the TP Link to my desktop. This is the important stuff, your PC must be wired into the standalone router you are using for the quest.
I don't have gig speeds either just 400-500mb down/up and VD runs fine for me. VD performance overlay says my speed is 2100mbps.
I'm not on v68 yet so I'll use link cable until I can't anymore.
-
1
-
-
3 minutes ago, Steel Jaw said:
Using a wifi connection though versus my link cable giving me over 2 Gigabits, will the wifi be fast enough...what's the minimum speed needed?
Minimum is 1Gb for VD. Only thing is if you need higher resolution other than “god mode” in VD then you can bump up Pixel density within DCS settings.
-
11 hours ago, slughead said:
Under C:\Program Files\Oculus there is a Staging and sometimes a tmp folder.
- Rename the Staging folder to Staging.bak
- Rename the tmp folder to tmp.bak
- Create a new file called Staging (you can create a new txt file called Staging.txt then rename it to Staging)
- Create a new file called tmp.
By creating files to replace the folders, the Oculus updater can no longer copy the download file to the staging folder because it's now a file. Hence, this blocks your Oculus / Meta Link application from being updated.
Reverse the changes to allow updates again.
This only stops the app on the PC from being updated. It doesn't stop the headset OS update from happening (which "could" be incompatible with the PC app should the versions not match).
I also make a copy of a good working Oculus folder, e.g. Oculus to Oculus.v67 so I can quickly revert if I need to.
Oddly enough I went to do this today. This is what my Oculus folder looks like and i never made changes to it. Somehow my headset was able to update to v67 from 64 today. Should I delete the bak.tmp and bak.Staging?
-
Definitely looking forward to it! Bought the Gambler’s and just now started learning the F16.
-
Thanks. Glad to be back to the same performance I had months ago. I'm sticking with link cable 500 bit rate as 960 still caused audio cutouts.
-
Should I be on v67 for best results? If not I will stay on v64. I shut down all oculus services in task manager if I am not flying. Leaving them running in the background I noticed causes my other full screen games to get minimized or go out of full screen. It was driving me crazy trying to figure out why that was happening and it all stopped when I shut down OVR and Oculus server, and other Oculus services running in the background when the pc boots up.
-
From what I understand, v68 has issues with DCS if you have openXR/toolkit installed and enabled. I don’t use it so I should uninstall it. I’m on v64 still on my quest pro. I turned off automatic updates in settings when last time it was broken for a while in DCS.
I am going to try the 960 bitrate again to see if I get audio stutters. I usually run super sampling 2.0 via oculus debug tool with quad views, DLAA and DLSS Quality with the latest nvidia DLSS dll toggled via OVGME.
I am still waiting for a company to make a headset of similar size to the Pro, decent FOV, decent resolution and eye tracking but with Display port. Seems like pimax missed the opportunity not including eye tracking in the Crystal light but I feel like they would be shooting themselves in the foot if they did that.
-
1
-
-
2 hours ago, gonvise said:
If "godlike" is not enough and you want more quality, it would be a matter of increasing the DCS PD or the central part multiplier of QVFR. But in my opinion, the problem with this is that in the end you are burdened by the 150Mbs of Hvec-10, or if you put h264+ then 400Mbs, but it is still far from the 900Mbs that you can put via cable link.
In short, I think that no matter how much you increase the scaling from the "god like" via DCS PD or QVFR, the encoding bitrate will not allow you to perceive the improvement in clarity as you should.
I insist, the quest pro "shine" with a 2.0 scaling, encode resolution 3905 and encode bitrate 960 via cable link (OTT), so the first thing I would do is test this to have a reference, then each one has his own eyes and expectations
Those are the exact settings I use with oculus link except 500 bitrate because 900 gives me audio stutter and I don’t want to wear extra headphones. I figured a 13900k and 4090 would be ok to drive that bitrate but I suppose it also depends on the encoding chip you get in the headset. If quad views is working as it was before on link cable without the hourglass pauses or stutter then i will be happy with how it looks.
-
3 hours ago, Phantom711 said:
So basically what you are saying is that eye-tracking isn‘t working for you with VD?
Make sure to follow mbucchias instructions on how to use the QuestPro with QVFR.
https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro
3 hours ago, gonvise said:Do you have to enable the option of send eye tracking data in VD streaming settings in-VR. For me, QVFR works the same via VD than link.
It said something along the lines of enable tracking data and then has two additional check boxes for for SteamVR controller tracking or another option. I enabled it, not sure how it got disabled. Now I see it working properly.
I remember setting this up properly but then it broke with the last update and I used the unsigned dll fix until the recent update fixed it. It looks like I may have been running link cable without eye tracking because the Quad views log was was not picking it up. Now the log shows it being picked up in Virtual Desktop. I will need to test link cable again.
Found option 'smoothen_focus_view_edges=0.2'
2024-07-26 17:13:07 -0400: Found option 'sharpen_focus_view=1'
2024-07-26 17:13:07 -0400: Found option 'turbo_mode=1'
2024-07-26 17:13:07 -0400: Found option 'horizontal_fixed_section=0.5'
2024-07-26 17:13:07 -0400: Found option 'vertical_fixed_section=0.45'
2024-07-26 17:13:07 -0400: Eye tracking is supported
2024-07-26 17:13:07 -0400: Recommended peripheral resolution: 1536x1608 (0.500x density)
2024-07-26 17:13:07 -0400: Recommended focus resolution: 1076x1126 (1.000x density)
2024-07-26 17:13:07 -0400: Stereo pixel count was: 19759104 (3072x3216)
2024-07-26 17:13:07 -0400: Quad views pixel count is: 7362928
2024-07-26 17:13:07 -0400: Savings: -62.7%
2024-07-26 17:13:15 -0400: Session is using quad views
2024-07-26 17:13:15 -0400: Edge smoothing: 0.20
2024-07-26 17:13:15 -0400: Sharpening: 1.00
2024-07-26 17:13:15 -0400: Turbo: EnabledWhen using Virtual desktop is it advised to increase PD in DCS or should I be doing that in the Quad views config?
-
I think this is the right forum topic for this inquiry. As of the latest DCS update I noticed a lot more hourglass loading and stutter using Oculus link cable. So i decided to try Virtual desktop with VDXR and HVEC-10 bit codec. I also tried other codecs. Using God Mode quality. Hvec-10 bit max bit rate is 150 and for H264+ it is 400. I am using a TP Link AXE5400 WiFi 6e router set up as an AP and the Quest Pro is the only device on it.
Virtual Desktop loads up quickly and DCS also is very performant. I get a speed of 2100Mbps in the performance overlay.
There is something weird going on I feel is related to eye tracking..basically it feels like I am wearing my HP G2 again. Everything outside of where my head is focused straight ahead appears as if there is Vaseline smeared all around the viewbox. I have to move my head and look at what I want for it to become very clear.
Is there a virtual desktop config for Eye tracking?
I don’t have this problem at all with link cable and Quad views eye tracking. I used the default Quad views config and you can barely tell stuff is blurry outside of your viewpoint and it is not noticeable at all because as soon as your eyes move, what you are looking at becomes clear.
Whereas with Virtual Desktop it feels like there is some sort of foveated rendering happening but it’s like the “box” is too large so everything outside of your immediate straight ahead gaze gets blurred out?
Don’t know if I am describing it correctly but again I don’t have the issue with Link cable so not sure what is going on and if maybe someone else has noticed this?
-
I still am having a lot of trouble with this one. Yesterday I was seeing some odd behavior with the F16's not merging into me, they kept flying off in the distance past me. That and Chig kept dropping lock. No mods installed so I did a long clean and repair and it seemed to have helped. But 3 times now I've been shot down before the merge even if I notch right when Paco says notching. I come back left when I hear the tone go away but then it comes back and I ended up getting shot down before the merge.
Uploading a track since I have no idea what I may be doing incorrectly but it feels like in this track I at least got killed after the merge? Hardest part after the notch is acquiring a lock manually since Chig is no help here. Not giving up but probably will take a break.
-
I haven't passed this one yet, run 1 went fine for me. Run 2 Chig always drops the lock if I roll to 320. Even staying too long on 310 you have to watch the TID and correct more to the left once you see the targets go too far abeam.
My understanding is you do want to fire your phoenix here and then crank right but this means not just following what Paco says, basically think outside the box which also means do whatever you need to keep the target locked. -
Check the qvr log to see if there are errors. Usually after a restart it works.Have you followed all the setup advice for VD, such as dedicated router, making sure you get a decent bitrate, checking you signal strength etc.? -
In VR it's a little easier but once I get a "good job" in close parade and then Paco starts turning or climbing unannounced and i have to keep up with him, makes it much more difficult because he changes pitch too much. I still did not pass this one yet but I did notice staying somewhat close to him does not trigger the "you're too far" message where you have some wiggle room to correct and try to stay close until the grade pops up.
Most current, best path for configuring and optimizing Meta Quest 3 and DCS
in Virtual Reality
Posted
Best settings I've found for my quest pro using link cable.
Bitrate 500-600 in oculus tool tray. If using external audio you can bump this to 960mb.
Encode width 3905
Super sampling at 1.5-1.8. don't super sample in DCS.
Quest desktop app settings leave the resolution at 1.0 and either 90hz or 72hz
I'm running 13900k, 64gb ram and a 5090.
I had stuttering when I started but no idea what solved it as after a few DCS updates I never had it again. I believe it was related to the multi threaded version of DCS. I'm also using quad views too.