Recluse

Did you turn up the Lighting Switch? Worked for me in VR See this video:

It has ALT HOLD (not implemented yet, I think Matt Wagner said in his latest video on Post-release questions) and ATTITUDE hold on the FORCE TRIM switch. See Manual page 63 (In the manual both are shown as "TODO" so maybe neither one is implemented yet)

This is my understanding from the video.

Watch CASMO's tutorial. He explains that the lock is a pin that slides into a hole in the wheel. So after castering, the wheel needs to straighten out before the pin can drop in and lock it.

Having same issues. I have Rudder Pedals, but maybe they are a little out of calibration. Still I watched Casmo's video and he seems to be able to easily taxi straight with tail wheel locked. I also start spinning when I get the collective up to 35-37 or whatever they say in the Taxi/Transition training mission even with tailwheel locked.

Me too! I turned off the Monocle Frame in the SPECIAL tab and that helped a lot, but the IHADSS symbology is still a bit too BIG EDIT: Lowered my Resolution, and IHADSS is looking better sized. (And everything else still looks good) Might turn the Monocle frame back on and see how it looks now.

Hmmm, I went to do this and I saw another folder metashaders2 with access date of yesterday... does this get deleted too?

It did not run well on my Quest 2/3070. Got a little better when I cranked the resolution DOWN from my usual DCS settings. One thing I found was that the IHADSS symbology seemed way too LARGE I had trouble seeing the Altitude as it seemed to be occluded by the cockpit ironwork and the IHADSS seemed to overflow the area of the cockpit glass. Maybe there is a setting for this? I also found the monocle piece that looks like a mirror sticking out that shows up on the right a little too intrusive, but it might be better if I could get the framerate up a bit. EDIT: Turned monocle frame off and it was a little better but still symbology looked too big. Might try the LEFT eye and see if it is any better. Well, I am going to watch some videos and read the manual in case I missed some settings.

So I jumped in and took off with a boot full of left pedal and then managed to get going and flew pretty easily. Then I checked the settings and saw that I had that FFB INSTANT TRIM on. I changed it to the Central Position Trimmer mode, and was all over the place. Of course I hadn't bothered to map any TRIM controls or learn how to use them It seems to me that the FFB Instant Trim setting is kind of a cheat code for flying.. Hovering and landing, not so much

OK got it! I figured I was missing something!

I misunderstood... content removed. See Nealius's post below.

I saw this image on the RAZBAM discord. For AV8B NA Harrier, of course... The "improvement" looks to me like a WORSE image closer to reality rather than an "improvement" to FLIR quality in DCS. Not sure what to think about it.... LEFT = NEW Right = Current

Thank you for the reply!! At least it confirms my thoughts. I found some workarounds using lesser used HOTAS buttons that don't interfere too much with normal functions when being used for Menu Nav, but I may look into some other utilities. DCS Menu Nav is true gift to VR users!!!

That WORKED!!! Many thanks!!!!

Thanks!! I will give that a try!

My experience too. I tried mapping the Recenter VR view, and it works if I am a little off in the Menus or Controls Screen, but once I get into the F/A-18, the view is down and to the right. Hitting RECENTER VR puts me back there every time, so it MUST have gotten saved that way somehow and I cannot figure out how to reset it. I did save the view with RALT-NUM0 when it was correct, and I COULD retrieve it with LWIN-NUM0 to recall the SNAP VIEW, but that was only as long as I held the key combo down. Every time I exit and re-enter the cockpit I get the skewed view. I cannot seem to change the @#$ default view.

So every time I get into the cockpit, my View is messed up, e.g. too far down and to one side. This seems to be worst in the HORNET but it happens in other a/c as well (AV8B, A-4, less so in the A-10C) I adjust my view using the camera controls, RCTRL-RSHF-Numpad keys and then hit RALT-Numpad 0 to save it. But it DOESN'T SAVE. Something must be saved because I get he same crazy unacceptable view EVERY TIME. In 2D view, without VR, the default view looks OK. I also crank my seat position a bit, but I don't expect that to be saved. What am I missing????

You can also use the built in DEBUG tool: C:\Program Files\Oculus\Support\oculus-diagnostics (or wherever you have your OCULUS folder) Run OculusDebugTool.exe Many of the same options as Tray Tool and no new download required Seems like most recommendations are to mess with it in the Debug or Tray tool and leave DCS Pixel Density at 1.0, but either way works. I've tried both and just ended up doing it in Oculus settings vs. DCS Note: I left Encode Bitrate at 0 which is the DEFAULT. It is probably set to about 120 at default setting. I usually crank it up to 300, but then I have to crank it down if I decide to use AIRLINK vs. the LINK CABLE, so I just leave it at the Default to have more flexibility. Haven't noticed much difference. Usually I use the CABLE for DCS since is a little more reliable and continues charging so I can fly longer before the battery runs down.

On my Quest2, the Hornet DDI's are much clearer than the Harrier (esp Harrier left DDI). Just recently started flying A-10C and it looks gorgeous in VR, though I DO have to lean in to really see the TAD page. RTX 3070 Core i7-10700K I keep changing my settings, but currently: 90 Hz 5152x2608 (1.4x) SS (Oculus Tray Tool) 1.2x (Hmmm I usually have it at 1.4.....maybe I cranked it down when I upped the resolution) DCS: Pixel Density 1.0 IPD 66 MSAA Mask 0.90

Question: I upgraded my HOTAS to a WINWING ORION, and I am trying to use some of the buttons/switches on the Throttle Base. I cannot get them to work. I suspect it is because the numbering on the buttons is above the Windows limit of 32. For example: [Buttons] BtnToggle = 3Joy7 BtnItemUp = 3Joy109 BtnItemDn = 3Joy111 BtnSelect = 3Joy85 The TOGGLE WORKS but the others do not. I guess DCS gets around this. Any way to use Menu Nav with higher numbered joystick inputs?

I am guessing the Cougar weighs pretty much the same as the Warthog...so probably a no-go.

Bit of a Thread Resurrection here... I bought the adapter just in case, though I didn't think I would ever use it. Just started messing with the A-10C and I find I want my TMS back, so was going to put on the Cougar grip. I AM leery of the Cougar weight on the ORION base. Wondering how many folks have actually done it and if it it OK despite the weight? Not sure I want to "spring" (no pun intended) for the new WinWing F-16 grip, though it looks mighty sweet! As an aside, anyone have an A-10C HOTAS mapping for the stock F/A-18 ORION that they would like to share? I was going to use the little RECCE MARK Hat as TMS, but as I fly in VR, I tend to use that for the DCS MENUS radio mod as well as paging through the Kneeboard.

LOL. Losing it on the Landing Roll in the crosswind on Mission 5 at caused me several re-tries after otherwise successful attack runs. TAKING OFF in the Crosswind on Mission 6 proved similarly difficult the first time I tried it. I realized that at the end of Mission 5, I forgot to put ANTI-SKID back on since it was off from Carrier Takeoff....but it didn't help much during Mission 6 Takeoff. Still felt like I was ice skating. Will get back in the saddle again soon...but now you have me worried about the rest of it. I have honestly NOT done many Night Ops to being with, so maybe I will do a few practice hops with NVG before I tackle the mission.

Ahhh good call. I didn't even think of it. NEXT TIME!! I might go practice strafing a bit as well on general principles! Hehe.. WAGS makes it look so easy

Good job! I made multiple passes as well, trying to conserve ammo but didn't get the hits. Seemed like the shells were gently floating down everywhere but where i aimed them... I really wished I could invoke a RELOAD cheat and just keep trying!