Hi BobFantastic work.I have a problem with the panel.cfg..... I am trying to use the CIVA INS and Lee Heatherington V/S-TCAS gauge, as I had on the previous mouse.Peter

Peter--you are missing the TCAS logic gauge--need to add gaugeXX=ILH_TCAS!Logic,1,5,1,1 to your Window00 main panel. Replace "XX" with one number higher than the last gauge number in that section, so if there's a gauge66=, then make your gauge67=ILH_TCAS!Logic,1,5,1,1RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Dear Bob,First of all, thanks very much again.I was writing the same issue with Kevin at the same time I think. I made a short,quick a test flight for checking existing bugs.-New sound DLL problem can be solve when re-install directX version (mine is 9.0c) as suggested above.-Autopilot warning has gone I think

Confirmed bug, will fix in next update

-1.26 version flap sounds better than new one!

Talked with a couple 737 pilot friends, and they tell me the flap motors are barely audible from the flight deck. The sounds are the same, just turned way down.

-there is no "no smoking" and "fasten belt" click sounds (chime)

The chimes only sound when the warning state changes...for example on the ground, the Fasten Seat Belt signs are on when the system is in auto, so you only get the chime when switching between OFF and AUTO. At cruise, the signs are normally off when in AUTO, so the chime sounds when the switch is moved between ON and AUTO.

-there is no sound when start levers turn to GND while engine start(click or else)

There never has been, but I'll make a note to add it for the next update.

-spoiler lever slide down sound probably much better in 1.26

Same sound as in 1.26...only perhaps the relative volume has changed

-altitude callouts doesn't say properly the counts (and very loud). I don't know it is causing from my configuration (winXP-SP2+onboard sound card). Does work properly in v1.26. It seems something wrong on sound recording.I'll try replace some of sounds from v1.26

You can't replace the sounds--they are contained in XACT soundbank files and are not editable. Wht do you mean they don't say them properly?

-is there any chance to add a "cart" object when we start cart with ground call button?

Not with the models we have now.

also just I'm curious, if cart support electricty and air, should we see power when GND PWR switch ON?I can't see any value while cart running (probably my fault)

Although gnd power and air can both be provided by most ground start units, they can and often are connected independently. Often ground electrical power is used during a ground time, and the APU is started just before pushback, so the air is never connected. I think separate is the way to go here.

MrSkyGuy's sperry177 looks great with new numbers.Is there any chance to add a cfg files for "sperry177+TCAS+INS"? (or I'll be follow your instructions about removing and replace lines "//" in cfg )

I went with the analog version of the SP177 instead of the digital one with the LED digits. I have never seen a -200 with a digital 177 in it.

Thanks for everything.Thanks very much for your effort. I wish you merry xmas, I hope you have get everything that you wish in new year.

You're welcome, and Happy Holidays to you and yours in Turkey as well!Bob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

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.

Mark; The TCAS gauge is Lee Hetherington's TCAS gauge, available separately. It cannot be run together with the ISG glass HSI, because the ISG gauge uses a version of that same TCAS logic gauge specific to the ISG units, and the two will not run together. Anyway, you have to install Lee's TCAS gauge into FS9 to make it work as the panel.cfg was intended. Yes, I inadvertently left the gauge references for your XML MCP in the SP177+ISG+TCAS sample...I posted instructions for fixing that in the "bug extermination status" post pinned to top of thread. How are you actuating your brakes?CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob,I'll add my voice to the congratulations on great work! This is a standout airplane simulation.The FSCaptain interface works perfectly. I do have one little request though.When the cabin temp gets initialized the cabin seems to be about the OAT or zero whichever is higher. This seems reasonable at first glance, but I couldn't find a way to warm it up before the PAX start boarding, and they aren't too happy about boarding into a 0C airplane, even though it will warm up later once I get the packs switched on after engine start. Could you initialize the temp to about 22C, either on startup, or more realistically perhaps, if the ground air is attached. After that let it free-float but start at about 22.Not a biggie, but I forgot to mention that to you earlier. I has bitten me in a couple of airplanes I interfaced.Many thanks, and don't work too hard :)Dutch

Mark; The TCAS gauge is Lee Hetherington's TCAS gauge, available separately. It cannot be run together with the ISG glass HSI, because the ISG gauge uses a version of that same TCAS logic gauge specific to the ISG units, and the two will not run together. Anyway, you have to install Lee's TCAS gauge into FS9 to make it work as the panel.cfg was intended. Yes, I inadvertently left the gauge references for your XML MCP in the SP177+ISG+TCAS sample...I posted instructions for fixing that in the "bug extermination status" post pinned to top of thread. How are you actuating your brakes?CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

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.

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.

Manually...with a key, joystick button, with brake pedals mapped to an axis, ...? In the FS options, what key/button/axis settings do you have? Anything in FSUIPC? I can't replicate any problems with autobrakes here, so looking for something in common between the few people that have reported a problem there.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

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?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.thanks very much once again.

I would start by going to the support.microsoft.com website and update DirectX, and also your video and audio drivers. The biggest source of trouble so far has been the XACT engine used for sounds, and older versions of DX9 and some drivers seem to be behind some of the gauge not loading problems.

Thank you for your reply. I already updated my DirectX and video driver to the latest version, but the sound driver is quite outdated. My motherboard is Asus P4P800 and its latest sound driver was released in 2003 :(. But thank you for your help and keep up the good work :(

Peter--you are missing the TCAS logic gauge--need to add gaugeXX=ILH_TCAS!Logic,1,5,1,1 to your Window00 main panel. Replace "XX" with one number higher than the last gauge number in that section, so if there's a gauge66=, then make your gauge67=ILH_TCAS!Logic,1,5,1,1RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

That fixed it. Thank you so much for this great plane. 1.3 really does handle superb.Peter

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

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

According to the manual, you have to enable the PCDS to have this work.

Please post your bug reports here in this thread. I can't fix what I don't know about.

The smoke coordinates in FSX do not appear to be correct. Can anyone verify this and please give the right coordinates? Thanks, Bob.

First, thanks again for all the help getting this installed last night. I had a chance to do a 'shakedown' flight today, and even poked through the manual a bit. Initially I found a lot wasnt working, but all minor stuff except for one major issue, the airspeed indicator guage had no indicator needle and would not register speed at all. The AP would control it ok but nothing on the guage itself.After trying numerous things, I finally tried loading a default plane first (172), then loading the TM, and VIOLA, everything worked. I 'saved' the TM then exited and reloaded FS and the same problem again.It seems that the only way I can get the plane to load correctly is to load a default plane first, which won't work in multiplayer, as you cant change planes once you enter a session. Is this normal or am I the only one having this problem? I do use a registered copy of FSUIPC.

Thank you for your reply. I already updated my DirectX and video driver to the latest version, but the sound driver is quite outdated. My motherboard is Asus P4P800 and its latest sound driver was released in 2003 :(. But thank you for your help and keep up the good work :(

If I were you, I'd go to the realtek website and look there for updated drivers for the ALC850 sound chip in that motherboard. RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

First, thanks again for all the help getting this installed last night. I had a chance to do a 'shakedown' flight today, and even poked through the manual a bit. Initially I found a lot wasnt working, but all minor stuff except for one major issue, the airspeed indicator guage had no indicator needle and would not register speed at all. The AP would control it ok but nothing on the guage itself.After trying numerous things, I finally tried loading a default plane first (172), then loading the TM, and VIOLA, everything worked. I 'saved' the TM then exited and reloaded FS and the same problem again.It seems that the only way I can get the plane to load correctly is to load a default plane first, which won't work in multiplayer, as you cant change planes once you enter a session. Is this normal or am I the only one having this problem? I do use a registered copy of FSUIPC.

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.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO