Falcon900flyer

Jay, I'm not sure if my previous post went through, so I'll try to type the same thing again: I just download the 737NGX (800/900) and am having the same black screen issue that you and Oscar described, except that mine happens from changing views. I have not tried the 4x or 8x speed acceleration. My computer is really fast (as shown in my signature block) so it's not an issue of whether or not I have enough "horsepower" to run 737NGX. In a previous post, you mentioned that you "uninstalled FSX from the Program Files directory and re-installed outside Program Files to C:FSX". How exactly did you do that? Did you just manually move the FSX folder from the Program Files directory to C: , or did you do a full uninstall and start all over with a fresh re-install to C:?? You also mentioned that you "updated FSX.cfg Graphics parameters (HIGHMEMFX=1 & TEXTURE_MAX_LOAD=4096)" Again, please bear with me as I'm a newbie with this computer stuff, but how exactly did you do that? Where do I find the FSX.cfg Graphics parameters?? I understand that you used ******* Bajote's tweaking tool once you did all the above steps. Have you had any issues since your last post in early March this year?? Any help would be greatly appreciated!! John B. ATP, CFI, CFII, MEI Type Ratings: Dassault Falcon DA50, DA2000 i7-2700K @ 3.5GHz (overclocked 20%), Asus P8Z68-V Pro, Corsair Vengeance 16GB (4x4GB) DDR3 1600, nVidia GTX580 1.5GHz Superclocked, 240GB Kingston HyperX SSD, Asetek 550LC 120MM Cooler, Thermaltake TR2 RX-850 Power Supply, Coolermaster HAF 912 Mid Tower. Windows 7 Pro 64 FSX Deluxe SP2 PMDG 737 NGX, Ultimate Traffic 2 Saitek Pro Flight Yoke and throttle quadrant, CH Pro Pedals Samsung 26" LCD

Thanks for your post, FP...I will recalibrate! John

Greetings, Having some real experience (about 500 hours PIC) in a King Air 200, I thought I'd share some findings that may interest people. Chances are that these issues may have already been addressed by other posts, and in that regard I apologize for being repetitive. Ok, here's what I saw: 1. This aircraft requires a ridiculous amount of power just to get it rolling on the taxiway. My power levers are almost at the halfway position! In real life (speaking from a King Air 200 point-of-view), the aircraft should start rolling and slowly accelerate in idle power alone. In real-life, I'd have to jockey the power levers between idle and beta to keep a reasonable taxi speed. I'm sure this is the same in the real C90B. 2. When either in cruise or after touchdown and moving the power levers to idle, the aircraft decelerates but it does so way too slowly. Once those 4 bladed props go to flat pitch, the aircraft should decelerate significantly (That is again, from a BE20 point-of-view. I have a hard time believing that the C90B would be any different.) 3. There is too much of a lag when bringing up the power levers from idle. Yes, there is lag, but not to the extent shown in this sim. Also, the power takes way too long to stabilize once the power levers are brought up. Don't get me wrong, this is a wonderful aircraft that Carenado has produced, but they could make it so much better if these issues were addressed. Just my 2 cents... John

Thanks Jacoba! Will give that a shot...

Greetings, I purchased and downloaded the C90B early this week and I'm having the following problems with it: 1. I can't get the Heading Bug to move left or right. It will sync just fine to the current heading of the aircraft, but trying to move it left or right does nothing. 2. I can't get the Course Knob to change the course in the EHSI. Trying to rotate the knob left and right does nothing. 3. I can't change the altimeter setting at all! Trying to rotate the knob left or right does nothing. I'm not sure if these issues have been experienced by other users, but I can say that these 3 things have 1 thing in common--I cannot rotate the knobs to do ANYTHING! If anyone out there has some suggestions, please chime in. Thank you in advance, John

Thanks VLJ

Greetings, After uninstalling and reinstalling FSX, I've tried to reinstall 737 NGX. I, for the life of me, cannot figure out how to reinstall this thing! I referenced my original email with the order and I clicked the URL and of course, it didn't work (apparently it's only good for 10 days). Where is the link to reinstall the 737 NGX?? The website is as clear as mud in accomplishing this! Any help would be greatly appreciated! Thank you in advance, John

Greetings,I left out the aircraft was lifted up by crane, placed back on pavement,and tugged back to the maintenance hangar on its own landing gear. I was told that there is "minimal" damage to the aircraft. I would've figured at the very least, the #1 engine would need a complete tear-down and inspection, perhaps a new radome, and new nosegear doors. John

Greetings,I just spoke with a friend of mine who's a Lead Mechanic for Delta in ATL. He told me that the news media was totally incorrect in saying the "brakes failed" on the airplane. What really happened was that the parking brake was set and the throttles were advanced to full power. (Apparently, the aircraft was in maintenance for a scheduled fan lube. The work was completed and the aircraft taxiied out to the run-up pad for leak-check, etc). Once the maintenance tech(s) noticed they were moving, they retarded the throttles to idle. By then, they had already skidded over 300' and we all saw what the end result was. At the time of the incident, the ramp was wet and the aircraft was of course, very lightly loaded. The aircraft was not chocked (as they normally don't chock aircraft for an engine run-up, but perhaps they may start now). The FAA was on scene after the incident and noticed the tires left skid marks for the full distance it travelled. (Since the parking brake was set, anti-skid is not available). The skid marks started out dark black then went to a lighter black color, followed by dark black. The FAA said that the reason for the lighter black color was apparently the aircraft went fast enough to put some load on the wings and take some weight off the wheels. The FAA concluded that the aircraft hydroplaned. (I find this interesting because the aircraft would have to be travelling at a high speed for this to happen. Hydroplane speed is calculated as 9 * the square root of the tire pressure. Perhaps the aircraft taxiied through grease or oil or jet fuel and coupled with the wet ramp, produced a very slick condition for the aircraft to skid). Guess that just goes to show you how much power those CFM's put out! Just my .02 worth...John

Greetings,Just when I thought I had all the issues worked out of my PMDG 737 NGX, they come back again. Here's what happened:I flew the tutorial from EGKK-EHAM with the 2D cockpit and everything was fine from start to, well, almost finish. I landed ok, selected a 60 sec Replay of my landing, and went to the external view of the aircraft. After selecting the external view, NO aircraft was visible (its full shadow on the ground was), NO runway was visible from the 2D cockpit view (only the PAPIs on the left side were visible). Additionally, the cockpit displays were frozen to show 45 KIAS, 0 feet MSL, 27.3% N1, -4 feet Radio Altimeter, command bars slightly above and to the right of straight and level. I selected Replay again (after writing down everything that I just described) and I had a black screen with a white 6 inch horizontal band with brown terrain visual on the top 1 inch of the white band. I had full sound throughout the replay, and because of the black screen covering most of my display, I had no Flightsim tool bar on the top. I hit the ESC key, exited out of FSX and got the "Fatal Error Occured" message. The Warning Stop SIgn also appeared saying "Flightsim did not shutdown properly the last time you ran it. You should reboot the computer." In addition to those, I also got the dreaded SmartAssembly Troubleshooting box to include the message "This feature requires that {smartassembly} is available on this computer. I first got the Smartassembly message a week ago and I downloaded a 14 day trial of Smartassembly to correct the error. Everything was fine for a few days, but the message came back today. BTW, I am STILL within the trial period of Smartassembly. After researching Smartass issue on FSX, I downloaded Visual Basic C++ 2008 per someone's advice. I will let you know if that fixed the problem.Has anyone else experienced this same occurence? I was beginning to think that it was an issue with either UT2 or PMDG 737 NGX? Not sure what to think...any thoughts would be greatly appreciated!! Thanks,John

Dennis,I do not have EZCA.

Greetings,First off, let me apologize in case this topic has been covered previously. I searched the forum for topics related to mine but didn't find exactly what I was experiencing. Ok, now here's what's going on:A few days ago I purchased the PMDG 737NGX 800/900 and when I ran it for the first time, everything was working fine and appeared normal with the 2D panel (my Track IR 5 was not set up yet). Yesterday was the second time that I ran it and the problems started. I selected the aircraft, put it on the departure end of Rwy 4R at KEWR, daytime, with real world weather, and 2D cockpit. As aircraft was lined up and waiting, I was inputing data into the FMC. I selected external view to look over the beautiful airplane, then went back to 2D cockpit. At this point, it appeared that the airplane was not at KEWR anymore and was on some snowed-over grassy area with some mountains in the background. I went back to external view and the aircraft was missing various textures, ie, landing gear struts, engine fans, tail cones of engines. I then went back to 2D cockpit and only to find that only some of the cockpit textures were there--there was no PFD, MFD, and lots of other textures missing. Additionally, the outside textures (as viewed from the cockpit) have turned 45 degrees clockwise. I then tried to select a default airplane, but the screen went black, there was sound for that airplane, and cycling through the views (to include cockpit view) came up black also. This morning, I figured I'd give it another go and try to troubleshoot what was wrong. At first, the aircraft performed like it should. Thinking that it was just some gremlins that reside in my computer, I shut it down for a bit. This afternoon I came back to try the Track IR with it and everything started fine. With engines running at the gate, I pushed back. At break release, the aircraft zoomed across the ramp without the pushback tug, and the only external aircraft textures were the grey cockpit windows, passenger windows, nav lights, anti collision beacons, and some antennas. The aircraft was casting a full shadow of itself on the ground, although no wings, tail, engines, etc were visible.I have the latest drivers on everything (this is a 2 week old computer and I updated every driver) and my system specs are in my signature block. Please help, as I'd really like to fly this amazing aircraft!! Thank you!!John