Andydigital

For the last time the dynamicfriction.lua does not change any core files, it patches in memory through FSUIPC dynamically, remove the lua file from the modules folder and its as if it was never there.

FSUIPC already has this facility built in, see the ALSO Autosave section of the manual, it allows you to save a flight at any time period you choose but just for that particular aircraft model and even for separate paints too, so all your aircraft remain where they were the last time you used them. All of my fleet it saved at various airports around the world.

They don't have to code their aircraft to use this friction tweak though, that is the beauty of it, it's dynamic and will not skew PMDG's landing and take-off distances, it only effects taxi speed/break away force and turning/side friction.

Taxi speeds are a little high with the dynamicfriction lua script and the T7, but that's all I've noticed. As was said above, above 30 knots it doesn't actual change anything as the tweak is reset to default friction levels. You can edit the speeds and even the frictions used in the script if you want, but the settings it comes with are fine as they are.

You can use EFB to build a plan if you want but it wont auto build a route for you, although you can very easily import a route from any other planning software or even a flight planning website like routefinder, the later is actually built into the App.

And setting it as the default state that is loaded when the 777 loads, exactly the same system was used with the NGX as well.

You are splitting hairs, its bloody obvious and you know it.

You are stating the obvious though aren't you, you aren't supposed to load payload into the aircraft any other way than with the CDU PAYLOAD page, but you still have to enter the ZFW in the PERF INIT page as well. And you can enter the payload accurate to 1/10th on the payload page by typing the weight into the ZFW box on the payload page, just type 194.4 for example and drop it into ZFW, you dont have to touch the percentage part.

Weight is weight, just take your zero fuel weight from the details page in PFPX and enter that into the ZFW box in the PERF INIT page in the 777 CDU. The weight won't be distributed the same as in PFPX but the total weight will be the same and that is all that matters.

I'm fairly certain the 777 will look in all PMDG FLIGHTPLAN folders so it doesn't matter which one you send it to.

Also make sure you haven't assigned a custom slope to the throttle either otherwise that will stop it working too.

Trust me its not out yet.

Do not start a flight with the Cold and Dark panel state there is a bug in it in the RTM version of the 777, use the Short panel state instead then put the aircraft in the state you want it and then save that and assign it as your Startup state. You should find the Caution bug will be gone now, along with a couple of others you have not come across yet.

You are talking about something completely unrelated to the topic starters question, so you are doubly burned, lol!!!!!!

Look at the left hand com radio and you will see a button lit with VHF1 written on it, immediately below this is the Mic1 button, press it.

We aren't talking about the V737 Overhead panel, we are talking about the CDU 1.

It's not a bug, you have to switch on the Mic on the radio stand next to the active radio. Hasn't anyone read the introduction manual.

According to the compatibility document on the website yes, but I've never tried it (mine is buried in the loft somewhere) so I cannot confirm it 100%. The CDU2 works wonderfully with it though.

Look for the Operations Centre in your "PMDG Simulations" Start button menu folder, that handles liveries among other things.

No its not a requirement.

Actually I retract my above comment, there was calibration data for the throttles, but it was actually only slope data rather than beginning/end point data. So it would seem even adding a custom slope to the throttles will cause problems. What I did was go into FSUIPC4.ini and completely delete the joystick calibration section for the 777 profile I had, then built it back up again from within FSUIPC and left the throttle calibration sections at reset. I then calibrated the flaps and brakes and everything works fine now. I think the problem probably stemmed from the distant past when I used to have a default set of calibrations for the general profile i.e. for aircraft which didn't have a profile assigned to it. When you create a new profile FSUIPC will ask you if you want to import that general profiles settings, you must say NO to this question. I think its that general calibration data that is imported to your 777 profile and it was that data that had the none linear throttle slope in it that PMDG obviously do not like with their aircraft throttles. So problem solved for me and now I have this knowledge I can fix my NGX profile too, as that never worked properly either, lol.

I'm fairly certain its got nothing to do with FSUIPC I have my throttles assigned in FSX and there is no conflicting assignment/calibration in FSUIPC and yet I still cannot set the throttles at any position without them moving instantly back to idle. The only way to stop this is if I turn the two AT switches off, then they work perfectly. I'm convinced this is because I am using two throttle sticks (Saitek Quads) one for each engine and the logic built into the 777 to keep the thrust sync'd is causing some conflict. Andy Baker.

It will be after PMDG release their SDK (software development kit) for the 777, VRi need this to write proper drivers for all their relevant hardware. PMDG have not given any date yet when that may be, but if its anything like last time when the NGX was released it will likely be after SP1 is released for the 777.

There is a detailed instruction manual in the post linked to below, please read that, there is no better resource of information regarding LINDA and how to set it up. http://forum.avsim.net/topic/376920-linda-beginners-guide-a-very-detailed-manual/ You MUST have the registered version of FSUIPC for LINDA to work.

Nice enhancement, thanks.