stevieb

I 'm not disagreeing with you on the logic that's needed, Kyle, as I said earlier: but that isn't how it's actually working. I did try to post a couple of screenshots to illustrate but the forum doesn't allow that. The first screen the installer displays is an invitation "Which version do you wish to install?" and is identical to the 8900 installer's first screen but the check boxes are not there. The only options are Back or Next, both of which lead on to the "Unable to locate Aircraft.cfg for PMDG 737-8900 NGX in FSX:SE" message. Incidentally, if you care to look closely at this message, it's title is "PMDG 777-300ER Expansion for FSX". Something wrong there, I'd say. So, I followed your advice and uninstalled everything, re-downloaded the installers and tried again. The outcome, unsurprisingly, was the same. The only thing I couldn't check was whether there was a registry problem (I wouldn't know where to start and have never used any registry hacking tools anyway). I then went through the process again, but this time I chose to install the 8900 base pack into BOTH sims. Having done that the 6700 expansion went on to install successfully, though it still put up that first screen which doesn't make a lot of sense. As a means to an end, I can live with having the 737 in FSX-SE. It does, however, beg the question as to whether this installer has been thouroughly tested.

Kyle, The base installer allows the 8900 to be installed in one or both, so there would logically need to be a way of optionally installing the 6700 in one or both as well (providing the 8900 is present). However, if the installer is working as you describe, then it's failing to find the location of the base pack under the conditions I've outlined above. Instead, it's simply saying there's no base pack in FSX-SE. Either way it's still a problem.

I've found the same thing happening here. I have both FSX and FSX-SE installed on a new Windows 10 pc, and I'm in the process of transferring my PMDG aircraft from my old pc to this one. So, earlier today I downloaded the latest installers for the base package and the 6700 expansion. It's my intention to install only into FSX for the time being and the 800/900 has been installed and activated successfully. The base installer offered two tick boxes for the two sims, one of which - FSX-SE - I unticked. It's a first-time installation on this pc, it's the latest installer and there are definitely two sims installed. If no-one has any answers I guess I'll have to raise a support ticket. Incidentally, the 777-200LRF Base installer found both sims as well, so it looks like it's just the 6700 expansion that has the problem. Any suggestions would be much appreciated, Thanks Steve

With the "8bit Texture Fix" ticked, the Realair Lancair Legacy's VC instrument panel doesn't display correctly. Here's a screenshot: https://dl.dropboxusercontent.com/u/25038678/Screenshot_1.jpg Please, does anyone have an explanation for this, or, better still, a solution to the problem? Steve

Many thanks, Rusty & Bryan. That's precisely what I needed to do. :smile: Kind regards, Steve

Loving this new release, and, for the most part, getting on well with the flows and checklists. One thing, though, is still eluding me; so far, I've not been able to get the FO to start either engine. I'm sure I must be missing something really simple, and would appreciate any suggestions. I'm following the steps in the tutorial and made sure that in the briefing the Captain has declared that the FO will start the engines. I've tried before, during and after pushback, and after starting one of the engines myself, but none of the conditions I've used has had any effect. In each case the FO has confirmed "Clear on two" at the end of the engine start checklist, and my start command is being recognised. Please could someone kindly explain what I'm doing wrong.

Hi, I have a couple of 737-800 saved flights, one that exhibits the problem and one that doesn't. Both are at the stage where we're ready to start the engines. The first - with the problem - was saved after starting with a cold & dark cockpit but before I'd even launched FS2Crew, having completed the preflight etc. myself. The second - without the problem - was saved after loading the above saved flight and simply launching FS2Crew. In other words, the only difference between the two saved flights is that the second one opens with FS2Crew already running. If it helps, I can send these on to you.

Top right, but click on "Google site search" to limit the search to this topic, forum, etc. Hope that's the answer you're looking for.

I have to agree very firmly with Alan. Even when the next frequency has been pre-selected on standby, hitting 7, swap and 1 (CTRL-1 in my case) has to be done very rapidly indeed to avoid being chastised. There have been many occasions when I simply couldn't do it quickly enough.

This is an interesting topic. As a new user of both RC and FS2Crew (voice edition) for the 737NGX, I'm intrigued to read that you're able to use VAC to interact with RC. I've looked up as much as I could find on VAC and it raises a couple of questions. Primarily, how do you request a different flight level or a direct routeing to a specific fix in your flightplan (since, as far as I know, the corresponding menu key choices can't be anticipated)? Any advice you can offer will be gratefully received.

I've experienced this problem, too, but as a new user (in early stages of learning) I still haven't tried different variations - just left the pushback settings at their default values. I don't have either GSX or AES installed. I'll experiment with different scenarios to see what I can reproduce. For information, other addons running include UTX, REX, EZDoc, TrackIR, UK2000 airport scenery.