Lots of bugs in this last release

[_Hoss]

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?

[GTFreeFlyer]

49 minutes ago, _Hoss said:

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?

Hey Hoss, it's the same GT from your group

Attach a track file where your engine quits and I'll gladly look at it for you and see what's up.

Taxiing and ground handling has been very difficult since the module was released.  There are other threads on that, so no need to discuss it here and start a new conversation.  It has not yet been addressed.

I'm confused what you mean about the slash command for comms.  I press it, the menu appears, and I'm able to hit the F keys to select items from the list.  So for VA, I would assign wingman cover me command as:  \ + F1 + F7.  Is that not working for you?  Would be strange.  Not sure if you knew this or not, but you can also assign keybinds to move up/down, select item, etc once the comm menu is open.  I assign them to a hat switch along with a modifier that I hold.  It's awesome and not so well known.  In the controls options, instead of picking the aircraft in the drop down, choose Coomand menu.  I have hat bindings for Command menu next item, Command menu previous item, Command menu return, and Command menu select item.   There are also keybinds for F1 thru F12, so check there that they were not cleared from your list.

 

Cheers,

-GT-

[_Hoss]

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.  

Edited yesterday at 06:56 AM by _Hoss

[Ghostrider 147]

Please attach a track file, so far a bunch of other people were having the same problem, but they were really overheating their engines because they didn't properly open up their oil cooler flaps. Magnitude 3 updated the engine behaviour and damage model in the last update making it more sensitive to higher temperatures I believe. Lots of things to take into account when flying the Hog 

[_Hoss]

1 hour ago, Ghostrider 147 said:

Please attach a track file, so far a bunch of other people were having the same problem, but they were really overheating their engines because they didn't properly open up their oil cooler flaps. Magnitude 3 updated the engine behaviour and damage model in the last update making it more sensitive to higher temperatures I believe. Lots of things to take into account when flying the Hog 

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.

[LeCuvier]

The engine management has obviously become more complex, and the early access guide does not provide good guidance on this subject. The "Enable Water Injection" switch is working now, but again, no guidance. I'm not flying the Corsair in air combat for now, as I have no clue how to keep the engine from just going on strike, and I'm a bit spoiled from flying the German birds..

However, I have no problem with turning left or right on the deck. I use the axis bindings for left and right wheel brakes, but I also tried with pushbutton commands. No problem here. I just tried again to be sure. If you can't left-turn with the brakes, that means you will do a pirouette like an ice skater when you hit the brakes after touchdown. Is that so? Do you use axis or button bindings for brakes?

[Scotch75]

I think weather vaning due to wind on the ground is too strong when taxiing. It is almost impossible to turn away from the wind (even with diffential braking and power), then the fuselage will snap around. Either that, or the tail wheel castering is not loose enough.
Cheers!


Sent from my SM-G998B using Tapatalk

[Art-J]

Hoss, the module never had separate push-to-talk command, so I'm surprised it was picking up your VA in the first place . Should be no changes here.

I'm away from my gaming rig so can't check  implemented changes now, but reading other threads, I can see it's going to be a challenging experience.

[JupiterJoe]

The aircraft is damaged from the moment you spawn and cannot be repaired:

I'm as excited as anybody to fly this gorgeous aircraft, so hope a fix comes soon, but I first posted about this in June and nobody's acknowledged it.  -Rudel- states in the above link that the Corsair has a unique damage model.  

Edited 21 hours ago by JupiterJoe

[Ghostrider 147]

6 hours ago, _Hoss said:

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.

No please don't think I'm accusing you of being a noob, I never meant my message to sound that way, apologies! I just figured a track file would help to see where exactly things go wrong because currrently I'm not experiencing any engine issues, I just did a 30 minute hop in the Corsair, almost all the time at full mil power (50-54 inHg MP at 2700 RPM) doing some aerobatics practice and the engine ran perfectly fine.

I kept my cowl flaps at about 20% open and I kept the oil and intercooler flaps at about 50% open. Oil and cylinder head temperatures never exceeded their limits. I think a track file would help, since you are experiencing issues, it seems your engine is overheating when it really shouldn't be. Just trying to help!

[Saxman]

I did the same last night: Cowl flaps partially open, oil and intercooler open to about 50%. Water injection master switch was on, and I was verifying good water pressure on the dial. Temperatures never redlined, and I managed to keep the carburetor light off. The engine still shut down (sadly, I had a CTD after I ditched so couldn't save the track).

One thing I noticed is that I was getting BEYOND max rated MAP with water injection. It's hard to tell because of the exaggerated needle jitter, but MAP appeared to be settling above 60in.

[C_casber]

do you need to open the intercoolers when you dont use the turbo?

[-Rudel-]

On 8/14/2025 at 8:27 PM, _Hoss said:

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?

We're gonna make you wait for 2 months.

In any case, just because you played simulators since 2003, doesn't make you an expert on the DCS F4U-1D.
Also, please don't compare it to the P-47D where 150 octane fuel was used on an R-2800-63W in the ETO.
The F4U-1s used 130 Octane in the PTO, and an earlier version of the R-2800 series; the -8W.  It, requires different methods of cooling control.

And provide a log and track file at least.  Saying everything was in the green doesn't necessarily mean anything.
You don't mention your aircraft's altitude when switching tanks, etc.  Are you below 19,000-feet?
Did you try restarting the engine before switching tanks....and if so, perhaps you over primed the engine?

Track files and logs are very useful for our programmers.

Next, we don't use Voice Attack, and it's not required of us to do so.
"\" has always been the required DCS default key for modules; you can simply change it to what you require.

14 hours ago, Saxman said:

I did the same last night: Cowl flaps partially open, oil and intercooler open to about 50%. Water injection master switch was on, and I was verifying good water pressure on the dial. Temperatures never redlined, and I managed to keep the carburetor light off. The engine still shut down (sadly, I had a CTD after I ditched so couldn't save the track).

One thing I noticed is that I was getting BEYOND max rated MAP with water injection. It's hard to tell because of the exaggerated needle jitter, but MAP appeared to be settling above 60in.

Do the test again and provide a track.  The engine can overboost with WEP depending on the RPM.

[Saxman]

1 hour ago, -Rudel- said:

We're gonna make you wait for 2 months.

In any case, just because you played simulators since 2003, doesn't make you an expert on the DCS F4U-1D.
Also, please don't compare it to the P-47D where 150 octane fuel was used on an R-2800-63W in the ETO.
The F4U-1s used 130 Octane in the PTO, and an earlier version of the R-2800 series; the -8W.  It, requires different methods of cooling control.

And provide a log and track file at least.  Saying everything was in the green doesn't necessarily mean anything.
You don't mention your aircraft's altitude when switching tanks, etc.  Are you below 19,000-feet?
Did you try restarting the engine before switching tanks....and if so, perhaps you over primed the engine?

Track files and logs are very useful for our programmers.

Next, we don't use Voice Attack, and it's not required of us to do so.
"\" has always been the required DCS default key for modules; you can simply change it to what you require.

Do the test again and provide a track.  The engine can overboost with WEP depending on the RPM.

Posted in the specific engine stops thread.

Edited 4 hours ago by Saxman

[_Hoss]

@-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..... 

 

Edited 2 hours ago by _Hoss