A-1 Skyraider Elevator Trim Has Mind of Its Own
I have the Elevator Trim Mapped to my Hat Switch on my Thrustmaster Warthog Stick and sitting on the ground, engine running, it will change the trim setting on the gauge (Left Lower Side) cockpit. Once in the air, or as I make power setting changes, the Trim moves on it's own, no input by me. It usually changes to gauge setting to full down reading on the Trim Gauge, while in reality, the aircraft wants to do 1500 to 2000 FPM Climb. Trying to make adjustments with my flight stick at this point is useless. Any clues what the issue may be?
Miltech Simulations @MiltechSimulationsPlease note that for the first 30 seconds (aprox) after aircraft has spawned, the trims will not be fully operative (will reset to zero) as all systems are being initialized. After that, it will be fully operative, as normal.
Does this occur for you well after that period of time? Have you tied an aircraft reinstall?
Edit: So the trim is going into full Down deflection? Do you have any keybinds set on your hardware that may be resulting on this?- BWilliam B Simpson @Bugeater64
I appreciate the information. I will double check but don't believe I have any double key binds. I have tried to delete and reinstall aircraft. Really appreciate your input.
- FIn reply toBugeater64⬆:Tom Perry @flyingscool
- Make sure you don't have any other assignments of the trim to any other buttons or controllers
- If this were a Honeycomb product, it could also be due to the fact Honeycomb switches send constant updates. But... It's not. I don't know if the Thrustmaster exhibits the same behaviour.
Your description, however, sounds mostly like you've got two assignments somewhere.
- BWilliam B Simpson @Bugeater64
Double checked all the key/button/controller bindings, there were no duplicates that I could find. Did a test flight today 12/14/25 and had the same situation, sitting on ground could adjust trim but would return to full down setting. After take off, trim would not allow adjustment. Stayed Full Down. No ideas left. Tried deleting and new download, no change. I'm at a loss. Thank you for your input. I still really like this aircraft.
Miltech Simulations @MiltechSimulationsCan you please try something - Disconnect all your hardware, launch the simulator, start a flight with the A1. Does it still do it?
Please note this issue has not been reported by any other user, so its most likely an incorrect or conflicting configuration on your side. Disconnecting your hardware would let us identify if it's a keybinding problem.- BWilliam B Simpson @Bugeater64
I will try that. Should be interesting trying to fly without hardware.
- In reply toMiltechSimulations⬆:BWilliam B Simpson @Bugeater64
OK, disconnected all hardware. Left only keyboard and mouse connected. The A-1 Skyraider worked ok. Trim being setup on keyboard worked as it should. I then start one at a time to reconnect hardware. Thrustmaster Rudder pedals, then Thrustmasted Warthog Flight Stick, then MOZA MTP Throttle. All worked well. Finally I reconnected the MOZA MTLP Panel (MOZA THROTTLE ATTACHMENT) and ran into the old problem. It appears the MOZA MTLP Panel is the source of the conflict. The A-1 Skyraider module is the only module I have run into this conflict with. All my other MSFS work without issue with the hardware I use for flight simulations.
- FTom Perry @flyingscool
So, what functions is the MOZA MTLP Panel controlling?
I'm not at my FS PC, but, you should be able to filter on all the functions it controls in the controller menu.Unless you're programming the Panel like you program Axis and O's?
- In reply toBugeater64⬆:Miltech Simulations @MiltechSimulations
We are starting to collaborate with Moza to create aircraft specific profiles to avoid these sort of problems - that said, most likely the issue is rooted on your keybind profiles. Please note that FS24 supports general, per-aircraft type and per-variant specific profiles, so these may be conflicting with eachother, triggering and forcing the Trim Down on repetition.
If the general profile is clean of key assignments, and other aircraft are not affected, review the model/variant specific keybind assignments. Most likely the issue is rooted there