Ron Burden

Thanks Tom.... Either direction requires me to learn the entire process, so, I may just make the decision to stay with 2.66 and start learning while putting up with the bugs. Thank you for your patience and time.. Ron

Sorry.... I am sure I wasn't clear. The 'version of Blender' is what I was speaking of. I've downloaded the 2.66 version.... Now I have to figure out what to do with it. I anticipate a lot of reading of its manual this weekend. If you have some simple points regarding "strategy", I'll accept any guideline(s). Have a good weekend Tom. Ron

Tom... I have read and read again the info you placed here regarding 3_D handling. Which 'Blender' level should I obtain to start with? Thanks, Ron

Whooh..... Thanks Tom. This information really gives me a 'LOT' to think about and experiment with. I am and will be taking very small baby steps in this entire process. But thank you for giving me a 'compass course' to start with. Ron

Good morning Tom.... And I can ask this of any one who may have a logical path for me to follow.... I would like to learn to do 3-D panels. With that said, I've been doing a lot of reading but I'm not finding the information I really need to get started in doing this. Can any one guide me in a direction where I might get some easy Steps to follow that would enable me to learn the basics of designing a 3-D panel. I know layering is involved, I know you need a 3-D folder in your aircraft folder that compliments the aircraft 2-D folder. But how does the resource folder with all the bitmaps and information all tie together with making it all work. I know I may be jumping into this over my head..... but I am technically interested in learning more. Thanks for any guidance. Ron

Thanks Tom.....

Good morning Tom.... Any possibility you could activate one or more of the 'COM/NAV' switches so you can listen to the Nav station identifier and turn it off after doing so? Thanks, Ron

Tom... if all else fails... hit your 'B' key to release the parking brakes. Ron

John.... YOU are NEVER to old to learn new tricks... :rolleyes:

Jcomm.... I agree with you regarding setting all your waypoints through the FMS, much cleaner. Now I would like to find out 'why' the VNAV quit working... It worked fine up until the last A/C update.

Hello John, I just finished flying the King C-90 at KROA following your description on the route you fly (hand flying it but allowing the Autopilot to fly the approach). I had my ILS Rwy 33 (34 now) set up using 109.7 for the Localizer. I flew it in its entirety, landed, taxied back and reconfigured the aircraft for takeoff. I set up the FMS to fly to MONAT Intersection - Direct to WOTUP Intersection allowing the autopilot to intercept the localizer and glideslope. Every thing worked fine. Sounds like your autopilot either disengaged on you (either by hitting an incorrect button or turbulence could also play into the disengagement of your autopilot) Just double check every thing.... It should work no matter how many times you decide to fly the approach. I am a retired Instrument Flight Instructor and if I can be of any help let me know. Ron

AHhhhh.... Tom, please don't take the FMS out. I realize the King C-90 never really had one, but I was getting use to programming it and having VNAV capture the altitude and fly it. The vertical speed works great, the 'Arm & altitude capture' works fine. :mellow: Do what you have to do..... I will still love flying it! :rolleyes: Thanks, Ron

Good morning Tom K...... Thank you for taking care of everything we talked about. I just flew the King C-90 yesterday and realized everything you had done, however I just also realized that we have 'LOST' the functionality of VNAV. Autopilot appears to be working properly with the exception of VNAV. It use to work very nicely and followed what ever altitude you had dialed in on the FMS... not any more. It won't turn on. Would you mind checking into this please? Also, I 'think' it was John who commented to me regarding the HUD brightness control within X-Plane. I will check into that John, thank you for your input. You all have a wonderful weekend. Ron B. KENW

Tom.... you are correct regarding Reverse Thrust, no indicator light exists...... just my personal preference. Regarding the HUD Display, real plane did not have one.... However, I can use an HUD provided by X-Plane... I just need a way of dimming it. Thanks Tom.... and every one else who has equipment knowledge regarding the C-90. It's been a really long time since I've been in the real cockpit so I am sure I am adding one or two things I would just like. Thanks again, Ron

Thanks Tom.... I look forward to flying the C-90 even more. Beautiful rendition of the real aircraft!

Tom Kyler.... X-Plane tech support pointed me in your direction.... and I am the newest NEWBI on this forum.... So much so I have no idea of how to post new question(s). I will cut and paste my e-mail request to X-Plane regarding the KingAir C90B. Since you are going to, or are in the process of doing some refining of the C-90 Panel maybe you could help out with some or all of the items I've listed. What ever you can do I would appreciate it. Thanks in advance. Ron Hi Randy.... I've been flying X-Planes C-90 - Tail Number 43XS using X-Plane 10 in the 64 bit version.... It is very nice. Who at X-Plane could I e-mail regarding having a few things added to the instrument panel? I know it's in 3-D and I have no way, or at least I believe I have no way of adding things. Things I would like to see added to the planes Instruments would make it even more realistic. They are: 1) Tail Number ID tag. 2) OAT gage digital or analog 3) Marker Lights for: OM MM IM 4) Ice Detect Annunciator light 5) Ice Detect ON/OFF Switch 6) HUD Display Dimmer Control 7) Back Lit Buttons for Auto Pilot & FMS (kind of hard to find what you need in the dark) 8) Altitude Select on Instrument Panel could use back lighting. 9) Thrust/Prop Reverse Annunciator light I'll be happy to talk with who ever builds your planes about this if you let me know. If these items can not be taken care, just let me know please. Thank you, Ron Burden KENW