PikalaxALT

I, like DVA238, also hate to revive old threads, but the FRDMM3 arrival into DCA causes this error as well. KSTL - KDCA via JHART3 CREEP J80 AIR J34 BUCKO FRDMM3 With just the arrival inputted (runway 01 transition), the error appears instantly.

I have FSX Acceleration box edition, which has been on my system for several years and has steadily acquired modifications including the PMDG 777X. I'd now like to slowly migrate over to FSX:SE, so about a week ago, shortly following the announcement that SP1d was available (i.e. on 25 Jan 2015), I redownloaded the 777 installer from my order page and attempted to install it on FSX:SE. However, the installer found the existing installation and gave me only two choices: Repair (INOP), and Remove (unwanted). This raises two questions, which I have also raised unanswered on the Steam Community forum: 1) If I want to install the 777 on FSX:SE, do I first have to remove my existing installation? 2) Am I able to have the 777 installed on both FSX box and FSX:SE?

I have FSX Acceleration box edition, which has been on my system for several years and has steadily acquired modifications including the PMDG 777X. I'd now like to slowly migrate over to FSX:SE, so about a week ago, shortly following the announcement that SP1d was available (i.e. on 25 Jan 2015), I redownloaded the 777 installer from my order page and attempted to install it on FSX:SE. However, the installer found the existing installation and gave me only two choices: Repair (INOP), and Remove (unwanted). This raises two questions, which I have also raised unanswered on the Steam Community forum: 1) If I want to install the 777 on FSX:SE, do I first have to remove my existing installation? 2) Am I able to have the 777 installed on both FSX box and FSX:SE?

Situation 2. 777 installed on FSX, now trying to install on FSX:SE. Installer only shows Repair and Remove. Repair function is INOP. FSX:SE is installed in a library on an external SSD. FSX box is installed on the same SSD. I am using the 777 installer using the download link on my order page, last accessed on 25 Jan 2015. OS is Win8.1x64

Seeing as PMDG got it working in the 777, they should be able to rectify the issue for NGX-SP2.

My default panel state has the forward left door open, which should be connected to FSX's interpretation of the Main exit. This I believe is how GSX determines whether the door is open or not. However, when the aircraft spawns with this door open, FSX does not set the Main exit open flag, so GSX asks me to open the door. Best workaround is to double-click the LSK at FWD LEFT DOOR.

To initiate a descent using VNAV, simply select the lower altitude in the MCP and make sure you are flying on LNAV and VNAV. The FMA will read [sPD | LNAV | VNAV PTH]. When the aircraft reaches the T/D point on your ND, the throttles will automatically retard. To start the descent early, depress the altitude knob to override the FMS-selected altitude. To initiate an open descent, use FL CHG.

Good idea. May I suggest using something like the A/P Disconnect sound as your incoming-call ringtone? /FSX/Sound/PMDG/777X/CAWS/PMDG_777_Wailer.wav

This has been bugging me since I first purchased the NGX edition software: in order to update any FS2Crew package, you have to redownload the full installer. When purchased from the FS2Crew main shop, however, you only get a limited number of downloads (15 or so), so any time an update is released, that eats into the download counter. What other developers have done is bundled an update checker into either the main installer or the main software, which would automatically query the server's version number and download the new installer if the server version is newer than the local version. I would like to suggest that FS2Crew implement a similar feature. That way, if you ever release more updates than the download limit allows, loyal customers won't be left in the dark.

Thanks for the explanation. I figured that's what it was doing, and it's actually kinda cool that PMDG simulates that detail.

Scenario: ATC tells me to descend and maintain a certain altitude, say, 6000. I don't get a further descent until well after reaching 6000 feet. While maintaining 6000, the PFD annunciates "FMC SPD | LNAV | VNAV ALT". However, the speed bug starts dropping down by 1 kt per second until it hits the flaps UP speed. Is this the intended behavior? And if so, how do I set up the aircraft to inhibit this deceleration?

Actually, that is correct. If you don't do this and have A/T override enabled, the throttles will roll back. By pushing the thrust levers forward, you are in essence authorizing takeoff thrust. Alternatively, you can disable A/T override. I will make these recommendations for underweight takeoffs: 1) Thrust derate and high assumed temperature (60-80 C when allowed; if runway is wet or contaminated, derate may be limited. Do not allow more than 20 knots between V1 and VR.) 2) Steep climbout. Use your pitch to manage your airspeed on takeoff and initial climb. 3) Fly the departure manually. Raise the gear and flaps on schedule, and stabilize your airspeed at or below 250 knots before engaging autopilot. If necessary, continue to fly manually until 10,000 feet (FL100).