Jump to content

RobW05

Members
  • Posts

    300
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by RobW05

  1. Maybe you can provide the log.txt to make it easier for the devs to look into it. Creating a new airframe should always be possible. Honestly I don't think it's overly difficult to get airborne. I can get it started and ready to taxi within less than 2 minutes if I want to. The airframe I use for "normal" flying is months old and all is good with it. You get used to it really quickly and not much can go wrong if you take care of the red lines. A beast? Yes it is! 850 horses want to be treated with respect.
  2. So you say you can't create a new airframe as long as the engine is burning? That would be weird. It always worked for me. (I did scrap a few airframes lately during "crosswind training" ) Which steps are you taking? Is the "create new airframe" button greyed out or non clickable?
  3. Good to hear that it works! Happy flying!
  4. It´s under Engine/Basics. Just type "reverse" in the search box and you will find it.
  5. Ok G, I think there we have it. You need to assign the command toggle thrust reversers, the general one without #1 at the end. It should be working then.
  6. You don't need spadnext. You only need the toggle reverse command assigned to a button, then you should be able to move your power levet through the gate. Maybe you could post a screenshot of your power axis and button assignment here?
  7. It's exactly all the little things like this which make this model so enjoyable. In the forums many call it the best GA plane ever made for a simulator. (for good reason)
  8. I too would say that the main gen load to decrease after startup is totally fine and to be expected. A constant high main gen load would be something to worry about.
  9. Not at my pc right now, but last time I checked the MFD keypad was able to pop out by clicking on its top.
  10. Did you release the parking brake?
  11. Same as in your first thread, check xplane default failures.
  12. RobW05

    Main Door

    That sounds like you had xplane's default failure system on and ran into one of them. You can reproduce it if you go the xplane failure menu and manually fail the door. If it was from the TBM the problem would have been persistent.
  13. You need to press the joystick first, then you will be able to pan around. Pressing the joystick again will revert back the map to be centered on the aircraft's position.
  14. Tech support guy, haha, if you only knew... The only questions I can answer are the ones I stumbled upon myself.
  15. Turn on HDR in xplane graphics settings The visual effects slider must be at High (HDR).
  16. Ok, no problem, I just couldn't imagine that the TQ6 would create such problems. By the way, could it be that you have some special drivers or software installed for the TQ6 which would interfere with xplanes own settings?
  17. Jack, this is not meant to be rude in any way, but you do know how the reverse logic works in the Hotstart TBM, do you? This is from the manual: Please note that in the simulation, as in the real aircraft, you cannot move the throttle from the POWER range into the TAXI and REV ranges without lifting the flight idle lockout to get over the flight idle stop gate. To actuate this lockout, you will need to map a button or key to the sim/engines/thrust reverse toggle command (aka “Toggle thrust reversers”). Pressing this button or key will lift the lockout. NOTE Activating the “reverse toggle” command does NOT engage reverse thrust. The default X-Plane behavior has been overridden by the TBM900 simulation to behave as in real life. Instead, activating this action simply lifts the lockout tab. You then need to move your throttle past the flight idle stop and into the TAXI or REV ranges. Once in the ranges, you can release the “reverse toggle” button/key. The lockout tab will not re-engage until you again transition the throttle into the POWER range. This means all you need to do is to map your physical throttle axis as "throttle" in xplane, no curve whatsoever needed. It will control the whole range from alpha over beta to reverse, but to get into reverse you need to press a button which you have assigned to the "toggle reverse" command.
  18. Hmm, ok but it doesn't need any specific switches. You just need to bind any button or even a key for the specific command.
  19. Just curious, what makes the TQ6 so special that it doesn't work with the TBM's reverse logic?
  20. RobW05

    CTD

    Xpst, I do understand your frustration. But we need to remember the TBM pushes xplanes limits in so many ways, like little or no other payware does. I think Hotstart could easily get rid of the problems if they stop coding around xplanes limitations and just provide default functionality packed in a nice looking model. That would mean no custom G1000, no synthetic vision, no custom weather radar or TAWS, etc... ... You get the idea. I highly appreciate what they do even if that means I have to stop using specific third party plugins temporarily.
  21. Your welcome! And just for the record, here's a flight planning KJFK to KJAC. Obviously this would never be done IRL.
  22. Hotstart has it correct and the TBM POH performance is correct as well. First you need to consider the conditions given for max range of 1730 NM: ISA conditions, MTOW, no wind, one pilot, 45 min fuel reserve, cruise altitude 31000 ft, long range cruise settings If you put in these conditions in the POH performance page you will really get a result of about 1730 plus reserve. For your planned 1300 NM leg you should even get away with 4 people and normal cruise settings if you leave all the other conditions untouched. Of course, mix in some heavy crosswind and things change drastically. You can use the real world POH, Hotstart has a link to it in their quick start guide in section 9.
  23. Check if you have xplane's own failures enabled. If yes, fix all and disable it. Hotstart's failure system is far superior.
  24. It was just a guess, because you said you did start it with the GPU.
  25. That is because you most likely left the source selector at "GPU" position instead of switching to "BATT" after disconnecting the GPU.
×
×
  • Create New...