Hi,ALT/Hod and FLCH do not work on my machine - I am climbing using VS and if I click on "ALT HOLD" before reaching target altitude, nothing happensI am stable, SPEED mode engaged, if I click on "FL CH" with a higher altitude dialed, nothing happens.Would you have any idea?Thanks!Olivier

If you do not have the PDCS engaged in climb or max-continuous thrust mode, then LVL CHG will not command the autothrottles, and with the power already set for a stable climb at the selected speed, LVL CHG will look no different initially.I haven't been able to reproduce a problem with Alt Hold...every time I press the switchlight, the jet does a fairly aggressive immediate level off.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

This is not a bug..however I have a question..?? Is it possible to have both AP versions (the 77 and the 177) active in your aircraft folder...FS9.. It would be nice to "select" your aircraft version without modifing the panel.cfg file.. Possibly renaming the panel folder..??Ray Lunning

Dear Bob,Thank you for your patience and answers of my bug reports/and question. I noticed thats you said.Callouts problem is; it comes like as "one" instead "one thousand", so seems like says half (or without a few letters) of call outs begin or last part. Also couldn't say last a few heights. I heard a bit distortion on sound recording. The same is trim sound, example if I use trim often(ie.three times in a few second), second or third trim sound is cutting.Maybe it happening on my system,becouse no one reported like that problem. In v1.26 there wasn't problem with older FSsound.dll. Could be cause of new sound DLL?

I saw this same thing (sounds cut off after the first syllable) when I started testing the new panel sounds. Believe it or not, updating my nVidia video driver from 258.xx to 261.xx solved it.

Meanwhile, did you touch FDE in new version?Because of, while taking off, in this time plane was very stable and she doesn't act to excessive positive pitch.In v1.26 she was nose up approx +4000fpm even pushing the nose and reduce thrust. Now seems like excessive nose up problem is gone in v1.30.

No FDE change. I may have the W&B different on the config, with the CG moved up forward a bit. I was testing that way...don't remember if that made it into the final aircraft.cfg file or not.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

This is not a bug..however I have a question..?? Is it possible to have both AP versions (the 77 and the 177) active in your aircraft folder...FS9.. It would be nice to "select" your aircraft version without modifing the panel.cfg file.. Possibly renaming the panel folder..??Ray Lunning

Yes, like this:1. Create a copy of the panel.B732ADV folder under the fsfsconv folder, for example panel.B732_SP77. Copy the contents of the entire panel.B732ADV folder into it. Make settings for the SP-77 in the panel.cfg file in that new folder2. In the panel folder under subfolder B737-200_TM2, create a new folder named panel.SP77, and in it, create a panel.cfg file that has just these two lines:[fltsim]alias=fsfsconv\panel.B732_SP773. In your aircraft.cfg file, in the fltsim.xx sections that define each repaint, change the line "panel=" to panel=SP77 for those aircraft that you want to come up with the SP77.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Loading a default plane first is a common requirement for add-ons, as it resets some internal variables that may be saved from session to session.The way to fix this is to load a default airplane like the C172, making sure the battery master switch and avionics master switch are both on, that the sim in not in GPS mode, and save that, checking the box to make it your default flight. That way any time FS is loaded, a default plane is loaded up even before you select an aircraft...has the same effect.

Thanks, I am aware that some planes recommend starting with a default flight, but honestly, I have never had to do that before and never had a problem until now.I just tried your suggestion and that's not working either so apparently its something else.I loaded the 172 on a runway, made sure everything is set correctly, saved it as a default flight, then exited FSX and restarted it. It started with the default 172, I selected the TM and went into a runway and had the same problems, no sounds, no AS needle, and a variety of warning lights on.Without closing FSX, I switched to the 172 then back to the TM and everything started working, it cycled through all the subpanels, no warnings, sounds were ok, etc.It appears that I have to actually load the 172 onto a runway then switch to the TM to get it working, so I assume I either hosed something on the install or something else is going on I'm not aware of, unless this is normal for everyone.Any sugestions appreciated at this point, since I only fly in multiplayer and switching planes once in a session is impossible.

Thanks, I am aware that some planes recommend starting with a default flight, but honestly, I have never had to do that before and never had a problem until now.I just tried your suggestion and that's not working either so apparently its something else.I loaded the 172 on a runway, made sure everything is set correctly, saved it as a default flight, then exited FSX and restarted it. It started with the default 172, I selected the TM and went into a runway and had the same problems, no sounds, no AS needle, and a variety of warning lights on.Without closing FSX, I switched to the 172 then back to the TM and everything started working, it cycled through all the subpanels, no warnings, sounds were ok, etc.It appears that I have to actually load the 172 onto a runway then switch to the TM to get it working, so I assume I either hosed something on the install or something else is going on I'm not aware of, unless this is normal for everyone.Any sugestions appreciated at this point, since I only fly in multiplayer and switching planes once in a session is impossible.

Are you running in DX10 Preview mode? Which lights are on? Some of the lights are on in the background bitmaps, and a light on may mean that the gauge bitmap isn't rendering, just like the AS needle. And when you say sounds don't work, do you mean just the panel sounds or the engine and other FSX sounds as well? If you have parts disappearing off the gauges, it makes me think there's something strange going on in DirectX or the video subsystem itself. With both video and audio anomalies, I tend to suspect a DirectX-related problem first. When's the last time it was updated? What video drivers are you using? Sound drivers?RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I had no problems installing v1.3 in FSX (as a test before installing it in FS9), but when I attempted to load the TinMouse (one of my all time favorite FS9 planes!) I got the following Ox7e error message:"FSAudio.dll failed to load. Make sure FSAudio.dll is installed in the windows/system32 folder and restart application".The problem with this is that I did, per the installation instructions, copy FSAudio.dll to my 32 bit windows XP system32 folder. I copied it to the main system32 folder, not a subfolder (as the instructions seem to fall for). Should I have placed it in a subfolder? If so, which one? Or should I have left a copy of FSAudio.dll in my FSX sound folder?A discussion in another thread mentions that installing a Directx 9c update (Directx June 2010 Redist)from Microsoft fixes the problem (at least for one person). However, this update is apparently intended for software developers, not end-users. Microsoft's description of the update states that it "provides the Directx end-user redistributable that developers can include with their product".Not being a software developer, I'm a tad bit reluctant to run this update on my system. Any chance this problem can be fixed without having to install the software developer Directx update?I have very much enjoyed the Sperry 177 gauge update for the v1.26 TinMouse, but v1.3 would solve a couple of problems I've run into using it!Thanks for an absolutely first rate aircraft for FS9 and (now!) FSX, Bob!Scott Miller

I had no problems installing v1.3 in FSX (as a test before installing it in FS9), but when I attempted to load the TinMouse (one of my all time favorite FS9 planes!) I got the following Ox7e error message:"FSAudio.dll failed to load. Make sure FSAudio.dll is installed in the windows/system32 folder and restart application".The problem with this is that I did, per the installation instructions, copy FSAudio.dll to my 32 bit windows XP system32 folder. I copied it to the main system32 folder, not a subfolder (as the instructions seem to fall for). Should I have placed it in a subfolder? If so, which one? Or should I have left a copy of FSAudio.dll in my FSX sound folder?A discussion in another thread mentions that installing a Directx 9c update (Directx June 2010 Redist)from Microsoft fixes the problem (at least for one person). However, this update is apparently intended for software developers, not end-users. Microsoft's description of the update states that it "provides the Directx end-user redistributable that developers can include with their product".Not being a software developer, I'm a tad bit reluctant to run this update on my system. Any chance this problem can be fixed without having to install the software developer Directx update?I have very much enjoyed the Sperry 177 gauge update for the v1.26 TinMouse, but v1.3 would solve a couple of problems I've run into using it!Thanks for an absolutely first rate aircraft for FS9 and (now!) FSX, Bob!Scott Miller

ScottI am running FS9 on Win7 64 bit, so not the same setup as you, but the FSAudio.dll goes in the System32 folder (not a sub folder).The DirectX update I used was this one http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3That solved my error message (same error message as you)Peter

Are you running in DX10 Preview mode? Which lights are on? Some of the lights are on in the background bitmaps, and a light on may mean that the gauge bitmap isn't rendering, just like the AS needle. And when you say sounds don't work, do you mean just the panel sounds or the engine and other FSX sounds as well? If you have parts disappearing off the gauges, it makes me think there's something strange going on in DirectX or the video subsystem itself. With both video and audio anomalies, I tend to suspect a DirectX-related problem first. When's the last time it was updated? What video drivers are you using? Sound drivers?

Not using DX10 preview, updated DX a few weeks ago with the latest update, DX11 here Video drivers: 6.17.11.9745 Nvidia Sound: 6.00.0001.6029 RealTekThe lights on are the fuel low pressure and cant be extringished. There are a few others I cant remember off the top of my head, but those are an immediate indicator the plane didnt load correctly.Engine sounds work but nothing else, no switch sounds, no flaps, etcAll this fixes itself as soon as I load a default plane then switch back to the TM. I think this may have something to do with the location of that 'fsfsconv' folder in the Simobjects/Airplanes folder. That is the only file that is NOT a airplane in there. I am going to do some experimenting today and will report back. Edit: Update, problem resolved with a 'workaround'. Once the plane is loaded, I hit 'CTRL+SHIFT+R' to reload the plane and all is well. Not the ideal solution but it works, thanks for the help.

Edited December 23, 201015 yr by PIC007

I had no problems installing v1.3 in FSX (as a test before installing it in FS9), but when I attempted to load the TinMouse (one of my all time favorite FS9 planes!) I got the following Ox7e error message:"FSAudio.dll failed to load. Make sure FSAudio.dll is installed in the windows/system32 folder and restart application".The problem with this is that I did, per the installation instructions, copy FSAudio.dll to my 32 bit windows XP system32 folder. I copied it to the main system32 folder, not a subfolder (as the instructions seem to fall for). Should I have placed it in a subfolder? If so, which one? Or should I have left a copy of FSAudio.dll in my FSX sound folder?A discussion in another thread mentions that installing a Directx 9c update (Directx June 2010 Redist)from Microsoft fixes the problem (at least for one person). However, this update is apparently intended for software developers, not end-users. Microsoft's description of the update states that it "provides the Directx end-user redistributable that developers can include with their product".Not being a software developer, I'm a tad bit reluctant to run this update on my system. Any chance this problem can be fixed without having to install the software developer Directx update?I have very much enjoyed the Sperry 177 gauge update for the v1.26 TinMouse, but v1.3 would solve a couple of problems I've run into using it!Thanks for an absolutely first rate aircraft for FS9 and (now!) FSX, Bob!Scott Miller

The 0x7e error means your DX9 isn't up to date. Go to support.microsoft.com, look on the left side of the page for downloads and updates, and click on the DirectX link. It should download a file named dxwebsetup.exe...it's not just for developers.The Microsoft XACT audio engine came along midway through the FS9 life cycle, and it requires a fairly recent version of DirectX 9. RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Not using DX10 preview, updated DX a few weeks ago with the latest update, DX11 here Video drivers: 6.17.11.9745 Nvidia Sound: 6.00.0001.6029 RealTekThe lights on are the fuel low pressure and cant be extringished. There are a few others I cant remember off the top of my head, but those are an immediate indicator the plane didnt load correctly.Engine sounds work but nothing else, no switch sounds, no flaps, etcAll this fixes itself as soon as I load a default plane then switch back to the TM. I think this may have something to do with the location of that 'fsfsconv' folder in the Simobjects/Airplanes folder. That is the only file that is NOT a airplane in there. I am going to do some experimenting today and will report back. Edit: Update, problem resolved with a 'workaround'. Once the plane is loaded, I hit 'CTRL+SHIFT+R' to reload the plane and all is well. Not the ideal solution but it works, thanks for the help.

Apparently several of the gauge bitmaps are disappearing (i.e. the light graphics that overlay the fuel press lights, the airspeed needle, etc. That together with the disappearance of the panel sounds suggests something off in the DirectX-driver realm. Your video driver is fairly dated...occasionally I have seen some issues with drivers that pre-date the DirectX update in use.Anyway, if the panel reload workaround will save you the hassle of playing musical drivers, good deal.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Using FSX Gold, loading the default Cessna at KSEA, I shut down the engine leaving just Avionics and Master Battery on. I then switch to the Tin Mouse II Continental airlines and let it fully load. I pull up the throttle quadrant and if I happen to click on the Stab Trim selector on the lower right near the parking brake light, I get a crash to desktop every time.ChuckCYXU

Using FSX Gold, loading the default Cessna at KSEA, I shut down the engine leaving just Avionics and Master Battery on. I then switch to the Tin Mouse II Continental airlines and let it fully load. I pull up the throttle quadrant and if I happen to click on the Stab Trim selector on the lower right near the parking brake light, I get a crash to desktop every time.ChuckCYXU

Yep, that's a confirmed bug. Found and fixed. Until the next update stay clear of the electric stab trim cutout switch.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Thanks for the heads up about dxwebsetup.exe, Bob! I almost missed it! I asked for email notification of replies but didn't get one and it was no where to be seen when I logged into the thread just now. It wasn't until I started to repost yesterday's post that I stumbled across your reply (which is really weird)!Scott

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.