Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Take off Config horn confusion

Featured Replies

Edit: I`ve made some progress. I now realise that I have to have the spoilers in the Up position on the quadrant for them to be down. Is this correct? I thought that "Down" was spoilers stowed in the wing, "Armed" was next , followed by the range through to "Flight Detent" which is the maximum inflight extension. Finally "Up" is ground spoilers position used after touchdown. Maybe this is reversed?Hi I am a little stuck. I`m being stupid somewhere but need an expert to show me the error of my ways.I have trim in the green band, flaps 5 spoilers down and not armed, pressurisation set and switched to flight, no warning lights and I get the intermittent warning horn when I advance the throttles. As soon as I lift off, I get the continuous horn sound until the flaps are fully retracted. What have I missed? I am using registered fsuipc to control flap (joystick buttons mapped to f6 and f7) as well as axis on prop 1 for the spoilers. I tried the x6D11 mapping for the spoiler arm button which seems to disarm them when they are armed but not toggle the state.I have had a quick search on this forum and can see lots of references to people battling to configure their flap and spoiler controls. Maybe I have done something wrong and my spoilers are extended when I try and take off. The visual model shows the spoilers extended (flight detent sort of position) but the lever on the quadrant shows the spoilers as retracted and disarmed.Using Tinmouse v1.21 and fsuipc3.7Thanks in advanceJames

  • 2 weeks later...
  • Commercial Member

Same problem here.The spoiler handle in the panel is in the down detent, but in spot view they are partially extended.Also, moving the spoiler handle doesn't have any effect on the visuals.I don't have any joystick axis mapped to the spoiler.PS why did you have to change the whole control assignment? Other addons can cope with the assignments within FS, why does this pose a problem to the Mouse?Regards,Mark

Mark Foti

Author of aviaworx - https://www.aviaworx.com

logo_avsim.png

>Same problem here.>The spoiler handle in the panel is in the down detent, but in>spot view they are partially extended.>Also, moving the spoiler handle doesn't have any effect on the>visuals.>I don't have any joystick axis mapped to the spoiler.>PS why did you have to change the whole control assignment?>Other addons can cope with the assignments within FS, why does>this pose a problem to the Mouse?>>Regards,>MarkMake sure you don't have any hardware controls assigned to Spoilers, Prop Pitch 1, and Prop Pitch 2. The panel uses the prop pitch axes in the background, so if you have, for example, a CH yoke with a lever assigned to prop pitch by default, it'll interfere with the spoilers.Other addons "cope" with the assignments so long as everything is powered-up and operating normally. My design intent is a panel that, as close as I can make it, accurately simulates system behavior including with nonstandard configurations. I can point you to a whole bunch of forum posts by PMDG's Robert Randazzo lamenting the inability to get spoilers to work correctly on their very well respected payware models. Take one of these "coping" panels, shut off all the hydraulics, and then try moving the spoiler handle. With most, it'll deploy the spoilers without any power...in others, the handle won't move. The correct behavior is for the handle to move, but not the spoilers. I've made it work with the TinMouse II, but it requires some manageable changes to the config to make it work.Bottom line, though, is that the TM II is now in use by at least four university level aviation programs that I know of, and having the systems work in detail for them and anyone else willing and able to do a little setup work on their system is far more important to me than trying to make this panel work automatically for someone that can't deal with anything beyond the default FS key assignments.RegardsBob ScottATP IMEL Gulfstream II-III-IV-V L-300Santiago de Chile

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

  • Commercial Member

Hi Rob,I don't have any axes assigned to those actions.Anyway, I didn't want to belittle your achievements and I apologize if that's how my remark came across. As a developer I admire your efforts you have put into this bird!I know PMDG had their issues with the spoilers (and not just with the spoilers ;-) ) but I do think that it is possible - I think Level D managed to make it work realistically. But who knows, maybe they read the FS9.CFG File manually and bind the shortcuts dynamically at runtime?!Anyway, not trying to sound smart as I have no clue how terrible the FS9 "API" really is. Ever considered porting the sim to X-Plane? ;-)Maybe one day you will find a way to implement the feature and then the already remarkable project will become even better!Take care,Mark

Mark Foti

Author of aviaworx - https://www.aviaworx.com

logo_avsim.png

Mark; I've had a couple folks that thought they had no axis assignments, and on closer examination, FSUIPC did indeed have an active assignment. Scroll through the joystick calibration tabs...for the spoiler and both prop axes you should see "Axis not processed" Anything else means FSUIPC is making an input on that axis regardless of whether there's a physical device assigned. Didn't take the first post as belittlement, but will admit to being a bit sensitive to the "why couldn't you just leave it alone" or "these other guys did X, why didn't you" sort of commentary. I never intended to try and keep up with outfits with multiple professional programmers...I'm just one guy developing the panel as a hobby, so I may not have the time, resources, or skills that a team of pros brings, and my solutions are likely to be a little less refined. But, that said, I'm happy with the fact that there are features built-in and coming that you can't find even on professionally produced products...and of course our money-back guarantee always applies. ;-)CheersBob ScottATP IMEL Gulfstream II-III-IV-V L-300Santiago de Chile

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.