Jump to content

Recommended Posts

Posted

Maybe I do too many inputs

 

But I noticed something I do out of habit

 

In real life the plane is always bent

 

You make small corrections to keep the plane parallel to the runway

 

Here you make small corrections and the FBW will not take it and if it did it’s a lot of input

 

Just curious if other flyers had it

 

It could be me

 

 

Sent from my iPhone using Tapatalk

I think I’ll reduce the curvature in roll to make it snappy


Sent from my iPhone using Tapatalk

[sIGPIC][/sIGPIC]

LUCKY:pilotfly::joystick:

Computer Specs

CPU: AMD Ryzen 5 2600 6-Core 3.4 GHz| GPU: Nvidia GeForce GTX 1660 6Gb | RAM: 32 GB DDR4 @ 3000 MHz | OS: Win 10 64 bit | HD: 500 Gb SSD

Posted

Sorry for not understanding your question fully. In terms of handling in landing configuration, the only stick input required is roll input. Roll should not require excessive stick deflection to achieve, gentle movements are possible. A small curve might help (I have 20 curve on just about every plane for roll, pitch, and yaw). Yaw shouldn't be required in a Carrier landing, but may be for field landings in a crosswind. Pitch should not be used at all, once you trim to on-speed angle of attack.

Virpil WarBRD | Thrustmaster Hornet Grip | Foxx Mount | Thrustmaster TWCS Throttle | Logitech G Throttle Quadrant | VKB T-Rudder IV | TrackIR 5

 

 

AMD Ryzen 5 3600 | Nvidia GTX 1060 6GB | 32GB DDR4 3200 | SSD

Posted

Yeah use power for descent rate. You still can flare a bit on a field landing and personally I never had too many issues with it. The FCS can be a little wonky at times though, especially on a bolter / touch and go.

Posted

Sorry for the terseness

How do you make the Hornet more responsive in roll

I use Chuck’s curve of 15 but it’s not responsive to my liking

Gonna reduce the curve to be more responsive

When is it too much or 15 is spot on for the curve


Sent from my iPhone using Tapatalk

[sIGPIC][/sIGPIC]

LUCKY:pilotfly::joystick:

Computer Specs

CPU: AMD Ryzen 5 2600 6-Core 3.4 GHz| GPU: Nvidia GeForce GTX 1660 6Gb | RAM: 32 GB DDR4 @ 3000 MHz | OS: Win 10 64 bit | HD: 500 Gb SSD

Posted

I completely screwed up operator error

Chucks Guide
Says deadzone of 4
Saturation 100
Curvature of 15

Gonna try these settings tonight


Sent from my iPhone using Tapatalk

I had a deadzone of 15 for both pitch and yaw my bad


Sent from my iPhone using Tapatalk

[sIGPIC][/sIGPIC]

LUCKY:pilotfly::joystick:

Computer Specs

CPU: AMD Ryzen 5 2600 6-Core 3.4 GHz| GPU: Nvidia GeForce GTX 1660 6Gb | RAM: 32 GB DDR4 @ 3000 MHz | OS: Win 10 64 bit | HD: 500 Gb SSD

Posted

Wonder if the DCS: Viper has the same issue?
Oh well


Sent from my iPhone using Tapatalk

[sIGPIC][/sIGPIC]

LUCKY:pilotfly::joystick:

Computer Specs

CPU: AMD Ryzen 5 2600 6-Core 3.4 GHz| GPU: Nvidia GeForce GTX 1660 6Gb | RAM: 32 GB DDR4 @ 3000 MHz | OS: Win 10 64 bit | HD: 500 Gb SSD

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...