Vampire_NZ

Hmmm, weird.Glad to hear it's working for you.David

Not anymore, however about a week ago I visited there, only to be told that I couldn't log in because my account had been suspended until September 2015.I've just tried now and all seems to be ok, so maybe it's just a temporary thing. Also, I received no notification of a suspension nor had I ever posted on their forums let alone caused and trouble :( so I suspected it may have been a forum error. Sorry I couldn't be more helpful :( Regards,David

I agree completely. It's much more enjoyable than the modern ways of navigating.

Check your email.

Hi Tim,Sure sounds like you're doing everything correctly. You're also right about the red warn light coming on as a result of the unit being somewhere other than where it was last time. Once the warn light comes on, clear it by pushing the 'Test' switch 2 or 3 times and this should clear it and allow the alignment to continue as per normal.Hope this helps,

Sorry, nothing quite so sophisticated I'm afraid. Have a look in the FAQ topic at the top of the forum. There's link to a guide on how to use the autopilot/flight director in the Tinmouse panel.Hope this helps.

Bob,These things happen to the best of us:D Just to change the subject somewhat, in my previous post I also meant to say thanks a lot to you and everyone involved in the project. It truly is a fantastic project.

Hi guys,This may or may not be an issue, but when once unzipped, it appears that there's no "panel.B732ADV" folder in the "fsfsconv" folder. As a result, if unzipped straight into the FS9 folder as per the readme, all the panel files just end up in the "fsfconv" folder.Of course those of us with a previous version installed can just copy into the correct location and overwrite as necessary, but new users may not be aware of it.Anyway just thought I'd mention it in case anyone was having problems.Regards,

Thanks for that. Will order a new copy real soon then.Regards,

Howdy, gentlemen.Following a recent total FS re-install, I discovered much to my horror, that I've mislaid my R4D/DC-3/C-47 cd. If I purchase a replacment copy, will it include the All-Theaters expansion or will I need to d/load it?Thanks is advance.

Hi guys,Forgive me if this is incorrect, maybe it's a bug, maybe not. It's my understanding that the "Speedbrake Armed" light should only come on when the speedbrake is in the armed position. At the moment mine seems to come on anytime the speedbrake is deployed as well.Anyway, just thought I'd mention it. It's hardly a big deal and certainly isn't stopping me from enjoying the aircraft. Thanks for all the hard work.Regards,David.

Yup,I did change it on my eCommerce account sometime between my first purchases and my latest, hence the query as to which one to use to register with PMDG Ops. I figured it'd just be the current eCommerce one but just wanted to make sure.Thanks again, and thanks also for the PMDG Ops idea. I'm already putting together some thoughts for a new article.

Hi guys,Near as I can tell, there's three versions available: NZCH_04v1 NZCH_04v2 NZCH_05v1 (notice the 05 instead of 04)The 05 version seems to be the latest and supercedes the 04 versions. It's not available in the AVSIM file library however. You can get it over at FlightSim.com by searching for the filename nzch05v1.zipPersonally I recommend this in conjunction with the af2_nzchv5.zip which is designed specifically for the 05 version of NZCH and can be found http://library.avsim.net/esearch.php?DLID=...hor=&CatID=msfsThis is the combo I'm using at the moment and it seems to work very well.Hope this helps.

Will do. Thanks Ryan.

I'm sure this is probably a silly question, but with regard to using the email address I used when purchasing my PMDG products, what if I've changed it?Originally I was using a Hotmail address when I purchased the 737s and 744 pax. I'm now using a proper address which is the one I use to login the the PMDG E-commerce section and is also the one I used to purchase the 744 freighter.So would I be correct in using the current non-Hotmail address to register for PMDG Ops?Thanks.

>>Go the 'Canes!Here's hoping anyway :D

Yup, the ILS-MLS line will only display PARK until 200nm from either the T/D or destination airport (can't remember which :) ). In the mean time, if you want to enter it manually, use the format: FFF.F/CRS, for example, here in Wellington the ILS for Rwy 16 would be entered as 110.3/161I'm about to go take the Queen for a fly anyway so I'll see if I can't come up with some more info for you as well.

You're most welcome. Hope it works out for you.

As far as the A/P is concerned, have a look in the PMDG options menu. There's a box in the somewhere called 'Control Override' or something like that. If memory serves, having these boxes un-checked could explain the disconnects you're describing.

Brian, That sounds like a plan. The other thing I've been wondering is whether or not there's enough of a difference between engine types to warrant different FSBuild profiles. Of course this would presumably apply only to those of us with the freighter. Maybe be something to look into at some stage.

Looks good so far. If you'd like some assistance with testing, let me know. I've been flying a few 12 to 13 hour flights across the Pacific lately and would be more than happy to help out.

Hi again,My apologies, it seems I was incorrect. I've just tried it again, and discovered that you can enter lat/lon co-ordinates on the main 'RTE' page. They need to be entered in the format xxxxN. Using the above example, it would be entered as 6860N.

Hi there,These Lat/Lon waypoints can only be entered in the 'RTE LEGS' page, although the PMDG 747 manual would seem to indicate that it's possible to enter them in the 'TO' column on the main 'RTE' page. Perhaps someone else may be able to confirm this.Hope this helps.

Howdy Tim,Kinda scary how many of us there are. Speaking of Hurricanes, not a bad result last night, except for Chiefs fans I guess:P

Hi there,I'm sure there's probably someone who knows more about this than I do but I'll see if I can help in the mean time. Most fixes such as those you mentioned above will have a distance and bearing from a navaid, for example a VOR. To use the first example you gave, the "D9.0" would be the distance from the navaid and the BPK would be the identifier of the navaid as shown on the chart. There should also be a bearing from the navaid to the fix shown on the chart.As for programming it into the FMC/CDU, take a look at the piece of chart below, it's slightly different than a Jeppeson but should serve the purpose.http://forums.avsim.net/user_files/148135.jpgAssuming we wanted to add the fix "HURST" in the the FMC, the first way we could do it is with a 'PDB' or Place Bearing/Distance waypoint. In our example this would be entered as TR057/11, since the fix is 11nm from the TORY (TR) VOR, on a bearing of 057