Jump to content

Some questions and perhaps frustrations with this module


Typhonus2

Recommended Posts

2 hours ago, deloy said:

Remember guys, the CAS (Command Augmentation System) is for a different reason than SAS, both systems are termed as SCAS as a whole.  The whole purpose of CAS (it is elaborated very well in the manual) is to give a "power steering" type of response where it augments your control input to make it feel the same when flying at all speeds, so this extra SCAS response you see on controls indicator is actually correct. The CAS should also function when FTR is depressed, which is not correctly modeled at the moment, therefore the helicopter response is the same as FMC off when you flying with Force Trim (FTR) depressed.  So essentially if you press and hold FTR, it just switches the CAS system off also.  This is very evident in control indicator, as you see no movement in "green cross".

 

Cheers

The CAS turning off when FTR is depressed may very well be part of the problem. But as far as I understand there is another problem, which comes from the interaction between the CAS logic and the "flight model".

(Disclaimer: I am sure we have some SME here who can explain the problem far more accurately than me. But I'll give it a try, based on my limited understanding)

AFAIK one job of the CAS is to provide a more immediate response to pilot inputs. In the real Apache there are delays in the control system. The CAS attempts to eliminate these delays by leading the inputs the pilot makes. The problem seems to be, that the delays, which the CAS is trying to eliminate, are currently not simulated in DCS. As a result the CAS in DCS needlessly exaggerates control inputs. Hence the twitchyness and instability.


Edited by cow_art
Link to comment
Share on other sites

I have literally explained how system works in both the real Apache and dcs in this thread as well as countless others. I’ve said the same thing more times than I can count. Keep going with the conjecture though, because it definitely resolves things and doesn’t muddy the waters or confuse people at all. 

  • Like 5
Link to comment
Share on other sites

1 hour ago, bradmick said:

I have literally explained how system works in both the real Apache and dcs in this thread as well as countless others. I’ve said the same thing more times than I can count. Keep going with the conjecture though, because it definitely resolves things and doesn’t muddy the waters or confuse people at all. 

Well said 🙂

OS: Win10 home 64bit*MB: Asus Strix Z270F/

CPU: Intel I7 7700k /Ram:32gb_ddr4

GFX: Nvidia Asus 1080 8Gb

Mon: Asus vg2448qe 24"

Disk: SSD

Stick: TM Warthog #1400/Saitek pro pedals/TIR5/TM MFDs

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

The Apache definitely got harder to fly after latest update. Before takeoff I usually disable yaw channel in FMC and during takeoffs and hovers use FTR to be stable and as I move into forward flight at around 30-50 kts I release FTR but yaw channel is permanently disabled. I tried flying it after the update and it has certainly has gotten harder at hover and slow speeds. Normal forward flight seems the same. 
 

I tried not disabling yaw channel using FTR and not using FTR and it’s almost uncontrollable for me…I know it’s a huge undertaking to get it right but it really needs to get fixed already. 

Intel i9-13900k, Asus Z790-E Gaming Wi-fi 2 motherboard, 64gb Corsair DDR5-6400 RGB ram 2x32gb XMP2 profile, 2TB Crucial T700 PCIE 5.0 SSD internal, 2TB Samsung 980 Pro PCIE 4.0 SSD internal, Asus ROG Strix OC GeForce RTX 4090, Corsair 7000X Case with 5 x 120mm side mounted intake fans and 3 x 140mm top mounted exhaust fans, 1 x 140mm rear mounted exhaust fans, front mounted Corsair H150i Elite Capellix 360mm liquid cooler w/Elite LCD with 6 x 120mm fans in 3 push, 3 pull intake configuration, 2 x 32" Asus 2560x1440 displays, TrackIR5 w/pro clip, Thrustmaster Warthog stick and throttle, CH Fighterstick Pro and Pebble Beach Velocity pedals. 

Link to comment
Share on other sites

  • ED Team

The flight model was not changed in this update. I would recommend double-checking that something has not changed in your hardware or control settings.

  • Like 3

Afterburners are for wussies...hang around the battlefield and dodge tracers like a man.
DCS Rotor-Head

Link to comment
Share on other sites

  • 4 weeks later...
On 2/28/2024 at 4:52 PM, 104th_Money said:

The Apache definitely got harder to fly after latest update. Before takeoff I usually disable yaw channel in FMC and during takeoffs and hovers use FTR to be stable and as I move into forward flight at around 30-50 kts I release FTR but yaw channel is permanently disabled. I tried flying it after the update and it has certainly has gotten harder at hover and slow speeds. Normal forward flight seems the same. 
 

I tried not disabling yaw channel using FTR and not using FTR and it’s almost uncontrollable for me…I know it’s a huge undertaking to get it right but it really needs to get fixed already. 

Flight model feels the same, what works better and has been refined was the ATT HOLD and ALT HOLD.

the only thing i agree with casmo is that, the feels on the wheels are weird when you lock the wheels and move forward and hit the breaks after collective down and wheter your reset the scas or not, the tail wants to go to the right, but apart from that, the fm have not changed.

Link to comment
Share on other sites

I've since decided to permanently disable the whole FMC before takeoff. It is much easier for me to control now, especially during takeoffs/landings/hovering...Only problem is that it disables all of the trim modes so I just fly by hand...

Intel i9-13900k, Asus Z790-E Gaming Wi-fi 2 motherboard, 64gb Corsair DDR5-6400 RGB ram 2x32gb XMP2 profile, 2TB Crucial T700 PCIE 5.0 SSD internal, 2TB Samsung 980 Pro PCIE 4.0 SSD internal, Asus ROG Strix OC GeForce RTX 4090, Corsair 7000X Case with 5 x 120mm side mounted intake fans and 3 x 140mm top mounted exhaust fans, 1 x 140mm rear mounted exhaust fans, front mounted Corsair H150i Elite Capellix 360mm liquid cooler w/Elite LCD with 6 x 120mm fans in 3 push, 3 pull intake configuration, 2 x 32" Asus 2560x1440 displays, TrackIR5 w/pro clip, Thrustmaster Warthog stick and throttle, CH Fighterstick Pro and Pebble Beach Velocity pedals. 

Link to comment
Share on other sites

Im into DCS helis since BS1 and had some RL hours in the R22.
The  Apache is a bitch 😄
I developed a habit that made the apache failry stable and enjoyable.:
Dont depress FTB, just spam like in the BS.

I use Att hold all the time but turn it off for manouvering and on right after.

Regulary reset the trim . Dont no why but i have the impression its less wobbling and oversensitive.

In short: trim,trim, att hold off, manouver, trim att hold on trim trim, reset trim, trim .... repeat

Only small inputs.

I found it funny that george is flying even worse than I. That guy must be drinking in the back. So AI is struggling with the FM too.

 

I have a TM WH with extension. no curves 
 

:matrix: =SPEED IS LIFE=:matrix:

http://www.planeandpilotmag.com/speed-is-life.html

Link to comment
Share on other sites

  • Recently Browsing   0 members

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