GTFreeFlyer

I found it. It was on Magnitude 3's Facebook post on Aug 14, describing the new changes in the update the previous day.

The taxiing got messed up with an update while you were away. Way too many posts already on this topic. It’s not an issue with the ferry mission. Search the bugs section for taxi issues and you’ll get caught up. Cheers.

I have been doing aerodynamics and aircraft sizing and configuration IRL for the past 20+ years and can chime in here. The size of the vertical surface alone tells you nothing. Please don’t make any assumptions based on how big that thing looks (insert “that’s what she said” joke here). You have to take the tail arm into account as well. This would be the distance between the wing and tail’s aerodynamic centers (tougher to compute, but close to the 1/4 chord of each). Also, there’s vertical surface ahead of the wing center (lonnnng nose) that will take away from the tail’s effect. The combination of all this is taken into account when computing the “vertical tail volume coefficient”. Someone here can research that, and then use three-view drawings to estimate areas and lengths if they want a fun activity. You can take that coefficient and compare it to some known coefficients of other similar aircraft. As for damping, that goes along with what I mentioned above, but one more thing to consider is inertia. In yaw, there’s a big ol’ massive engine being swung around. If you aren’t slow and smooth with it, it’s going to be tough to tame. Wish I could fly a real Corsair to verify, but I used to have scale RC Corsair that exhibited similar behavior. Even when comparing to other scale RC warbirds I’ve flown, the Corsair was always the most “wiggly”. Yeah, small scale planes aren’t representative of full scale, so take that for what it’s worth. At least in comparing it to others of same size, the characteristics match my experience in DCS. I haven’t really had any issues keeping the nose steady with some curves on the axis, and some good rudder pedals that allow me to be smooth and precise. I can see it being an issue with my old cheapo pedals (CH), or even worse, twist sticks. I definitely suggest playing with the curves and just training the muscles to be smooth, with slow movements. Push a very little, wait a second, repeat. I find it not fair to compare to the other warbirds. Each plane always has its own quirks to learn which is why we all love picking up new planes in the first place. I think it would be quite boring if they all flew the same, not to mention, the Corsair would never have been so legendary if it was exactly like everything else in the sky. Every time I hop into the Corsair in VR, I feel like I’m part of that amazing history. Anyway, if you are taking on my “tail volume coefficient” challenge, feel free to ping me for help if you get stuck with something.

Good question. Can’t remember. It was either from the manual in the install folder (whatever the current version was on the date I posted that), or from an updated post I found by Rudel as he has shared some stuff like that in the past before it was released in a DCS update.

Yup, this one confuses lots of people initially. Trimming nose up will move the trim tab on the elevator down, not up. Same principle with the other control surfaces.

…but if you trim, and the control surface takes on a new position, and the control surface is directly connected to the stick via cables and pulleys, then it should move the stick, no? I haven’t flown a real Corsair (still waiting for someone to offer!), so I’m asking, not correcting you. Cheers.

I think you’re correct in that it isn’t optimized yet. I also get some lag compared to other modules with 9900X, 4080 Super, and 64 GB ram. I have a lot of my settings turned down for VR. It’s manageable, close to 25-30 FPS on the boat, then increases past 45 or even 60 when I’m away from the carrier (and other ships)

The module has evolved, and the original training is still the original. Don’t close your cowl flaps like the training says to. Open them to keep your cylinder head temp in check. Also, your oil temperature (not pressure) requires you to open your oil cooler flaps. I set these 50% open for the entire flight and never worry about it afterwards. You can choose to close them in small increments every few minutes and keep an eye on the oil temp if you are concerned about the small drag penalty.

Don’t quote me on this, but I thought I remembered reading somewhere that that switch was an older method. The tanks are dropped electronically like bombs (hit the arming switch for the pylon, then weapon release). In case that fails, there are two manual release pull handles located back near the wing fold handle that works as well.

Doesn’t exist. It’s already in the wish list section of this forum and Rudel has acknowledged it.

If you try using multiple hydraulic systems at the same time, the gear will hang up occasionally. For example, if you drop your flaps too early and they have trouble extending, the pressure isn’t available to push the gear down. Try dropping the gear first, and confirm they are fully down before extending the flaps.

That's what I thought too, but the trim is isolated from the elevator axis. So, with the trim being backwards, I had to invert the elevator axis in Moza, and that made the trim and elevator work in the same direction. However, as expected, things were now backwards in DCS, and pulling the elevator sitck back would result in a nose dive, so that's why I had to invert yet again, but this time in the DCS control settings for the F4U. So yeah, inverting the inversion kept the elevator behavior the same, but it didn't affect the trim, which now follows the same direction as the elevator. None of this will affect my other modules because I use separate Moza profiles for each aircraft. Cheers, -GT-

Haven't had a chance to test things since my original post. Although the behavior is different than the other modules, the solution here is to not only invert the pitch axis in Moza, but also in DCS. The trim now moves the stick in the correct direction. Marking as solved. Thanks all.

This is the correct behavior. They are all switches, not proportional levers. Right in front of the handles are two indicators for oil and intercooler positions. Cowl flap position is done with the eyeball since the cowl flaps are visible from the cockpit.

Up

Love this. Cheers!

Not sure that will work. My elevator axis is correct. My elevator trim is assigned to key bindings and is on a hat switch. I think the trim is working correctly if I force the stick to stay in the center position. But if you let go of the stick so that it finds its new position, it moves in the opposite direction intended by the trim.

I know this was recently mentioned in another thread, but M3 asked for one issue per thread, so here it is: As mentioned already by another user, I also confirmed in a quick test just now that the new FFB elevator trim, implemented in the latest patch, is backwards on my Moza AB9 as well. If I pull the hat switch down and towards me, the stick moves forward and my aircraft dives....and vice versa. I'm glad to see FFB trim implemented, so that's a step in the correct direction before early access ends, it just needs a -1 multiplier at the moment. I'm still unable to provide a track file, even after updating and running a repair. I'm not sure what's going on with that. Thanks!

I believe that step in the procedure was for visibility. It’s already difficult to see over the nose with the cowl flaps closed. Turbulent airflow over the wing from the cowl flaps is negligible since it propagates straight back with little outward expansion. Besides, there’s a ginormous propeller chopping up the air there anyway. If anything else, I can see it needing to be closed to clean up airflow for the tail control surfaces, but again… ginormous prop messing up the air there anyway.

You can also try out the miz I posted, Engine Diagnostics. It also shows the aircraft health percentage, so if you spawn in and it’s not 100%, then something is damaged. The problem with this, and also calling for repairs, is that we don’t know what’s broken. It might not even be the landing gear if a repair is needed or the script shows less than 100% health.

Interesting. I have the AB9 and am not getting a tick when engine is not running. Maybe something with your PC processor is getting bogged down and the tick is a side effect in the FFB data stream? I honestly have no clue how that works, just taking a wild guess. I have also reported stall FFB behavior. I think it’s occurring too early, at lower AoA than necessary because I’m able to continue pulling much higher G’s and alpha before the wing actually stalls. Rudel has asked for a track file. For some reason my track file generation is broken and DCS gives me an error when I try to save one. I probably just need to do a repair. Perhaps you can attach one so the devs can get a hold of it?

.miz updated with the new lua. No changes to anything in the lua script except the commented-out lines with the instructions. It now specifies that you should set the fuel capacity to the internal tank capacity only. No need to touch the lua script if you are only testing the Corsair. You must open the lua file and change the fuel capacity only if you wish to test on another aircraft.

Love this. Thank you. I will update the instructions in the script later today based on your findings, and you’ll get a special mention in the credits as well

Interesting. The script uses the built in function to get the fuel, which is returned as a percentage (value zero to one). What I’m doing with the script is simply multiplying that with the total capacity that you set in the script. I’ll have a look to see what’s going on later, but what I’ll do is simple and you can try if you want. Set fuel capacity to zero in the script and then I’ve coded it to show the text in the mission as percentage instead of gallons, and it will give you an idea what’s happening. It almost sounds like DCS is giving a value of more than 100% fuel remaining if you are carrying the drop tanks, which I did not expect. I didn’t test for this, as my speed trials were with a clean configuration. If you get to it before I do, let us know what you’ve found. Thanks for the feedback