ofentress

Jeff............. I don't know what happened to the downloads the first time, but no problems this time. Installed and the voices are clear. You and your "gang" have done a wonderful job. Thanks a bunch. Jack Fentress

Jeff......... No. Not as yet. I was waiting to see if there was something I might overlooked. That'll be my next step. Thanks for the quick reply. From what I'm reading on the forum, this is a great series of packages. Jack

Jeff.......... I don't seem to be able to open the wav files. I've installed the Capt (117 files) and the F.O. (127 files), but when I attempt to activate the Airbus I get a message as follows: Error opening wav file xxxx. None of the wav files could be opened. I installed as individual files, so at the moment, the Sound_ASC folder has 344 individual files. That's the same way I installed for the previous Sound_ ASC folder. I installed per your suggestions, but so far, no luck. Jack Fentress

Jan......... Thank you for the quick reply. A simple solution which worked perfectly. My thanks again. Jack

Talk about surprised. Because of a Firefox glitch, I used my Acronis backup to re-install my system. The backup was from the first week in August. After adjusting various programs, I decided to give the Regina/Edmonton flight a chance, since I'd checked out so many other areas. To my surprise, everything worked just as it was supposed to. Finally! Whatever the glitch in FSX, flight plan, the airport or whatever, it seems to be corrected. Thanks to the gang who provided possible solutions even though apparently it was beyond all of our help. Jack Fentress

I had to use my Acronis back up to re-install from a few weeks ago and the update for the 200 and 300 took place after the back up date. The Operations Center is telling me that the 300 er is version 6036 and needs to update but for the life of me I can't find the update download location for this aircraft. I hope someone can direct to the right download area. Jack Fentress

Kyle.......... Well, this is actually a miniscule problem as far as the 737 NGX is concerned. After all, it's only one flight plan in one kind of minor area. I'll get back to it at some point, but "Time Marches On". I think you're too young know the significance of that (lol). Jack

KEVIN........ No, the QRH reads "OFF". I really do appreciate the time your spending on this with me. I double checked the departing runway and it's been changed from 13 to 31. I don't see how that could make any appreciable difference, but who knows. I've got to work on another project for the rest of today, but I'll be back at it tomorrow. By the way, I checked Navigraph to see if they updated PMDG data as they had done the past two cycles. Nothing changed. Jack

Kyle......... Yes, I select the departing/arrival runway(s) just after I enter the departing and arrival airports info, usually as a company route. Jack

Kyle.......... Tried that, but result was exactly the same - no v speeds and partial altitudes in the legs area. There are no sids for Regina, but there is a star for Edmonton. Jack

Kyle.......... I can't think of what I may have overlooked. It seems that the event occurs only when Regina or Edmonton are used. I'd send a pic of the PERF INT, but I can't see any way to attach one here. Yes, I flew the tutorials when the aircraft was released, but it has been quite a while ago. I've been flying the 737 NGX pretty constantly since then, with very few bugs. Jack

Tony/Kyle............ Well, I changed to metric but the same thing happened. No v speed, but partial altitudes in legs area. Then I loaded a flight plan from Vancouver to Edmonton, using the same method(s) as I did from Regina to Edmonton. Everything worked perfectly. I think I'll try Edmonton to Regina and what happens. I'll also try Regina to another airport rather than Edmonton and see what happens in that instance. This getting to be quite a mystery. Jack

Tony/Kyle...... I'm sorry if anyone took offense. That was meant to be just a "tongue in cheek" remark. Nothing more. I should have added an (lol) after that sentence. Tony, I really do appreciate your offer of help. Jack Kyle........... That an interesting bit of news. I've been flying in Canada fairly frequently for years and never had that problem pop up. It's possible that when it didn't I hadn't converted to the Imperial system. I'll give that a try. Jack

Tony.......... Mostly because of my age, I use pounds and other Imperial measurements and have those checked off. The metric measurements, to me, have no relevance in my life. A few years ago, it was tried in the U.S., but after a couple of years, the Government gave up trying to force the issue and we are where we are. Please, those of you who are metric crusaders, don't use this as a new front. Jack

Well, I decided to try again. Still no V speeds but partial altitudes in the legs area. I decided to "fake" the v speeds and off I went. About five minutes into the flight, all of the altitudes "popped up" in the legs area and I had an uneventful rest of the flight to a perfect autoland. Just for the record, the flight was from Regina,Saskatchewan to Calgary, Alberta. Is it possible that the Regina airport runways could be the culprit? Could a livery (as far fetched as that sounds)? Earlier, as a test I used a flight plan from Calgary to Seattle and everything worked perfectly. Jack Jack

Thanks to all of you who responded. Here's what's selected: IRS is aligned, perf entries done and executed, departure and ariival runways selected with sids and stars as necessary. Still no v speeds but altitudes were there on legs page. Next, a used a 777-200 using the same flight plan, same airports etc. Everything was normal. Then used a different flight plan and different livery with the 737NGX. V speeds showed up but only altitudes after the star area showed up in the legs page. I'm beginning to wonder if something has gone bad within the 737 data and needs a delete and re-installation of the aircraft. Jack

I've been flying the 777 ever since the 200 came out with no problems. A couple of days ago, I decided to go back to the 737 NGX for a couple of flights. What I found was that no matter what flight plans (Flight Sim Commander) I used or re did, I'm not able to show the altitude read outs (in the legs area) and the FMC continually says "V speeds not available". My first guess was that I'd forgotten something I needed but darned if I can find what that might be. It's tough getting old! I'm hoping that someone has had this problem and could help me get a complete flight plan into the FMC. Jack Fentress

Oliver........... That explains it. I was just to fast. Sorry for any confusion guys. Jack

Kyle/Jared........ Thanks guys for the quick and helpful response. I figured that the answer was something I didn't read, overlooked or just plain didn't understand. Now that you two have confirmed that it was the last one, I'll give it a go. One thing though. I see that my post never made it to forum itself to be read. What's that all about? Not a complaint, but just curious. Thanks again. Jack

Not a big thing, but I've noticed that in the area where we see "apu running, no smoking etc" the symbol FMC is showing up on the 300. Is there some significance to this that I've somehow overlooked? Jack Fentress

Mike................. I'm back in business. What I was doing was not looking beyond "Camera Definition.003" to find "Camera Definition.3". Using "HotKeySelect=2" put the panel just where I use it - F 10. My mind is turning into a sieve!. Thanks very much for the help. I couldn't have done it without you. Jack Mike....... I also forgot to thank you for the use of the "full cockpit/jump seat view". Really looks good. Jack

Mike........ Thanks for the reply. I looked in the SP 1, 777-200 aircraft config and the panel config and I no longer see any camera definition 3 relating to Overhead Lower Panel in either location. Has something changed with SP 1 which prevents that? As I recall, it was a very simple procedure using the "hotkey.etc" as you indicated. Surely, I've missed something. Jack

I had F 10 assigned to bring up the upper panel, but with SP 1 that's gone. Problem is, I've forgotten how I did it. I know it was pretty simple and I think was connected to the aircraft or the panel config file. Could anyone help me out on this? I'll write it down this time! Jack Fentress

Kyle.......... Thanks for the quick response even though it appears you're very busy today. That pretty much explains everything for me. Now, I can just sit back (theoretically) and wait for SP 1. By the way, any idea how long R.R.'s recovery might take? Jack

Kyle............. While we're waiting for SP 1, I'm still kind of curious about a couple of things. 1. Using your 1L and 1R, request etc., when I hit execute, actually, nothing showed up. No legs. Nothing. Why? 2. After adding sids and stars to the flight plan and following the same steps as in 1, the sids and stars showed up but no other waypoints. I manually added them to see if it would work that way and it did. Why? Since you and Ryan have indicated that SP 1 would handle this issue, I'm just curious about the difference in 1 and 2. No hurry on this. Just whenever you've got the time. Jack