X24

Kevin - this is what worked for me. Go to %ProgramData%\Lockheed Martin\Prepar3D v...(whatever version yours is) and open the dll.xml with a text editor. I added the following lines to the end just before </SimBase.Document> which should be the very bottom line: <Launch.Addon> <Name>Carenavigraph</Name> <Disabled>False</Disabled> <Path>.\Carenavigraphx64.dll</Path> </Launch.Addon> I saved it, opened the sim, and now the Carenado Navigraph database works as it should. I hope this helps. This is very similar to what you did but with the "other" dll.xml. I'm not sure what the difference is between them or why your fix didn't work. I'm using P5D and there is no dll.xml in the AppData folder, only the ProgramData folder. Cheers

Bump. I am having exactly the same issue. Running P3D v5.

Are you burning more or less - flying faster or slower?

Maybe that's why they call it "original" - any resemblance imagined or real to any ProLine product alive or dead is purely coincidental and Carenado can not be held liable in that event. Their big selling point, what they do really well, is the visual quality. Most of us though seem to have moved on and are learning to live with ourselves again. I have to say, there is something strangely seductive about this machine, and it's been a favourite of mine since I first saw a picture of it in one of my plane books back in the 60's or 70's. This rendition looks amazing, and I get a buzz from just staring at it. Tim's videos over at FsMaNiA bring her alive, and he speaks of his relationship with her a bit too and the learning and personal growth he has experienced as a result of this union. Systems-wise, you just have to let it go, which is a process, not an event. If you haven't tried Bert Pieke's GTN750 mod, then I highly recommend you try it out, and keep persevering. When you actually start to be able to knock a few flights off in this bird and then watch the playbacks, it can be very rewarding. Depends what you're looking for I guess.

So far I have been able to enter waypoints such as 6600N and the like. After some experimentation, I'm pretty confident this version of the FMS will only accept waypoints from the database. It does not seem possible to enter custom waypoints.

Greetings Bert Thanks so much for the great work you did making this modification. I've been testing it out around the South Island of New Zealand while I'm still actually learning how to use the GTN 750. I'm very happy with this - thank you! PM is en-route for the FD version...

Nope. Sounds like it's working perfectly. Far as I know, the radar is not modelled, so if some weather DOES show up, there's something wrong (right...). You can set the range and the tilt, but selecting radar seems to just remove the terrain display.

Kyle One of the "interesting" features that Carenado have designed into the auto flight system is that arming or engaging a particular lateral or vertical mode does not necessarily disengage the previously armed or engaged mode(s). Engaging a mode after takeoff can engage the autopilot too. Disengaging the autopilot may completely or partly disengage whatever modes were active and/or armed. There is a clickspot in the centre of the altitude knob labelled PUSH TO CANCEL or some such (I'm away from my computer till tomorrow when I can have a look at this in more detail). The FMA is not always a reliable indicator of the state of the auto flight system, so I generally have tooltips ON: hovering the mouse pointer over a button or knob will let me know what state it is in - ON, OFF, ALTS, ALT HOLD, NAV etc. It's worth having a play around with the push to cancel function which I can use to put me into pitch mode that you can then directly control with the thumb wheel. I've also found that even when in FLC, VS can remained armed in the background, so that moving the thumb wheel will change the VS selection "donut" on the VS scale, and the aircraft will now pitch towards the commanded vertical speed. Some more button pushing is required to re-acquire FLC. In many cases, the auto flight remembers the most recent selection made, and although this may now become the active mode, it does not automatically disengage or remove the previous mode. That's why it seems to be necessary to reset the AP/FD just prior to arming an approach sometimes. It dumps whatever was active, and starts with a relatively clean slate. Figuring out the logic pertaining to specific modes and manoeuvres takes a lot of patience, practice, note taking, and trial-and-error. It may appear to be inconsistent, but it is nonetheless just following the logic that was designed into it. Our task, should we choose to accept it, is to determine the exact sequence of commands that will produce a desired result. The PFD option for FL ALERT is supposed to remind you to set QNH or 1013 when descending or climbing through transition if you haven't already. My scale flashes, but won't stop regardless of what's set. Have a look here too if you haven't already: http://www.avsim.com/topic/470992-hawker-flc-does-work/

Huh! Neither has mine. Thanks for noticing Bert.

I thought I'd tried using STANDARD ATM TEMPERATURE and when it didn't work, I thought the text must have been wrong. Looking at your version, I think it would have been a missing minus sign... Thanks for that. The next thing is to make the UTC readout on the bottom of the PFD actually read out zulu time instead of jumping an hour each time it hits a new time zone! In the HS25B_pfd.xml look for utc_value_label and change the <GaugeString> value that starts on line 7956 to read: <GaugeString>%((P:Zulu time,hours) flr 24 %)%!02d!:%((P:Zulu time,minutes) flr 60 %)%!02d!</GaugeString> The original text is spread over about 9 lines and gets replaced by this one line.

The SAT, TAT and ISA displays on the PFD & MFD do not display correctly. The TAT should show the temperature due to ram rise, the SAT should show the ambient air temperature, and the ISA field should show the deviation from ISA, not the ISA temperature itself. Here are some proposed fixes: To display TAT correctly on the PFD: in HS25B_pfd.XML do a search for "tat value label" which should take you to line 7992. Change the variable A:AMBIENT TEMPERATURE to A:TOTAL AIR TEMPERATURE To display SAT and ISA correctly on the MFD: In HS25B_mfd_pilot.XML do a search for "SAT value label" which should take you to about line 7240. Change the variable A:STANDARD ATM TEMPERATURE to A:AMBIENT TEMPERATURE I also edited the ISA section as follows just to tidy it up. Do a search for "ISA value label" which should be on about line 5828. In the section at line 5850, remove the first, second and 4th lines %((A:AMBIENT... %{if} %{end} leaving just line 3, and towards the end of that string, change %!+02d! to %!+d! so it should now look like this: <GaugeString>%((A:AMBIENT TEMPERATURE, Celsius) 15 (A:INDICATED ALTITUDE, feet) 1000 / 2 * - - near)%!+d! oC</GaugeString> All the fields should now display the correct values.

David, Before you install, right-click on the HA100Xv1.2.exe file and it should give you a drop-down list of options including Run As Administrator. You can also "hard-tune" this feature by right-clicking on the file, going to the bottom of the drop-down list, select "Properties", select the "Compatibility" tab, and down near the bottom in the box called "Privilege Level" is a check box where you can select "Run this program as administrator". Clicking in this box should create a tick, and the radio button "Apply" will appear on the bottom of the small window. Click "Apply", then "OK".

How about sox? That's not how you spell "socks"! Really, so what does it spell..?

In the real world, ideally ATC will give you a descent clearance before top of descent, although here in Australia, sometimes it's after! So, you would set that cleared altitude on the FCU or other appropriate acronymical device, but not actually initiate the descent till TOD using either VS, pitch or FLC. VS can be nice to use, but some operators forbid its use for initiating a descent because it is possible to navigate away from a captured altitude with it without requiring a lower (or higher) altitude to be set, so you can actually start descending without a clearance which is of course a big no-no. Pitch will do the same thing. FLC should automatically try and fly to the selected altitude. This ain't written in stone of course, just offered as food for thought...

Absolutely refuses to arm approach this time. No amount of button-pushing, engaging or disengaging modes has had any effect. There are valid LOC and GS scales, but all I can get is LOC 1 and ALT. I'm uninstalling it.