richboy2307

Hi, We appreciate your enthusiasm for making the plane a better version of it self. However, nothing in the pipeline regarding this for now. As mentioned in the recent development deep-dive post accompanying the v1.1.2 update, we have IRL operators of the type on the team and are working with their professional insights with regards to the realism aspects of the product. In their assessment, Thanks!

There will be blog posts, FAQs along with a teaser trailer release.

Thanks for your detailed reports guys. I was able to reproduce the same issue. We'll look into it. Thanks!

Hi @markoxley Wow these caravaners are getting out of hand! 😅 But yes we're seeing this too. We anticipate an update to resolve any compatibility issues with the latest World Update. In the meanwhile if you notice any other anomalies, feel free to report. Thanks!

Hi, please ensure Photogrammetry is enabled as there may be terrain elevation issues without the right mesh data. In case you're still having an issue, please share a screenshot of the issue for issue tracking. Thanks!

Hi @Johnnyyang There are static aircraft models as part of the scenery. Due to encryption done on Marketplace, it isn't possible to configure this on the iniManager. However you could try to manually disable them by renaming the klax-scene-statics.bgl to klax-scene-statics.disabled. You will find these files in your Official Folder, under inibuilds-airport-klax-losangeles folder. If you're on PC and you purchase KLAX directly from the iniManager, then you can disable Statics via the configuration panel under 'My Products' section. Thanks!

Use your Pilot ID (Numbers only) in the EFB. Usernames will not work any longer, this was changed as some users had issues with simbrief connectivity because of the special characters in their usernames. Its not a separate slider. It is part of the SYSTEMS volume slider. Before warnings/callouts/alerts volume was not user configurable. Yes it has no bearing on functionality of the aircraft and is a by-product of the XML Interactions re-write for performance optimizations. Known issue as acknowledged here, and even replied on by you: Please avoid re-posting the same issues across multiple threads. Thanks!

Hi @village1111 Perhaps check with BATC support regarding this issue? There are multiple gate types on the scenery - Gate Small/Medium/Heavy and RAMP GA Small/Medium/Large defined already. These are also working for AI Traffic as well as for users via GSX. Thanks!

Thanks for the report, logged.

Thanks, this is a WASM Crash. You'll need to exit to the menu and start the flight again to fix. Also if you just updated, please also try to clear the contents of this folder. It will regenerate these files (for each variant seperately) next time you load the A300. Steam: MS Store: Additional Info Are you getting this crash consistently by repeating the same steps that you did? If not, then this type of "memory allocation" WASM crash post SU-15 is not just limited to us or our code. We suspect this happens when WASM is asking the platform to reserve some memory, but it sometimes attempts to reserve memory its not allowed to and crash the WASM as a result. This is entirely the sim's doing and a process we do not have any control over. If yes, you're getting the crash consistently by following the exact same steps (clicking the same things in the FMS, on the same airport/fplan/procedure) then that's a bug we can further investigate. So please share a video of the entire process. Thanks!

Thanks for your suggestion. It is noted internally, we may look into it at some point however no such plans in the immediate future. Thanks.

Your suggestion is noted, however not planned at the moment. Thanks!

As it says in the message, no plans to make changes in that regard. You're entitled to your opinions but a decision has been made, as such topic is closed. Linked Message: https://forum.inibuilds.com/topic/22201-nose-down-look/?do=findComment&comment=54089

As stated, we have it tuned per IRL data set available to us. If you have any data source to the contrary please do share. Failing that there will be no changes made. Thanks!

The warning will disappear when the IRS is aligned. There is no issue in function, perhaps only an erroneous warning on overhead. We'll look into it. Should also work for you, but only when IRS is aligned. With it set to instant it will sort itself immediately, with any other option it will take longer but will be resolved once aligned. To align the IRS set all IRS on overhead to NAV, then on MCDU INIT A page input FROM/TO airports and then select ALIGN IRS from LSK R4. Thanks!

Reported already and noted, see :

Thanks everyone, logged. We'll look into it.

Hi @mustard7627 Noted on the bug list. What aircraft did you have this issue with? Thanks!

Thanks for sharing. I have forwarded to the team.

We're open to feedback and making improvements where necessary. However there are currently no plans to update the external fuselage model of the A300. If you have any more detailed, specific references please feel free to share. However in my personal opinion, I do not see the issue you are trying to point out from anything shown above as yet. Thanks!

Hi, in the EFB Settings app you can select IDC to HIDE and that will revert to the old radios. Thanks!

Hi @LukeFF Currently there is a bug where the INIT B page is pre-filled on spawn-in. You should over-write all values manually with the actual weights loaded into your aircraft. Alternatively, toggling the weight units (i.e. Imperial to Metric and back) from the EFB Options should clear all pre-filled weights. Thanks!

Hi @browns11 As mentioned earlier, it is on the list and will be looked at whenever the team is working on EGHI next. As you will note on the iniManager, the latest version of EGHI is 1.0.1, updated 6 Oct 2023. Thanks!

Noted. We're working on stability improvements for the next update, as we have recently with the A300 update (v1.1.2). In the meanwhile, please keep posting all instances of WASM crashes along with the following info: route you were flying (i.e. active F-PLN) route you had as secondary (i.e. entered in SEC F-PLN) Navdata Used (Navigraph or Default) Airport Sceneries used (The Departure, Arrival and ALTN airport if any was part of the secondary flight plan) Where you were when you activated the flight plan. (Go around, but at approx what altitude and near which waypoint) Thanks!