OK guys, the V1.31 update is available in the library. Link posted in the pinned FAQ.I'd like to hear back from the people that were having problems with disappearing/nonfunctioning airspeed needles etc to know if this update has solved that problem.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Thanks Bob, I was one who had this weired airspeed problem. Hope that this fixes it.

Thanks Bob & Happy New Year to you and yours.Pat

OK guys, the V1.31 update is available in the library. Link posted in the pinned FAQ.I'd like to hear back from the people that were having problems with disappearing/nonfunctioning airspeed needles etc to know if this update has solved that problem.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Thanks indeed Bob.Best wishes for the new year.RegardsTrevor

I still have problems with the black screen and FS says the error is related to RXP's WX gauge, so it turns out that it wasn't due to Directx or conflicting TCAS. The wxr works fine on other aircraft though.

I still have problems with the black screen and FS says the error is related to RXP's WX gauge, so it turns out that it wasn't due to Directx or conflicting TCAS. The wxr works fine on other aircraft though.

Is this in FS9 or FSX? I use the RXP radar in FS9, but have never used the FSX version. There's no interface at all between the RXP radar gauge and the panel, so no idea what's causing that.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Is this in FS9 or FSX? I use the RXP radar in FS9, but have never used the FSX version. There's no interface at all between the RXP radar gauge and the panel, so no idea what's causing that.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob, never mind I fixed it, turns out that RXP needed a reinstall and it was for FS9. Too tired to properly fly this beautiful bird now but I'll take her on a few hops tomorrow, thanks again for your hard work!

Hi Bob,Thank you for the v1.31 update. I have a question regarding the location of the TM.INI file. In the Readme file you state that TM.INI should be located in the FS root directory, but in the TM.INI file itself, the header comments state that the file should be located in \fsfsconv\panel.B732ADV directory (ie; in FS9 <your FS9 directory>\aircraft\fsfsconv\panel.B732ADV\).Could you please confirm which is correct?Thanks,

BobJust some feed-back.All fixes appear to be corrected except #5 in your read-me notes.MCP - Mach readout - .62 and .74 do not appear. Goes from .61 to .63 and from .73 to .75I hope you follow my next point - difficult to describe - when clicking on the mach numbers, you can click twice on .56 and .68 and .81 - first click, nothing changes, second click moves on to next number.Also - when climbing at 300KIAS (LVL CHG) the mach numbers increase until .70 appears in the window. I then click on the C/O feature and M.69 appears in the window instead of .70 and the plane climbs at about .71I trust you are able to fix this one.Again, thanks for all your hard work, especially over the holiday season - much appreciated.RegardsTrevor

Hi Bob,Thank you for the v1.31 update. I have a question regarding the location of the TM.INI file. In the Readme file you state that TM.INI should be located in the FS root directory, but in the TM.INI file itself, the header comments state that the file should be located in \fsfsconv\panel.B732ADV directory (ie; in FS9 <your FS9 directory>\aircraft\fsfsconv\panel.B732ADV\).Could you please confirm which is correct?Thanks,

FS root directory...it was initially in the panel.B732ADV directory, but that wouldn't work for those that are setting up multiple folders for SP77/SP177 dual configs etc, so I changed it. Guess I forgot to change the comments in the ini file.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

BobJust some feed-back.All fixes appear to be corrected except #5 in your read-me notes.MCP - Mach readout - .62 and .74 do not appear. Goes from .61 to .63 and from .73 to .75I hope you follow my next point - difficult to describe - when clicking on the mach numbers, you can click twice on .56 and .68 and .81 - first click, nothing changes, second click moves on to next number.Also - when climbing at 300KIAS (LVL CHG) the mach numbers increase until .70 appears in the window. I then click on the C/O feature and M.69 appears in the window instead of .70 and the plane climbs at about .71I trust you are able to fix this one.Again, thanks for all your hard work, especially over the holiday season - much appreciated.RegardsTrevor

How/when are you switching to mach to get this? It's caused by rounding errors happening behind the scenes, but I tested it extensively inflight and can't reproduce it.The initial value for the mach when c/o is pressed is the mach equivalent of the MCP set airspeed, not the airspeed being flown. If you have 300 KIAS in the MCP window, then you get the mach equivalent for 300KIAS at the time the button is pressed.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

FS root directory...it was initially in the panel.B732ADV directory, but that wouldn't work for those that are setting up multiple folders for SP77/SP177 dual configs etc, so I changed it. Guess I forgot to change the comments in the ini file.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Hi Bob. Thanks. Is the FSX root folder also the right location for it in FSX? Bob.

BobMany thanks for your work on this. Happy new year.Peter

BobWhat about the .62 and .74 that do not appear and are skipped ?RegardsTrevor

BobWhat about the .62 and .74 that do not appear and are skipped ?RegardsTrevor

I can't duplicate that here on any of my machines, which is why I asked you to fill me in on what you're doing that produces that.I have a suspicion as to what could cause it, if you send an e-mail to the support e-mail listed in the readme I'll send you a patch file to try, and we can see if my hunch is correct.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO