richboy2307

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!

Hi Wolfgang @flykorni, Thanks for your post. According to Tom, our sound engineer, the wind sound is tied to TAS primarily, but is also modulated by so many other variables. This particular aspect of the sounds has not been changed since release. However if you have any specific video evidence of what you're noticing, and where you think the problem lies, I'd be happy to share that with him for further investigation. Thanks!

Hi Yes there was a conflict caused by Horizon Simulations (HS) 787 as it modified some default simulator files that affected other developer's EFBs as well. This has since been resolved by HS devs, so please ensure you are on the latest version of their product. Thanks!

Hey @janjoensson Thanks for your feedback, unfortunately this is not likely to be changed. We recommend instead turning down the AI traffic density in your settings ( Options > General Options > Traffic > AI Aircraft Traffic Density )

Thanks, reported.

Hi, just to confirm, you are having this issue as of 1.1.1 HF1, wherein if you exit a hold, the FMC freezes (aka WASM crash)? Can you please let us know if you are able to recreate this issue? If this is specific to a certain HOLD procedure (at a specific waypoint), or happening universally across holds for you? More information would be appreciated. Thanks!

Hey @LukeFF, can I just confirm if you have cleared the scenery index between switching textures?

Hi, I just checked and am able to use it just fine using my xbox one controller connected. Please note that with PC mode enabled, the triggers wont allow for acceleration/deceleration on the controller itself (as by default the triggers are assigned to rudders, instead of toe brakes). This will only function if you have rudder pedals with toe-brakes connected, or if you assign your controller to toe brake functions (Left brake axis and Right Brake Axis on the controls) Thanks!

Thanks for this, noted and reported! I loaded up at FACT to check. And can confirm the RMI is reading the TRU bearing instead of MAG bearing. Need to adjust the data source for the RMI.