X24

Bret, or Bert?

Hi. I figured it was just a detail - the 777 readme correctly refers to Prepar3d. The quote I mentioned above is from the QOTSII readme. Cheers

Greetings Just downloaded the latest installer, and reading through the EULA, I noticed (for the first time) the following: "b) This software is for use only with the retail version of Microsoft Flight Simulator X. You may not use this software on any platform other than Microsoft Flight Simulator X." Is there something I'm missing here? I'd really like to run this on LM P3Dv4... Cheers,

Their official forum where you can get support is here: http://www.orbxsystems.com/forum/forum/218-orbxdirect-and-ftx-central-3-support-forum/ You will need to register if you have not already, and remember to add at least one product order number in your signature or beside your forum name - something that shows you are a bona fide customer. Good luck! You should check out the FTX forum - there's a heap of really valuable discussion and advice over there. That is their official forum, as opposed to this "unofficial" one I have had a couple of problems too, similar to what you describe, when Central v3 was first released. I always use a download manager - my one is Internet Download Manager - IDM, and I can recommend it. Before you start the download, you are given the option to choose where you want the download to be saved and I save the downloads to (in my case) E:\Downloads\Compressed\.... If you do a full install from a manually downloaded file, Central will look for a zip file. If you do an update, Central will look for the folder where the collection of zips are located. I have seen the installer/updater take quite a while sometimes, as in many minutes. It seems to be looking, then it seems to be copying, then downloading... so I just walk away and leave it alone. Looking at the progress bar sometimes, I think the process is going to take over an hour, but then suddenly it changes, starts installing, and after a few minutes, maybe 10 sometimes, the job is done.

Don't unzip the files. The installer uses them exactly as you downloaded them. In Central, click on the product, and then click on "installation options" and select the one that says "install from my manually downloaded file" and then navigate to the zip file location.

Thee are a few .exe files in your Cheyenne aircraft container folder. One of them will have the characters "GTN" and "750" in it. Use that one. The name of the file is slightly different from that stated in the instructions.

Check to see if the control assignments have changed in your Prepar3D.cfg file. Mine changed after I installed this - my brakes are assigned through FSUIPC and those axes are normally disabled in P3D. After installing the Cheyenne, I discovered all my controllers had returned to their default assignments, which of course conflict with FSUIPC.

I had this today too. I haven't looked in the code yet, but be careful not to exceed the maximum torque on take-off or climb out for too long. It may be designed to generate engine failures like some of their other twins. The other possibility ( I think someone else mentioned it) is the fuel system although I don't think the engine would have lasted that long if the fuel selector was off. I went through another flight from cold and dark making sure that every item was in its proper configuration prior to start, and had a relatively uneventful flight around the mountains in Orbx's NRM. Here's what I have seen so far. After the installation, the default joystick and button assignments all reappeared in Prepar3D. I had previously deleted some of them, preferring to assign them through FSUIPC, so I had to do this again. I can confirm that during engine start, the Ng gauge remains at zero until the fuel lever is set to RUN, and only then does the gas generator spool up begin to indicate. After starting the first engine, the torque went straight to maximum and stayed there until I cycled the propeller lever. The second engine was ok. The altitude ARM button takes some persuasion. Click it once, and it quickly switches ON then straight back to OFF. I had to do it multiple times before the ALT ARM indication registered. I tried this multiple times with the same result. The altitude captures anyway, regardless of whether ALT ARM is indicating or not.. In flight, using the mouse to move either throttle caused both throttles to move together. I have dual throttles (TM Warthog). Throttle 1 would move both levers, throttle 2 would move neither. However, the engine response to my TM throttle inputs was correct. Placing the mouse over throttle 2 in the VC showed the "Throttle 2" tool tip, and moving the mouse would change the power on engine #2, but the throttle itself did not move in the VC. Placing the mouse over throttle 1 in the VC showed the "Throttle 1" tool tip, and moving the mouse would change the power of engine #1, but both throttles would move together in the VC. The error seems to be with the VC modelling. Later in the flight, it went back to normal, with both throttles in the VC moving independently again. The handling was good, no complaints about the flight model. Power response seems good over the range of power lever movement, and controlling speed on final approach does not take too much getting used to.

@ryanbatcundHi Ryan, tried sending you a PM but I guess your Inbox is full

PM me - I have what you need.

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

Hi Bert I'd also like to add my thanks and appreciation to this growing list. I've recently been able to get back to flying the Hawker (and the TBM) 850 with your mods installed and it's been great being able to shoot coupled LNAV/VNAV approaches where I can find them. I'm off to look for any mods for the Phenom 300 now. Cheers from OZ - you are a champion!

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.

Evan The performance file goes in the AircraftTypes folder, and the template goes in the AircraftTemplates folder. From that you should then be able to create individual aircraft files for the various regos you fly. PFPX will create and store them in the Aircraft folder. PM me if you have any issues.

I sent you a personal message (PM) with a link for the training manual. I haven't seen a startup guide similar to what ES produced, but autogyro I think on these forums and possibly some others have produced kind of pictorial tutorial step-by-step guidance for getting started. Ialso recommend that you watch the videos that Tim Garris aka FSMania has made, they are entertaining and informative and inspiring to say the least, and you can find a cold and dark setup on YouTube here. Good luck!

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.

Can you PM me and I will send you a link for obtaining a copy of a pilot training manual.

Yes indeedy! From what I can gather the TopCat files are quite a mission to produce which is why they only exist for a handful of aircraft. I don't think it's as easy as just building some tables. Never tried, actually...

@C525B Thanks for the modified files - they work really well and after getting used to the overhead panel working the way it used to, now I'm getting used to it worked the way it is supposed to. Fantastic - thanks!

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.

Glad to help. Hoping to get onto the OEI performance over the next few days.

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/

You guys...!

@ barrel_owl - thankyou for your kind words. These forums are a fantastic learning resource and it's very humbling when you begin to realise the level of knowledge, experience, dedication and effort that is evident. How do you thank everyone? I'm just scratching the surface really with a lot of this stuff, so it's nice to be able to share what little I do know (I was a dispatcher in another life). I suspect too that producing tables for FSBuild and PFPX helps to feed the OCD, so it may not be entirely altruistic! Glad you like it though...