Jump to content

CJSouthern

Members
  • Content Count

    101
  • Joined

  • Last visited

Everything posted by CJSouthern

  1. Running TBM V1.1.13 on XP 11.55. Previously worked fine under XP 11.52r3. Hi all - I haven't flown for a few months. When I started XP it updated itself to v11.55. When airborn with the AP configured and engaged on a horizontal navigation mode it disconnects instantly whenever I tap the button to trim nose up or down. I've deliberately crashed the model and sporned a new airframe ... same result. Also getting an issue with the fuel pump; on v11.52r3 the pump wouldn't come on when set to auto. Now under v11.55 I also get a fuel pressure warning if I start in auto mode; to clear the me
  2. Another option - perhaps just add the maintenance manager to the menu system much the same as we can use for getting to the additional info for ECS / gear / engine etc - and then have a checkbox that hides it all the time when the aircraft isn't moving? Can't say it bothers me, but would seem like something pretty easy to impliment.
  3. Good to know that I wasn't the only one!
  4. Thanks for all that you and your team do Cameron - I appreciate it.
  5. If you ever win Lotto, check these out ... I'm still drooling ... https://slawdevice.com/en/
  6. At the risk of starting a flame war, my 40 years of experience as an IT guy taught me that in terms of reliability & compatability, AMD's "walk" never seemed to quite match it's "talk". Personally, I run X-Plane on an Intel 10700K (not overclocked) on a Gigabyte Aorus MoBo with 64GB RAM - no plugins - and ... everything just works (with the exception of the occasional glitch). Take that as you see fit.
  7. As an "aside", I suspect that P-Factor would make the aircraft a nightmare on takeoff for people like me who fly with a yoke but no pedals (thus have no rudder control). For what it's worth, I started my TBM simming with the 930 in MSFS 2020 and found it to be a worthless piece of cr^p (I since uninstalled the entire product) - so many many things that just don't work right (if at all). If you want a "pretty game" then I guess it's fine, but if you're wanting an accurate simulation then they're as different as chauk and cheese.
  8. At the end of the day it's a simulator; so it should simulate. If you leave something a certain way in a real aircraft then guess how it'll be the next time someone returns to the aircraft? It's doing what it should do -- and it's one of the features I like.
  9. For what it's worth, over the past week or so I've flown the TBM from Nelson, New Zealand to Tahiti to Honolulu to Los Angeles to Montreal to Goose Bay to Greenland. Most of those legs are 2000 nautical miles plus - and took 10 hours plus. No issues.
  10. You might like to check that you don't have the random failures feature of X-Plane turned on. Load the model and then click on Flight -> Edit Failures. Start by clicking the "Fix All Systems" button.
  11. I've seen this issue too. For what it's worth, all you need to do is rotate the small knob one way (I think I roll the mouse wheel up) - and it takes you to the list of stored flight plans. So not quite 100%, but still quite usable (I use it all the time).
  12. For what it's worth, I flew the beta last night and the rain effects looked great (RTX 3080 based system, no addons). Also for what it's worth, I have mixed experiences with NaviGraph; I've had some great support on a couple of issues but was very surprised to discover that their Navigraph Charts product doesn't include altimetry for enroute phases which is "kinda important" for IFR flight planning.
  13. I'm no expert, but I would suspect that that would cause an issue. I can only see a limited number of practical options (the phrase "you're telling me what we need but I'm telling you what we have" from the Apollo 13 movie comes to mind). 1. Find a way to make what you have give the model what it needs 2. Use hardware that's compatible with the model 3. Fly a different model that's a better fit with your hardware Not seeing a "magic wand" option here unfortunately.
  14. To be honest, my issues have mostly been "own goals" (with a few exceptions). One thing that some other kind folks helped me discover is what's under the Flight -> Edit Failures Menu; if you haven't already, you might like to see if random failures have been programmed and/or just hit "fix all systems". I'd be interested to hear if this is the source of any of your problems.
  15. Per my post above (and elsewhere here) I had the same issue. It went away the INSTANT I updated using 11.41- format data. If I update using 11.50+ format data then the TBM shows data that's about 4 years out of date. Using the 11.41- format it shows the current AIRAC cycle.
  16. Thanks Goran, I've not used Discord before, but seem to have figured it out enough to ask a couple of questions there. Hopefully I'll quickly figure out who's who.
  17. Thanks Goran. As a test, once I arrived at NZCI after I got a new a new air frame I parked up - switched the generator off - turned on all the anti-ice systems and landing lights and flattened the battery. MFD cut out at around an hour later at 11 volts - and (using the "output battery voltage" facility in XP) I took the battery to less than 1 volt ... engine kept running just fine - so pretty sure we can eliminate the battery as being the cause. Can you tell me a bit more about the sim failure logic? eg "even with a relatively new airframe (best guess maybe 20 hours total) and "all
  18. Thanks for that - but it doesn't quite add up; I would have though that that would have resulted in a CAS Master Caution of "Main Gen" and "Low Voltage" - and there weren't any CAS alerts prior to the shutdown. You can see in the screenshot that there's still no "Main Gen" alert - and although there is a "Low Voltage" alert I'm almost 100% sure that wasn't there prior to the shutdown (I was there in front of the screen the whole time). I do seem to get Main Gen alerts when starting from the external source, but they're well and truly sorted prior to take off.
  19. Thought I'd treat myself to a flight from NZCH to NZCI. Climbed up to 31,000ft - and at some point during the cruise (had power set quite low - and fuel flow at 39GPH (which is the most relevant figure I could find for best range)) and ... the engine just quit. Notes: 1. At the end of EVERY flight I both refuel & check the maintenance manager - EVERYTHING was in the green prior to takeoff. 2. I tried an inflight restart; Ng was in the zone for introducing fuel - igniters were on - but no ITT rise (tried several times) - eventually flattened the battery. 3. Checked logs
  20. Ah - roger. Thanks for that. I'm guessing that was Jason? (I asked him the same question via YouTube). Does seem like a bit of sloppy wording in the manual then given that it refers to "pulse and landing lights" when in reality the landing lights can never pulse - only the taxi lights.
  21. Thanks for chipping in. I could be wrong, but I'm interpeting it like this: - The TBM 900 only has the one switch to control both landing and taxi lights. - Therefore, if the manual is referring to "landing lights" then I'm assuming that it's meaning "that switch in the landing light position" - So when the manual refers to "controlling landing light flashing" I'm assuming that that's with that switch in the landing light position and with the pulse light switch turned on. It seems disingenious to me that in order to make the landing lights pulse one needs to have to put th
  22. I can do, but I doubt it'll add anything that I can't describe. Basically, 1. If I turn taxi lights on - and leave pulse off - I see two taxi lights on in a steady state. All good. 2. If I leave taxi lights on - and turn pulse on - each light altenates between "taxi light brightness" and "landing light brightness". I don't think it should do this. 3. If I turn landing lights on each light remains at "landing light brightness" regardless of whether pulse is on or off. Is that what you get? If I'm reading the book right then when taxi lights are on - and pulse is off - t
×
×
  • Create New...