javelina1

there's a mod for the Jug to slow down the trim. I was using it before I dropped from the Jug to fly the Corsair.

excellent videos! I've learned quite a bit. looking forward towards your Corsair campaign.

went 3 for 3. launch and trap. woot! just gotta watch out for that engine torque. keep her steady.

good point. I'm editing my Carrier mission to now have the wind at +20kts. I had it at 10kts, but I have the Essex moving at 27kts. on the first 3 attempts, all were bolter's. The 4th I managed to snag a wire and got a C rating. I'll give it a whirl with the increased wind.

indeed, it does help a little bit.

hopefully so too!

awesome, what a great find!

Here's what I'm using: Pitch - curve 22, y saturation 80, deadzone 3 Roll - curve 22, y saturation 80, deadzone 3 Rudder - curve 30, y saturation 80, deadzone 3 This is working good for my setup, (rig specs in my sig). Using a WH stick with a VPC WarBRD base and no stick extension. YMMV.

too bad there's no way to temporarily use the P-47's sound for the Corsair....

Started out with 2 free flights, to help with adjusting the controls. Then went through 2 take off and landing cycles. Managed the engine much like I did in the P-47. Made sure to get off the max RPM a couple min into the flight. Watched the cylinder head temps, along with the oil, etc. Played a little bit with the cooler and cowl settings. Really didn't have any issues with the ground handling. Made sure to lock the tail gear on the take off roll. For the moment, I'm using for the pitch a 30 degree curve and 5 deadzone. Roll is 15 degrees and 5 deadzone, and Yaw is 24 degrees and 5 deadzone. I'll fine tune them further. I've got a 3 day weekend. As noted by others, I think the sound is the soft spot. Would expect a bit more, like the P-47's R2800. Roar! Overtime she'll improve. What was cool. I put in her in a steep dive and really picked up some speed. I could hear the whistle!!!

The Jug was doing this as well when it was initially released. I remember keeping the fuel load under 60%, or something like that. Tamed her out a bit. But then further updates came out. In a little while, I'll jump in the Corsair. I've been flying the P-47 for the last few weeks, so I'll have some sort of reference (for the R2800). She's fresh out, so I have my expectations set accordingly. All will come together.

It notes this module is early access yep, it's there. mods/aircraft/F4U-1D/Doc

mine too! you know what I'll be flying for a while with... woot!

my bad I missed the sale. but the next time it comes around, I'll definitely buy! Keep it going slughead!

I installed the 566.03 driver. Did the normal removal of the DCS fxo & metashader cache. Also, flushed the NVIDIA cache via the disk cleaner. Then I took the additional step of clearing out: C:\Users\USERNAME\AppData\Local\D3DSCache C:\Users\USERNAME\AppData\Local\NVIDIA\GLCache C:\Program Files (x86)\Steam\steamapps\shadercache\ C:\Users\USERNAME\AppData\Roaming\NVIDIA\ComputeCache C:\Users\USERNAME\AppData\LocalLow\NVIDIA\PerDriverVersion\DXCache C:\Users\USERNAME\AppData\LocalLow\NVIDIA\PerDriverVersion\GLCache There's a dude on the MSFS forums who says to flush these out as well, whenever you put in a driver update. (I don't have DCS or MSFS via Steam, but I still cleared that one out, though I know it wouldn't have any impact) I then flew one of my toughest Syria missions. It was FLAWLESS! I swear, it was the smoothest flight I've ever had. FWIW, I'm happy and flying along just fine.... (though those poor b*st*rd's on the receiving end of my Rhino aren't....)

thanks. I'm going to give that one a shot as well....

what driver version are you using? I'm on 560.70, and having a lot of crashes since the latest DCS update, including the most recent hotfix

same here... even after this hotfix, all of my Syria missions are crashing several minutes into them... (yep, I've even done the long repair to try and rule out my install...)

I've tried yet again, after many updates and such. Still the same issue with AAR missions with the Aero. Starts to flicker and then blackout for 10 seconds or so after I connect to the boom. Any suggestions to trouble shoot?

thank you, looking forward to this bird!

I tried launching via mt, and have been at a white screen for about 10 minutes. I hear the F4 theme music jamming away. I have no mods installed, just vanilla. trying to get an image on my Aero, but nada.... earlier, I had checked that the toolkit did not have DCS checked. but I just went in again and looked, and there's the DCS and DCS World. so I made sure both were not checked (to be enabled). I'm now able to launch into VR. But unfortunately, cannot do any further testing until tomorrow...

same issue as well...

rats.... and here I was all excited about the new patch, and planning to fly the Rhino after I'm off work. (With my Aero)...

I've always flown F-16 style, so my stick has always been to the right of me, for all aircraft. So if I had an FFB, I'd have it off to right.... Been using a WarBRD (and TM stick), no issues getting to my crosswinds. Will continue to watch and assess these products as they come out. He's one opinion/data point, so I take it as such...

too bad you couldn't encapsulate the time/date into a virtual container, and just run it in that... (sorry, just pulling stuff out of my six....)