PrestonIV

I just had this issue again where I could not enter my information into the Microsoft login box. I unplugged the mini usb connections to both my Honeycomb yoke and throttle quadrants and alas was able to enter information into the box. I then plugged them back in and continued to sign into the flight simulator and everything worked fine. How bizarre....

ROTFL........No wonder its all washed out. Went back and read some earlier post looking for a good preset, and its on by default. No wonder it looked all washed out when I "Enabled it"....HAHAHA....Im an idiot :Doh:

Thanks Dave, that did the trick, now I see a difference. It was naming the preset inside the sweetfx_preset text file that was getting me. I used the torchlight2 beta just for testing, but it only made it all lighter and hazy, but at least it did something. :dance: Now I just have to find the perfect balance preset.

If you can take a look at post #261, eight posts above, I have a screenshot of what I copied into my main FSX folder. Is that what it should have looked like? To test it, I tried Cartoon mode, Sepia mode, Splitscreen, etc in the settings txt....there were no changes at all, nothing. ^ Maybe this is where Im hanging up. Thanks for the heads up on Shade and SweetFX :Peace:

I love the MD-11 and have no problems at all with the way the cockpit looks as it is now. To me, at night especially, it looks quite realistic to me, and Im happy with the sounds as well. Im really looking forward to version 2 of the 747-400 though. The NGX gets the most usage as Im most familiar with it, love the JS41 but its complicated, and like the 747 but its VC is WAY outdated. Im holding out for 747 V.2

I tried everything to no avail, but couldn't get it to work. I'd bet it has something to do with Shade for FSX. If anyone here has Shade installed along with SweetFX, Id like to hear how they got it working.

Will try that next. I did read the log file and I had a BackBufferFailed line in there. I am running Shade already and have read they work together. I will try the Inspector settings first, then look at shade.

I just installed this but see no difference at all. I had to bind my Insert key to it as I have no Scroll Lock key, but still nothing. I copied and pasted 9 files along with the folder SweetFX into my main FSX folder. That sound right? Here are the folders I copied over:

Same with me. If I start from cold and dark and run Pre-Flight everything powers up but the guages wont display current info. The Primary Flight Display and Navigation Display initialize when power comes on, but there is little info with everything highlited in Yellow. NO TCAS in yellow, no route showing in Nav Display, no airspeed and relevant info showing. Then I get the SDK errors, only sometimes however. If I start on runway with power, everything is fine. I did one flight each two nights in a row, and on the third night this stuff started happening. I uninstalled both 737 ngx and FS2Crew and reinstalled and it still happens. Weird as I had not installed anything during that period. I will have to try cold and dark setup myself without FS2Crew and see if it still happens to try and narrow it down. I have not tried that yet.

Ive found that sometimes FS2Crew for some reason will quit responding, even if your in the correct mode, or flow. This occasionally happens with saved flights. If this happens, I found that turning Voice off, then back on in the main panel restarts FS2Crew. I dont know if that was by design, or if it just works that way by chance. But if it stops responding, try turning the Voice button off, then on again. Wait a few seconds, then cycle back to the flow you need.

With the exception of the J41!......Ive had that plane a about a year and a half and have NEVER, I repeat, NEVER been able to successfully configure, takeoff, fly a route, and land until I purchased the voice control for the J41. If it werent for FS2Crew J41 Voice I would probably still be fighting it. What a load that takes off the user. NGX is till my favorite commercial aircraft, but the J41 is gonna come close now for overall favorites thanks to the FS2Crew for it.

For Tutorial # 2, you would start the Preflight at the end of page 9, or begining of page 10. If its not completely cold and dark, then after loading the Tutorial Flight load the cld/drk panel state and run Preflight. FS2Crew Preflight will take to you around page 79-80 of the PMDG tutorial # 2 when "Before Start" begins for both PMDG and FS2Crew.

Keep in mind you can still get the "Flaps Up" no matter what the panel state is. You have to double check the COMM frequency if it happens and make sure its not on 121.65. Some airports use that frequency for Ground communications, like KLAX. As soon as you request a departure, it switches the panel to that "bug" frequency.

BWAHAHAHAHA! :( NO! :( How could I have missed that in like, oh I dont know, 30 tries! I think that will clear up my last problem. Off to test.Thanks Andreas

Another thing to do thats useful, is go to somewhere like Edwards Air Force Base and program a big loop into the FMC. Then take off and practice using various flight commands with the FO like setting the altitude, speed, heading, flaps, etc. Then you have plenty of room to practice the landing flows and takeoff again.

It is surprising how many people dont have the SP1c update, even the ones that THOUGHT they had it. I read posts where people updated thinking it converted to the newest SP, only to find out that for some odd reason it was still SP1b. Check the "about" button in the FMC for the version. Also, I had my speakers turned up just a tad to much on one flight, and the FO went crazy with all my commands. I literally reduced volume one notch and it cleared everything up.However, I still cant get pushback no matter what. The ground crew responds with "All hatches and doors closed, bypass inserted, release parking brakes please", I release the brakes and nothing ever happens after that. Still trying to figure that one out, its got to be a flow error on my part somehow.

I did not know this. I tried the autothrottle off command last night for the first time last night at touchdown to VHHX (Kai Tak). Then noticed the plane wasnt slowing down. I remember hearing the FO say "Autothrottle off" and was wondering why it was on, thought it was something I did wrong. Good to know, and glad its been sorted via the SP.

The memory is key on an older system. Im running a Q9650 with a GTX 260 BUT with 8 megs of ram in Windows 7 64. FSX really needs at least 4 megs min to avoid OOM errors, and you need 64 bit to take advantage of the larger memory. I had OOM issues to when I was on Vista 64 with 4 megs, then upgraded to 8 and NOT A SINGLE ONE SINCE. Then I upgraded to Win 7 and FSX has never run better even on my old system. I can get 15+ fps in VC in NGX at Orbx Seattle...with night lighting! LOL

I always start cold and dark so I dont know if this is the answer, but the flow has to be in the corresponding condition for which your plane is. Is the plane powered? If so, click on the arrows on the FS2Crew panel until it says "Before Start" [ if engines not running ] or "Before Taxi" [ if engines are running ] then follow the flows for that section. If your in the wrong flow for a particular aircraft state, the FO will never respond to commands.

Brian,Just wanted to update and tell you Im downloading the JetStream Voice version as I type! :(

+1 Julio is VERY prompt with PM's and emails. Wanted to say "Thanks Julio!" in public :(

Just wanted to give some MAYBE useful information. By now everyone probably knows about the de-ice comms freq prompting the continuous "FLAPS UP" by the FO, and to avoid that channel. Well to my surprise, while preparing my flight from KLAX to KLAS I got the ole "FLAPS UP" loop from the FO again after requesting taxi clearance. Its seems KLAX uses 121.65 for their ground frequency. So remember, request whatever clearance you need, then switch off that frequency and continue with your flight prep at Los Angeles.

Yep..Thats the exact section. I did it again just now at KLAS and got it to work. This time after calling "Securing the aircraft please", I waited for the FO to click 3-4 things then I called "Securing the aircraft checklist and he did his flows per my request. When I printed this on release day from the online manual via the Config Manager, the second line under SECURE said:2.After FO completes the Securing Aircraft procedure, called "SECURING AIRCRAFT CHECKLIST". [ note "called" instead of "call" ]Did this get revised since release day? That "ed" at the end of "call" made a world of difference.Love your product btw..... I already had it for the default 737 and PMDG 747, now this is making my flying more streamlined and professional. I think I may go ahead and purchase it for the PMDG JS41 as I cant fly that thing for the life of me, its such a cool aircraft.

I called for the "Secure the aircraft please" per the manual stated flow. The manual says the FO completes the securing aircraft checklist, then HE reads it. But that never happens. Power source at the gate, you know, I dont think Ive ever thought about that. What SHOULD it be for that procedure? LOL

I think Ian is asking how to load the cold and dark panel state by default, not switch to it after loading the plane the first time. I too have been tring to figure this out. By default the PMDG 737 loads with systems running. Is there a way to set it up so that no matter where you are, the first time its loaded into FSX it loads in the cold and dard state by default?