NedH

It says version 07JAN11.

I think Jason actually did try to pick a date with extremely bad weather.

I have no proprietary information but if you think it through it has to happen in a year to 18 months. It's not too difficult software-wise to overlay an HUD on the FSX exterior view. It's not trivial but an advanced graphics coder could do it. Also it's pretty sexy as far as getting marketing points. And it's got a wide open field with very little competition on non-PMDG aircraft.

Someday soon this will be available in PMDG's HUD and for any aircraft using FSX via an add-on.

I don't think FCOM is saying that the NAV radios are automatically tuned to the approach in the FMC. Ii is saying that the aircraft's position is obtained in some cases from DME radios which are tuned to the strongest signal which may or may not be the ILS transmitter. The referenced FCOM pages don't say that the NAV radios are automatically tuned.

In FSX when you assign a button to a function, there is a slider on the right hand side that allows you to make the button action be repeating.

I've done lots of autolands with neither of the EFIS selections set to APP. Actually I almost never set the EFIS to APP mode.

My two cents worth: Adding CDU data to the SDK input and output functionality will be very useful. However I seriously doubt that PMDG will be doing this so that it will be available as USB signals. That would require the SDK contain a USB driver which is a formidable task. Also a USB driver is outside of what I think PMDG's business should be. They have excellent aircraft physics engines and cockpit and external views. And they have provided "hooks" to the plane's data with the SDK. It's up to others to interface the SDK data to hardware, e.g. via a USB driver.

No progress yet because I haven't received my Sismo hardware. It's about 3-4 weeks away. I'm getting the DST casing and most of the instruments and gauges except for a few FO things and clocks. I imagine it's going to be a trial and error process but I plan on using FSUIPC and there's a pretty active help community on their forum. Lets stay in touch as we go thru this together maybe we can help ease the pain.

Has anyone had experience in connecting any of the Sismo hardware using the PMDG SDK and FSUIPC? I'm getting some Sismo hardware in a few weeks and want to start thinking about the software configurations and could use any suggestions that others have who have been down that path.

I've done this several times and it never works very well. But on the other hand what do you have to loose? If you are going to get a larger HD, might as well try to clone the old one, if it doesn't work then you can re-install. Many hard drive manufacturers have utility programs on their web sites that do the cloning.

It isn't in the start menu. It's in a subfolder, I think documentation

Cycle hidden hides that particular view when you cycle thru the views with the A key

I believe there is a C++ VS2010 project in the PMDG SDK. Also this link may help http://forum.simflight.com/topic/71035-pmdg-ngx-sdk/page__st__80

When did I post that they will release EFB in 777? I said "newer aircraft" and this was said at Aerosoft Convention. by PMDG CEO in Munich in late March.

The EFB probably will be available sooner than later. They are building it into their newer aircraft and claim that once tested it can easily be retrofitted to the 737

I saw in the manuals where the gear warning horn can be turned off. But what causes the warning on a normal approach? The warning gets mentioned in the manuals as occuring with excessive flaps during a go around.I can't find any mention of a warning on approach.

I'm flying approach on LOC and gear is up. When G/S is captured, I lower flaps to 15 and a warning sound starts buzzing? It stops as soon as I start gear down. Is this simply a warning to put gear down?And more importantly, where is this explained? I've looked in both FCOMs and the FCTM and can't find anything about it.The manuals are great for reading thru but awful for finding something specific even using the PDFs and searching is problematic.

For all those who posted answers, many thanks.More than enough info to get me moving in the right direction. I'm beginning to see in my mind how I will start.But I'm still concerned about how much I can load my PC that's hosting FSX. I plan for that PC to display outside view on two or three monitors. And I want to display PFD, ND, and Upper DU, Lower, F/O displays on multiple monitors. So should I try to have all these monitors on the main PC or can I safely move the PFD, ND, and other DUs to a separate networked computer(s)?I guess what I'm asking is how do folks handle the 6 large displays on the MIP and lower panel?Maybe the answer to that is in the several sites that were suggested.Thanks again. This is a great forum.

I am about to make the plunge into building a simpit with FSX and 737NGX. And I have some simple but fundamental questions.I'm a software developer with years of coding in most languages and I'm an experienced hardware builder. I'm also a pilot (just not current). So I know how to write software and build things. I just don't know the best ways of hooking things together. And how well they work in practice.So question 1: How does the SDK work? Will the 737 SDK allow me to "get" to all the events and devices displayed on screen. Does the SDK work on a polling or event system? (I've seen some sim SDKs that use some very old-fashioned methods like polling offsets.) Will the PMDG SDK give access to FSX stuff or will I have to get that separately? And since the SDK isn't out yet I'm asking for best guesses based on how PMDG's other SDKs work.Question 2: Connecting PC's: Should I use sockets, UDP, HTTP, or some form of client-server configuration. I guess that depends on the hardware. But any tips like: "don't use IP for displays--it's too slow" would be helpful.Question 3: Is it likely that the SDK will have connectivity to FSUIPC or will the connectivity be something else? Will I be able to write code that can connect directly to the SDK??Switches, lights, levers, I assume can be put on separate PCs because a little latency with those is OK. But is it wise to put things like PFD & ND on networked PCs or better to keep them on the master PC.Finally I'd appreciate if anyone can point me to a web site that discusses networked pros and cons and tips and tricks. There is a lot on the web about home-built sims but not too much detail about the fundamentals. I don't want to get down the road with one methodology and find out that it doesn't work well.I'm asking a lot but I want to have a pretty good picture of the forest before I plunge into the trees. (Bad metaphore for a flying forum!)Thanks for any help.

That isn't the way mine works. As stated in my original post, when I run FSX with my default flight, the NGX Panel State is the one from the default flight not the Startup Panel State displayed in the FMC.So I ask again when does Startup Panel State run?

I'm confused about the inconsistency in the Introduction pdf manual about Startup State.The manual says:When you save a filght in FSX the NGX app will intercept the save operation and save the FSX settings and separately the Panel State.But the manual also says that the Startup State will be used as the configuration each time you launch the simulator.It can't be both ways!When I start FSX with my default flight, the Panel State that is loaded is the one that I used with the last saved flight. So when would the Startup State ever load?

Where does the "key" come from--during the install??

I just downloaded 737NGX and am looking forward to a weekend of play.I'm wondering if there's a reason to buy the Extended Download Service versus just making a backup copy of the downloaded zip file or the install EXE.If my PC dies or I need to reformat, can't I just re-install it from my backup?

Can I install 737NGX on a desktop and a laptop as long as I'm the only user and will always be flying only one PC at a time.