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.

MrSkyGuy

Members
  • Joined

  • Last visited

Everything posted by MrSkyGuy

  1. Ah ha! I haven't had the opportunity to flight test that on the real bird, as the ships I had the opportunity with had the autobrakes deactivated.Thanks Bob!
  2. Bob, I have thoroughly diagnosed the issue throughout my flights from KLAX to Uganda and back (to Houston), 12 flights in all.The auto-brakes work perfectly. The only time they give an "odd" indication is when on the ground and preparing for flight. If the switch is cycled to RTO, the INOP light briefly illuminates and extinguishes as it should. If any of the other three modes (except OFF) are selected while on the ground prior to departure, the INOP light illuminates and does not extinguish. If in flight and any of these 3 modes are selected, the INOP light briefly illuminates and is extinguished.Application of the autobrakes is unaffected and fully functional.
  3. Bob, we can chalk the TCAS question up to a failure to "RTM" on my part. Apologies for that.I corrected the gauge reference as you explained--thanks!I actuate my brakes manually.. in fact, I don't typically start brake application above 80 knots unless the length/conditions of the runway warrant. To be fair, I really only use the autobrakes on super-short field landings and in the RTO position for departure.
  4. To the folks with bug reports, it might help to remind you that Col. Scott has spent (and continues to spend) many sleepless nights working on this aircraft. Without Bob, the Mouse would have been squashed a long time ago.. So when you are posting your bug reports, try to avoid comments like "Im not happy with" and "wow, this was better before," etc. Choose your words a little more carefully and please show a little respect. This is, afterall, blood/sweat/tears freeware.Now, for the bug report:I do also concur that (in FS9 using the SP177 standard panel), the autobrake functions in RTO mode only. the MIN, MED and MAX settings leave the INOP light on. I have not yet tested the brakes for actual function in autobrake mode.
  5. Stellar work, Bob.. you know how I feel about this jet.Being an avid ISG user, I immediately installed my Smith's FMC and related EFIS + EFIS control panel. My preferred setup differed a bit from yours, adopting a little of how SWA flies their -300s, and a little of how the current -200s are used with modern FMC units. That is to say, I like how SWA doesn't have glass panel EFIS displays replacing their HSIs (they fly their -300s using just the Smith's FMC and no visual EFIS display), but I also like how some have replaced the radar with a nav + radar display above the throttle stack where the old radar used to go. My point in all of this is that I fly a modified version of your modified version, so some things are bound to work a little differently.That said, I tried out your ISG1 panel and discovered that the FCU is still set to my original gauge vs. your re-coded FCU. Also, the TCAS control panel (transponder set and mode) were replaced by a gauge which appears to be a BMP background.. it's non-functional in any way as if the gauge isn't present, leaving me no way to enter my squawk code or the transponder mode. Lastly, the square VSI/TCAS gauge didn't show, though I see the black space where it was supposed to be.In the end, I reverted back to the basic panel file and manually edited in the ISG1 components, leaving the HSI alone (preferred). However, I would like to see the VSI/TCAS work.
  6. As you may have already noticed, Bob's little surprise is available in the AVSIM library with all of the little pleasures we've been looking for! I'd like to be the first to thank Bob for his fine work on this wonderful aircraft. You've done us proud, yet again Bob. We'd be nowhere without the lovely TMII, and now we get ALL of the bells and whistles too! The link is stickied in the forums, but is here for those too lazy to go find it: http://forum.avsim.n...on-20-dec-2010/ Please join me in congratulating Bob on his latest release and thanking him for his hard work and daily support of the Tinmouse II! ***Thank you Bob!***
  7. Thank you! Bob's version will use this gauge, but he's gone the extra mile and hard-coded it behind the scenes to do all of the fun stuff we dreamed of with the FD, etc.
  8. NOTE: I will no longer be supporting this gauge as a panel add-on, as Bob has elected to take this very same gauge to the next level and integrate it in to the new v1.30 panel coming out on Christmas, complete with the hard-coding necessary to make it work with the FD.You can read about it here: http://forum.avsim.net/topic/321636-major-update-on-short-final/
  9. I have confirmed this issue with a few individuals using the uncondensed layout.. though on another group, the issue is not present. I am still working to isolate what's causing this and why.I'll keep you posted.
  10. That's very unusual. I will continue to research and will keep you posted. If you notice anything that causes it to react that way.. any additional steps, etc. please let me know.
  11. Wow, Scott.. I have tried everything but I am unable to duplicate the issue. Perhaps try a re-install of the gauge and make sure that you've // out the Flight Director as listed in the instructions.
  12. Glad that worked.. we are very blessed to have Bob responsible for the Tinmouse. Bob knows all!
  13. Hmm.. it's probably taking it's distance from a point on the fuselage vs. the gear points. This might be a question for RealityXP.I am looking forward to your mod--that Sandel install is one of the more unique I've seen flying!
  14. Scott, that's very unusual.. can you post a screenshot here so I can better identify what you are referring to?The file is *live* in the AVSIM library as: tmii_sperry177_v2.zip
  15. I've just uploaded the new version to the network. It should be live in a day or two.
  16. The file listed in my OP is no longer linked, as I have re-uploaded the file to the AVSIM file network as Version 2.1, which incorporates Dutch's XML file updates.Search the library if you are looking for the file!
  17. Dutch, thanks for the feedback. Unfortunately while it appears relatively simple, I just haven't taken the time to get as frisky with XML files as I probably should. Part of why I didn't implement these is due to the way in which I fly.. I almost rarely use the scroll wheel to change the values, but I could see where that would be helpful (pilots with external control panel units). I'm a clickspot pilot, but this is all very valuable information. I would certainly entertain your modified XML file! You can post it here or email it on over, and I'll test it and drop it in as an addon fix.As for the disconnect sound, it's something I've tried with both buttons in both versions back to v1.0 with no success.
  18. Remember that the Sperry 77 controls attitude, not rate of climb. Your rate of climb/descent is a byproduct of power AND pitch adjustments. If you set the aircraft to a specific pitch and roll, it will attempt to maintain that state (in a vacuum). Proper maintenance of your attitude requires continuous (read: not "fixed") throttle management and CWS "fine tuning" (very very gentle bumps to the control yoke in the desired direction) to correct.
  19. MrSkyGuy replied to a post in a topic in The TinMouse Support Forum
    Well, that may be true from an initial performance standpoint but the point I was making was how FS loads sideviews. Once you visit that particular view in a flight, the BMP is loaded in to your PC's memory and remains there. So if you visit all 7 views at 30mb each, that loads 210mb worth of BMPs in to RAM. That *CAN* have a performance impact if your available RAM is not very high (which would be more likely to affect system performance on longer flights, or continuing flights). Indeed, 284 downloads! Congrats!
  20. Indeed! It was the refresh rate of the gauge, which has been corrected.The new modification is available here: http://forum.avsim.net/topic/319493-tinmouse-ii-sperry-177-modification-version-20-released/
  21. MrSkyGuy replied to a post in a topic in The TinMouse Support Forum
    It wasn't much for me after you've loaded each view once (looked in all 7 directions), but still.. I don't know what the extended impact is with 210mb of images loaded in to RAM on longer flights or on PC's with less RAM available.
  22. Rich, thanks for the kind words! Yes, if you choose the extended option, you will loose the ability to set the F/D command bars. It was for this reason that I split the update in to 2 options. Personally I prefer the condensed SP177 gauge as I do use the FD, but I'd received many requests for an un-condensed version. To have the best of both worlds, the Gyro would need to be replaced--something I didn't want to do as it'd be very difficult to match the quality of Bob Scott's panel and keep it true to the aesthetic spirit of the TMII.
  23. As I'd mentioned in this post here: http://forum.avsim.n...7-modification/ I have been working on a version 2.0 release of my Tinmouse II Sperry 177 panel modification. Today I've completed this modification, and uploaded both to AVSIM and FlightSim for download. I made a slight error in the installation instructions which I am correcting with both AVSIM and FlightSim, so until that's been fixed (expecting about a week or less) I've opted to upload this modification for you to download now. Click HERE to download the Sperry 177 Panel Modification Version 2.0 The features of this newer version include: * Actual Sperry 177 layout and functionality* Corrections for full course knob functionality (now works in synergy with the gyro course knob)* Improved and more accurate panel refresh rate (no "click delay")* LNAV now tracks the GPS track* Install options for the Sperry 177 in full MCP layout or condensed w/ FD layout (reflected in screenshots below)* Correction for immediate 2500fpm climb/descent upon altitude change -- now climbs and descnds only when selected via fpm knobI may consider adding LNAV and VNAV support for owners of Ernie Alston's Simavioics ISG1 pack (specifically the Smiths FMS) at a later date in a newer version.Screenshots:I decided to include 2 options for users--a condensed Sperry 177 FCU which preserves the TMII Flight Director controls, and an un-condensed Sperry 177 FCU which removes the Flight Director controls. These are reflected in the 4 screenshots below.FIRST OPTION - Uncondensed Sperry 177 FCU covering the Tinmouse II Flight Director controlsSECOND OPTION - Sperry 177 FCU preserving the Tinmouse II Flight Director controls
  24. I am growing close to releasing version 2.0 of my Tinmouse II Sperry 177 gauge, this time with options for the condensed FD control preserved option as well as the non-condensed FD removed as pictured below. This release will mirror and look more closely like a true Sperry 177, and contains corrections to the known issues with the previous version.I hope to have the release out soon! Here's 2 screenshots below of the two options which will be included:
  25. MrSkyGuy replied to a post in a topic in The TinMouse Support Forum
    By accident, I've discovered where all of those megabytes went.. the left, right, forward right, forward left, etc. views. They are 30mb each. 30mb!

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.