Jump to content

xpst

Members
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About xpst

  • Rank
    Member
  1. Hi Goran ! > details about the flight before the crash The "flight" was fine. I killed a brake during my braking "training" on the ground (I got myself some rudder pedals, but I just can't manage to apply equal pressure on the pedals when landing, and keep having to pay for repairing the grass). This plane is costing me. A lot. The brake failed pretty fast, I'm not sure how realistic that is, but then the plane simulated the failed brake perfectly (swerving to the correct side, etc.). For me it's easy to reproduce : 1) either kill a disc by blocking your airport for 15 minutes, powering up to 90 knots and braking, powering up and braking, etc. or set gear/comp/3/brake_disc/wear = 1.000000000000000 in the airframe state file and start X-Plane. 2) Go into maintenance manager -> landing gear
  2. I get a crash which looks like a maintenance manager bug when handling a worn brake disc state. (I was testing my toe braking skills by zipping up and down a long airfield, and finally killed a disc). Now, as soon as I go into maintenance manager -> landing gear, X-Plane crashes with : 2019-02-19 22:45:28 TBM900[fail.c:932]: Component right gear brake disc has failed due to excessive wear (worn: 100.000000%, slope 1.0). You can prevent this by observing performance limitations and servicing the aircraft regularly in the maintenance hangar. 2019-02-19 22:45:28 TBM900[fail.c:935]: Failure impact: sim/operation/failures/rel_rbrakes 2019-02-19 22:46:15 TBM900[maint.c:2039]: assertion "fail->fail_name != ((void *)0)" failed: Workaround which worked for me : I set airframe state file value gear/comp/3(or /2)/brake_disc/wear value to < 1.0, then maintenance manager access worked again, and I could pay $$$ for fixes. Log.txt
  3. xpst

    CTD

    > ... if you have AI, to get rid of it and that CTD no longer happens. OK, I have deleted the three AI planes that were there by default, to see what happens. Thanks Goran !
  4. xpst

    CTD

    I have had this "Something reinstalled our exception handler" twice now. First time was a few minutes after starting up, taxiing. Second time (log attached) was halfway through a 3h flight, cruising on AP, not doing anything in particular :-( Am flying with a parachute lately, was able to reach ground alive. 11.32 and 1.1.4c Log.txt
  5. xpst

    TBM 900 v1.1.4c Update Released!

    No problem for me, worked as usual.
  6. Hi, Looking through the TBM900 checklists, I notice this "L.H. brakes" check. I wonder why it is left-hand brake instead of right-hand, or not both ? Also, I think the Hot Start supplied checklist is missing a "Pilot OXYGEN switch ... ON" check. Given that there was a real TBM loss, probably caused by an OFF state, I've added it to my checklist !
  7. xpst

    CTD with X-Plane 11.31rc1 and TBM 1.1.4b

    Hi MD111977, I'm not in any way connected to X-Aviation, and I understand you, but I'd recommend some patience. When the fix is out you will probably be very satisfied.
  8. xpst

    CTD with X-Plane 11.31rc1 and TBM 1.1.4b

    Hi X-Aviation Support, Any idea now of a tentative availability date of a workaround or fix (for when rolling back to 11.30 is not an option or difficult) ? Thanks !
  9. xpst

    CTD with X-Plane 11.31rc1 and TBM 1.1.4b

    Hi All, Exactly same crash for me after upgrade to 11.31 suggested by X-Plane.
  10. Works for me. Maybe : Is the recommended frequency flashing ? If so, make sure your radio is selected/on ?
  11. xpst

    TBM 900 v1.1.4 Update Released!

    Hmmmm... I replaced the battery and succeeded starting twice now. I don't really understand why it did not even work with the GPU though. Either on battery or GPU I got to 30% NG in 30s. If I get in trouble again I'll post log.txt too. It didn't seem to have anything interesting there either though. Thanks Goran.
  12. xpst

    TBM 900 v1.1.4 Update Released!

    I upgraded from 1.1.4a to 1.1.4b today. I had no problem with 1.1.4a. All of a sudden I can't start the engine any more, ITT rises very quickly to 700+ degrees, there isn't the pause at 40% NG, then it overheats and I have to cut off fuel. I tried letting the engine start tutorial do it and it works. Then in the tutorial I start the engine myself, and it again works and I can fly. When I try outside the tutorial, with a cold engine, with or without GPU, inertial separator off or on, it won't work. The inlet and exhaust covers ARE off. I do not understand. I have done it many, many, times before. Nothing interesting in the log. In maintenance manager everything is as new. XP version is 11.30 Any ideas ? TBM900_Log.txt
  13. xpst

    TBM 900 v1.1.3 Update Released!

    I guess it's in some way related to this "rudder calibration"... http://forums.x-pilot.com/forums/topic/15387-nosewheel-steering/
  14. xpst

    TBM 900 v1.1.3 Update Released!

    > you don't have a dedicated axis defined for rudder Well, the keys are assigned to the rudder from the beginning. Actually, since I only get a few degrees of nose wheel turn, it's actually a lot gentler than using the rudder "pedals", and the plane doesn't swerve as much when steering.
  15. xpst

    TBM 900 v1.1.3 Update Released!

    Hi, I have been trying out 1.1.3 on XP11.26 for a few days. And very happy with this plane. I have no pedals, so I'm using a few keys for that. However, I notice that nose wheel steering works with my yoke's roll input (the nose wheel turns a few degrees, not all the way) when I start up the simulator, IF I don't touch the rudder at all. It's just turning enough to taxi slowly if there are no sharp turns, and to get off the ground. Once I touch the rudder pedals/keys it doesn't work any more. Is this the expected behavior ? Thanks !
×