GTFreeFlyer

Just to answer this… No, it does not help with any feeling in regard to keeping the ball centered or holding your altitude more constant. I fly with the Moza AB9 and Simshaker driving a bass shaker attached to my chair. Pilot IRL too. However, I can’t fly without the FFB or simshaker anymore. It just adds so much more to the VR experience, and all the little feedback you get for everything in game is amazing. I can feel my bombs come off the racks, landing gear “cah-chunk-ing” into the uplocks and downlocks, etc. You’ll even feel the bumps on ground during slow taxi. And the gun… oh, the gun That’s what FFB is good for. It’s not for getting your plane trimmed, although in some DCS modules you will notice the center position of the stick move based on your trim, which is accurate to IRL. I also get a feeling of how fast I’m going based on stick force required to deflect the control surfaces. Perhaps when someone makes feedback that pushes your butt left or right, we’ll be able to use that to help keep the ball centered. Sure, motion platforms can tilt you for this, but your brain also interprets a roll motion at the same time. We need G-forces to sense small changes in vertical acceleration to hold altitude more accurately. It’s a no-brainer thing IRL to hold altitude, but in any sim it’s always a challenge as you have to constantly look at your VV gauge. Easier when you are in close formation as you have a visual reference for vertical velocity. The M3 Corsair holds altitude well without touching the stick or throttle once you have the trim dialed in, but you still can’t leave it unattended for long and go grab coffee or a bio break. Make sure to keep an empty cup nearby if you need true realism Anyway, hope that helps in case you are considering FFB in your future… I say go for it

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