Crankpin

Hmm, while I don't have the overheads I do have MCP, EFIS and CDU from Opencockpits and been very happy with them. Software/drivers specific to and for the PMDG 737/777 come from http://flightsim4fun.com/ The software is a direct link to the PMDG SDK and makes the whole process very easy and is well supported in my experience.

ooops

The livery availability thread is here, the best place for requests http://forum.avsim.net/topic/340475-pmdg-737ngx-livery-availability/page-313 all 313 pages of it The AVSIM library has 722 NGX repaints 26 of which answer to being a BBJ http://library.avsim.net/search.php?SearchTerm=NGX+BBJ&CatID=root&Go=Search All of these are free, we aren't allowed to charge for repaints, it's against the EULA

Hi Davit To do liveries for the NGX you need a serious paint software preferably Adobe's Photoshop. Then Download from the PMDG website Downloads/Paint Kits the Paint Kit for the NGX 800/900 and/or 600/700. In the paint kit files you will find a .pdf document that will get you started.

Here's something/ a theory, that actually makes sense http://www.wired.com/autopia/2014/03/mh370-electrical-fire/

First place I'd look is OC's forums, how's your Spanish ? But sry I don't own either of those so ummm.

Oh no, I use the MCP especially, with all sorts of aircraft. Basically you can use it to control the auto pilot functions of pretty much most aircraft. From my 2nd fav seat, the Flight1 BN2 to whatever. Most aircraft, in particular the default FSX planes and most freeware just use the generic FSX keycodes and there's a generic sioc script file that you'll have got with your hardware that you can use for them. It's simply a matter of changing the CONFIG_FILE = setting in sioc.ini to point to the 'generic' .ssi/txt sioc file before you fire up the hardware. More sophisticated payware is a bit trickier simply because there are more functions and controls than the basic FSX auto pilot abilities, but with a bit of google, the OC forums, and getting to understand the concepts of sioc scripting it'll work at least to some extent with just about anything.

Hey that's good klamal. Yes the OC 'lua scripts' were just earlier iterations of Roar's development process which led in the end to OCP4NGX. Having 'all' the files in one folder makes for simpler pathing in the config files ... but a messier main folder. Which is no issue if you only use the hardware for one aircraft - the NGX. If you use the hardware with multiple aircraft having the multiple sioc scripts, one for each aircraft, in a separate folder makes them easier to find and tinker with, that's the only difference.

Hi klamal I have the MCP v2 which is the difference in the MASTER line. Put a close bracket ] at the end of the [** line, that'll help. or better, make it [MASTERS] it's just the section name. When you can get the roar stuff to work that will be better than the lua files overall, so pursue that. The MASTER lines and the rest of the sioc.ini is needed using OCP4NGX or anything else. My whole sioc.ini is below [sIOC] IOCP_port=8092 IOCP_timeout=4000 Minimized=Yes toggle_delay=20 CONFIG_FILE=.\OCP4NGX_V2.ssi [iOCARDS MODULE] IOCard_disable=No IOCard_LPT=No [FSUIPC MODULE] FSUipcdisable=No FSUipcRefresh=60 [iOCP CLIENTS MODULES] IOCPini_delay= 3000 IOCPclient0_disable=no IOCPclient0_host=localhost IOCPclient0_port=8099 IOCPclient1_disable=yes IOCPclient1_host=localhost IOCPclient1_port=8092 [sOUND MODULE] Sound_disable=Yes Volume=100 [MASTERS] MASTER=5,5,1,84 MASTER=7,7,1,86

Hi klamal Good on you, you made the right choice for the hardware Now, what might be wrong - could be a number of things, I'll mention some that tripped me along the way. And Roar has his own support forum now at http://www.flightsim4fun.com/Forum/ Both MCP and EFIS each need their own 5v power supply. For me the automatic setup never gets the text of the [MASTER] section of the sioc.ini correct, for me it should read as ; MASTER=5,5,1,84 MASTER=7,7,1,86 Those last numbers of each line will be different for you. Sioc.ini file must be in the main SIOC folder wherever it is and whatever it's called. Near the top of the sioc.ini file there's an entry CONFIG_FILE= , for me it's CONFIG_FILE=.\OCP4NGX_V2.ssi it needs to be a 'relative path' to your '.ssi' file. Last but not least, with everything turned on, when you load into the NGX wait until the NGX initialisation countdown has completed then on the MCP hardware press the C/O button (near the A/T ARM switch). If you are 'cold and dark' not much may appear to happen until you power up the aircraft. One or more of those thing may have given you an 'aaah ha' moment, which would be good, but maybe not, getting it all to work the first time is bit of a juggling act, but once you start to understand how all the bits of software and hardware work together it's a synch. If you are still getting no joy, go to Roar's support forum , he is very helpful and will 'get it working' for you probably by writing your sioc.ini for you. In desperation I could lead you though it on TeamSpeak3 or such. Good Luck John

I'd add my recommendation to roarkr's. I have the OC EFIS, MCP and CDU, all work well and accurately and roarkr's software makes the whole deal pretty easy ... very easy after the setup phase.

Hi Mitch While I know better than to say 'never' especially when dealing with anything software related, I'd say it's really really unlikely that it's addon liveries themselves that's causing the issue, especially if it's official pmdg ones. Couple of other questions that may help identify whats happening. When you first drop into the cockpit, do you see the '20 second Initialisation countdown' and don't touch anything while that's happening ? (Making sure the aircraft initialises correctly) When you first drop into the cockpit, are you in VC mode and not 2D mode ? (Loading in 2D mode can cause similar issues, you should load in VC mode) The (any of them) standard pmdg livery is not your default aircraft when FSX loads is it ? (Changing from one livery to another after using the first can/will cause issues. Only load/use one livery per FSX session and don't have the NGX as your default aircraft) [Touchy question, don't be offended] This is a legit install ? (Copy protection causes similar issues with pirated downloads... so I've heard) What, if any, other hardware do you have plugged in, joysticks, headsets, yokes, anything ? Cheers John

Hi Mitch It may/probably has nothing to do with it, but I had a similar issue when I had no sound device connected. I use a USB headset and have the computer's onboard sound device disabled. If I didn't plug in my headset before starting FSX I'd see what you are seeing. As long as the liveries you are getting are from PMDG or AVSIM library and use the livery manager for install they 'shouldn't' be causing the issue. Good Luck John

hmm think I'd still go for FSX Deluxe edition as it comes with the FSX SDK which may be useful later. System specs are moooor than adequate for FSX other than the SSD IF you go overboard with addon sceneries = bad habit of mine.

BA 38. Obviously I have no clue either, everything is speculation at this point, but the similarities are striking, long flight, steep descent, no power at final, short landing... me too. Sometimes though building a motorway just shifts the traffic jam to the next/another point. Hmm we'll see eh. I'm not trying to make an argument for anything, it just struck me as a " I've seen this before " moment.