November 28, 201015 yr 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
November 28, 201015 yr Thanks for the Sperry upgrade! It looks great!One question, if I choose Option #1 for the full SP177 display, will the SP177 control the flight director or will I loose the ability to set the F/D command bars?Thanks,Rich Boll Richard Boll Wichita, KS
November 28, 201015 yr Author Thanks for the Sperry upgrade! It looks great!One question, if I choose Option #1 for the full SP177 display, will the SP177 control the flight director or will I loose the ability to set the F/D command bars?Thanks,Rich BollRich, 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.
November 28, 201015 yr 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.Thanks for the info. Again, a very nice addition to the panel!Rich Richard Boll Wichita, KS
November 29, 201015 yr Commercial Member Thanks for this release! It works much better than the first one -- the knobs turn smoothly and it looks and feels more authentic. I really like the option for the better-proportioned one that fits over the flight director controls (I never use those anyway, just a personal preference.)There are a couple of problems I'd like to suggest changes.The button "VOR LOC" is actually driving the FS control "AP Back Course". The button "LNAV" is driving the "NAV1 lock" FS control, and the VNAV button is driving the "GPS Drives NAV1" FS control.I think that logically, from the way most pilots think and most MCP panels work, it should be this way:VOR LOC should drive FS NAV1 Lock" buttonLNAV should turn on the GPS Drives NAV1 signal.VNAV should be INOPThere doesn't appear to be a back course control. You could assign that to the otherwise unused VNAV but if done the legend VNAV should be replaced by "BC".Also, using the mouse wheel on some of the numeric settings produces strange results. Placing the cursor to the right of each setting (the "Increase" location) and it works fine. But placing it on the left ("decrease") for the SPEED will actually decrease the COURSE. To the left of the VERTICAL SPEED will actually decrease the ALTITUDE. Note that click on these spots works normally -- it's only if the mouse wheel is used are these oddies seen.I have a corrected XML that rearranges the buttons as I suggested above. I'll be glad to send it to you or post it here -- but the fix is simple I just moved the mouse hotspots around on the display and mouse sections.I have not fixed the mouse wheel weirdness because I can't see and coding error that's causing it, and I left VNAV inop rather than assigned the BC function to that button.I also note that switching off the SP-177 doesn't give the AUTOPILOT DISCONNECT warning, but I don't think you can do much about this since it looks like the C code in the gauges aren't tracking the FS signal but some internal signal.Thanks again! I'm enjoying the Tinmouse even more with your SP-177 in it.Dutch Charles "Dutch" Owen - Developer at Military Visualizations - currently working on the C310R and SR-71A project for MSFS.
November 29, 201015 yr Author Thanks for this release! It works much better than the first one -- the knobs turn smoothly and it looks and feels more authentic. I really like the option for the better-proportioned one that fits over the flight director controls (I never use those anyway, just a personal preference.)There are a couple of problems I'd like to suggest changes.The button "VOR LOC" is actually driving the FS control "AP Back Course". The button "LNAV" is driving the "NAV1 lock" FS control, and the VNAV button is driving the "GPS Drives NAV1" FS control.I think that logically, from the way most pilots think and most MCP panels work, it should be this way:VOR LOC should drive FS NAV1 Lock" buttonLNAV should turn on the GPS Drives NAV1 signal.VNAV should be INOPThere doesn't appear to be a back course control. You could assign that to the otherwise unused VNAV but if done the legend VNAV should be replaced by "BC".Also, using the mouse wheel on some of the numeric settings produces strange results. Placing the cursor to the right of each setting (the "Increase" location) and it works fine. But placing it on the left ("decrease") for the SPEED will actually decrease the COURSE. To the left of the VERTICAL SPEED will actually decrease the ALTITUDE. Note that click on these spots works normally -- it's only if the mouse wheel is used are these oddies seen.I have a corrected XML that rearranges the buttons as I suggested above. I'll be glad to send it to you or post it here -- but the fix is simple I just moved the mouse hotspots around on the display and mouse sections.I have not fixed the mouse wheel weirdness because I can't see and coding error that's causing it, and I left VNAV inop rather than assigned the BC function to that button.I also note that switching off the SP-177 doesn't give the AUTOPILOT DISCONNECT warning, but I don't think you can do much about this since it looks like the C code in the gauges aren't tracking the FS signal but some internal signal.Thanks again! I'm enjoying the Tinmouse even more with your SP-177 in it.DutchDutch, 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.
December 3, 201015 yr Author 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!
December 5, 201015 yr I need help with with update to your sperry 177 panel modification! The digits in the FD covered up version, in displays in the Sperry 177 (except for the Course setting display) on the far left side are all squashed to the right. The digits in the speed hold window, for example only use about half of the space in the window. The digits themselves, along with the digits in all the other windows other than the afore mentioned course setting display, are thinner and their left sides are cut off. When I click on any of the displays, including the course setting display the digits of all the displays to the right of the course setting display expand to their proper size...unfortunately, to the right outside of their respective windows!I recall seeing the "squashed" nature of the digits in the v2 release but only discovered the expansion problem, purely by accident, in the v2.1 release. Apparently, something went wrong with the installation, though I'm sure I followed the option A instructions correctly (I already had v1 installed some time ago). Other than this "minor" problem I think the v2/2.1 release is outstanding! I'd hate to have to go back to the original version (don't get me wrong its great, these are just better covering up the FD and having digits that are easier to read and change), or at the very least go with the version still showing the FD switches!I'm very much hoping you can tell me were I messed up!
December 6, 201015 yr Author 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
December 8, 201015 yr 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 Huh, sure, but (at the risk of sounding like an amateur) I've never done a screen shot from within FS before. How do I do it?
December 8, 201015 yr 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 Never mind, I managed to find instructions on doing a screen capture. However, I have no idea how to place the screen shots in a forum message! I'll have to use the attachment option to send them to you...Ok, that seems to work! The files are attached below...the "before" shot is before attempting to click on the display window or use the knobs to change course, speed, altitude, etc. The "after" shot shows what happens to the display windows after attempting to change course, speed, altitude, etc.Incidentally, would monitor size (square vs. widescreen)or screen resolution cause this I use 800x600 instead of 1024x768 (I don't see any change using the latter except to make the tool bar much smaller and hard to read)!Scott
December 8, 201015 yr Author 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.
December 9, 201015 yr 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.Yeah, that looks like the only alternative. I did try switching to a 1024x768 screen resolution, but it didn't fix the problem. However, it did improve the appearance of the digits in the display. I guess I'll have to use the 1024x768 resolution whenever I fly the TinMouse!BTW, here's a screen shot of the panel in 1024x768 resolution...Here's the contents of my panel.cfg file. Is there anything I messed up of left out?://*EZ-GPS v4 This file updated by ezgpsv4inst.exe // Panel configuration file.// TinMouse II Boeing 737-200 for FS2004// Copyright © 2005-2006 Richard Probst and Robert Scott.// Version 1.25 Basic Configuration// Released under the Artistic License v2[Window Titles]Window00=Main Panelwindow01=Radio Stack - LowerWindow02=GNS530window03=Throttle Quadrantwindow04=Lights Panelwindow05=Timerwindow06=Overhead Lowerwindow07=Radio Stack - Upperwindow08=EZ-GPS_V4Window09=ISG1 Smiths FMSWindow10=Extended Flight InfoWindow11=Flight Info IconFixed Window30=Forward RightFixed Window31=RightFixed Window32=Rear RightFixed Window33=RearFixed Window34=Rear LeftFixed Window35=LeftFixed Window36=Forward LeftFixed Window37=Up[Views]VIEW_FORWARD_WINDOWS=MAIN_PANEL, 4008, 4009///// FORWARD VIEW DIRECTION ///////VIEW_FORWARD_DIR=2.0, 0.0, 0.0///////////////////////////////////////VIEW_FORWARD_ZOOM=0.80VIEW_FORWARD_RIGHT_WINDOWS=30VIEW_FORWARD_RIGHT_DIR=0.0, 0.0, 45VIEW_FORWARD_RIGHT_ZOOM=0.80VIEW_RIGHT_WINDOWS=31VIEW_RIGHT_DIR=0.0, 0.0, 90.0VIEW_RIGHT_ZOOM=0.80VIEW_REAR_RIGHT_WINDOWS=32VIEW_REAR_RIGHT_ZOOM=0.80VIEW_REAR_WINDOWS=33VIEW_REAR_DIR=0.0, 0.0, 190.0VIEW_REAR_ZOOM=0.80VIEW_REAR_LEFT_WINDOWS=34VIEW_REAR_LEFT_ZOOM=0.80VIEW_LEFT_WINDOWS=35VIEW_LEFT_ZOOM=0.80VIEW_FORWARD_LEFT_WINDOWS=36VIEW_FORWARD_LEFT_DIR=1.0, 0.0, 315.0VIEW_FORWARD_LEFT_ZOOM=0.80VIEW_UP_WINDOWS=37VIEW_UP_DIR=-90.0, 0.0, 0.0VIEW_UP_ZOOM=0.80[Window00]file=Main.bmpfile_1024=Main.bmpsize_mm=1280,960window_size_ratio=1.5position=0visible=1update_rate=20ident=MAIN_PANELgauge00=B732ADV!systems, 1, 800, 1, 1 //invisible gauge//gauge01=B732ADV!asi, 0, 592, 167, 172gauge02=B732ADV!adi, 178, 566, 201, 195gauge03=B732ADV!rmi, 7, 775, 150, 180gauge04=B732ADV!altimeter, 397, 624, 134, 131gauge05=B732ADV!vsi, 399, 774, 131, 131//gauge05=ILH_TCAS!IVSIb, 393,769,142,142, pic:nogauge06=B732ADV!epr_1, 742, 495, 95, 99gauge07=B732ADV!epr_2, 844, 495, 95, 99gauge08=B732ADV!flap, 1156, 530, 79, 81gauge09=B732ADV!dimmer, 687, 504, 17, 43gauge10=B732ADV!gear_lights, 1250, 567, 27, 47gauge11=B732ADV!gps_switch, 394, 925, 34, 34//gauge11=ISG1!LNAV, 388, 917, 44, 44gauge12=B732ADV!effects, 110, 544, 52, 52gauge13=B732ADV!pdcs, 2, 800, 1, 1gauge14=B732ADV!fuel_qty_left, 552, 881, 81, 79gauge15=B732ADV!fuel_qty_center, 601, 792, 82, 84gauge16=B732ADV!fuel_qty_right, 650, 879, 80, 80gauge17=B732ADV!fuel_ptt, 623, 479, 16, 16gauge18=B732ADV!oil_press_1, 951, 596, 82, 82gauge19=B732ADV!oil_press_2, 1045, 595, 86, 85gauge20=B732ADV!ra, 542, 619, 148, 147gauge21=B732ADV!sb_lights, 543, 822, 51, 49gauge22=B732ADV!n1_1, 750, 595, 78, 79gauge23=B732ADV!n1_2, 847, 595, 78, 79gauge24=B732ADV!n2_1, 750, 784, 78, 80gauge25=B732ADV!n2_2, 847, 784, 78, 80gauge26=B732ADV!ff_1, 750, 879, 80, 80gauge27=B732ADV!ff_2, 847, 879, 80, 80gauge28=B732ADV!egt_1,749, 689, 80, 80gauge29=B732ADV!egt_2,847, 689, 80, 80gauge30=B732ADV!hsi, 185, 795, 187, 167//gauge30=isg1!EFS50_EHSI_NB, 200, 802, 157, 139 //134//gauge31=B732ADV!fd_cont, 709, 372, 174, 101gauge31=PS737CA!PS737MCP, 695, 355, 615, 120, 1gauge32=B732ADV!oil_qty_1, 950, 786, 80, 78gauge33=B732ADV!oil_qty_2, 1048, 786, 79, 78gauge34=B732ADV!oil_temp_1, 952, 690, 78, 80gauge35=B732ADV!oil_temp_2, 1048, 690, 78, 80//gauge36=B732ADV!ap, 895, 355, 385, 120, 1gauge36=PS737CA!PS737MCP, 895, 355, 415, 120, 1gauge37=B732ADV!apd, 447, 496, 96, 108gauge38=B732ADV!engine_lights, 942, 533, 205, 51gauge39=B732ADV!ap_disc, 399, 576, 38, 36gauge40=B732ADV!windshear, 70, 553, 34, 33gauge41=B732ADV!alt_alert, 387, 536, 49, 23gauge42=B732ADV!out_of_trim, 692, 823, 50, 24gauge43=B732ADV!autobrake, 1140, 691, 102, 269gauge44=B732ADV!antiskid, 1140, 660, 101, 23gauge45=B732ADV!le_lights, 1140, 625, 100, 23gauge46=B732ADV!caution, 492, 402, 196, 44gauge47=B732ADV!omi, 644, 506, 30, 102gauge48=B732ADV!comparator, 188, 525, 181, 26gauge49=B732ADV!marker_switch, 450, 458, 151, 37gauge50=B732ADV!toggle_clock, 708, 734, 20, 20gauge51=B732ADV!toggle_go_around, 708, 754, 20, 20gauge52=B732ADV!toggle_atc, 708, 774, 20, 20//gauge53=B732ADV!toggle_gps, 708, 714, 20, 20gauge54=B732ADV!toggle_overhead1, 708, 694, 20, 20gauge55=B732ADV!toggle_lights, 708, 674, 20, 20gauge56=B732ADV!toggle_map, 708, 654, 20, 20gauge57=B732ADV!toggle_throttles, 708, 634, 20, 20gauge58=B732ADV!toggle_radio, 708, 614, 20, 20gauge59=B732ADV!toggle_radio2, 708, 594, 20, 20gauge60=B732ADV!yaw_damp_ind, 1072, 495, 59, 27gauge61=B732ADV!test, 445, 923, 79, 35//gauge62=ISG1_TCAS!Logic, 1,5,1,1 //Invisible TCAS logic gaugegauge63=B732ADV!asi, 0, 592, 167, 172gauge64=B732ADV!ldg_gear, 1039, 874, 90, 83gauge65=B732ADV!hyd_dig, 945, 876, 90, 80gauge66=FS9Garmin530!GNS530 Icon_nc1, 708, 714, 20, 20gauge67=Autoland!Autoland, 708,794,20, 20gauge68=PS737CA!PS737HOUSEKEEPING, 635,1065,71,50[Window01]size_mm=660, 960window_size_ratio=1.0position=2visible=0ident=RADIO_STACK_PANELgauge00=B732ADV!radio1, 0, 0, 660, 960[Window02]size_mm=500,366window_size=0.5window_pos=8background_color=0,0,0visible=0ident=210gauge00=FS9Garmin530!GNS530_nc1, 0,0,500,366[Window03]size_mm=542, 635window_size_ratio=1.0position=0BACKGROUND_COLOR=16,16,16visible=0ident=THROTTLE_PANELgauge00=B732ADV!throttles, 0, 0, 542, 635gauge01=B732ADV!throttles2, 158, 20, 223, 328gauge02=B732ADV!throttles3, 65, 93, 68, 228gauge03=B732ADV!throttles4, 401, 134, 52, 327[Window04]file=lights.bmpsize_mm=1262, 158position=1visible=0ident=OVERHEAD_PANELgauge00=B732ADV!lights, 101, 4, 1084, 130[Window05]size_mm=140, 140window_size_ratio=1.0position=2visible=0ident=COMPASS_PANELgauge00=B732ADV!timer, 0, 0, 140, 140[Window06]file=overhead3.bmpsize_mm=1148,960window_size_ratio=1.0position=1visible=0ident=11// multiply vertical coordinate by .9375gauge00=B732ADV!ovhd_fuel, 0, 597, 256, 364gauge01=B732ADV!ovhd_apu,256, 847, 259, 113gauge02=B732ADV!ovhd_seat_belt, 523, 162, 113, 795gauge03=B732ADV!toggle_overhead1_close, 1060, 0, 88, 88gauge04=B732ADV!ovhd_gen, 255,580,259,267gauge05=B732ADV!ovhd_csd, 255, 310, 258, 282gauge06=B732ADV!ovhd_elecmeter, 255, 0, 259, 310gauge07=B732ADV!ovhd_hyd, 640, 408, 261, 142gauge08=B732ADV!ovhd_fltcontrol, 0, 103, 256, 351gauge09=B732ADV!ovhd_pneu, 901, 325, 247, 357gauge10=B732ADV!ovhd_press, 901, 683, 247, 277gauge11=B732ADV!ovhd_press2, 638, 688, 265, 272gauge12=B732ADV!ovhd_doorcvr, 640, 548, 261, 140gauge13=B732ADV!ovhd_iceprot, 639, 0, 262, 408gauge15=B732ADV!ovhd_ac, 901, 62, 246, 262[Window07]file=radio_upper.bmpsize_mm=975,565window_size_ratio=1.0position=2visible=0ident=12gauge00=B732ADV!pdcs_cdu, 701, 5, 248, 219gauge01=B732ADV!transp, 701, 232, 243, 122gauge02=B732ADV!alt_alert_cont, 421, 38, 157, 65gauge04=B732ADV!memory, 700, 506, 253, 54gauge05=B732ADV!fo_gyro, 718, 377, 213, 54gauge07=RealityXP_WX500!RDR, 319, 220, 354, 266gauge08=B732ADV!gyro_capt, 0, 389, 320, 176 [Window08]background_color=0,0,0size_mm=250,375position=0visible=1ident=EZ-GPS_V4zorder=10 gauge00=ezgpsv4!ezgpsv4,0,0,250,375[Window09]Background_color=0,0,0 size_mm=415,640window_size_ratio=1.000 position=0visible=0ident=4004window_pos=0.7312, 0.4541window_size=0.2623, 0.500gauge00=isg1!SMITHS_FMS, 0,0,415,640,B737_200[Window10]background_color=16,16,16size_mm=600,450window_size_ratio=1.0position=2visible=1ident=12012gauge00=EFinfo!FINFO, 0, 0, 600, 450gauge01=EFinfoH!FPL, -20, 0, 10, 10gauge02=EFinfoH!FPL2, -20, 10, 10, 10[Window11]background_color=16,16,16size_mm=50, 23window_size_ratio=1.0position=6visible=1ident=12013gauge00=EFinfoH!Icon, 0, 0, 50, 23 [Fixed Window30]file=FORWARD_RIGHT.bmpvisible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=30//gauge00=B732ADV!ap, 1, 1, 1, 1, 2[Fixed Window31]file=RIGHT.bmpvisible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=31//gauge00=B732ADV!ap, 1, 1, 1, 1, 3[Fixed Window32]file=REAR_RIGHT.bmpsize_mm=1024visible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=32//gauge00=B732ADV!ap, 1, 1, 1, 1, 4[Fixed Window33]file=REAR.bmpvisible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=33//gauge00=B732ADV!ap, 1, 1, 1, 1, 5[Fixed Window34]file=REAR_LEFT.bmpvisible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=34//gauge00=B732ADV!ap, 1, 1, 1, 1, 6[Fixed Window35]file=LEFT.bmpvisible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=35//gauge00=B732ADV!ap, 1, 1, 1, 1, 7[Fixed Window36]file=FORWARD_LEFT.bmpvisible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=36//gauge00=B732ADV!ap, 600, 1, 1, 1, 8[Fixed Window37]file=UP.bmpsize_mm=1024visible=0nomenu=1render_3d_window=1window_pos=0.0,0.0window_size=1.000,1.000ident=37//gauge00=B732ADV!ap, 1, 1, 1, 1, 9[Default View]X=0Y=1SIZE_X=8192SIZE_Y=3151[AdvDisplay]Day=255,255,255Night=60,60,60 //8,8,8Luminous=240,240,200Scott
December 9, 201015 yr Have that issue as well. Had to go back to the condensed version. Couldnt figure out what was wrong with it.Thanks
December 9, 201015 yr Author 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.
Create an account or sign in to comment