Barbs

I just get a cloudflare page today. Same with www.aussiex.org

Posted this question above but then went away and thought about it to make sure it could be done... now I'm back and here it it. I realise this is an old thread but the upcoming 777 SP release got me thinking about RF legs again. A lot of the discussion is about navdata and ARINC etc. The premise of my question is that navdata and ARINC is irrelevant when PMDG already give us the ability to create our own procedure code. Example: APPROACH RNPY05 FIX IBABU AT OR ABOVE 10000 FIX OVERFLY QN577 10000 SPEED 220 FIX 300R1 FIX 290R1 FIX 280R1 FIX 270R1 FIX 260R1 FIX 250R1 FIX 240R1 FIX 230R1 FIX OVERFLY QN573 9200 FIX 210R2 FIX 198R2 FIX 186R2 FIX OVERFLY QN571 8200 FIX 163R2 FIX 151R2 FIX 139R2 FIX OVERFLY QN569 7100 SPEED 180 FIX QN565 6300 FIX QN562 5500 FIX OMUBO 3100 FIX OVERFLY QN555 2440 FIX 118R3 FIX OVERFLY 109R3 FIX OVERFLY QN550 2040 FIX 292R4 FIX OVERFLY 304R4 FIX 316R4 FIX OVERFLY QN545 1480 RNW 05 FIX OVERFLY QN547 FIX 131R5 FIX 119R5 FIX 107R5 FIX 095R5 FIX OVERFLY QN551 FIX 070R5 FIX 056R5 FIX 042R5 FIX 028R5 FIX OVERFLY 014R5 FIX 359R5 FIX 345R5 FIX 331R5 FIX OVERFLY QN553 FIX 303R6 FIX 289R6 FIX OVERFLY 275R6 FIX 261R6 FIX OVERFLY 247R6 FIX 233R6 FIX 219R6 FIX OVERFLY QN557 SPEED 170 FIX 038R7 FIX 045R7 FIX 052R7 FIX 059R7 FIX 066R7 FIX OVERFLY QN560 FIX OVERFLY QN878 FIX 074R8 FIX 079R8 FIX 084R8 FIX 087R8 FIX OVERFLY QN882 AT OR BELOW 11000 FIX OVERFLY SUNGU FIX 266RQ FIX 261RQ FIX OVERFLY QN890 FIX NV This is RNP-Y RWY05 at NZQN (thanks to Jock McIntyre - www.vapap.com). We can already code where the basic fixes are (eg. QN562, QN555) as they are charted. All these other fixes are "fill-in" fixes that create the radius to fix legs which looks really messy on the ND but gets the job done. My point is, WE can calculate where the aircraft should fly. All we need is the ability to code it more concisely. What would be so difficult about the following? Instead of the first part of the missed apch being... FIX OVERFLY QN547 FIX 131R5 FIX 119R5 FIX 107R5 FIX 095R5 FIX OVERFLY QN551 FIX 070R5 FIX 056R5 FIX 042R5 FIX 028R5 FIX OVERFLY 014R5 FIX 359R5 FIX 345R5 FIX 331R5 FIX OVERFLY QN553 FIX 303R6 FIX 289R6 FIX OVERFLY 275R6 FIX 261R6 FIX OVERFLY 247R6 FIX 233R6 FIX 219R6 FIX OVERFLY QN557 How hard would it be to have the FMS read the following code? FIX OVERFLY QN547 ARCL 2.6 FIX OVERFLY QN551 ARCL 1.7 FIX OVERFLY QN553 ARCL 2.0 FIX OVERFLY QN557 The waypoints can be declared in the SIDSTAR file, you can even code in the centre points of the arcs if you need to (nt that I think you do). All we need is an FMS that can read that new bit of code [ARCL|ARCR NN.N].

nevermind

I found the problem. The patched EZCA.exe had not extracted to the right place so it was trying to load the old one still. Thanks for your help.

Me too. I have: Installed the fixed EXE file found here http://www.simforums.com/forums/ezdok-and-prepar3d_topic40274_post236510.html#236510 Created an EXE.xml file in AppData/Roaming/Lockheed Martin/Prepar3d v2/ and it looks exactly like above (tried both exe.xml and dll.xml in the filename prameter) EZDok doesn't load when I load P3D like it does when I load FSX and it doesn't appear in the Addons menu. Do I need to run the config tool some way like you do with FSX? If so how is that done?

Your exe.xml file has <Filename>dll.xml</Filename> in it. Are you sure that's correct? dll.xml is a completely different file.

When NGX came out I said "Wow, I can't believe what they've been able to do with FSX! Well worth the $70." When 777 came out I said "This is really nice, but most of the wow factor comes from differences in the actual plane. Not sure I can justify the extra $$$" Extra US$20 on the NGX? Hmmm.... maybe just inflationary rise over 2 years but I hope the 300 model is going to be in line price wise with the 600/700 and not more expensive as well. Still, brilliant execution from PMDG once again. I have a modest system (i7-930, 16GB RAM, 1.4GB GTX480) and have not had any issues with texture loads or frame rates. I'd say comparable to slightly better than NGX as has been reported.

yeah sorry. had a typo when I searched... I see now. :blush: But seriously, THAT made it out of beta?

Ah thanks

Hi All, I have a caution light with no associated EICAS warning that won't clear. It appeared as I started number 1, 2 was already running and stable. Recall gives no information. If I press the Caution button on the glareshield, the Caution light remains lit. All systems pages appear to be normal. There are no active failures in the CDU. I have sent a screenshot of my overhead to a rated B777 pilot who said it looked good. I have been able to depart as normal, and am now in the cruise at F390 on a short flight with no other issues. Just this unexplained caution. Any ideas?

In some configurations (not sure the exact settings in the CDU Menu for it to happen) you get an automated callout AND an F/O callout. The solution is to disable one or the other.

Marko, Just out of interest, at what weight are you practicing your landings? If you are too heavy that can make landing difficult as it affects so many factors. Don't just go blasting off with full tanks as that will most likely put you above Max Landing Weight and be making your life harder. If you want a nice weight for circuits, use about 50% in each wing tank only. You mentioned your were having trouble slowing down too... Don't think you mentioned how long a final you are making but assuming about 8-10nm you should be flap 5 and about 180-190kts when you turn toward the runway. Just before you start down hill take flap 15, gear down,arm speedbrakes and set speed about 160. Once you get down to 160kts, bring her back to Vref+5kts (speed over the fence) and take flap 30 or 40 (depending on config and runway length etc). At 60T and flap 30 your "speed over the fence" should be about 142-147 kts. In this config, 60% N1 and 700ft/min vert speed will stand you in good stead. The important thing I want to stress is that you need to be configured. Most airlines will have a stable call at either 500ft or 1000ft where they must be on speed, on slope, landing flap selected and stable. At this point they are for lack of a better term "ready to land". If you follow these simple rules you will have less of your concentration on flipping switches during the final approach segment and more time to fly the plane.

And he's STILL not signing his post.

Ah right yeah sorry, It was probably 3 years ago that I followed it.

Hi Rod, Yes I have tried that. The only thing that works for me for sure is to completely disable the controllers in the menus. To mynetdude This is a pretty thorough tutorial that can be adapted to suit just about any controller. http://www.tropicairvirtual.com/company/misc/utility/tutorial/fsuipc-guide-v1.pdf Greg

This works for me however FSX randomly re-enables my controllers in the menu. I have to include a check of the Enable Controller checkbox as part of my preflight. Does anyone have a method to disable the damn controller for good?

Gary, As long as when you first load FSX, in the Create Flight screen you see Friday Harbour and the Trike you should be fine. Weather and time is of little importance You can then make whatever changes you want, select NGX by the "Change..." button under CURRENT AIRCRAFT and select you desired location using the "Change..." button under CURRENT LOCATION. Then click "Fly Now!" Or if you have a saved flight with the 737 loaded at your gate of choice, just choose "Load..." and choose your flight. There is no need to click "Fly Now!" with the trike selected. (unless of course you want to fly the Trike!)

Yup. The pointer appears on the PFD when you turn toward the glideslope right?

Lek767, you are correct, not sure what I was thinking.

Hi, Typed out a big long response and then lost it. Here's the short version. There are a number of ways (modes) to fly the plane and there are a number of reasons VNAV will not arm. Most obvious would be the A/T is not armed (switch on the MCP). Also check that BOTH flight directors are on (switches on the Capt and F/O side of the MCP) to ensure you have full automatic flight capabilities. If you are still having problems there's no need to stay at 5000ft. You can set your desired altitude and speed on the MCP and select LVL CHG and the aircraft will climb. Or you can set SPD, ALT and V/S and select V/S mode to climb. If A/T is not armed this will result in your losing speed and having to set thrust manually so that'll be the give-away.

Active sky and the CDU are not related. You will need to import them both separately (I think from separate files).

I don't think this has anything to do with VNAV, it's about the A/T in takeoff mode.

If you start APU and turn on APU Gen does it stop?

I'd suggest that's a bug. The A/T remains in THR HLD until 800ft RA then changes to ARM. At this point you are supposed to be able to select N1 manually. This is similar to another question I saw a while ago where a second press of the TO/GA switch below 800ft was not selecting full GA thrust. I'll have to run some tests to see if they are related.

Make sure IRS switches are set to NAV and alignment is complete. This is not something FS2Crew does for you as it's part of the Captains flow. IRS alignment needs to be complete for the yaw damper to work. Otherwise the switch just resets. Don't know why the APU wouldn't stay running.