Jump to content

Help please F/A 18 C module take off trim and trim control


Go to solution Solved by razo+r,

Recommended Posts

Posted

Hi folks,

PC Specs in footer, currently running latest STABLE version of DCS in single player mode in a self created mission on Syria map (and similarly on South Atlantic map)

In my mission I have 4 F/A 18C’s setup. 2 setup hot start on airfield parking spot. 1 setup hot start on my carrier and 1 setup in the air at 6000ft x 350knts.

My problem is with 2 F/A 18’s hot started on airfield parking spots. When i jump into these, pitch trim is set at 12 nose up and my HOTAS trim switch seems unable to change this 12 nose up setting. When I take off, get airborne, wheels and flaps up I still seem unable to adjust the trim setting to lower the nose and have to fly with the stick pushed a long way forward just to fly level? I do not have this issue with the F/A 18C that is already setup flying at 6000ft.

I’m still pretty new to DCS; due to a recent family bereavement, I have not had my PC on for the last two months, recently started it, opened DCS to play, and updated DCS to latest stable version from previous stable version. Had no such problem when last played prior to bereavement and latest DCS update but no idea if update is relevant to issue?

My controls seem to be setup fine, as they were before the problem arose but I’ve no idea what to look at next to solve my problem? Maybe, it is some thing important I’ve forgotten to do? Who knows?

Any advice, ideas will be much appreciated.

Thank you

Regards TS

 

 

Self Build: 5000D Airflow Case, Asus ROG Maximus Z690 Hero DDR 5 MOBO, 1200W Corsair Modular PSU, I9-12900K CPU, MSI 3080 ti 12GB GPU, Corsair Vengence 64GB DDR5 5600 RAM, H150i Elite CPU Cooler, 2 x 1TB & 1 x 2TB Samsung 980 Pro M.2 PCIe 4.0  SSD's, Windows 10 Pro OS, Samsung Odyssey G7 28" G-Sync (3840 x 2160 Resolution) Monitor, Thrustmaster, ROG Strix Go 2.4 Headset , HOTAS Warthog Stick, Throttle & TPR Rudder mounted on WheelStandPro V2 rig. TrackIR 5 - DCS: Channel, Normandy 2, Persian Gulf, Syria, Nevada, S. Atlantic, Sinai, Kola, Afghanistan, Iraq, Germany - FC3, Super Carrier, Spitfire, Mosquito, F4U Corsair, P-51, P-47, Bf-109, FW-190 A-8, AH-64D, Huey, Kiowa, Chinook, F18-C Hornet, AV-8B, F-16C, F-5E, A-10C II, F-86E Sabre, F-15E Strike Eagle, F-14 Tomcat, Viggen, MB-339. Android Tablet with DCS UFC & DCS NAV

  • Solution
Posted (edited)

You can only change trim on ground if the flaps are set to half or full. For takeoff, trim should be set to minimum 12, depending on weight. After takeoff, when flaps are retracted, you should not have the need to adjust trim, unless you changed it manually before. 

But to make sure, check the trim key bindings, make sure they are bound and not have any double bindings. 

If the issue persists you should consider uploading a track that briefly shows the issue. It helps a lot to identify any potential issues. 

Edited by razo+r
  • Like 1
Posted

Thank you razo+r.

I checked my key bindings and discovered a duplicate entry for button 2 on my HOTAS Warthog joystick; which apparently was also assigned to some function in the GUI layer. I. Did not think to check this as I’d not had my PC & DCS running for the last six weeks so, not a change I made. Consequence of upgrading to latest stable version???

All working now

Thanks again

Regards

TonyRS

Self Build: 5000D Airflow Case, Asus ROG Maximus Z690 Hero DDR 5 MOBO, 1200W Corsair Modular PSU, I9-12900K CPU, MSI 3080 ti 12GB GPU, Corsair Vengence 64GB DDR5 5600 RAM, H150i Elite CPU Cooler, 2 x 1TB & 1 x 2TB Samsung 980 Pro M.2 PCIe 4.0  SSD's, Windows 10 Pro OS, Samsung Odyssey G7 28" G-Sync (3840 x 2160 Resolution) Monitor, Thrustmaster, ROG Strix Go 2.4 Headset , HOTAS Warthog Stick, Throttle & TPR Rudder mounted on WheelStandPro V2 rig. TrackIR 5 - DCS: Channel, Normandy 2, Persian Gulf, Syria, Nevada, S. Atlantic, Sinai, Kola, Afghanistan, Iraq, Germany - FC3, Super Carrier, Spitfire, Mosquito, F4U Corsair, P-51, P-47, Bf-109, FW-190 A-8, AH-64D, Huey, Kiowa, Chinook, F18-C Hornet, AV-8B, F-16C, F-5E, A-10C II, F-86E Sabre, F-15E Strike Eagle, F-14 Tomcat, Viggen, MB-339. Android Tablet with DCS UFC & DCS NAV

Posted

Glad you found the solution. I am far from a PC guy but I have noticed similar problems here over the last couple of years. Apparently some DCS updates change some things. I also have noticed w/ mine, and others here, that some sticks, throttle etc will have some assignments built in by the manufacturer. I think their idea is that you plug in your shiny new stick and it would be nice if you can do at least simple functions right away. I think the combination can have undesirable effects at times.

  • Recently Browsing   0 members

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