MrSkyGuy

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!

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.

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.

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.

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.

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!***

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.

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/

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.

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.

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.

Glad that worked.. we are very blessed to have Bob responsible for the Tinmouse. Bob knows all!

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!

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

I've just uploaded the new version to the network. It should be live in a day or two.