Merry Christmas Bob, and thank you for sharing the ultimate Christmas gift for us. I've noticed a problem however, with a module requested to be placed into the Windows/System32 folder, which was FS2AUDIO.dll. I've installed it on the folder but while loading, FSX displays a message saying that the module is not found, and the aircraft only managed to run on the tarmac at KIAH before eventually CTDing while I planned the setting for the trim settings. I wonder what went wrong? Please help me. I can't bear to wait till Chinese New Year just to enjoy this wonderful Christmas gift!! :Cry:Dave.

Pretty much all of the problems related to FS2Audio that I've seen so far have been caused by a non-current install of DirectX 9 on the user's PC. Try updating your DirectX, and make sure \windows\system32 is in your system path.Microsoft DirectX End User UpdateRegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

AP Mach readout:when changing from IAS to Mach and scrolling it UP, the readout jumps from .78 back to .70 then to .81 It seems like .79 and .80 is missing

I'd like to add my thanks and congratulations to Bob Scott and all the team for v.1.30, overall it's definitely an improvement over v.1.26. One little problem I've found is that adding "JT8D-9" in the title line in the aircraft.cfg [fltsim.x] section does not result in the selected engine's dynamics and characteristics being modeled. At least as par as the PDCS is concerned. I can't tell if it's only the PDCS that's affected. Is there something else I should have done?

AP Mach readout:when changing from IAS to Mach and scrolling it UP, the readout jumps from .78 back to .70 then to .81 It seems like .79 and .80 is missing

Confirmed bug. Fixed, will be included in V1.31 update. This one can (but usually does not)cause a divide-by-zero error/CTD when stationary on the ground.ThanksBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I'd like to add my thanks and congratulations to Bob Scott and all the team for v.1.30, overall it's definitely an improvement over v.1.26. One little problem I've found is that adding "JT8D-9" in the title line in the aircraft.cfg [fltsim.x] section does not result in the selected engine's dynamics and characteristics being modeled. At least as par as the PDCS is concerned. I can't tell if it's only the PDCS that's affected. Is there something else I should have done?

Confirmed bug. The parser was only capturing the option if it was at the end of the Title= line. This will also affect the -MB, KGS, ISG, options--right now only the last one is recognized. Fixed, will be in V1.31Thanks for identifying it.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Thanks Bob. But even though I put JT8D-9 at the end of the Title=line, the PDCS still shows JT8D-17R.

Confirmed bug. Fixed, will be included in V1.31 update. This one can (but usually does not)cause a divide-by-zero error/CTD when stationary on the ground.

Good thing I only change it in the air! :-)

Thanks Bob. But even though I put JT8D-9 at the end of the Title=line, the PDCS still shows JT8D-17R.

The other possible gotcha is if the Title= line is over 75 char long...right now the option has to be in the first 75 characters (and it must be at the end). For the next update I am going to extend that to the full 256 characters allowed in the Title= line.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Hi Bob ! First ... thank you very much for your hard work and the pleasure you give us with V1.3.One thing i found is in the SP177 programing. When selecting V/S mode the value in the V/S window should be the same as the VSI. The same for FLCH, when selecting FLCH the value should be the same as the actual ASI/MACH. For me FLCH only works with AP engaged, in real it can be used with FD only for hand-flying. (like all FD/AP modes)Best regards ThomasMovement ControlTWR LOWW

The other possible gotcha is if the Title= line is over 75 char long...right now the option has to be in the first 75 characters (and it must be at the end). For the next update I am going to extend that to the full 256 characters allowed in the Title= line.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob,I'm afraid there's something more going on here than you say. I have 2 aircraft with much less than 75 characters in the Title= line of the aircraft.cfg file, with JT8D-9 at the end, and the PDCS still says JT8D-17R.

Bob,I'm afraid there's something more going on here than you say. I have 2 aircraft with much less than 75 characters in the Title= line of the aircraft.cfg file, with JT8D-9 at the end, and the PDCS still says JT8D-17R.

Can't tell you any more than it's been fixed already for the next update, and tested successfully with about 10 different configurations.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Hi Bob ! First ... thank you very much for your hard work and the pleasure you give us with V1.3.One thing I found is in the SP177 programing. When selecting V/S mode the value in the V/S window should be the same as the VSI. The same for FLCH, when selecting FLCH the value should be the same as the actual ASI/MACH. For me FLCH only works with AP engaged, in real it can be used with FD only for hand-flying. (like all FD/AP modes)Best regards ThomasMovement ControlTWR LOWW

Hi Thomas; The behavior you describe for the V/S mode is correct for the newer digital versions of the A/P like the SP-300 and later, but I suspect not for the analog boxes. Do you have a manual for one of these autopilots? I'm going on recollections of guys that flew them in the (not recent) past. Examining the box itself, I'm finding it hard to imagine they put in a servo control for the VSpeed dial, given the technology available when these were first introduced. Not to say it's not possible, but I'll need a definitive source before I change the behavior.A flight director mode for hand-flying a LVL CHG climb/descent is something we're going to have to live without for the time being...way too much work for me right now.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Hi Bob,Having a bit of a problem. When I try to select the "Tinmouse" from the aircraft menu I get a "boink" sound and an error message that states "FS2Audio.dll failed to load". I did put that dll in the windows/system32 folder.Also, something you wrote in the "Readme File" that contains the installation instructions has me confused (which can easily happen, I admit). I'm assuming that the main "Quick Start" part of the readme is for FS9 since you state at the beginning to see the next section for FSX. However, line 8 of the Quick Start says:"8. Copy the three files in the \sound folder to the FSX\sound folder. These files must be in the fsx\sound directory or the panel sounds will not work."Are those files also for FS9? I put them in my FS9\sound folder just in case...I'm running FS9 on a WinXP machine with SP3. I have registered version 3.98a of FSUIPC.Thanks a bunch for all the work you've down on this project!Cheers,Scott KJMS (or thereabouts)

Scott, Try reloading Directx. That solved my problem. It should solve your FS2Audio.dll error.Pat

Hi Bob,Having a bit of a problem. When I try to select the "Tinmouse" from the aircraft menu I get a "boink" sound and an error message that states "FS2Audio.dll failed to load". I did put that dll in the windows/system32 folder.Also, something you wrote in the "Readme File" that contains the installation instructions has me confused (which can easily happen, I admit). I'm assuming that the main "Quick Start" part of the readme is for FS9 since you state at the beginning to see the next section for FSX. However, line 8 of the Quick Start says:"8. Copy the three files in the \sound folder to the FSX\sound folder. These files must be in the fsx\sound directory or the panel sounds will not work."Are those files also for FS9? I put them in my FS9\sound folder just in case...I'm running FS9 on a WinXP machine with SP3. I have registered version 3.98a of FSUIPC.Thanks a bunch for all the work you've down on this project!Cheers,Scott KJMS (or thereabouts)

Scott, Try reloading Directx. That solved my problem. It should solve your FS2Audio.dll error.Pat

Hi Pat,Thanks for the reply. By "reloading" do you mean reinstalling DirectX 9.0c? I did a quick google search on how to do it and it does not sound like it would work. It won't reinstall over the current version since it detects a current version (if that makes sense). Perhaps there is a line that needs to be added to the FS9 config referencing the FS2audio.dll?Cheers,ScottKJMS (or thereabouts)