Cameron

Well, it seems like you're being a PITA. Somehow you wish to drag this into some awkward battle, when in reality I had a simple request to bring in further assistance to the original developer of XACARS. This topic is closed.

Starting on page 38 and extending to 51 of the charts manual you will find what you're looking for.

Does the correct VOR pop up on the EHSI showing distance to it? Can you tell me which VOR you are flying from and which one you're going to? Or better yet, your whole flight plan leading up to this point?

"....It also doesn't mean a problem doesn't exist on ours...." "...it's one we're actually willing to investigate for you..." "...I stated we would be investigating this for you." The above are from multiple posts in this thread. Direct quotes by me. At the end of those all, you came back with: "...and now you say you do not deal with with this program?" Read what I just quoted above. It's not about being always right. You deliberately stated I said something that I didn't. You don't need to come back with the silly rolled eyes, or the PITA remarks, but you choose to. I'm hoping you misread or misinterpreted what I said instead. Thanks. Understood.

Who the heck is Chris? Um, what? I said we WOULD look at it and investigate it for you. I also said we would appreciate you contacting the regular developers in addition. I don't see the relevancy of this point. You have an issue, we said we'd look at it, we asked you to contact the original developer too. The only one being reluctant at this point is you, not me.

If you could let them know, that would be great. We do not deal with this program on a daily basis and they'll likely know where to look first. Anything else is shortsighted. Did you, or did you not say the following? - "The very bad news is that I might not be able to fly SAAB..." Perhaps I misunderstood. Did I not understand you right, or did you basically say that if the Saab does not work with XACARS you cannot fly it? No offense, but I think the tally thus far is about three bugs, all of which have been resolved and slated for an update. Most other topics are general questions of people not reading the manual and wanting quick answers. No one brought up perfection but you (probably impossible by any standard), but none-the-less.... They aren't meant to be offensive. It is how YOU decide to read it. See above question about what I believe you stated. Why are you disappointed? Looking back at my post, I stated we would be investigating this for you. I also insinuated that contacting the original developer would be good. Now I'm a bad guy for this? Come on.

I know what you said. This doesn't mean a problem doesn't exist on their end. It also doesn't mean a problem doesn't exist on ours. I asked you a direct question. Did you, or did you not let them know? Understandable, except for the part where you're throwing papers into the fan where if this doesn't work, you apparently won't fly it any longer. At that point, with that attitude, it becomes a bit of a PITA, even if it's one we're actually willing to investigate for you.

Hey, there's a smiley at the end of it for good reason, but if you want to retire to a buddhist temple and reflect upon your past mistakes, or reflect on the possibility that you should have written to your grandmother more often, that's your prerogative. Not something I would have ever suggested, but to each his own. Technically you could have read it and then "f*ck'ed" off if you chose not to buy I guess, right? But that's a discussion for another day and not really why we're here. At the moment, we consider these value added. Quite a bit of care and execution went into writing them. This product is extremely thorough.

Hey, XACARS might be the cause of it malfunctioning too! Have you brought it up with them?

So basically you're saying it works with Gizmo. That de-bunks your previous theory that disabling it fixes the problem.

I always used to wonder the same thing when I walked into my local flight school and they wanted me to buy literature to learn to fly. For some reason they think it's right that I should pay money to read some literature that someone spent many hours and care in doing that is full of knowledge and teachings. Who knew?

Hey, thanks for the compliments!

X-Plane does not run the plug-ins and their custom datarefs in full when using replay mode. Considering these sounds are using a custom built 3D sound engine, the sounds will not work in replay mode.

There's no optimizing on our end. HDR is what it is, and as is overly clear, the Saab gains significant FPS with HDR off. Hurry up and wait is the name of the game. I don't know if it will ever be "fixed" but they will certainly further optimize. By nature, HDR is inherently a big performance hitter with or without the Saab due to more geometry being drawn multiple times. It's only now when you get such a beautifully detailed aircraft that you realize how little overhead is available to you as a user (normally seen by sceneries like you have already mentioned). A good example showing the impact with just the CRJ rather than the Saab. Thanks to Ola.

Nope.

If you read the topic this has been solved.

Correct. Mistyped even though I was thinking exactly the opposite. Figures.

The yellow dot broadly signifies an ARM or ENGAGE. You cannot solely go by this. The EHSI color is more or less what I am interested in. By all accounts, to me it sounds like you were ARMED but not ENGAGED.

Don't those only work in 32-bit? Doesn't sound like an option to me.

I'm not so convinced there's any bug here. Please verify the COLOR of the lights that came on. This is correct behavior. If it's just a one time deal it's generally not a bug. It would be REALLY unlikely for this. Since the Saab is programmed in the Gizmo API, it utilizes that plugin, which has been shipping to customers for MONTHS across many products now. This likely would have came about much sooner than now, especially during our beta period. That said, do let us know what you find.

The KLN 90 will not properly integrate or show AP status on any of the displays. It's in no way realistic to the real aircraft as they were never outfitted with one. We will void any support for any issues incurred while this product is installed.

Left/Right = Heading Up/Down = Vertical Speed These are drag and hold manipulators that spring back to their location when done. In other words, grab the vertical speed one, pull up (lower V/S) or down (higher V/S) and hold in the position until you are satisfied with the number.

Can you tell me which airport this was at so we can run some tests?

We need a screenshot of this error the next time you see it, please.

Correct!