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.

SR22 Covers removal

Featured Replies

How do you do it?  I understand the Controls option Quick Preflight should do it when bound to a controller button but that doesn't work - at least for the SR22 but then I haven't needed to do this on any other aircraft.  Nor does the multitude of other options I have seen around the web.  The only thing that does work for a cold and dark start is to spawn on the runway with the engines running and get GSX to warp you to a parking spot then shut down the aircraft.  I have just been through an extended exercise of setting up controller bindings and  Chaseplane camera views and the SR22 is the only aircraft that has given me significant hassles.  As a side, but possibly related matter, I can't get the walk around mode to work.  Is that because of Chaseplane even though disabling it doesn't help.  Thanks

Bruce

Bruce Bartlett

 

Frodo: "I wish none of this had happened." Gandalf: "So do all who live to see such times, but that is not for them to decide. All we have to decide is what to do with the time that is given to us."

At my end, hitting the key that I have assigned for QUICK PREFLIGHT does indeed remove the covers and chocks from the SR22.

So at least that narrows it down to a localized problem, and nothing inherent with the SR22.

I think the fact that walkaround is not working either with the plane, probably links the two problems together.

I don't use Chaseplane so if that is the cause, I'm not able to assist but perhaps a Chaseplane user can chime in and advise whether it can affect walkaround mode and using the QUICK PREFLIGHT function to remove all covers and chocks.

Bill 😎
FS2024 • Currently in 'GA mode' : A2A Comanche 2024 & Aerostar • Black Square C208, Bonanzas, Barons, TBM850, Dukes • COWS DA40 & DA42 • FSW Legacy, C24R Sierra & C414 • Echo Falco F8L • FFX HJET, Visionjet and P180 2024 • Got Friends A32 Vixxen • FSReborn Sirius TL3000, Sting S4 and Piper M500 • Flyboy Rans S6S • Skyward DA50RG • SWS Zenith CH701, RV-8, RV-10, RV-14, PC12 • Milviz C310R • Air Foil Labs Bristell B23 
TrackIR • BeyondATC • PMS GTN Payware • RealTurb • Axis & Ohs • FS Realistic Pro
9800X3D • RTX 3080 • 64GB DDR5-6000
NPPL licence holder in the UK

  • Author

Thanks but problem solved.  I am not a gamer so WASD keys are new to me but having informed myself on their use I can get Walk Around mode to work and I quickly found click spot to remove the covers.

Bruce

Bruce Bartlett

 

Frodo: "I wish none of this had happened." Gandalf: "So do all who live to see such times, but that is not for them to decide. All we have to decide is what to do with the time that is given to us."

22 hours ago, brucewtb said:

I understand the Controls option Quick Preflight should do it when bound to a controller button but that doesn't work - at least for the SR22 but then I haven't needed to do this on any other aircraft. 

Issue is one of

1. SR22 related, something wrong/buggy

2. MSFS related, something wrong/buggy

3. User Error - is the key bind actually working at all?

4. Some other program (chase plane)

My bet is 50/50 between 3 & 4. Either user error (key bind messed up, conflicting controller assignments, etc), or Chaseplane. 

I would start by trying some other plane. If it works on that and not the SR22, you know instantly that it's a SR22 issue. That is unlikely since it works fine for me and others. 

If it does NOT work in other planes, your options are bad/not working key bind, issue with MSFS or issue with Chaseplane/other program. Highly unlikely to be an issue with MSFS, so leave that be for now (this works fine for all users.. if it didn't we would hear a lot more)

To eliminate that, start by removing everything from your community folder (except the SR22, of course). No ChasePlane, no GSX, no FSLTL.. nothing. Just the SR22. 

Does it work? Yes? it's an add on conflict (probably chase plane). You can then put addons back one by one (start with Chaseplane, easy to confirm whether it works with that or not) and see which one breaks it.

If it doesn't work after trying all this, check your key bind to see if these is even working and also try on another plane. Works there = SR22 bug. Doesn't work there = MSFS bug.

That should help you narrow it down. 

9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen

  • Author

The SR22 is a default aircraft so not in the community folder. I'm pretty sure it isn't a faulty key bind as I have a lot of those that work just fine.  It maybe Chaseplane but the issue remains with Chaseplane disabled.  Anyway I am now able to get rid of the covers during walk around which I have managed to get working.  However, when I first installed Chaseplane and fired up the sim and loaded Chaseplane it took me to the intro tutorial at the end of which I was presented with option to have Chaseplane disable all the MSFS2024 Camera bindings.  At that point I backed out in order to do some research on the implications of this.  In MSFS2020 I elected to manually delete default camera bindings myself. When I returned to the sim and loaded Chaseplane I no longer was given the option concerning NSFS2024 camera bindings - the app fired up and was ready to go.  So I am not entirely sure what Chaseplane has done to the default camera bindings.

Bruce

Bruce Bartlett

 

Frodo: "I wish none of this had happened." Gandalf: "So do all who live to see such times, but that is not for them to decide. All we have to decide is what to do with the time that is given to us."

Sorry, saw SR22 and for some reason read it as SR72. Looks like you got it working. 

9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen

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.