Auger

My MFCD's in the A10CII will flash black screens and black partial screens, particularly the left MFCD. This is when the Maverick camera is on screen. I've also noticed the TGP has Gimbal Roll at times, even when flying straight and level and the target is dead ahead. I Haven't had this problem on other maps.

It would appear not to be a cable issue. I fired up Airlink with the Quest 2 and had NZXT running to keep an eye on temps. I loaded into my regular MP server, got into my A10 and as I proceeded with startup, the fans spooled up, I got dumped into Quest Home, and the monitor was off. I was raising my goggles occasionally to check temps. At one point I noticed a temp as high as 84c, but I'm not sure what it was as I was sitting on the ramp. I'm guessing 84c is high for a GPU? The CPU was showing about 40c. When the game shut down and the fans were running, I checked to see and both GPU fans were running pretty fast. At this point I assume it's time to look for a new GPU. Just my luck of course, when the price of vid cards are so high. 3070 ti or 3060 ti to replace the 2080???

Yeah, I have two new cables and it still happens, so I automatically ruled out a cable issue. I also tried USB 3.0 cable instead of USB C. I guess I should try Airlink and see if the problem persists. The problem started just a few months ago, so I have to wonder if maybe a Oculus/Meta update or a DCS patch caused something to glitch?

Thanks for the reply Alpine. I have an 850W power supply, so I would think that's enough for my system. In the 2 1/2 years I've had my system, I have never heard the fan run as loud as it does when the problem happens. My system was built by Xidax and came with liquid cooling but about a year ago the CPU started to overheat. On the recommendation of a local PC tech the liquid cooling was replace with a Cooler Master Masterair MA620M which is working well at keeping things cool. I've kept the video drivers up to date. I bought the Quest 2 for DCS and it is an improvement over the Rift S. Sucks not to be able to use it. At this point, I'm not sure what to try next. I doubt taking it to a PC tech will resolve anything, because they'd have to be flying DCS with the Quest 2 on to replicate the problem. I have Speccy and NZXT CAM to keep an eye on temps but when it happens I cant see the temps because the monitor is not receiving a signal anymore. Also when it happens I notice the HD light going. Fan_Trim.mp4 Open for suggestions from anyone.

I got a Quest 2 during Christmas and it seemed to run well for a couple months, but I've been having a problem with it the last few months. I have a Rift S that I keep plugged in to my PC and I use the Oculus Cable USB cable to connect the Quest 2 when I'm flying DCS. System specs Windows 10 i9 9900K @ 3.6Ghz Ram 32G RTX 2080 4095MB The problem is that sometimes while flying with the Quest 2 the game will throw me out and I'll be in the Quest 2 home screen. My monitor will lose the video signal, a fan in the PC has spooled up really loud and there is no way I can get the monitor back on, or close down the computer other than pressing and holding my PC power button (which I know is not good for my PC). I went back to flying with the Rift S and flew for over a week with no problems. I thought maybe it was the Oculus USB/C to USB/C cable giving me a problem, so I ordered a USB 3 to USB C cable made for the Quest 2 and tried that. 20 minutes into the game, the fan spooled up, I was dumped out of DCS into the Quest Home Screen and my monitor was black. I thought maybe it's a heat problem with the vid card, but then the Rift S doesn't cause this problem. I hate not being able to use the Quest 2 and I'm not overly tech savvy but I'd sure appreciate any suggestions anyone can offer.

Awesome, thanks.... love your co-pilot.

Would it be possible to see a photo of how you attached the throttle? I've been thinking of upgrading my Warthog Throttle also. It would be great not having to buy a new plate.

I've cant seem to figure out how to get GBU12's to pick up a buddy (Reaper) lased target. I don't have any problems self lasing, but I'm not sure the procedure for picking up buddy lased targets. I have the GBU12's set to 1688, Master Arm on, GBU's selected and set to CCRP, Master Mode set to CCRP, but as I make my approach to the target I'm not seeing the targeting cue fall line. I've searched YT tutorials on GBU12's but most seem to be dedicated to self lasing. Can anyone tell me the steps for using them with a buddy lased target, or point me in a direction that shows the procedure? I can do this effectively with the AV-8B, but that's a whole different work flow. Thanks

I've had this issue as well. Like Yurgon said it takes a very steep dive angle to get a valid CCIP. I find myself at about a 65 to 70 degree dive angle before I get a solid line and can view the bomb circle. Makes for an exciting bomb run. hehe But then, I'm a big fan of the CBU 97. There's no problem that can not be solved with a righteous amount of 97's applied.

Thanks Cap..... that did the trick.

Is it possible to have Scratchpad give Lat and Long in decimal for use in the A10C2? I seem to remember an older version that showed multiple type coordinates. I'm new to Scratchpad and not sure if I'm missing something. Currently using ver 5.0.

Did you get throttle only or buy the set (throttle and stick)? For some reason the TM site (US) is only showing the set or the stick separately but no throttle.

I've been contemplating replacing my Warthog throttle for a Virpil CM3. There's nothing wrong with my Warthog aside from the fact that I hate the slew control with a passion, so much so in fact, that I use one of my joystick hats for slewing, which of course takes up a valuable joystick controller that could be used for other things. After reading through all of the glowing recommendations on this slew replacement, I decided to take the plunge an order one today. It's not cheap, but it's a heck of a lot cheaper than a new Virpil throttle. Hope I made the right choice. lol

Sometimes it's the simplest of things... sheesh Well, I had turned off Air Link in Oculus Home and couldn't figure out why the Quest 2 was ignoring the cable and using Air Link when I had it plugged in. Well, that's because I had failed to turn off Air Link in the Quest 2 settings and it was choosing Air Link instead of cable. Once I figured that out everything came together and the cable connection was made and setup completed. I can not get over how much better the graphics are using the cable, and the Quest 2 is definitely an upgrade from the Rift S. The cockpit labels were readable even with these old eyes and the terrain looked sharp and detailed. I'm a happy camper. Now, I'd like to get the best possible, but not really sure I can figure out Oculus Tray Tool, Oculus Degug, SideQuest, etc. All those settings are a bit intimidating and I'd hate to screw up a good thing. Are there any tutorials on how to use these different software? Much thanks guys for the help and encouragement. I was pretty bummed last night thinking I had made an expensive mistake. The Q2 was well worth the purchase.

System specs. i9 9900k 3.6g 32g mem RTX2080 Thanks, I'll give that a try. Going to work on figuring this out today.... or I'll be back to flying on the Rift S and looking through a screen door. lol

So the wife got me a Quest 2 for Christmas to replace my aging Rift S and I've got to say it's been a real PITA. For starters, I have every light in the room on and I always get a message saying there's not enough light for the headset, yet it doesn't seem to effect tracking of the headset or controller. I use about 1/4 of the lighting with the Rift and have no problems. I go into Oculus Home and it shows the Rift S and the Quest 2. I have the Quest connected via Oculus cable to the back of my computer and Oculus Home shows that it is connected and the Rift is in standby. Yet when I try to launch DCS via Steam it doesnt show in the goggles and Steam VR says it cant detect a headset. When I try to launch in Oculus home it says it cant detect a headset. Yet the Oculus Home say Oculus Quest Connected. I was finally able to connect via Air Link, but the graphics at distance looked muddy and up close didn't see to have as much detail as in the Rift S. Not sure where to go from here. I'm not a tech wizzard like most of you and I chose the Quest over the G2 because I thought it would be plug and play like the Rift was... NOT. Any suggestions, greatly appreciated.

I have and use the Rift S. While it's good for what it is, I can not recommend it considering the new headsets out there today. The screen door effect is the main reason I'm upgrading to a Q2. I was having a hard time deciding between the Q2 or the G2. In the end I decided since I already have quite a few Oculus games and I don't feel like jumping through hoops to get a headset to work, the Q2 was a better fit for me. It's plug and play, should have much better clarity than the Rift S and no screen door effect. Also, I can use it without the cable for other games (Onward, Contractors, etc) while in the living room. I wouldn't buy a Rift S unless as Tundra said, you get a massive discount. That said, I'm sure I will eventually get another PC devoted headset like the G2 in the future. From what I've read, HP has already made some major upgrades to the G2 and I'm sure it will only get better. And who knows what Steam and other VR hardware developers are going to come out with next year?

I'm working on my ordnance delivery skills with the Harrier and am a bit confused and frustrated. The last couple days I have spent quite a few hours on MP servers practicing with APKWS and dumb bombs. I'm finding that getting kills is almost impossible on some armored vehicles. I had made multiple runs at both a T72 and BMP3 using lased APKWS rockets shot in salvos of 4. Neither the T72 or BMP3 sustained any damage with direct hits. On one particular run I did manage to cause 5% damage to the T72 with 4 rocket hits. Maybe it was the angle of attack? I'm finding MK20's all but useless, but when flying the A10A I would normally clean up with the CBU97. Practicing with the MK 82's and dropping doubles, again, I couldn't scratch the paint on the T72, despite both bombs hitting about 5' either side of the tank. What am I missing here? Do the 82's need a direct hit to be effective? Are the APKWS's just to weak, even in salvos of 4? Is the MK20 useless against armored vehicles?

Thanks for all the replies. So far it looks like the Quest 2 would be the better choice as I need to consider that all the Oculus games I've already bought would be useless with the G2. Two quick questions... Will the Oculus Link cable, connected to the back of my PC keep the headset running/charging for marathon flying or do I need a second USB cable connected to a hub? Watching YT videos I see a couple people say that while connected to the PC there is compression going on that makes the Q2 look worse than the G2 or even Q2 stand alone. The comments were on reviews of about a year ago, so wondering if that compression problem has been fixed.

With all the Black Friday sales going on I'm seriously considering replacing my Rift S. DCS is running pretty smooth with the Rift S, but to be honest I'm starting to tire of the screen door effect and these old eyes need better clarity. Was flying on a MP server yesterday, I was in a Harrier and had been chased by a Mirage who must have been bingo weapons and turned for home. I had no missiles left but decided to turn and pursue with the hopes of getting a gun kill. I knew where he was via the map and we were at the same altitude, but damned if I could see him until I was just about in gun range. Made the kill and it was my first gun kill. Was great fun, but decided then and there that a new VR headset was in my future. My thoughts for the Quest 2 is... it's cheaper and easier to setup. I would have it connected to the PC for DCS, but I also like the idea that it can be used in the living room for other VR games. I'm not sure if this is correct, but I've read that because of the battery you only get a couple hours of playing time and that the cable does not power/charge the headset while playing. Is this correct? If so it would be a deal breaker as I sometimes spend 3 or 4 hours on MP servers. The Reverb G2 appears to have better clarity and colors. The downsides are the setup, I'm not tech savy, so all this talk of WMR, debug tools etc, etc, leaves me scratching my head. Also heard the G2 needs some horsepower to run well (my system specs below) and that the controllers feel cheap compared to the Oculus controllers... and I do use my controllers while in game. And if a better graphic card is needed.... I refuse to pay the inflated prices for the 3000 series cards. Would have to wait for a price drop and that could be a couple years down the road. Sorry to be verbose, but cant seem to make the decision one way or the other. I surely dont want to make a $400-$500 mistake. System specs. i9 9900k 3.6g 32g mem RTX2080 16g Know this topic has been batted about quite a bit and I've read most of the threads, but still would appreciate some input. Thanks

If I may... I think your problem is you have "Documents" in the path. My A-4 is in C:\Users|My name\Saved games\DCS\Mods\Aircraft\A-4E-C

LMAO I saw the title of this thread and thought WTH???? Who could ever go back to 2D after flying in VR? Even though I'm on a lowly Rift S the immersion is unbelievable and I could never fly again in 2d. It would be like going from UHD TV to an old black and white with rabbit ears.... and yeah I'm sure there's more than a few of you who can relate to that comparison. lol

I was wondering the same thing about a Virpil Black Friday sale. I have the Mongoos Stick paired with a Warthog throttle, and while the Warthog is not giving me any problems, I'd really like to upgrade to the Virpil throttle. Keeping an eye out for a sale. The Winwing throttle looks tempting, especially at the sale price, but the throttle QC complaints in the Winwing forum makes me leery. I know the quality of Virpil.

I thought that also, but in reality you have to go in and clear that column for every plane you have. I also cleared "General" and "UI". I was then able to assign the buttons I wanted to the command I wanted. Also, assigning the controller buttons is not like assigning the HOTAS buttons, where you open the box and then press the HOTAS button you want to assign.... instead when you open the box in the column (mine said Oculus) you have to use the pull down menu and select which button, A B X or Y, or thumb controller you want to assign to that particular command. For example, I assigned my A button to bring up the Communication menu, the B button to bring up the End Mission menu, the X button to bring up the Kneeboard and pushing in right and left sticks cycles the pages of the Kneeboard. I'm sure I'll make some changes in time, but it's actually working pretty well. I just wish that when we got the patch, there would not have been buttons already assigned. It was a bit time consuming to go in and clear each and every plane and helicopter. Still... the more I'm using the controller buttons for my selected commands, the more I'm liking it.

Since the patch, I've gone from mid 40's to mid 20's fps in my Rift S. Im not overly tech savy when it comes to graphic settings. All I know is that before the patch I was flying along smoothly and spending hours enjoying the game, now I find myself shutting down after 30 minutes. Hope it gets fixed soon.