gscottfuller
-
Posts
27 -
Joined
-
Last visited
Content Type
Profiles
Forums
Latest X-Plane & Community News
Calendar
Downloads
Store
Posts posted by gscottfuller
-
-
I am still unclear how to revert to the 11.41 format with the latest AIRAC data from the FAA but without using Navigraph for which I don't have an account. Is there a step by step procedure someone could please post? Many thanks.
-
Does the Navigraph fix for the ILS issue work for those of us who don't have Navigraph accounts? If not, doesn't do much good. I get my AIRAC updates directly from the FAA so can't use that fix. Thanks.
-
CJ - Yes. You have to quickly learn the art of troubleshooting to fly this plane. It is the most finicky plane I've run across in any sim. I had one normal flight after fixing this control problem and already another gremlin has shown up. Yesterday, the pitch control stopped working. I tried restarting X-Plane, recalibrating the Yoke, checked the AP Trims switch several times, checked the maintenance status of everything. Finally had to go to a new airframe which solved the problem. My plan has been to get really comfortable flying the TBM, then start using it with Pilots Edge. At this point, I don't trust it enough to use on Pilots Edge where you don't want equipment problems when your focused on learning ATC and airspace skills. Thanks.
-
I am also seeing 2016 data on the MDF boot page and suspect it could be causing nav issues I'm having. I have updated the X-Plane nav data to the latest AIRAC cycle using FAA data following the procedure that has been in effect since before 11.50. You basically download the CIFP file, move it into the X-Plane Custom Data folder and convert it to the format: earth_424.dat. Has this procedure changed in some way? What do I need to do to insure that the TBM is using the current data? Thanks.
-
Reporting back that the BRG1 problem now seems to be affecting other planes in X-Planes so not a TBM problem. Not sure if it's a navdata issue or what. Have tried all the other troubleshooting steps with scenery, plug-ins and preferences to no avail. Thanks for all your responses.
-
CJ - Thanks for suggestions. I seem to have solved the problem. First, it turned out to be an X-Plane issue as it repeated with a stock SF-50 Jet. I followed the standard X-Plane troubleshooting sequence (which I only just discovered in a video on their support tab). I removed all plug-ins and custom scenery and still had the problem. Next removed all preferences and that solved it. Added back plug-ins, custom scenery and then preferences one at a time - basic flight controls, graphics settings, etc. So far, it has not recurred. Last step is flight control curves then should be good to go.
-
On the takeoff roll, the TBM immediately went out of control and began a nose dive into the runway while accelerating extremely quickly. Lost complete control and paused before it actually crashed and burned. Then, got a new airframe and started up on the same runway and the speed tape was registering 45 KIAS while standing still. Weird things going on. I've attached the logs. I rarely have a completely trouble free flight on the TBM. Getting close to giving up on this plane. I have an excellent PC build and have no trouble whatsoever with stock X-Plane equipment. Any help appreciated.
-
I had a similar towing issue once and realized I had set the chocks when I parked! I assume that has been ruled out already.
-
Please consider a fix for this issue on the next update because not using Vulkan just to have the AOA meter doesn't make sense. Thanks.
-
On 12/13/2020 at 4:48 PM, Goran_M said:
Not really sure what is happening here on your side, but we'll investigate a little further.
Just checking in on this issue. Still not able to see either BRG1 or BRG2 arrows on the OBS dial. Could that be impacted by scenery plug-ins like Orbx TE or custom airports? But I have this issue everywhere - even away from custom scenery and airports. Thanks.
-
On 12/13/2020 at 5:55 PM, CJSouthern said:
For what it's worth, I've been "getting to know" the G1000 & AP systems for a few days now - and have discovered quite a few "gotchas"; I'm assuming that most are correct G1000 / AP behaviour but as I don't have any experience with G1000 IRL I can't say for sure.
Some of the following might (or might not!) help.
1. You need to turn on the Flight Director by pressing the FD button before you can select a lateral navigation mode.
2. You need to turn ALT on before pre-selecting an altitude; if you do it the other way around it'll change whatever you've entered to whatever altitude the aircraft is currently at.
3. If you don't engage the AP quickly enough you can get a situation where the aircraft is "out of position" relative to the waypoint you wanted to track to and when you do engage it it won't track to ANY waypoint. From there it can be a real wrestling match; usually highlighting the waypoint and selecting "activate leg" won't work - sometimes it's possible to get it to work by using Direct To (or just activating a waypoint further down the list). Sometimes it just won't steer the aircraft in NAV mode no matter what I do; at that point all I can do is use HDG mode. Some times I'm able to get it working again, but I'm really not sure what the "secret sauce" is (I think it's not only a combination of "what I do" but also "where the aircraft is relative to waypoints" as well).
4. If you have an enroute phase entered - and you have an approach phase entered (but not activated) - but you don't have an arrival entered - it won't track from the last enroute waypoint to the first approach waypoint unless you activate the approach - even though the waypoints are listed in sequence. You HAVE to activate the approach or it'll just say "arriving at waypoint" and then carry on past it.
5. Vertical nav has a 5 min timeout. If you arm it more than 5 min before top of descent it'll just dis-arm after 5 min.
6. Vertical nav doesn't navigate to a final approach fix altitude.
7. Vertical nav still respects selected altitude - so this needs to be set lower than (or equal to) the VNAV altitude or that's where it'll level off (or more likely the reason why it won't start to descend)
8. Altitudes next to waypoints are for "information only" if they're in white (white "sheds light" on the situation). If you want the VNAV to act on them then you have to select them and press enter to turn them blue. If they're in small blue then they're "per the database" - if they're in large blue font then that's something you've over-ridden the database with.
9. VNAV sometimes just blatantly refuses to control the aircraft - seems to happen when I'm "slightly behind the aircraft" and forget to set something correctly prior to TOD; from that point all I can do it use VS to get the aircraft going down using guideance from the VNAV section on the MFD.
Hope this helps someone ... and in return if those who know more about it than me can help me understand where I'm going wrong that would also be greatly appreciated.
CJ - Your observation about engaging FD before a lateral AP mode has consistently worked now through several flights -- thank you. If I engage FD, it then allows me to engage NAV which previously I could not do. But it's worth noting, that's not the same as all other X-Plane planes I've flown. All but the TBM allow you to arm NAV or FLC on the ground without having the FD on. Once in the air, engaging AP will then activate NAV, HDG, FLC or VS. So I'm not sure why the TBM was set up to require FD before arming lateral and vertical modes. I have not tried your VNAV suggestions yet as I have not been using SIDs and STARs lately where VNAV becomes more relevant. Thanks.
-
Is there an ETA on the next Hotstart update that will remedy the "navdata" issue? And if it's not soon, should I revert to the older version of X-Plane in order to fly the TBM with ILS working? By "navdata", I assume we are talking about something in the X-Plane software code, not the AIRAC data for the GPS, correct?
Thanks.
-
Thanks - was the Nav 1 radio -- now fixed. What through me off was that it happened in cold/dark with no battery on.
-
On 12/13/2020 at 4:50 PM, Goran_M said:
The ILS bug is something we've been aware of for a while. It's fixed for the next update. In the meantime, reverting back to X-Plane 11 navdata (not 11.50) will fix this for you.
Not sure what you mean by reverting back to X-Plane 11 navdata. I'm running the latest version of X-Plane 11 and I regularly update the GPS data from the FAA on the AIRAC cycles. Should I be doing something different for the Hotstart TBM? Thanks.
-
Appreciated.
-
My latest issue with the TBM is -- the second it loads up there is a fairly loud static that permeates the audio. It cannot be eliminated either with a new airframe, reloading X-Plane or anything else I've tried. Basically, you have to mute all audio to fly the plane which is no long term solution. Again, I don't have this problem with any other planes in X-Plane so it's particular to the TBM. I have already re-installed the Hotstart once so hoping I don't have to do it again and that there is a less drastic fix. I love this plane but find I spend more time on the ramp troubleshooting issues than enjoyable flying!
-
Thanks CJ for these observations. I'll check them out on my next TBM outing. Some of the items you describe have not been an issue in other planes but if they help with the TBM, that's great.
-
Yes, I've turned it on and cycled through to the GPS window in BRG 1 which immediately shows the problem. It says NO DATA rather than showing the airport or waypoint that is active as shown in the screenshot. I cannot get the BRG 1 window to register the active waypoint in the FPL which in the case of the screenshot is KVAX.
-
The issue of the intermittent failure of the NAV button in the AP has gotten worse. Today while in flight, I could not get the NAV button to arm at all so could not fly an ILS approach using AP to the destination airport. I am not running any plug-ins in X-Plane and do not have this problem with other planes. Any ideas how to troubleshoot?
-
Still not seeing the bearing needles in OBS. Any help appreciated. See attached screenshot showing the Direct To to KAVX not being verified in the GPS bearing window or the OBS dial. Thanks.
.thumb.png.20bf7707593071df2c8ba2f9ee2e8d9a.png)
-
Thanks. That worked.
-
I have not been able to get the AOA gauge lights to reflect off the glass reflector so cannot use the gauge when flying. I have raised the reflection setting to highest in the X-Plane graphics settings and it has no impact. I've tried messing with the angle of the glass reflector but has no impact. But the lights themselves seem to be operating OK. You just can' see them. Is there something else I need to do to use this gauge? Any help appreciated.
-
Just uninstalled TBM and reinstalled. Opened up the new TBM in X-Plane with same results. The BRG 1 and BRG2 both say "GPS" "No Data" rather than displaying the Direct To Waypoint in the FPL. And again no bearing arrows in the OBS. Please let me know what other troubleshooting steps I can take. I am not having this problem with any other planes in X-Plane. Thanks!
-
Happens every time I load the TBM 900. Any suggestions? Should I uninstall and re download?
Thanks.
.png.d88902cedd8284cd32e85fd7d2322b42.png)
No bearing needles displayed
in TBM 900
Posted
I have had this same problem and never found a solution. Nothing I did had any impact. It's frustrating as I use those bearing needles on other planes for flying airport patterns and other purposes.