richboy2307

Do you have any hardware/control bindings that could cause conflicts? Such as master battery/alternator switches on Honeycomb Alpha Yoke for example. Also does this happen even when spawning on the runway/mid-air? How about when using EFB panel states? Thanks

To allow for a seamless experience on all platforms, there is a further step one must do to get the enhanced features (4K Textures, Passenger Cabin Model).Please go to the Marketplace section, and download the free 'Airbus A320NEO Enhanced' package. This will install some additional files in addition to the base version for PC users. After installation, restart the sim.

The CALL/RECEIVE functionality of the Audio Control Panel(ACP) is used to control communications. VHF1 is used for com1, and VHF2 for com2. To hear the ATC, you need to select (pull-out) the appropriate reception knob and tune it's volume (rotate). You will see it lit up (blue) when enabled. To speak with the ATC, you need to select (press in) the appropriate transmission key. You will see it lit up (green) when enabled.

If you are using third-party liveries, ensure they are updated and compatible with the latest version. If you have the 'Horizon Simulations Boeing 787' package installed, ensure it is updated to the latest version. Previous versions modified some base simulator files which could cause conflicts with the EFB functions of all other aircraft.

https://dispatch.simbrief.com/airframes/share/347385_1701976694015

Yes that is the plan, but cannot provide any time estimates. Thanks!

Hi thanks for the post, a potential fix has been included in the latest build (v1.0.2) which is currently live on the iniManager (PC), and will be available via Marketplace (PC/Xbox) in the coming days/weeks. Changelog: https://inib.uk/eggw-v102 Thanks!

This was addressed in the 1.0.2 update which is already live on iniManager, and hopefully will be resolved once the update is available via Marketplace to PC/Xbox users Changelog: https://inib.uk/eggw-v102 The necessary photogrammetry data is probably not downloaded by your sim client as yet for whatever reason. We cannot reproduce such issues via our testers or internally unless PG/Bing Data is turned off. I would also check if you have the UK world updates installed and updated. Alternatively wait for the 1.0.2 update listed above to go live and check then. Thanks!

https://forum.inibuilds.com/topic/22062-my-scenery-is-not-showing-even-though-it-shows-as-installed-in-content-manager/

Logged, thanks!

Hi @ErikThanks for the post. Yes we had seen this suggestion in your original post, and it was decided against using RAMP_GA_Large because of potential conflict with other AI and ground services addons. Unfortunately the missing ramp connection option is an on going sim issue/limitation that we hope Asobo themselves will address. Thanks!

Thanks this has been reported already and the team is looking into it!

Thanks, i've reported to the team. Will have to investigate further.

This has already been answered before, please see linked post. Thanks!

It is labelled as GSX, so I wouldn't go that far. But note your feedback, maybe we could include more obvious disclaimers going forward, but in any case I dont think what was shown was purposefully misleading or "false" in any way.

Thanks, reported.

Reported, thanks!

Hey thanks, the Nool included with the airport has not been updated as yet, hence the issues. Will report to the team, maybe we can take another look at it when doing an update for these airports. Thanks!

In-game ground services not working properly is a bug, that has been logged as such. Once fixed, it most likely will work on both PC & Xbox. I was referring to the ground services shown in the trailer video specifically, and those are from GSX. As far as I know, GSX is currently PC only, so ground services (as seen in the trailer specifically) are only available on PC currently. Thanks!

The bug is logged, as reported above. When a "version/build" (.e.g V1.0) of the scenery is made, it is submitted simultaneously for release on iniStore (PC Only) & Marketplace (PC & Xbox). It is the same version/build of the scenery, even though it is available at different times to you as a user. That is why if a bug was present on a particular "version/build", it will remain on that "version/build" no matter where it is downloaded from (iniManager or Marketplace). The availability of a particular" version/build" on Marketplace (PC & Xbox) is dependent on MS/Asobo's internal validation process and thus out of our control for when exactly it is available. So we are usually not releasing products for platforms "separately", even though it may seem like this to you as a user. In any case, I do not see where you are drawing this impression from. There is nothing that was listed on the the product page or shown on the teaser video that was not present in the product since v1.0. The ground services advertised were specifically shown to be for "Official GSX Profile Included" feature as well. In any case, we note the submitted bug report and will address it when we can in a future update.

Thanks, reported

Thanks, reported

Thanks i'll pass on the suggestion to see if anything can be done. However as you have identified correctly this is a MSFS photogrammetry object so out of our control directly.

Hi, Just to confirm that it isn't some addon conflict, try running with only the A300 in your community folder (no additional liveries either) To run with a blank community folder without losing your addons: 1. Rename your existing community folder to ``_Community`` 2. Create a new ``Community`` folder in its place. 3. Copy only the ``inibuilds-aircraft-a300-600`` folder inside it. 4. Run the sim and see if same problem persists. If YES, then you can close the sim, and restore your original folder as follows: 1. Copy the ``inibuilds-aircraft-a300-600`` folder back to ``_Community`` 2. Delete the new ``Community`` folder you made 3. Rename the ``_Community`` folder to ``Community`` If NO, then that means there is some other addon conflicting with the A300. Usual suspect is bad liveries, so you could try by adding only some of the other a300 liveries in until you can reproduce the problem. Same process for other addons till you find the culprit. The team is looking into CTDs and addressing the reproducible ones each update, however crash-on-load is not something our team or testers have been able to reproduce successfully as yet. Please report back with your findings, thanks!

Hi @matty moor, can you confirm whether you have Photogrammetry enabled in your settings? (Options > General Options > Data > Photogrammetry - ON) This may be caused by discrepancy in terrain data without photogrammetry, or connectivity issues with photogrammetry, wherein the data has not been streamed to the simulator yet. Either way it is recommended to use this scenery with photogrammetry enabled, as that is what it was tested and designed for. Thanks!