Negativghostrdr

Within Quest link there is an option to view your desktop monitors and I can click on the icon on the desktop from that. I also have the virtual desktop app, but so far this is working well enough. Yeah, it's always something with DCS and all the other elements that make up this eco-system. Right now I'm able to play, so happy about that. Off topic: Hey, I'd like to start playing some multiplayer in the F-16. I've been playing DCS for years on and off-just enough to forget a lot in-between play sessions (ha!). Is there a multiplayer server you would recommend for getting the basics down?

Hey guys, Weirdest thing. I get the crash when I try to launch DCS from Quest link while wearing the Quest 2. If I take the Quest 2 off, Start DCS from my desktop, let the splash screen run until it's over (about 10 seconds) I then see DCS in my taskbar signifying that it's running. I put my Quest 2 on...and DCS is running in the headset. Go from there. None of these other fixes has worked for me. This is EXTREMELY frustrating after the amount of money I'm sure a lot of people have invested in these systems that can run this well, I know I did. Anyway, this workaround worked for me. I hope it helps others. Figured this out completely by accident. Cheers.

Thank you I have forwarded my message to Obi and he has responded that he will be taking a look. Thanks again Reflected for getting me to the right people!

I actually did try exactly that last night. Unfortunately nothing. I think it's the DCS gods nudging me to join a multiplayer server!

Here is a track showing my AI wingmen just hanging out in line to get on the runway...for eternity....I've tried running this mission (and others) many times over the last few days with similar results. Once in a while one plane will crash into the one in front of it while lining up, but then all planes simply sit there. I finally purchased a good enough system to play this about a week ago, so I haven't been experimenting for months or years or anything. I am running the multi-threaded version. I have an intel i9-13900 and an RTX 4090 in an Alienware Aurora R15, with 32G Ram. You can also see planes parked in the surrounding fields. I ran a repair and update of DCS, I am running the latest version of DCS beta. Bottom line is that AI wingman functionality appears to be broken. Spoke to the creator of the campaign, this does not appear to have anything to do with the campaign itself. I did see other folks on the campaign thread that I just came from complaining of the same issue. buggymission4.trk

10-4.

As promised. Here is a track showing my AI wingmen just hanging out in line to get on the runway...for eternity.... You can also see planes parked in the surrounding fields. I ran a repair, I am running the latest version of DCS. buggymission4.trk

Will do. Thanks for the fast response!

This is happening to me as well (on Normandy 2.0, Multithreaded). There is one Mustang that stops on the runway that I must go around to take off. I do not have any un-official mods, but I do have a lot of official DLC. It does appear that there are a lot of aircraft just parked in farmers fields adjacent to the airport that I can see once I'm airborne. I have had the issue where a couple of mustangs collide at the runway entrance on a couple of tries. That does not happen every time however. (My squad?) the mustangs stacked up behind me, definitely do not ever take off.

Try turning off Motion Blur if it is on in settings. I was having (I think) the same issue using a Quest 2 and Oculus Link. Very frustrating! Not to mention the Oculus app was telling me that my USB port was a 2.0 when I know for sure it is a USB 3.2. Anyway, the bottom half of my view was black, the top half blurry, and that's what it turned out to be. As soon as I turned off Motion blur, it looks great! I thought maybe it might be one of those things that doesn't work at all with VR? So it might affect other VR HMDs as well as the Quest 2?

I'm flying the Hornet, I'm using MT version. Using a Quest 2 with it's controllers for flipping switches, pushing buttons etc. Have "Use Hand Controllers' enabled, but have 'Hand Controllers use Cockpit Stick' and 'Hand Controllers use Cockpit Throttle' unchecked. The result is that I can grab the stick or throttle with the Hand controllers, and they work exactly as expected (which doesn't seem like this should be happening??).....however.....I want to use my HOTAS and throttle. When I use the HOTAS.. the in-game stick flickers on and off, and seems to be 'flickering' in taking information as well! The plane does not turn smoothly! *Answered my own question! The Quest 2 controllers get Axis controls by default!! I didn't see that initially, because when I looked at the controller bindings it was showing "everything but axis" Cleared those axis bindings in the controller settings....problem solved! Hopefully my struggle helps someone else!

Just an update. I made those adjustments. I had to take my PD down to 1.0, but the game is MUCH more playable. Serbia with the new clouds....it's still got a ways to go (at least in VR with my rig) , but it is definitely an improvement. I will not play without VR... the VR experience is kind of the whole point for me. I know they will improve it! Thanks again guys!

Thank you Sirbum and fab.13! I did try reducing the Pixel Density, and that seems to help. My framerate was dramatically reduced from what it was in the previous version. I have some hope now though that digging further into my settings can help that. It's considerably better after the PD reduction, but still relatively bad. Thank you Sirbum for the insight on the controller thumbsticks as well as the mirror eye source! I will try unchecking the palm button when I get home tonight. Thanks again folks!

Did I mention that I am a complete Noob compared to probably just about anybody on this board?? I will give it a try. PD means Pixel Density? It seems that the options have changed. Don't know what Mirror eye source is. Unable to use hand controllers to activate things the way I could a couple of weeks ago. Ugh...Thank you for trying to help, Fab!

I tried the complete uninstall, fresh install, re-install modules, This didn't fix anything for me. hmmm....