Mike777

You should be able to do it with the (modestly priced) payware Remote CDU while waiting for the new 747 and added 777 & 737 functionality.  It has its own network connection program and AFAIK doesn't use FSUIPC.
 
http://www.avsim.com/forum/742-remote-cdu-for-phone-tablet-official-support-forum/
 
Mike

Hi, Nick,
 
Sorry I got a little hot under the collar.
 
I set up an approach using an NGX to 16R w/ stock airport. The ILS is definitely off to the left from the actual runway
location. I selected an ILS approach in the FMC, same waypoints as you have. In fact, the magenta line connecting them
does go to the runway properly. When I slew over to get the localizer dot centered, JARNU is slightly to the right of the
approach path, as it is in your screen shot (using same Map range, 10NM). This may seem like a small discrepancy, but
actually the localizer path is offset enough from the magenta line to put you on the grass instead of the runway. So I
think the FMC nav data is correct.
 
This sort of issue is unusual for FSX. I can't think of another example like this one. Changes in runway numbering, new runways,
changes in ILS/Loc frequencies are much more common, as FSX was released nearly ten years ago.
 
I installed one of Jim Vile's fixes for KSMF. Perfect ILS approach and autoland.
 
Info on this file:
http://library.avsim.net/zipdiver.php?DLID=102743
 
Download link:
http://library.avsim.net/download.php?DLID=102743
 
There's at least one much more recent scenery that may also include the fix.
 
Mike

Hi, David,
 
It might be a problem with ARPT_RNWY.DAT.  It is a cache file used by the 777 FMC.  I don't have P3D but in FSX it is located in FSX/PMDG/NavData.  It is not part of the Airac cycle data.  Back it up to another folder and then delete it.  It will rebuild the next time you load the 777.  See if that fixes the problem.
 
Mike

Hi, Mark,
 
Thanks for your (as usual) quick reply.
 
It looks like I am the one who created this problem in the first place, not Remote CDU or ASN.
 
EXE.xml, located in ...Appdata\Roaming\Microsoft\FSX_SE (or close to that), allows helper programs to be started with FSX
(same in FSX Boxed version). ASN uses it, for example, at least in a networked configuration.
 
It turns out I myself added lines to this file to automatically start simserver.exe when FSX starts. However, when
simserver.exe starts that way, it is somehow marked as part of FSX. So neither Steam nor ASN detect that FSX has closed,
apparently, and therefore don't react correctly. This is because simserver.exe doesn't close when FSX does, but also because
simserver is somehow marked as part of FSX.
 
When I removed the autostart instructions for simserver from EXE.xml, my problems with Steam and ASX disappeared! Simserver.exe
continues to remain in memory after FSX closes, but does not cause any conflicts.
 
I thought EXE.xml was just a simple file that allows the startup of FSX helper programs like yours. But this approach had
unintended consequences! Go figure!
 
Sorry to have bothered you about this, but it took me awhile to figure out what was going on.
 
Mike

Hi, Rick,
 
This may very well be a problem with ARPT_RNWY.DAT.  It is a cache file used by the 777 FMC.  It is located in FSX/PMDG/NavData but it is not part of the Airac cycle data.  Back it up to another folder and then delete it.  It will rebuild the next time you load the 777.  See if that fixes the problem,.
 
Mike

Hi, rafikihd,
 
i have FS9 working again.
 
There are two things to check:
 
I) Do you have the following entry in your panel.cfg file?  There are two gauge entries that are especially important.  I've marked them.  Also make sure the [VCockpitXX] entry is correct.  Without this entry the lights don't work. If there are no other [VCockpit...] entries, it should go after the last [Windowxx] entry.
 
------------------------
[VCockpit01] //<< IF THERE ARE OTHER ENTRIES [VCockpitXX] this should be at the end and have the next consecutive number
size_mm=512,512
pixel_size=512,512
texture=$Posky_ACU
background_color=0,0,0
gauge00=Posky763!Pky_AdvInit, 140,80,140,80
gauge01=Posky763!PkyCALC, 140,80,140,80
gauge02=Posky763!Pkygearcalc, 140,80,140,80
gauge03=Posky763!Pky6WINGFLEX, 140,80,140,80
gauge04=Posky763!PkyNosegearsteerling, 140,80,140,80
gauge05=Posky763!PkyAileronL, 140,80,140,80
gauge06=Posky763!PkyAileronR, 140,80,140,80
gauge07=Posky763!PkyLSAileron, 140,80,140,80
gauge08=Posky763!PkySpoiler, 140,80,140,80
gauge09=Posky763!PkyAPUDoor, 140,80,140,80
gauge10=Posky763!PkyEngRev, 140,80,140,80
gauge11=Posky763!Pky_PB_Towhead, 140,80,140,80
gauge12=Posky763!PkySEA, 140,80,140,80
gauge13=Posky763!PkyFlasher, 140,80,140,80  //*** THIS ENTRY CONTROLS THE BEACON & FLASHER
gauge14=Posky763!Pkycondassign, 140,80,140,80 // *** THIS ENTRY APPEARS TO CONTROL SOME WING LIGHTS
-----------------------
 
II) Do you have a folder inside your panel folder called "Posky763"?  When you look inside it do you see a bunch of gauges ending in "xml"?  Especially important are one called "PkyFlasher.xml" and "Pkycondassign.xml" -- these are the two gauges to which the above last two gauge entries are pointing.
 
Mike

Hi, everyone
 
Here is the reply from PMDG Tech Support:
 
"Route Request is not a function that should be available in flight.  It is used only on the ground to call up an company created route to be loaded into the FMC.  It is OK to copy the route after you have completed the route during preflight so that it is available if needed but pulling a new route, enroute is not going to work properly in the FMC and should actually be inhibited.   I will ask the team to look at disabling the feature in the air mode in a future update."   In other words, using Route Request should not be available at all after takeoff, as I read it.  The proper procedure is to use Route Copy, either on the ground or in the air.  it works just fine in either situation.  So those of you who suggested that it was only meant to be available on the ground -- Michael, as you said, it is only discussed in relation to ground operations -- were correct.  And those who said it's better to use Route Copy were also on the mark.  Thanks to Romain, Michael and Kevin for experimenting with this, and thanks to Dan for filling us in on RW procedures and his own practice (which would have avoided the problem I encountered).   We did find a bug, but the bug is not that Route Request doesn't work properly in flight, the bug is that it is available in flight at all.   PMDG asks that people not expect this fix to be available right away or to start inundating them with requests for a fix -- it will have to wait for the next update.    Mike

I don't quite agree that you won't lose any of your existing configuration by running a new installation as described above.  It depends upon what you have modified. 
 
If you have added gauges to the panel.cfg file or modified some display settings -- such as moving a popup CDU display to a different location or resizing it -- you are likely to lose those modifications.  If you have edited the aircraft.cfg file -- for example to make Function view commands to work differently than  the default -- you will lose those settings.  So it is best to back up the main panel.cfg and all the aircraft.cfg files if you have edited them.  After the installation, you can't just paste them back and overwrite the newly installed files (that may overwrite PMDG's improvements to these files) .  But you can use the backups to copy your modifications back into the panel.cfg and aircraft.cfg files. 
 
Also it should be noted that some older startup situations may use panel states that are not compatible with the newer 777 versions.  If you notice strange behavior when you use an older saved situation or saved panel state, you may need to stop using it.
 
Mike

If you only have FSX:SE installed you may be missing several versions of SimConnect.  This is known to cause this issue.  In the FSX:SE SDK there is a facility for installing them.
 
Mike

To sum up:
 
FSX:MS=original MS version of FSX
FSX:SE=Steam version of FSX
 
1) Run the installer for the Level D 767 and then for the Winglets version, pointing them to the main FSX:SE folder, typically
...\SteamLibrary\steamapps\common\FSX
 
2)  See if it works by loading the aircraft in the usual way.  Make sure all the gauges are showing up and working.
 
3) If it does not, find the DLL.XML file, found in a typical installation at:
C:\Users\[Your Name]\AppData\Roaming\Microsoft\FSX-SE.  You might want to back up your DLL.XML file in FSX:SE just to be on the safe side.
 
You can open and edit it with Notepad.  This is most likely missing with a dual FSX:MS and FSX:SE install on the same computer.  If it does not have the following entry, copy and paste the following immediately after similar entries that should be there:
 
<Launch.Addon>
    <Name>Level-D Simulations</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Modules\LVLD.dll</Path>
  </Launch.Addon>
 
4)  Try it again.
 
5)  If it still doesn't work, you need to install "legacy" simconnect dlls (probably missing if you don't have a dual FSX:MS and FSX:SE installation).
 
Go to:
 
...\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces
 
There you should see three subfolders.  Each one has a "SimConnect.msi" file in it.  For each folder, click on the "SimConnect.msi" file in it to install that version of simconnect.    It is safe to install all of them, and indeed may make other addons work as well.  You can also see which SimConnects are installed on your computer by looking in Control Panel - Remove Programs.
 
For further information on SimConnect, please take a look at:
 
see especially post#9,
http://forum.avsim.n...nect-v61612590/

specifically on FSX:SE, post #19:
http://forum.avsim.n...y-thread/page-2
 
There are still some issues w/ how the 767 saves and loads flights, but these are not deal-breakers for me.
 
Thanks to Chalkman for his input!
 
Mike

Hi, AlxMrx,
 
This topic has been discussed extensively.  Please read the following thread, especially post #12 by Tabs/Ryan Maziarz, who is a member of the PMDG team:
 
http://forum.avsim.net/topic/405014-will-the-sdk-provide-enough-access-to-create-a-2d-panel/?hl=%E2%99%A6panel
 
There are many other threads on this topic.
 
Also, PMDG wants you to sign your full name in its forums.
 
Finally, curious to know why you are including a Garmin GPS, when the PMDG 777 comes with a fully integrated navigation system including GPS and INS?
 
Hope this helps!
Mike

Hi, jmslwl25,
 
From your description, I think you are opening the saved situation file, not the recording file. When you start to record, FS-Recorder saves the situation just as if you had saved the flight at the start of the recording. When you say that you "navigated to the file," how did you do this? Were you inside FSX or outside?
 
AFAIK, you cannot start playing an FS-Recorder file from outside FSX. To play back a recording, you need to start FSX, start a flight (the default Trike/Friday Harbour will do just fine), open the FS-Recorder tab, choose "play," and then select the name of the recorded flight. (In fact, you did not need to close FSX at all after finishing the recording.)
 
If you are using some third-party add-on aircraft such as one by PMDG, things can get a bit more complicated, but that is the basic idea.
 
Mike

Please see Ryan's post #12 here:
http://forum.avsim.net/topic/448846-confusion-on-deleting-old-panel-states/
 
where he says,
 
"That paragraph in the SP1b readme should have been clarified more - you do NOT have to delete SP1 panel states - they are compatible with SP1b. The ones that need to be deleted are the ones from the RTM version released last year."
 
Also Kyle's post in that thread, #11
 
Mike

Sorry, Jeremy (and for all of us hovering expectantly) but it's still there:
http://www.precisionmanuals.com/ProductCart/pc/viewCategories.asp?idCategory=14
 
Mike

Hi, Kevin,
 
Most probably the runway you chose is missing from your scenery.  Since FSX was made, a new runway has been added to KSEA that is missing in FSX. I am guessing that you selected 34L.  The old 34L is now the new 34C.   The nav database in the 777 has the new information, and LNAV (and VNAV) will line you up for the runway you selected where it is now, not where it is in FSX.  If you selected an ILS approach, it will also autotune the frequency and course for the runway you selected as they are now, not as they were when FSX was made.  Open up the FSX map window, click on KSEA and see what runways and frequencies are showing there.  My guess is that 16C/34C is missing and the ILS frequency tuned by the FMC is missing as well. 
 
I often have the caution light come on for unknown reasons, w.out using the C & D panel state.  I think this is a bug scheduled to be fixed w/ SP1 and has nothing to do with your issue.
 
Mike

Hi, George,
 
So it sounds like the flight is loading, you just find yourself outside of the FSX window and you can't get back in.
 
A couple of things:
1) are you using alt-tab to get into the FSX window?
 
2)  If that doesn't work, try opening the task manager (Ctrl-Alt-Del) and then alt-tabbing into the task manager followed by alt-tabbing into FSX
 
3)  If you are loading the saved flight by clicking on the name of the saved flight in an explorer window, try loading it from the opening window of FSX instead.
 
4) Make sure your display resolution in Windows and your display resolution in FSX are the same.
 
5) I am guessing you are using Windows 7 -- try shutting of Aero, a display feature.
 
Hope this helps!
 
Mike

Kyle,
 
You are quite right about that.  As I understand it, in the real T7 the pilot can maintain the throttle where he wants it by keeping his hand on the throttle levers.  On most FS systems, certainly on mine, I would have to keep making small movements on the throttle lever just to keep it where I want it.
 
BTW, my understanding of what happened to Asiana 214 is that the PF had FLC set, along with the missed approach altitude, so the aircraft started to power up and climb.  He then forced the levers to minimum and held them there, causing the A/T to go into HOLD, no more airspeed regulation, and we all know the rest.
 
Mike

 
 
 
David,
 
From what you said about your throttle levers causing the engines to firewall on takeoff, and what Kyle said about spikes, I am guessing you are getting a spike on landing.  If you set the manual throttle either to NEVER override autothrottle or override only in HOLD, this problem should go away.  The A/T should never go into HOLD during final approach.  It should be either in SPD or, shortly before touchdown, IDLE.  This should be the case on an Autoland, on an ILS approach where you switch of the Autopilot (but not the Autothrottle) at some point, and on a VNAV approach.
 
Although PMDG does not advise it, I use FSUIPC for my throttle control.  It has a box to eliminate spikes that you can check.  If FSUIPC throttle causes you problems, you can always go back to FSX.
 
Mike

Hi, UAL873,
 
Just noticed this in the http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread-read-before-posting/
 
"- CTD on load that results from errors in the runways.csv or ARPT_RWY.dat files.
If you're getting a CTD upon selecting the airplane or pressing Fly Now, please try deleting these two files. runways.csv is in the root FSX folder, and ARPT_RWY.dat is in the FSX\PMDG\NAVDATA folder. runways.csv can be remade using Pete Dowson's MakeRunways.exe tool, found at his website." Mike

Hi, Nick,
 
I suggest you run through your flight plan, both by scrolling through the LEGS page, looking at the distances and direction from waypoint to waypoint, and in STEP mode (don't use the lower EICAS to do STEP mode  -- it will cause a CTD.  Use the left or right HSI).  Something is wrong, as your CDU shows plenty of fuel for your destination, over 3000 miles away, but no fuel for your next two waypoints.  Also, it shows you are at the TOD now, more than 3000 miles from your destination.   If the FMCs "think" you are at TOD, VNAV will make you descend to the altitude set in the MCP window, which is what it appears to be doing. 
 
Temperature shouldn't be a problem as you are at a low altitude where ambient temperature can be very high.
 
Mike

Hi, Marko,
 
You need to press the separate A/P Disconnect button located between the FLCH and HOLD buttons. But due to issues about silencing the A/P warning sound you might be better off using a mapped key or button (you need to press it twice a second or so apart to silence the alarm).
 
Mike