Highwayman-Ed

I've been running the Quest 2 after grabbing one as a stop gap whilst waiting for Pimax to return my 5th RMA, and have found it a much better experience than the 5K XR or the newer 8K Plus headsets that I had purchased. I did tinker around with the settings in the Debug tool, and even with SideQuest for a while after reading a bunch of forum posts and watching some YouTube reviewers claim that they had discovered the holy grail, but never really saw any significant gains without compromises, and in some cases only saw performance drops. I'm currently running the v28 bundle of the Oculus Desktop software and v28 of the Quest 2 software with 120Hz enabled, although link doesn't recognize this yet and despite the Oculus guide saying it should be available, there is no AirLink showing in my beta tab of the desktop software, but I much prefer Link over Virtual Desktop anyway, so I don't expect this to change my mind and use it instead. I'm running link via this cable from Amazon which keeps the headset at about the same charge level whilst I use it, so I can fly for hours and hours with no problems plugged into the USB C 3.1 port on my MSI z390 Gaming Carbon Pro motherboard. I will add here however that this cable will draw a lot of power from your system and a friend of mine that got the same one to use with his quest suffered from connection drops with link as it was drawing too much in combination with his other devices over his motherboards USB header. He downgraded to a USB A cable that only drew 3A instead of 5, and the problems went away. I've added my settings below, and other than the Clouds making me want to throw up if I fly with them for more than 15 minutes, I've got the smoothest experience in DCS I've had in a long time. Running an i7-9900KF@5GHz, MSI Gaming X-Trio 2080Ti, 32GB RAM and Windows as well as DCS on SSDs of course. I performed a full clean of my DCS and Saved Games folder before the update and deleted the mandatory FXO and shaders folders, but other than what you see in the images attached, all other settings (NVidia) are stock defaults. The only thing I've ever done with my Quest 2 itself is add the Elite Strap and a silicone face cover for workouts which positioned the quest a little further from my eyes, but that alone gave it the largest sweet spot I've experienced in any of the VR headsets that I've used (Rift CV1, Vive, Index, Pimax 5K Plus, Pimax 5K XR, Pimax Vision 8K Plus, Pimax 8K X). At this point however, I've returned my Pimax headset for a refund (after the 6th one had a fault with the lenses), and only borrowed the Index for a extended trial, so the Quest 2 is the only headset I have without going backwards and until the next gen is out, I'm more than happy with it. Final note to add, I pretty much fly the Hornet exclusively, so haven't spent much if any time in any other aircraft whilst I wait for the patch to fix the clouds.

Interesting thing I noted this afternoon, the cloud shaking for me at least seems to be directly linked to minute movements of the headset. I had my Quest 2 on my desk this afternoon after tinkering with a few settings to try and get them stable as some YouTubers have commented that they do not experience any shaking in VR and saw that on the desktop, the clouds didn't shake in the reprojection. I took my phone and attempted to compare the view through the lens to that on the desktop and noticed that they were not shaking on the image on my phone either and thought I'd struck lucky with some tweak I'd made. I put the headset back on, and they were shaking... I took the headset off then, removed the head strap and effectively clamped it to the edge of my desk. Moved my eyes up to the lenses and no Shaking! Now I'm off to the hardware store to get some really strong glue to fix my head in place so it can't move and I too can enjoy the clouds in VR in DCS with no wobble

i have this exact issue too, Oculus Quest 2 via Link. I can notice it occasionally with objects, especially shadows, but the Deck crew mention is what really nailed it for me. It’s just some little details that are different between my two eyes.

Same results here, the bouncing clouds can only be tolerated for so long before nausea starts to sneak up on you, and it doesn't seem to matter what the quality for the clouds is in the settings, they look 'too soft' in VR and no different whichever the setting. They look much better on my monitor if I fire up DCS without VR enabled.

Do you have winds in the mission by chance? AI seem to be ‘blown off’ formations by the relative wind and have been for quite a while now. Fly the same mission with no wind, and you’ll find they get right into position without any problems. you can test it by flying as you are here, into the wind, then turn 180 with a tail wind and watch them move too far forward.

hey @Mustang You're a god as far as all these shaders and textures go in my book Any chance you know how to get DCS to use a single shadow LOD? For example, when flying in close formation with a wingman, their shadow under their wings, keeps switching between the high and next level down LOD, over and over and over and it really breaks the immersion. The same thing is true when you're flying close to the ground, I often see half of my helicopters shadow in a high LOD, and the other half in a low LOD, sometimes only half a shadow! Thanks for all your hard work!

That is annoying too, but it's not the only issue, and I believe he's mentioning the transition from the High LOD shadow to a lower LOD that kicks in over and above what you've linked when you're about half of the distance from the Aircraft that you are in the video. I'm with the OP, it kills immersion when flying off your wingman. I've been searching for ages to try and find a way of getting rid of the high LOD shadows entirely.

Yeah, I wish I could just disable the whole shadow LOD switching entirely, and have average shadows everywhere rather than great shadows up close and a noticeable 'Shift" between LODs. It's especially annoying when flying formation with a wingman to have it's shadow switch LOD's over and over as you fly off of their wing.

I have a friend with a custom Hornet pit having this exact same issue, I’ll get him to try, but thanks for posting the workaround!

Most excited I've been about a campaign release in ages

Just to add to item 1 with the TGP wandering off, I saw this again tonight, although I haven’t seen it in a long time. I then started another flight to see if I could re-create it, and got the same behaviour after the DCS window loses focus whilst the TGP is displayed on an MFD and is tracking.

Same issues still present with Mission 1. I flew it today with OB 2.5.6.59625, and it seems that an F-15 is trying to park at an occupied parking space (F141) where a static aircraft is positioned. As a result, there is a massive queue of planes on the taxi way behind it that eventually queue all the way back to the Runway and prevent further AI landings. Got the mission success message after landing without clearance and taxiing to parking, but it's a simple fix. I tried to save a track of it, but going to the Tracks folder after coming out of DCS, and there was no track file recorded...

Are you sure that you are setting up the Fuzing options correctly? I’ve also used these weapons in the Syria map in Liberation generated missions with no issues.

Getting similar issues since the most recent update too. The server reports via the My servers page on the DCS site, and I can stop, start and restart mission no problem, but the server is not available for clients, even on the same LAN using the local IP address. My logs also don't show any errors, or clients attempting to connect... We've tried the following Rebooted the Router Deleted the Port Forwarding rules on the Router and re-created them Issued a new IP address to the server, and repeated the above step again with the new IP Deleted the Windows Firewall rules on the server and allowed access when the server starts up again Still we get the server management page in the DCS profile page, but no response from any clients from the internet, nor locally on the same LAN. Router: DCS Profile Page: Dedicated Server GUI: After a lot of troubleshooting and diagnostics, it seems to be the Windows Firewall rules that have decided to block the Server, or that the server is simply not accepting requests, disabling Windows Firewall temporarily still didn't allow any connections. Despite deleting the rules, and re-creating them several times, the Dedicated server will not accept incoming connections over the client port (10308). I've been able to successfully run a mission on the same machine with the DCS game client running as a multiplayer host, but of course this isn't a long term solution. I'm going to completely delete and re-install a fresh DCS Dedicated server to attempt to resolve the issue.

Got some odd behavior here too. All of the commands work, except "Kneeboard" I can browse all the tabs, dictate without issues, but I cannot open or close the kneeboard with a voice command, I just get the little speech bubble with a red cross in the top right of Voice Attack and nothing shown in the log. All of the other commands show up as recognized, and if I say something completely wrong like "I would like a keyboard" it shows as unrecognized, but the word "Kneeboard"... nothing apart from the VA indicator that it wasn't recognized. I've gone through the troubleshooting steps above, tried VSPX on and off, imported a new profile, deleted the VAICOM folder in the scripts folder in DCS, run a cleaned and mod less version. It's not the end of the world, I can bring up the kneeboard with a button press, it's just really odd.

There's a part there that seems to be conflicting, at least to me anyway. You have the section local a320skins={"Turkish Airlines TC-JUJ", "Vietnam Airlines VN-A308", "cebu pacific RP-C4107" } but then later you're calling; a320:Livery(a320skins) This might be causing issues for you. Here is a snip from one of my RAT scripts; local a320out=RAT:New("RAT_A320") a320out:SetDeparture({"Beirut-Rafic Hariri","Adana Sakirpasa"}) a320out:DestinationZone({"European Gateway","Tel Aviv"}) a320out:Livery({"Aeroflot", "Air France", "Al Maha", "Egyptair", "Emirates", "Emirates SkyCargo 1", "Kuwait Airways", "MEA", "Turkish Airlines"}) a320out:SetMaxRespawnTriedWhenSpawnedOnRunway(0) a320out:StatusReports(false) a320out:SetSpawnDelay(math.random(300,600)) a320out:Invisible(true) a320out:SetSpawnInterval(600) a320out:SetTakeoff("cold") a320out:RespawnInAirNotAllowed() a320out:RespawnAfterTakeoff() a320out:Spawn(1) The liveries themselves are from the folder names in your liveries directory, not the livery names as they appear in-game.

As far as the radio menus and built in DCS comms go, it's Super carrier all the way, BUT it may only be that way if you own and/or have the Super Carrier installed... Here is what VAICOM is capturing from DCS when I use the in-game radio menus to communicate with the Tarawa 12:49:29.984 [AUTO:] Player: 100 12:49:22.466 100, Tower, Roger. BRC is 209, signal is Charlie 12:49:13.973 Player: Tower, 100, overhead, angels 4, state 4.0 12:49:08.114 Player: 100 state 4.0 12:48:30.227 update state, switch tower 12:43:32.604 [AUTO:] Player: 100 12:43:14.182 100, mother's weather is visibility ten plus miles, clear, altimeter is 29.93, CASE I recovery, expected BRC 209, report see me at 10. 12:43:00.813 [AUTO:] Player: Marshal, 100, Marking mom's 070 for 45, angels 15.5, state 4.7 Interestingly, the only message VAICOM doesn't see is the player calling "see you at 10"

Having issues when trying to transmit VAICOM commands to the Tarawa in my Harrier. Whenever I transmit to it, I get the following error 3:27:55.996 Joystick : 'Transmit TX1 release' 3:27:55.452 Selected recipient is not a Supercarrier unit. 3:27:55.452 Recipient for ATC set by call contents. 3:27:55.451 Identified unit: Oliver Hazzard Perry class with id 16777728 3:27:55.451 Getting selected unit for category ATC 3:27:55.451 Have result, identified as command: See You At Ten 3:27:55.450 Captured sentence: see you at ten 3:27:55.432 Recognized : 'see you at ten' 3:27:52.990 TX1 | COMM1 AM 141.000 MHz tuned for ATC unit Beslan [AI] 3:27:52.989 TX1 | COMM1 AM 141.000 MHz tuned for ATC unit Tarawa [AI] 3:27:52.792 Listening resumed 3:27:52.767 Joystick : 'Transmit TX1 press' Now the Tarawa is on 141.000 MHz, but the escorting Oliver Hazzard Perry class is not, I've changed that to another frequency. Whilst the Tarawa is indeed not a Supercarrier, for the purposes of VAICOM, it should be treat as one. I'm not sure if this error is being thrown because of the OHP in the Tarawa group, if it's because the Tarawa's frequency clashes with Beslan Tower, or if it is simply not eligible for the command as it's not seen as a Carrier by VAICOM, but the in-game comms treat the unit as a Super Carrier.

You'll get them updated automatically with the ED updates, however, there have been a bunch of updates to a lot of things that have not just been fixed but also changed, and with the work on the Raven One Campaign, work on these was stalled for a while.

You need to wrap your Skins in Brackets local a320skins=({"Turkish Airlines TC-JUJ", "Vietnam Airlines VN-A308", "cebu pacific RP-C4107" }) All Values must be contained in the Brackets () and Curly Braces {} are used to define an array of values within if you want more than one value possible.

Wow, I'm very pleased to see ED taking an active role in notifying Mod makers and users that a patch will impact them. Bravo.

This was resolved for me around June, but since the A-10C II patch last week, it’s back... :(

Best performance in VR for me of any map by far. Great job Ugra.

Looks great, especially whilst we wait for the official fix to the normal maps.

So in an odd sequence of events, I ended up completely removing DCS from my system, both open beta, and stable. I then deleted the remaining folders, backed up my inputs and mission files to my OneDrive. I then re-installed the current stable version, and the current Open Beta, and using SkateZilla's tool I rolled back to 2.5.5.41371. Performance there was back up to an average of low 40's which was much better. I rolled back the open beta 2.5.6.49798, but after it was finished it was late and I was tired. I ran it the next morning, and without thinking updated when it prompted for the update. After it did so, it wanted to cleanup the old files which I thought had been fixed in the July 15th patch, but I had every single file on the drive where my DCS Open Beta was installed deleted. All of the folder structure remained. This was incredibly frustrating, as I lost my IL2 and Half Life Alyx installations too, but I reinstalled everything. Here's where it gets odd... After re-installing from scratch, the latest Open Beta is actually performing well! Mission: F-16 Runway start at Batumi. Settings: Preset "High" Settings, Anti Alaising OFF, Ansiotropic Filtering 8x, Terrain Shadows OFF Open Beta: 34fps Stable 2.5.5.41371: 42fps Open Beta after Hard Drive deletion: 44fps Why? I have absolutely no idea, and I'm at a complete loss to explain it. None of these builds used any mods and all files and folders, both game directory and Saved Games had been removed prior to installation. The tests were done within 48 hours of each other for the Open Beta, and there have been no system setting changes, Windows or driver updates during that time.