MELKOR

Chuck, I'm not clear if updating to 3.2 scenery would require you to re-install your scenery add-ons. They say the content and scenery updates are "optional", but they never do say whether upgrading those will impact third-party add-ons! Personally, I want ALL of the updates, not just the client update! But, at the same time, I don't want to have to re-install all my third-party things. Does anyone have a definitive answer to this? Thanks.

I am talking about MOVING the CDU, not SIZING the CDU. Thanks.

My issue is that I cannot move the CDUs around once they have popped up. I'm pretty sure that worked properly during my first couple test flights. Anyone else see this behavior?

I was a pilot of the PMDG Fly! 777, and have a sneaking suspicion that this version might be somewhat more comprehensive. =) Thanks Rob for the update, and thanks to the broader team for all the hard work, every product PMDG has released has been of the highest quality! Best regards, and I look forward to what the future will bring to our favorite hobby! - Bill

"The cheque is in the mail!"

I fly on VATSIM with FSInn, and I certainly see traffic on TCAS. Would you please post a screenshot showing the ND, and the FSInn "Radar" and "Network" windows? Capture the screenshot at a time when you believe that an aircraft should be showing on TCAS.

Ever since PMDG started modelling random failures (I believe with the 747?), I always fly with them turned on (I vary the probability based on whim), and have had many scores of failures, many of which were "catastrophic" - although I've never had any lead to a crash. Even after all that experience, I still find my adrenelin rushing when a bell goes off. I recently had an engine fire during an approach with the NG on VATSIM, and that got my attention "real quick like".

I've had no issues with these drivers in FSX (as of yet), but I once had the drivers deadlock (which is worse than a crash, they at least half-&@($* recover in a crash, albeit screwing up any game you may have been running) while viewing a YouTube video. Ironically enough, the video was one of the four in RSRs recent presentation! :LMAO: (Great presentation BTW, Robert's a natural charismatic speaker, no wonder he ran for office!)

To confirm this is not a joystick problem, you can use AxisViewer to compare the reported axis position versus the reported control surface position.http://library.avsim...php?DLID=165339

Actually, I mostly fly PMDG planes, that's why I posted here. In my experience, the positions reported by SimConnect seem to match up very well with the actual control surface positions.

I finally got around to polishing up and writing docs for a little tool I wrote for myself last year, and recently added it to the file library.http://library.avsim.net/esearch.php?DLID=165339&CatID=fsxutilHopefully some of you will find this useful, I never fly without it!

Surely you guys mean x1080 when you say x1024?

Thanks Chris

Same thing here. I put back the original files, and now I'm reluctant to try this update at all... how to you find the changed flight model?

Before you run out and get a USB headset + mic, consider this:Most motherboards these days (and, well, for the past 5 years or so) have an onboard Realtek chipset, which supports your standard miniplug headset + mic at front, and the usual stuff at the back. Caveat: You have to configure the chipset using the Realtek drivers to allow for separate front vs back in/out, the default is to override the back in/out if the front in/out is used.And, if you have a separate soundcard, there is nothing stopping you from also using the Realtek chipset for your headset/mic.I've been doing this for years with great success (I'm no audiophile, the Realtek chipset is "good enough" for me for a headset).

So, let me get this right: you've got FSX installed on an external HDD, and you're trying to use it on two different computers??You need to be an expert user of FSX if you expect to be successful doing that... (there are FSX files installed in c:Users and c:ProgramData that will not be captured on your external HDD, registry entries, and god knows what else).Good luck!

You know, I wonder is this behavior is related to the known SP1 "Idle Thrust" issue. Remember that when on VNAV PATH, the plane will follow the descent path regardless of your speed, and a higher speed means a higher descent rate.Try using the "G" key to raise your gear when you take off, and see if that makes a difference to your descent.

Iain, I've noticed the exact same thing, you should report a bug.

With regards to Alt-Tab stability. In the past, I've had many stability problems using Alt-Tab with FS9 and FSX. Because of that, I've always switched to Windowed mode (using the menu or Alt-Enter) before switching to a window in another task. And, since doing that, I've never had any sort of stability issue.

A suggestion: in order to get some VATSIM controller coverage, arrange something with the Seattle ARTCC events coordinator.http://www.seaartcc.net/general/contact.php

I guess you don't watch Mythbusters.

He probably means Issue #1 one listed in the above pinned article.

Ugh. Yep, almost certainly the monitor. Sorry bud.

The JS41 FMS is nothing like its big brothers. So there is nothing to "improve" in SP2...I quote Capt Randazzo from an earlier post: Use "Direct To" to your next waypoint, then engage NAV.

I'm wondering if anyone has written a gauge that shows the position of a particular joystick axis, versus the "actual" position of the axis as far as FS is concerned.Let me give an example:In planes that have an auto-throttle, the plane will control the position of the throttle, and the position of the joystick axis is ignored.However, if I now disconnect the auto-throttle, the throttle position will suddenly "jump" to wherever the joystick position happens to be at that moment.What I would like to be able to do is prevent that jump by positioning the joystick axis such it matches the "actual" throttle position, prior to disconnecting the autothrottle!Is such a gauge even possible?Thanks!