GTFreeFlyer

I remember seeing another post about this message being used for dev purposes. I think the bug to report here is that the training still prompts us to look for that message, not that the message fails to appear.

All planes are like this. Restricting the movement would become very nauseating once the movement in VR doesn’t match IRL. I like realism, so when I lean too far over by mistake, I simply come back a little. Never considered the side of it being used as a cheat in MP (I don’t really do any PVP) so I totally understand that now. Hopefully nothing changes, but if it does, I like the idea of a fade, kinda like a G blackout maybe? That would also help simulate your pilot blacking out from being afraid of heights

Awesome, thanks for the feedback!

I usually roll 1/2 to 3/4 of the runway length with the tail wheel down and elevator stick fully back in my lap before touching the wheel brakes. Your maintenance crew will thank you as well Towards the end of the roll, I hold maybe 25% brakes and that seems to work well. Let the ground friction do as much work as possible before going to the brakes. Taildraggers don’t do well with hard braking. Everyone has their own technique. Find what works best for you

Sometimes when staring at the F10 map in flight, I return to the cockpit and find my aircraft in an unusual attitude, especially in warbirds even when I think I had them trimmed well. I think a small artificial horizon in the corner of the F10 map would go a long way, kind of like what a TGP has in the corner as well. Thanks!

Nothing different on my end. Same procedure as before. You didn’t mention whether or not you prime the engine and open the throttle 1 inch before starting. Those steps need to be done. I also take fuel from the reserve, not sure if it matters for startup, but that’s what the procedure calls for takeoffs and landings. After priming 5 seconds, both mags on, battery on, fuel pump on, throttle 1 inch open, RPM max, mixture idle cutoff, and fuel tank set to reserve, my crank procedure is as follows: Hold starter until RPM gets around 500, wait a second, go straight to auto rich, wait another second, release starter. Works every time. Sometimes I gently pump the throttle forward just a bit immediately when releasing the starter and then set it to 750 RPM, just in case it wasn’t getting fuel.

No different for me compared to others

Flying with the Moza AB9, using direct input (not telemetry input) and the stick shakes with gentle pulls in gentle turns, nowhere close to stall or typical buffet. Needs a little tuning in the future when you see fit. Thanks!

It’s not the hard landing. There is chatter in the forums for all the carrier aircraft causing a CTD when catching a wire with the hook on the various carriers. I’m hearing reports that calling in your inbound with ATC commands is a fix for now, but I haven’t tested it yet.

I tried multiple times this morning to confirm the following behavior. In single player, carrier homing works and I hear the correct Morse identifier. However, after a respawn I can no longer hear the signal when tuning the radio the same way as before. I tried several different aircraft slots (I have several set as Client) and same thing would happen. I exited the mission completely, restarted it with a different aircraft than before, and the signal worked again. I switched slots to the aircraft that worked the first time, and no joy… no signal could be heard. I repeated several times, picking different aircraft slots and can verify the issue did not stick with the aircraft. I always heard the Morse on whichever aircraft was selected first after starting the mission, and did not hear the Morse on any other aircraft after switching slots. The issue is repeatable. To confirm, this was for the Essex carrier’s signal. Test procedure (after spawning in): Battery on C38 nav radio switch on C38 CW/Voice set to CW C38 preset channel 3 (that’s what my carrier was set to in the ME) On the manual tuning box, two modules aft of the C38 (I’m drawing a blank at the moment on its name), the CW/Voice switch was left in the default Voice position (CW position and not touching the knob would result in hearing “AGA”, Agana’s broadcast) And again for summary: Always heard my Carrier’s identifier after starting the mission fresh, regardless of which Corsair slot I took. Never heard any signal, regardless of chosen slot, after switching aircraft mid-mission. Haven’t had a chance to test in MP yet. Love everything so far. Great module! Keep up the great work Cheers, -GT-

I think everyone has the same plane where the tail wheel doesn’t swivel 360, but if you have good rudder pedals and are gentle with the inputs, along with some axis curves and tuning to tame the brakes a bit, then it’s not too difficult to taxi around and do nice S-turns down the taxiway. Also, back-taxiing on the carrier to the stern, then spinning around for takeoff is totally do-able even with the tail wheel swivel limited. Just takes a little practice and very gentle taps on the brakes. I’m sure this will get tuned eventually, as we also all have the same early-access module.

I love how you provided sources rather than just spitting out opinions on how you think the module should behave. Well done. This post should be a template for all.

How about wind over deck? Are you starting on a carrier each time? Switching back and forth from airfield to carrier? Is the carrier always facing the same angle into the same wind speed? I haven’t noticed anything like this yet, but it is an early access module and anything is possible.

So who’s got a decent Moza AB9 profile for the F4U? I’ve been using the default one for the Mustang, which is okay, but I’m getting a lot of stick shaking when pulling G’s in a turning fight and can’t seem to get rid of it by adjusting the telemetry settings. I turned off the G effect, and also increased the critical AoA for stall, yet I still get the shakes which I’ve seemed to tune pretty well for the other aircraft I fly, but just can’t seem to get it right for the F4U. It’s causing me to go gentle on the turns because my brain keeps telling me I’m going to stall when I feel the stick shake, but it’s far from true in this bird, so I just keep pulling thru the “stall feeling”.

It will work as long as you aren’t playing a mission on a dedicated server, or launching from a dynamic spawn slot on a local MP server. I’m sure they’ll fix that soon enough. Main radio (C-38) on, CW/Voice switch in CW position. Preset channel as desired. Then, on the remote unit two boxes aft of the C-38 (I forgot the actual name of it at the moment) set that CW/ Voice switch to Voice.

You have to set up the presets in the mission editor. Click on an airfield in the editor and view its info. You’ll find the frequency here.

I’m not at my PC now to check the name of the binding, but I definitely have the Prop RPM tied to an axis (TMWH throttle) where one lever is throttle (manifold) and the other lever is for RPM. I remember inverting the axis for it because I like forward lever to be max RPM and inside the Corsair the lever works the other way.

When I set date to Jan. 1, 1944 and enable historical list of units, I also do not get the carrier. When I disable historical list of units, it shows up in the list for USA and Combined Joint Task Force. Same is true for the F4U.

I'm assuming you are in the Corsair using manual frequencies based on what I'm reading? If so, your answer is in the manual, section 5.2.3.3, Note #1. It says, "As there is no correlation between the frequency range..." You'll find the rest of the answer in the manual.

Didn’t realize the interior lighting knobs weren’t in the list. I added them, but since they aren’t in the StreamDeck’s catalog, I can’t get them to work. We have their DCS ID’s, but how do I find the button ID’s (usually a four digit number)?

Yes, this would be helpful, but also have option for individual key binds for each flap position so that it can work for some of the hardware that exists. After all, it is a discrete 6-position input, not an axis, but an axis would still be a big step in the correct direction.

Did a bunch of flying last night with my new Stream Deck profile and got to test out a lot more. These 5 engine controls had incorrect decimal formats. Change your lines to what you see below. I still haven't tested out the radios, mostly because there are still some bugs in the way they operate and I didn't want to mess with them too much in case things change in the next ED update. Side note: Which GitHub account is the official, and current one to get ExportScripts? There are several forked ones. I wanted to open up a pull-request and get the F4U officially in, but don't know with whom to do that. -- Engine (Device ID 3) [43] = "%.2f", -- Throttle [44] = "%.1f", -- Supercharger Lever [46] = "%.3f", -- Mixture Lever [59] = "%.2f", -- Fuel Selector [105] = "%.3f", -- Ignition Switch (Magnetos)

This used to happen to me a few years ago for all aircraft, but no longer does. It was a great cheat for finding targets hard to spot on the ground. I thought it was quietly fixed, but perhaps I changed a setting somewhere? i don't know. I haven't experienced this in a very long time, and still fly with dots only. Wish I knew the reason. Can confirm as of last night I looked for this in the Corsair and did not see it. Cheers

Alright, I got most, if not all the clickable data (switches, knobs, etc) in here, with the exception of circuit breakers. I was able to test out a lot, but not everything. What I tested works so far. Feller, I added your name along with mine at the top for credits. This should satisfy most Stream Deck users. Work to be done: 1. Test and let me know if anything is broken. 2. Add more outputs (gauges, needle positions, indicator lights, etc.). I likely won't get around to this as I don't need these for my personal Stream Deck needs. 3. Continue sharing the love of this bird and reupload any additions/fixes you may have. Cheers, -GT- F4U-1D.lua

Interesting timing. I started working on my own last night and was going to continue this morning. I just took a quick look at yours and was hoping to replace mine and test it out. I have only built the weapons stuff so far into my Stream Deck, and have tested it all out, working. After a quick look through your lua file, there's lots missing. I didn't see any of the weapons stuff (main panel, rocket panel, bat bomb, etc.). I know this is just a work-in-progress, so I'm just throwing this out there for anyone else who might download it and expect more functionality. The ID's you have for all the clickable elements seem to match up with what is in DCS Interface's ID Lookup table. However, all the stuff you have for the gauges and indicators do not appear in the ID Lookup table, so I don't know if they'll work without any additional work involved. That was just my quick-look. I'm going to take the few switches you have and combine them into mine and continue plugging and chugging. Thanks for sharing.