cannonplug

¡Estupenda la serie, Jaime! Mil gracias.

Did you push the fire handle back in?

Are you by chance running MyTraffic 6.0a? If so, take a look at this thread: http://forum.simflight.com/topic/80955-getting-ntdlldll-crashes-consistently-after-mt60a-install/

The "altimeter setting" nag is RAAS talking to you. I think it defaults to a transition altitude/level of 10000, so if you're flying in the US, you'll hear the warning between 10000 and 18000. You need to go into the RAAS settings to set the transition level or, as I've done, just disable the warning altogether.

Hello all, Now that Swiss has taken delivery of its first 777, I'm wondering whether there are any insiders in our forum who might be able to let us know what the different configuration options are on this airplane. Thanks! Cheers,

The hat switch (sorry, should have been two words) is an 8-position switch on many game controllers that quickly lets you pan around the VC. Both FSX and P3d will even assign the "View (pan)" function to the hat switch by default if your controller has one.

The hatswitch on the yoke/joystick for panning around also does the trick quite nicely. That together with the A key soon made me forgot about 2d panels.

We've really strayed from the original topic, so I'll keep it short and just say that I'll do some more troubleshooting on this issue starting tomorrow before I contact support at My Traffic. I'll let you know what I find.

Bob, Did you by chance recently install the newly released MyTraffic 6a? I've seen reports of this failure elsewhere. And it's happening to me as well.

Do you tune the tower frequency in manually? The few times I've tried this, I've been stuck with the approach controller who never switches me over to tower. Only after landing does it switch me to ground.

I've tried to do this and, unfortunately, it doesn't work. The best I can get is the approach controller, even if I'm lined up on final. After landing, I do get instructions to contact ground. Needless to say, I don't do this anymore. If you don't feel like talking to real people on Vatsim et al., Pro ATC X is doing a fairly good job of things these days. It still needs work, but the developer seems to be quite active, so it does look promising for future improvement. I also liked VoxATC at one time, but it's not P3d v3 compatible and the developer has gone quiet.

Odd... I'm running P3d 3.1 and don't have this issue. The lights illuminate the ground just fine (both landing and taxi), even when I start up during the day (I think. I'll have to do a test to be 100% sure about this). This did not work for me in 3.0, so 3.1 was definitely the fix. I didn't do a complete installation of 3.1, just the Client and the Content.

This is certainly one way to do this, but if you want to flip the functions in Windows only, go to your Boot Camp Control Panel within Windows (right click the gray diamond in the taskbar). You'll see the same option there under the keyboard tab.

Have you tried holding down the fn key together with F5 and F7? If this works, you can change this setting within Boot Camp so that you don't need to press fn to enable the function keys.

Search the forum. You'll find the answers to all your questions.

If you're using the acceleration feature built into the 777 (right click on the chrono button), you should not be seeing this. The simulation will adapt to the conditions and only accelerate when these are ideal, i.e., flying in a straight line in smooth air). If you're using FSX's (or P3d's) acceleration feature, you'll encounter all kinds of trouble.

You can still save it, just don't make it the default. From the startup screen, just press on "Load" and select your saved file rather than starting a new flight from scratch. Works for me every time.

It's working fine for me, though it took two tries before it connected. Now it works better than it did under v. 3.0

Yes! Just a few days ago in fact: http://www.avsim.com/topic/479882-fs2crew-ngx-reboot-sop1-reference-sheet-2-page-pdf-voice-commands/

I got this callout as well and it is indeed RAAS. The default transition level in RAAS is 10000 ft, so in the U.S. you'll hear the nag when you're between that altitude and the time you press the std button. You'll need to either set the correct transition level in the RAAS settings or simply disable the callout. There are two checkboxes for that.

Add me to the list of Windows 10 proponents. I upgraded from 7 early on in August and it's all been good. Everything just seems to work better (very objective, I know :smile: ). The only minor issue I had was that the display and computer would not go to sleep as long as one of the Saitek controllers (I forget which one) was plugged in. That was resolved with the big Win 10 update a few weeks ago. Also, I didn't do a clean install, just upgraded directly from Win 7. This too didn't seems to cause any problems.

I wanna flip switches. 737 it is! :smile:

I've had a similar issue, but I don't know whether it's exactly the same one because once the engine quits, I don't see any movement whatsoever. Anytime I use an airframe for the very first time, one of the engines quits while on approach and will not restart, even with the engine start switches in FLT What I do then is go to the CDU Maintenance pages and clear all faults and service the airplane. The engine will then relight and the issue will not recur. It's a mystery as to why this happens but at least there's a solution. My setup: NGX with 6/700 expansion on Prepar3d v3. I have service-based failures enabled.

Hi Stefan: There are a few in the Avsim library: I use the one from Sharonna. It's the only one that has the tail number painted on the bottom of the wing. Best,

That's my exact setup. Works fine.