Jump to content

oldflyguy

Members
  • Posts

    196
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by oldflyguy

  1. 18 hours ago, Pils said:

    Inputs to the FMS don’t change anything but the FMS.

    Thanks very much @Pils!  For the link as well.  I was under a misconception as to how that all worked.  So, as I go about redoing all of my saved states, will those states then keep the payload at the saved time?  And if I use "sensed fuel" will that be sufficient for proper calculation.  Or do I have to use the FBO sheet?  Thanks again.

  2. I typically fuel up using the fuel truck panel and the interior fuel panel.  Select these from the CL650 plug in tab.  This is very straight forward and I do think you are missing something in the checklists as starting a jet engine is way easier than starting a Piper trainer.  Never use the XP weight and balance window for this aircraft model.  Have you been able to watch any tutorials?  I recommend you give "foxtrot alpha aviation" on youtube a look.  A RW CL650 driver with terrific tutorials.

  3. Hello @Vulcanyz.  Well, either you are not following the checklist and are improperly configuring because there is no reason the engine won't start.  It's a pretty easy process in the Challenger.  Or, your install could be corrupted.  I don't know if it would help but you could attach a log.txt file (XP root folder) to your post for review.

  4. No real information provided.  So, first things first.  Have you configured and updated your Navigraph FMS Data Manager.  That's all it should take as the CL650 uses the XP11 data as it's source.  Now that I'm thinking of it - looks like you have a monthly subscription to the Nav Data.  I don't know if Navigraph Charts is included with that.  I will check further and let you know what I find.

    • Downvote 1
  5. 4 hours ago, Cameron said:

    f so, I'd expect that you guys set up a test environment and see if you can reproduce the error.

    Have you requested that the "X Life" devs do the same?  The TBM works wonderfully with XP (along with many plug-in's) some don't work.  It's not a perfect world.  Not an XP issue.

  6. Hi @Vulcanyz!  I believe this is due simply to the XP11 lighting model and also (to a lesser degree) to the color/gamma selections of the monitor/TV.  There isn't any way to fix it other than your specific monitor settings.  Which will of course upset some other color/gamma situation in the sim...LOL!  So, live with it until XP12.  

  7. I'm curious whether others have found that the CL650 Reverse Thrust Lever Up (left and right) no longer work in the latest update.  At least I was not able to do this.  The CL650 bindings for this worked fine in the earlier versions.  No worries as I found the generic XP reverse thrust controls for engine 1 and engine 2 worked fine.  I'm wondering if this is a new bug.

  8. @Oscar PachecoThank you for attaching the log.txt.  Nothing in the log.txt seems "off" looking at it as a lay person (non-expert).  It does appear that Vulkan may be doing it's "texture thing".  The reason I say this is because when I'm running XP my GPU is always at or above 4GB.  It may be that the TBM and your particular XP installation do indeed use more texture memory than other models and this is causing the texture shift you are seeing.  I don't see this on my rig - the TBM is in the middle of the pack of add-on aircraft (way too many - and the CL650 is coming.  Yikes!!) in terms of texture usage.  I don't have the FF A320 to compare.

  9. Hi @Oscar Pacheco and welcome!  I don't want to step on any toes here but attaching the log.txt from a flight that had this issue is a solid first step.  I don't remember ever experiencing this myself but I do recall the XP team discussing this a long while back.  There was also mention of this in the XP forums some years ago during the Vulkan beta run - it was a part of the way Vulkan worked to reduce / eliminate stutters.  Should not affect the cockpit res though.  But way above my paygrade.  Nothing in recent memory though.

  10. Hi @nrey001.  Your main install is awash with plug-in's - both stand alone and contained in scenery.  And you scenery order is also borked although this typically does not cause a crash.  I would download a second "light" copy of XP (only one scenery area) and install the TBM into that copy.  If there are no issues - and I don't believe there will be - you know that one or more (it is probably more than one) of your plug-in's is not playing well with the TBM.  The folks here are able to explain why the TBM - a very complex model - may have issues with other 3rd party plug-in's.  On the bright side I use a good many tried and true plug-in's along with complex scenery on my aging rig and have not had a crash with the TBM al least not that I remember.  Full disclosure - in my mid 70's so the not remembering thing should be taken with a grain of salt.  

    • Like 1
×
×
  • Create New...