silentghostx

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.

Checking in to see if this is logged by the team? Thanks

Also on the gear page the gears should be numbered. It is in the 35K but the 359 gear numbers are missing…

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.

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 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.

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.

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

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

Yep. I don't think the first waypoint/distance should be shown until the IRS is aligned.

Also first waypoint and distance is shown top right on ND before IRS is aligned in the picture. Not the case in prior versions and pretty sure it’s a bug.

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.

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!

This happens in FS2024 also

+1 Main flight control unit panel should remain lit with ground power on and battery off during the battery test.

Glad to see improvements on this in v1.0.6 and that LS button now only activates the LOC/GS scale on PFD, and APPR1 only engages after LOC* which is corrects ongoing issues: - Still no FLARE mode on manual landing. - APPR1 should not disappear until the plane has vacated the runway Thanks for the good work!

Just tried v1.0.6 appears to be an regression on this? Didn’t have auto zoom on touchdown with the flight

Hello, On 1.0.5 - After manual ILS landing FMA went from ROLLOUT into HDG and V/S 0 temporarily. I also note the APPR1 mode remains on the FMA when it should disappear after clearing the runway. Thanks for the ongoing improvements. Cheers, Chen

Your screenshots do not show any issues. Did you switch the ignition switch to IGN/START? On the engine ECAM your starters are not running - should be a vertical line through the circle at the bottom

Hi team, Thanks for all the work on the updates. Here are several bugs that I noticed on my recent flights. 1) Cruise page - LDG elevation - this appears to display random numbers? I was approaching NZAA 05R last night, the EFB Landing Calculation Page showed correct elevation at 15ft, however the Cruise status page showed elevation of 70ft. 2) Checklists - Before take off checklist from the CL menu - the T.O. Perf Normal - this displays in green, even though the T.O. Perf check button has not been pressed - this is correctly displayed in blue on the ECAM but on the checklist it's already ticked off as Green. - Shutdown - Fuel pumps off - this displays in green, even though the pumps are not off. Cheers, Chen

Hi Eddie, Thanks to the team for all the hardwork. I bought this addon since day 1 - to be honest the initial release 1.0.0 was the most stable version for me in terms of loading into the game. Since 1.0.3 I've had issues with loading the aircraft into the game, I have cleared my WASM folder with every update as suggested. However it's very hit and miss. I understand the first load does take time, however the subsequent loads should be taking much less which is not what I'm finding on my end except for the initial release. I have the loading circle rolling, and the background music going, but the plane still hasn't loaded for 10-15min now (subsequent load). I'm on FS2024. I don't use AI traffic, I don't have GSX. FB NZAA scenery. Default iniBuilds Cathay A350-1000 B-LXP updated to the latest livery version. Cheers, Chen

WASM: Varget of NAV HAS TACAN in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm failed with error 0xffffffff Had this one earlier today... feels like after 1.0.3 I've had more crashes. I've reinstalled the whole thing today, and deleted the WASM folder. FS2024 SU1 A350-1000 default iniBuilds livery AMD 7800X3D / nVidia 4090 / 32GB DDR5 No AI traffic. No GSX Frozen on start up - background music still going, the circle still going, after 20min. Have loaded into sim after reinstallation (i.e. not the first time plane got loaded in)

Can confirm this, I was at FL390 with traffic at FL400, TCAS showed they were +24.

Yep had same issue on this! Surely you can get bigger rings in the real aircraft with ETOPS. I think the smaller buses can only do rings up to 256nm

Current work around is ensure your simbrief plan is loaded into the inibuild manager, and exported. I was crashing MSFS every time I loaded NZAA/YBBN, but was ok with all the other airport combos. At the time my simbrief flight plan was NZAA/YBBN, but it wasn’t loaded into the inibuild manager. It will crash MSFS with whichever airport combo you have in simbrief. The current simbrief import doesn’t work for me, stuck on pending when I have my username in.

Hi all Had similar issues - the bindings for the A310 work if you use the throttle axis as “Throttle 0-100%” If you have the Fenix A320 the throttle axis is “Throttle”. It doesn’t work when you have set up it as “Throttle” axis, so save different binding profiles and change it to the “Throttle 0-100%” axis is the way to go here… Cheers, Chen