Jump to content

silentghostx

Member
  • Posts

    38
  • Joined

  • Last visited

Posts posted by silentghostx

  1. At the moment the FPV doesn’t actually point to where the aircraft is heading to, so it’s not that useful until it’s fixed…

    • Like 2
  2. Hi @haza2

    Thanks to the team for continued improvements!


    1st item here is completely resolved - thank you.

    Regarding the 2nd item, I don’t think it’s fully fixed. 


    After the recent fix everything is rounded UP to the nearest 50ft. 

    The correct logic should also include rounding DOWN to the nearest 50ft. 

    eg ZSPD 34R being at 12ft elevation, this should round down to 0ft. Similarly WSSS 20R being at 13ft, should also round down to 0ft. At the moment both of these are rounded UP to 50ft on the inibuilds A350.

    When the landing elevation is equal or more than 25ft it should round UP 50ft, if it’s under 74ft it should round DOWN to 50ft; above 75ft / below 124ft should be rounded to 100ft and so on..

    Thanks,

    Chen
     

  3. Hmmm I wonder if this is a navdata issue? I’ve definitely seen the ILS listed beside the runways on departure page and the ILS freq shown. The most recent video by A330 Driver also shows it’s there for his OTHH departure @14:50
     

     

  4. 9 hours ago, Der Michel said:

    The plane is really getting annoying....a lot reports by myself and most of them still open/not fixed...every time I try something differnet, I find new bugs.

    I suggest STOP adding new features and do some weeks of bug hunting. New features are nice, but if the basic plane is bugged as this...sorry but I have no appreciation for that.

    Agree. Especially when each update breaks things that have been working in the past. Slow down on the new features and fixing the inaccuracies to make the A350 an A350 would be appreciated.

    • Like 2
  5. Great report.

    although the first point - DCLB is indeed the first displayed thrust mode.

    see around 3:20 when he boots it from cold and dark. 

  6. Hi team,

    Also noted on the latest version 1.0.10 - the VSD is not showing the level off altitude. If the FCU altitude is set less than the cruise altitude, it should be showing in a solid green line on at the FCU altitude, with the predicted VNAV path shown in dashed line until the next altitude is selected. 

    On the image below, the FCU altitude is set at 8000 ft, there should be a corresponding solid line at 8000ft on the VSD, with the rest of the predicted path as a dashed line.

    cruisepage.thumb.jpg.7258f2b79ab3be78d92f4473c6deceb7.jpg

  7. image.thumb.jpeg.2d848b7652494acf22f2a43b47154f26.jpeg

    This picture shows that CAB PRESS MAN is indicated - however the CAB PRESS section on the cruise page remains in AUTO for both CAB ALT and CAB V/S

    image.thumb.jpeg.cfd5798363f6d60e7af0ae65df6b7983.jpeg

    image.thumb.jpeg.ca4d9ce0da4c4e6ce4b44b5b8d71561a.jpeg

    Both these show that the LDG ELEVN on the CRUISE PAGE IS 540ft, this is incorrect as for this approach (LFBO 14R) - it is 488ft on both the Navigraph charts and 488ft on the OIS Landing Perf page. 

    The correct LDG ELEVN on the CAB PRESS section on the CRUISE PAGE should be 500ft (rounded to the nearest 50ft).

    Hope this helps to clarify the bugs described above.

  8. 7 minutes ago, Eddie said:

    Hi Chen,

    I'll look into what can be done regarding this. Would perhaps renaming the threads to include "LOGGED" in the title suffice? 

    That would be better, but if a bug is on page 4 of the forums it might be missed… a pinned list of sorts would help a lot. Thanks again for considering. 

    • Like 1
  9. Hi team,

    Bugs noted 

    1) The cruise page pressurisation status remains in Auto even though Manual is selected from overhead panel, same with cabin altitude, remaining in Auto despite Manual selected. The pressurisation page appears to show Manual. 

    2) Landing altitude - should be rounded to nearest 50ft of field elevation. Currently this value from what I’ve observed is field elevation rounded to nearest 10ft, then add 50ft. Eg NZAA runway 23 has field elevation of 23ft, should be rounded to 0ft. At the moment it will show 70ft on the Inibuilds (23 rounded to 20, then add 50ft)

     

    Cheers,

    Chen

  10. 7 minutes ago, Eddie said:

    Fair enough. I'll take a thorough look throughout today and tomorrow. 

    Hi Eddie and team,

    Thanks for all the hard work. I wish that there could be consideration given to having a pinned topic with “known and logged issues” that’s worked on by the team. We understand not everything will make into the next update, but at least we know it’s being worked on.

    This would reduce a lot of cross and double posting. Might also be useful to use it to create the next change log when there is an update, can just take the issues from the post into fixed.

     

    Cheers,

    Chen

    • Thanks 1
  11. TO config becomes green as soon as A/BRK is set to RTO on the C/L MENU Taxi Checklist page.

    This differs to the checklist on ECAM where the TO config is still blue until it is checked. 

  12. I was under the impression that the initial page should show the GPS position that the aircraft was positioned at, rather than dashed lines on the first screenshot of OP ahairyrat (as per other airbuses eg FBW A380).

    You would only use the align on other position if you are concerned that the current GPS position indicated is incorrect. Nevertheless this doesn’t negate the issue above, as it should still work. 
     

    Could the Inibuilds team have a look at both of these issues?

    1) initial GPS position aircraft is aligning to not showing 

    2) align to another position not working.

    Thanks!

×
×
  • Create New...