killerbee1958

Now i am not a RW pilot either (i have flown gliders) but if you would wake me up at 3AM in the morning my experience with NGx would make me: 1. establish if enough fuel is onboard to divert 2. If so first climb out of the valley to a safe altitude (using terrain info from ND) using the A/P. 3. call up the fmc to find out if i can divert to a airport with a long enough and cat III equiped runway (probably munich or linate) 4. Establish communication with ground to get assisted by a really good capable 737 instructor 5. Perform an autoland on the best possible runway at munich or linate where atc would make sure all other traffic is out of the way. 6. Start the APU before final 7. Have the aircraft come to a halt on autobrake (i would be able to reverse the engines). 8. Put APU on the bus 9. Shutdown engine 1 and 2. 10. evacuate the passengers i guess. Ground services (firedept etc would be ready at the rw anyway). BTW: i couldn't care less about this talk of Company SOP. We are talking here about a emergency where a non trained individual (me) would be required to put the plane down. THe company cant fire me for not following SOP as i was not hired by them at all. Btw: If everything would be really perfect i might ask tower to taxi to a gate but i guess that would never be allowed. And yes this is dreaming. Never will happen as the 737 is flown by a compliment of two and they even take the precaution still not have the same dinner stuff. My guess is however i could pull off 1-10 and my point is that my sim experience would prevent me from trying to do a circle to land on lowi when possible and know how to get to this alternate solution.

Ryan, although it wasn't me quoting the above i do want to react. Thanks first of all for your clear and to the point answer. I am dissapointed that PMDG is not making it possible to run the screens networked but i do agree this is a business decisions and it is PMDG's right to make this decision. You are absolutely right that you deserve it to make money on your investments. I do wonder however what market there would be if PMDG would make a cockpit edition. I for one would certainly buy it but i also understand this is not a proper marketresearch answer. So with regret but with the utmost respect for your decision i will now go ahead and focus on prosim for my cockpit build. i bought many of your products and stil believe you produce the highest quality plane addon's out here. Perhaps in due time the market for this cockpit builder version is increasing and i hope (and i think you will, but again you rightfully first need to be convinced of a proper roi) PMDG will enter this market when viable. Until then: Thanks for all the hours of fun you delivered to me with your products. regards Fred Koch

Pete, i do not have a website (yet). I am thinking of setting one up but need to study how to do that first. You can find my progress on mycockpit.org http://www.mycockpit.org/forums/where-start-building-home-cockpit/23649-starting-build-737-ngx-cockpit-6.html i am not on facebook or any other social media

Hi Pete, I am on the same journey you are. Building a 737 cockpit. The good news is that with the NGX SDK available you are able to interface switches, annunciators, indicators (brake press, yaw, flaps indicator etc) to the hardware of your choice. For outside view i have choosen to go with a eyefinity triple monitor display (5760x 1080) which is currently working flawlessly and with great performance on my main fsx pc. However, unless things have changed recently, it is not (yet) possible to put your displays (PFD/ND/CDU/EICAS etc) on a separate networked PC with the NGx. For me this is a showstopper as i want to set it up with too many displays to want it to be attached to one single PC (i am buidling a dual seat trainer, so i will need a display for captains PFS/ND, F/O's PFD/ND, Upper eicas, Lower Eicas and then also still 2 times CDU.) I have yet to decide what route to take but for now i believe the best solution is to go for Prosim737 with additional the jetstream fly model. This looks like a nice package at a decent price (lower than the ifly cockpit builders edition and more functionality like instructor station and also more supported hardware and future development). But this package does not work with the PMDG 737NGx as PMDG had to do some very high level direct programming to get this beauty to work the way it does. I do not own the IFly 737 so i can not comment on the flight characterics of this bird. I have used it once at a friends place and couldn't get used to handling the switches and knobs but that is not so important for a cockpit builder of course. Good luck in your research and decisions.

I think you are making a basic mistake here. Prosim and PMDG NGx is not a happy marriage. (in fact to put it even more correctly they are not able to live together). I am building a home cockpit myself and sofar i have learnt that indeed interfacing switches/led's etc (albeit with some limitations) is now possible with the use of the released SDK===> FSUIPC===> interfacecards (with their approriate software programming of course like for instance sioc). There is also a thread here on the NGx forum that shows how to undock windows and place them on different monitors however as far as i have read there is one big limitation. These monitors need to be attached to the same PC you are running FSx and the NGx on. So as long as you are indeed intending to run everything on one computer you should be able to do so. But if you are aiming to have the other screens on a different PC (like i want to do), it seems it is not possible. Other forum attendees, please correct me if i am wrong

that's a deal. Mind you, it will take me at least a few months before i am ready to interface my hardware to ngx so i will be more getting from our cooperation than giving. :Thinking: But still if i have info i will share it either here or through pm

Hi Ned, Have you made any progress on this? I have received my sismo glarewings/shields with captain and fo annunciators and sixpacks and am also very interested to learn how to interface these with the pmdg 737NGx. Have you made a choice yet as to what interfacecards you will be using and do you have confirmation these can be read/written to with the current sdk? Looking forward to your answer

Below this thread you will find often a banner for the jetmax solution, stating it to be working with the pmdg 737NGx. This setup has everyting a cockpit builder is looking for Separate PFD/ND separate EICAs Hardware switches (landing gear, auto brake) Hardware annunciators (landing gear, flaps extension, speedbrake armed, etc) Prebuilt units (MCP?EFIS) They explicitly state in their FAQ this setup works with PMDG 737NGx and this was shortly after the SDK was released. So although i have no knowledge of how this was achieved it goes to show it can be done. I have ordered my mip panels(DST) so i guess i will have to find out how this can be done in a few months from now. I am especially looking for info how to interface the switches and annunciators

I just had another occurance with ICMC just like this. His config worked flawlessly and suddenly it started to fail intermittenly while nothing even changed. I had him connect 5V to the MCP directly (to the power input port on the back) and low and behold everything was working again. So from this thread i really learn that OC modules are very power sensitive and probably best thing to do is find a separate 5 V powersupply and feed the devices by this instead from internal usb power, The usb power is too critical i think. Just my lesson learned. YMMV BTW: OC sells this 5V adapters on their side but if you are building a cockpit you probably have a seperate PC Powersupply installed anyway so might be a good idea to supply the 5V from the 5V PC power rail.

Sven Why do you think ngx does not support wideview? I have not found any thread saying so. Wideview is pretty integrated into fsuipc and fsx probably even doesn't know wideview is running so i do not really see the problem But i will have to test it myself later when i am ready to test this specific setup.

Very interesting topic. I have just ordered the hardware to start building the mip so in a few months i will require this info to i guess :Idea: But why would you want to use orion? as far as i have researched sofar the screens can be undocked and moved to another display or, by using wideview, even to another pc. Would't that serve your goal?

HI Ian., Indeed the 3,5 mm jack is for a direct 5v power supply. OC is selling these separately and it seems in your case it might be advisable to try this as this again looks very much like a lack of power problem. Yoy might be able to find a compatible poweradapter in your old drawer also but not always will the jack be compatible. On the OC site you can find a schedule of how the jack should be wired if you are able to solder a different jack to the wire Good luck

I guess john is the better guy to do this but i would love to help if you just give me some guidance on what to change exactly and where to find the correct input,output numbers for the P&P MCP. great opportunity to learn more about sioc (which i will require anyway i guess once i start putting switches etc in my cockpit build)

Still strange, i use fs2crew also. Does it happen when you, just as a test, do not start fs2crew?

For the record THis is not a failure of the fedex paint. I am flying also all the time with the fedex paint and the tcas (as this is indeed the tcas signalling) only shows up, correctly, on tcas test and on traffic conflict. BTW this image is from tcas test as on a true conflict the arrow will either point upwards or downwards depending on traffic advisory from tcas If they are on constantly during flight this suggest the tcas test is continuously being peformed. Check the tcas switch (the tcas test is performed by pushing the button in the middle of the 4 position tcas switch) If this is on without the switch being pressed please change to another livery and check if the same happens there. If it does this indicate some weird bug. Probably best to first try to reinstall ngx but if it stays on even after re-install i think it is time to submit a support ticket good luck

RoarLooking forward to test it with my mcp and efis module.

I would recommendAS2012 above anything else. (the weather engine and tetures inserted into fsx makes it so much more real)There are more if you can spare the moneyFSC as it helps you generate realistic flight plans that can be inserted directly into the ngx fmcTopcat if you are serious about doing your own load planning (fuel and pax/freight)Avlasoft EFB as it makes flight monitoring and planning a bit easier (but there is a overlap with fsc so you might want to skip fsc and go for avlasoft efb as only flight planning/monitoring tool)fs2crew as it helps you understand the workflows for 737 and also has some fun in ordering the coffee from the flight attendant.Voxatc if you like to improve the atc (but still it is syntehic and the best experience is through online (vatsim/ivao flying)And last but not least (as mentioned) scenery of your favorite places. (Nothing gives as much as an immersion as recognizing the place)good luck

Buy Airhauler as an add-on.It will give you random destinations to fly and it will give you a reason to fly.Your flights will give you rank, money to expand your company and also if you fly in career mode it will give you the satisfaction of growing your mtow with your flight (i take i believe only 100 flights in lighter craft before you can fly the ngx)I have my ngx as one of my planes in airhauler and since then i have never been in need of a destination.Airhauler will generate the flights randomly from the fs database.

Oke this is were i get lost.The fsuipc log looks fine. The keypresses gets properly logged so the interface between sioc and lua is in place(But then i already expected that since you mentioned that the ngx is acting upon keypresses from the MCP)The last thing i can now come up with is a timer issue.When you open the NGXMCP_202_lua file (with wordpad or other wordprocessor) you will find at the bottomevent.timer(100, "run_update")Please put 1000 at the place of the 100. save the Lua and try again.If the MCP still not updates than i am afraid i am at the end of my capabilities.You will need roar to step in here to investigate in that caseBut lets first try this last step

hi valkythat is the lua log again.We now need the fsuipc4.log (that is also the name of the file and it is located in your modules folder of fsx)

ValkyOke this shows we have indeed everyhting in place for it to work but it doesn't.The lua log shows lua being properly called and not terminated for any reason.Please confirm you have just started the flightsim and then closed it again within 2 minutes (as this is what the log shows)Next thing we need to examine now is the fsuipc4.log.Repeat the sequence from above and when you have started sioc after having loaded the ngx just press the n1 switch and turn the v/s dial up two notches and down two notches.Close fsx and sent or copy/paste the fsuipc4.log

valkyoke that looks all allright.One more thing to check.Is there a section[Luafiles] in your fsuipc.ini?And if so (it should be there) is there an entry withXX=NGXMCP_202_PP-202 ? (the xx can be any number)If that all is oke we should be looking at fsuipc logFor that to happen you have to start FSxgo into fsuipcopen the logging tabselect in this tabLua program loggingButtons and key operationssend to console logclick on okenext start siocNext look in the fsx/modules folderThere should be a fileNGXMCP_PP_202.log please sent this file or copy paste it in your reply

thanks for the info gary.Indeed will be a relief. (especally to roar :( )ValkyDid you notice the remark by roar about your [Auto] section?I had this with one of the guys before and indeed the blanks should not be there.Indeed the fsuipc seems registredDon't compare the ifly method of using the mcp with the ngx method. Indeed IFly uses iocp but NGX uses lua.This makes a lot of difference and this is why you need to start sioc.This will make sure you connect through fsuipc instead of iocp.Lvld767 uses yet another method of interacting with the mcp.All this is quite confusing and error prone but until OC delivers their scripts we need to work with the scripts from roar. Which to be honest are working like a charm once you got it to work

ValkyOke so you have the exact same MCP as i have so that one we should be able to get to work.From the pictures i can see you also were able to have all 8's when pushing all on. Can you please confirm? (the picture is a bit unsharp)Also your sioc window looks good so it seems we can safely assume the problem is not with sioc.So off we go to the more difficult part. The fsuipc with lua part.For your information i have it working with fsuipc 4.754. But as a normal debugging approach one should always start with the latest version.Please explain why you can't upgrade to 4.840? One more thing to check here. Please confirm in fsx on the fsuipc add on window that you have a registered version of fsuipc

Oke SimonOn my home screen i was able to see what you mean (the white dots in the nd are very present when viewed on my home screens but not on my work pc)That is the good news. The bad news (for you that is) i do not have that problem at all while i am only at multi sample aa (lowest aa mode). (i even tried to put the ND at very bright to see if that would cause the dots but it doesn't)Please note i have however in the CC put Anti-Aliasing under application control and FSx has AA set at checked only (no possibilty to select a certain level of AA in fsx)For your info i am running three ilyama's e2409hds on a asus eah6970 dcII at a 5760x1080 setting.Hope this helps somewhat in finding what is causing your problem