Pappy_Gunn

More info that might help: Usually I run DCS on Quest 3 using the Meta Quest Link (open XR toolkit etc) in Oculus VR mode. Not Steam VR. It works for me, getting 80 fps on all aircraft except F4U. Today I ran DCS using Virtual Desktop (the version for Quest) on Quest 3 starting the program from there (not steam). Asking for 72 fps. On the Normandy map, I got a pretty steady 60 fps on the F4U (solid 72 on the P47). On the Mariana map I got about 60 fps, dropping to 30 on takeoff. I assume it's the scenery pointing in that direction that tanked the frame rate. With some altitude it went back up to 60 fps.

I recorded it. It's towards the end at about 13:50h (mission time 55 mins). FW 190 A-8 (lw11 #003). That bugger is flying in circle at about 3000 ft, on fire, trailing smoke. He's doing between 350 and 440 mph. As I said, I've seen this before, and as I recall pumping more lead into a plane that does that is useless. Tacview-20250811-193757-DCS.zip.acmi

Flew a P47 mission today (Wolfpack DLC), bomber escort. We mixed it with FW190s and Me 109s. A FW190 was on fire, trailing heavy smoke and kept flying around in circle at about 3000 feet. I could not catch it with 52 in of manifold. He flew like that for 5 minutes (at least) and I gave up. He never crashed. I flew another 20 minutes going home and it was never recorded destroyed, he's probably still out there on fire doing 400 mph. I have encountered this several times before.

Tried it with cockpit global illumination turned off and it helped. Still only getting 40 fps versus 80 with P47. Spikes here and there, but at least it's flyable.

I will try turning cockpit reflections off, thank you. For others, note that I said this is not limited to the Mariana map (although it is the worse). It alsho happens on the Normandy map, on the ground, with zero other aircraft. Only for the F4U, all other aircraft OK. AMD Ryzen 9 7950X3D, X870 Gaming Plus Motherboard, NVIDIA GeForce RTX 3080 Ti, 128 GB RAM. Meta QUest 3.

Is this happeneing to others? I play VR, and my "ask" for frame rates is 80 per second. I have half a dozen warbirds, 3 helos, and a bunch of jets. I get 80 fps steady with all of them. Playing Reflected campaigns in the P-47, I still get 80 fps. With the Corsair, I get about 15-20 just standing still in either Mariana WW2 or Detling. Same setup with a P-47, I get 80. On the Essex, I get about 40 fps in the Corsair tops, usually less. This make the aircraft unplayable in VR. Thank you for your attention on this matter...

Reflew the mission. Waited until the pilot (me) sighted the airfield and ordered the attack (there is a voiceover where he orders the attack automatically). I then Used F10 menu to order the attack. This time the F10 menu had to option to attack primary (as opposed to attack primary and rejoin). Ordered Flight, second element and wingman to attack. They all did, and the mission worked fine. Issue solved. Maybe I ordered the attack too soon the first time around.

Many of the needles on the instrument panels are all over the place. RPM, manifold. Most of the other warbirds (like the P-47, Spit and P-51)have steady needles, allowing you to set RPM and manifold to a set value. F4U? Sure, there is a bit of vibration, but this feels like a prop blade has a foot missing or the engine is missing a few cylinders. Well you'll just have to guess. I doubt very much it was this bad in real life.

I am familiar with the use of the F10 menu. I have flown the previous P47 Wolfpack campaign as well as the P51 and Spit campaigns. I watched the video previously also (good one). I have also mapped a button to talk to the formation as suggested (that is different from the \ ). Works like a charm, except for this one mission. I will re-fly it again, and wait until the pilot (me) says he spots the airdrome and try the F10 menu again.

Dang, sorry, it's mission 8! The mission where you attack an airfield with just Platform.

Mission 2 cannot complete. When I get set up to land back on base, the game crashes. Maybe it'e just me. Mission 9: The Squadron does not attact the airfield. I've tried ordering them via F10 (attack mission target and reform). Bomb with me. Etc. Nothing. Then I hit a trigger where my alter ego orders the attack but the Sqn does not attack. I order them again with the F10 menu. Nothing. Maybe I confused the AI? What steps should I follow to get them to attack? Does the trigger make them attack without player intervention?

A bit dissapointed with the flight model but I assume they will tweak it. It handles poorly on the ground in that it is difficult to swing the nose around it doesn't feel like a taildragger. It doesn't want to turn, you need to input the brakes too much. Little inertia. I have all the other DCS warbirds. The controls are definitely very twitchy at low speed, especially the pitch. Way too much response at low speeds. Same with the rudder, unlike on the ground. It is difficult to trim. You always have to be on the trim, way more than a Spit or Jug. All 3 axis. Yuge amount of torque low speed carrier approach, but I understand that is historic but I wonder how much. They have to smooth down the response. I have my joystick curves set up as per the manual.

Easy. Set yourself up, crack throttle 1 in (or to about 1000 rpm equivalent), prime 8-10 seconds. Engage starter. Keep on the starter until you hear the engine cough and run. Run. Yes, you gotta hear it run before you engage mixture, it's a bit different from the Jug. THEN engage mixture and let go of starter. I have starter and mixture mapped on 2 different buttons for this aircraft. Works like a charm.

Very late in answering, but here goes: I use the Thrustmaster Warthog throttle. The R/H throttle I use for the throttle (engine manifold pressure). The L/H throttle I use for the turbo. I never link the two together. The gray slider I use for prop RPM. So this also duplicates the layout of the P-47 throttle quadrant. As a bonus, I use the thumb switches for the various radiators (oil cooler, cowl flaps and intercooler).