_Hoss

I've got two Battle Es. One from VA-94, And one from the Enterprise, 1986, 1988 WESTPACS. Which ever squadron wins the Battle E at NAS Lemoore gets to paint the static display Hornet at the main gate in their squadron colors each year. AIRPAC inspections play a major part in winning. AIRLANT on the East coast. So you need to have your shiznit all in one sock, and remember where you keep it. Sustained Superior Performance all year.........because one awe shiznit erases a thousand attaboys.....

Battle of the Philippines Sea, Surigao Straits, San Bernardino Straits, Okinawa... Korean Peninsula. Vietnam, Laos, Cambodia, Thailand.

A-20G is good for ETO and PTO. P-38L, same situation...

Battle of the Philippine Seas, Surigao Straits, San Bernardino Straits.... Or Okinawa....

@-Rudel- LOL, who died and left you in charge..... Next, we don't use Voice Attack, and it's not required of us to do so. Who all is "WE" pray tell... are you speaking for everyone?...... You might want to run that past the people who use Voice Attack, along with VIACOM for the F-14, F-4, AH-64, or anything else with a Jester, Phester, Petrovich, George, or any other Tom, Dick, or Harry in the back seat that you need to relay commands to or get information from.... Not to mention call outs to the Tower, Tanker, Ship, Ground Crew, and any other entity you need to interact with, without taking your hands off your HOTAS. The funny thing is, the Comms push to talk (Call Radio menu) RAlt + \, actually pushes the mic button on the throttle like the VOIP command does when pushed. The \ does not. Certain universal commands should be uniform among all the modules, and not a hit or miss situation. Attention to detail is a must.. especially when someones money is involved...... That's JMTCW.....

Mines a bit overkill on axis....

I'm no noob when it comes to using the Warbirds in DCS. I've had Lock On or LOMAC since 2003, and I was one of the idiots to go into the Go fund me for the initial warbirds. I learned really early (day one) the Corsair was touchy when it came to overheating. I have treated it like I do the Jug, except I can close the cowls on the Jug and and leave the Oil-cooler and Inter-cooler in neutral, and fly like my hair was on fire, if I had any. So I started doing the same thing with the Corsair, except I usually leave the Cowl flaps at 50% and set the Oil Cooler and Inter-cooler radiators to 50% like I do the Jug, and I never overheated. And all of my gauges were in the green when the engine stopped, I paused the game and looked at them when it seized up twice and the one time I thought I had ran out of fuel in the first 5 minutes of the flight with the engine windmilling. I normally fly at 2300 to 2400 RPM, and 35-45"MP. I hardly ever break the MilPwr throttle wire, there was just no need for it, unless I needed to expedite a One Pass, Haul Ass escape maneuver.

I've got a WW Super Taurus, the Afterburner detente on it stops just before the Corsairs throttle breaks the Military Power wire. Before this last update I never needed to break that wire to take off, or execute most of the mission. All three times my engine quit I had never gone into MILPWR. 2400-2300 RPM and 30 to 45 MP... Cowls around 50%, oil and intercooler at 50% (just like the Jugs Neutral). I had heard lots of complaints about taxing but I always had to be careful not to use too much differential breaking or it would turn way to fast. Now it will not turn left at all while trying to taxi on shore, it'll still do donuts turning right. In case your wondering most of my tests were from the boat, just go straight. I put her on the elevator and she'll be a Hangar Bay Queen for a while.

Everything I mentioned in the above post all worked before this last update. I'm not changing anything in my setup for Voice Attack, it works perfectly with all my other modules. Sadly the Corsair will remain an SSD Hanger Queen until M3 puts out a hotfix and hopefully gets it back to the way it was before this last update. Thanks for the thought though. Appreciate it........ Here is the comms menu for the Corsair... No Radio Call Menu command... i.e. RAlt + \ Here is the Comms menu for the Jug.... Oh look....Bingo, Bango... Push to talk (call radio menu)...... you're going to need this for Voice attack. All the Radio command menu items need to start with this. Things like Pause Game, Mission Brief are not on the Comms menu, they are regular commands in the Settings GUI. But to call the boat, tower, or your flight, you need it. I've got 73 commands on VA now and I will not go and change (RAlt + \), to (\), just for the Corsair. And why bother if it's all wonky now..... I'm not posting any track files, I'm not the only voice in the wilderness that is complaining about this last update. Any Beta tester worth his salt would of found these problems in a New York minute. My group has shelved the Corsair for any of our weekly missions. It's just to buggy right now. Which sucks, because we are a Carrier based group, and really wanted the Corsair to shine.

Well, my engine has quit on me three times. Once, like I ran out of gas, with the engine windmilling, I switched tanks, and it would not start again. I paused the game, checked all the gauges, and saw that everything was in the green and with a full tank of gas. The next two times, the engine seized up on me, and the gauges were all in the green as before. The second little Easter egg I found is that it will not turn left while taxing on shore, it turns right just fine... I immediately checked my curves, which are the same for all my modules, and then went to the Jug to test it, and it turns left with the brakes just fine. My third little Easter egg was that there are no Comms commands. I use Voice Attack, and the first action in the command line is to press RAlt + \ for radio calls. Well, it's not there in the Corsair Settings GUI; the backslash is there (\), but nothing else for communication with the game. After that, with a few select curse words, I put the Corsair to bed because there was no further reason to mess with it. I also did three repair functions on it, two quick ones and a long one with all Mods turned off. The Mods were all off for the third engine seizure, the brakes not working, and the Comms RAlt + \ issues. All the guys in my group are having the same problems, plus a few I hadn't experienced before. I find it hard to believe a group of beta testers could miss issues this significant. Now, how long do we wait for a fix?

How many different asset packs are there to Massun's pack? I'm still trying to play some old A-4E missions and I'm either missing some Massune pack item or a Tetete item... It's frustrating as hell when these threads become all convoluted and you don't know what you are missing.

I'm still waiting on my Me-262..... got hornswaggled out of that.... Live and learn

I slowed all of them down.

The PTO2 comes with the two mounting brackets, your going to need four T-Slot nuts in M5 and four M5 x 45 screws. Two on each side of tour 4080 extrusion. I would suggest downloading the manual from WinWing for the PTO2. And looking at MTSIM for their T-slot nuts. You can probably get them faster off Amazon. The M5 cap nut screws you can find at any hardware store. Look for 4080 extrusion hardware on Amazon. But definitely go look at the manual for the PTO2. And MTSIM s manual assembly of the MIP to 4080 desk mount.

Well, I don't have a problem with braking or turning in the Corsair. The curve I use is a J curve (something I used on the throttle in TARGET) and it works great. 0 90..... acts as a dead zone 0 -35..... The J curve The 90 is a dead zone at the top... What I have issues with is the spastic trim, especially the rudder trim. The slightest adjustment is like kicking the rudder pedals. I've tamed it somewhat with extreme axis curves. But don't get me started with low speed handling...... It is what it is; very early access, hopefully it gets fixed sooner rather than later. Because it has great potential......