Jump to content

Transair

Member
  • Posts

    123
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Transair

  1. 1. I've also noticed that on winding down the altimeter to set descent target level, the TOD indication vanishes from both the FMS and the ND

    2. I also get a 'Speed limit' row in the FMS which commands a higher level (in this case 10,000) in the midst of a descent profile having lower levels, so the aircraft climbs during descent.

    3. In the attached, the FMS shows very low levels inconsistent with the STAR, so had to set VNav manually.

    4. Despite update 1.2.3., there still seem to be numerous problems with the V Nav.  Hopefully this is getting extensive, urgent treatment!!IMG_2107.thumb.jpeg.d9a84f0d246995c7e4e57c723c37c1f0.jpeg

    • Like 2
  2. 11 hours ago, LineDX said:

    Hi team @iniBuilds I did a couple of test flights on the V1. 2.3. In the new update VNAV has some serious issue. About 25-50 miles or so before TOD on dialing the cdu alt to about 3000 feet, the TOD disappears from the ND as well as from the OFP on the FMS without pressing the ALT knob button(activating the Des). This is a serious VNAV issue requiring an immediate hotfix to make the plans fly able. 

     

    Regards 

    yes...totally agree with this....happened to me on two successive flights today.

  3. maybe some connection with the TM.  I had this with the TCA which went berserk flying the 350.  So I disconnected the USB, then re-connected, and into a different port.  No trouble ever since - poss dirty/poor connection.  try that..

  4. ok...just a long shot.  Using GSX sometimes causes this, and all that needs to be done is to stop Coutl.  OK in your case.  Does the thrust increase if you power up?

     

  5. I've had this with the PMDG737 then the A350.  It proved to be a Navigraph problem for me at least. 

     

    Suggestion: when updating the Navigraph Airac, update the inibuilds 350, PMDG 777 and PMDG 737 via the OIS/EFB - NOT through the hub. 

    • Like 1
    • Confused 1
  6. On 12/16/2025 at 6:42 AM, frank_m said:

    Since it does not happen very often, there is an easy workaround and the reason behind it is a simulator issue, it is really no showstopper. 

    Frank, having had very few WASM crashes to date, I just had three in a row.  All on the ground during the set-up process.  I found the AIRAC had re-set to a previous one interestingly.  i cleared WASM, Updated Nav, and re-callibrated the throttles (forgot to do that between crashes), and now all fixed and running.  I thought it very odd to have WASMs as I have not had them for a long time. It's a very stable platform and I've been enjoying it right through the updates.

  7. 7 hours ago, SAN738 said:

    Can I add that the flap motor sounds are gone for me when sitting in the cabin behind the wing.

    yes..such a shame.  I hear very loud flap noise in the cockpit now when airborne, with both flap retraction and extension. 

    But also, now I have no reverser sound at all  in the coockpit.  Hopefully Inibuilds will read this and investigate.

  8. Hi

    I want to map two functions to keys, but can't currently in the 350.

     Would really like to see an LVAR for the PUR call button, rather than having to push it with the mouse

    delete this...it now appears OK

    Would like to see an LVAR for the SURV DEFAULT SETTINGS and CONFIRM KEYS, so save having to open up the Surv page.

  9. 3 hours ago, frank_m said:

    It seems you have the Navigraph data for MSFS2020 and MSFS2024 in the same community folder and therefore maybe both active in MSFS2024. That is of course a problem, since the 2020 data is not compatible with 2024.

    That’s interesting. Not sure how as I don’t have 2020 on this computer. I’ll check that. Thanks Frank. 

  10. 19 hours ago, Eddie said:

    Hello,

    Will attempt to reproduce and get back to you.

    Thank you 

    Hi Eddie.....maybe a breakthrough here.

    After several reintroductions of files, I have determined that Navigraph files are the problem.

    First, AIRAC 2510r2 was updated and displaying correctly in the OIS, although the Default/Navigraph/AIRAC bar was flickering when that page opened.

    Note with Navigraph files installed in CF, no VOR CDI, FREQ or DME on ND, or ILS freq/DME on PFD were showing - see 1st pic below

    With Files (see pic 2 below) removed from CF - all normal - see 3rd pic below

     

    Is Navigraph an issue with the A350?  How is that fixed?

    I'm also thinking that my issue MAY have been caused by updating Navigraph more than once.  Could this create a problem?

    SUGGESTION: In the 3rd Party tab in the OIS, could there be a comparison tab for AIRAC, comparing loaded version with latest available so we'd know whether to update Navigraph for instance

    Navigraph Files installed in Community Folder.png

    Navigraph Files in Community Folder.png

    A350 (Navigraph removed from Community Folder).png

  11. 15 hours ago, Eddie said:

    Hello,

    Will attempt to reproduce and get back to you.

    Thank you 

    Eddie, I am investigating this and I can test by inserting NAV ILS/VOR data into the FMS. For info, I cleared WASM, and actually uninstalled/reinstalled the 350 - to no avail.  

    What I have found though, is if I remove all but the 350 base product from Community Folder, I get ILS and VOR indications as normal.  So I think I have some corrupted add-on (scenery or utility perhaps) causing this problem.  I am now adding product back into Community folder in batches so I can test which is possibly causing the problem.  

     

×
×
  • Create New...