IniJamir

Hi, These issues are known to the team and being investigated. Thank you all :)

I shall pass this along to the team, thank you :)

Hi, another user raised this on the discord as well and the team is aware of the changes. No ETA for when these changes can make it into the sim however. Thank you :)

If you were to buy it on Marketplace, transfer it to the IniManager and then follow this bit it should work, I see no reason why it wouldn't since the Airport would be activated under your account once the transfer is finalized

Hi, if you could please copy and paste all of this in the link here as this is where our team directly pulls and ingests WASMs. Thank you https://forum.inibuilds.com/topic/35419-inibuilds-a340-master-wasm-crash-thread-v1012/

Hi, There should be a fix coming for this in 1.0.8. When that releases let us know if you still see this issue occurring. Thank you!

I'll see where the team is with this issue.

Hi, You are on PC correct, if so you can just do an marketplace transfer by following this link: https://forms.inibuilds.com/order-transfer I will raise the issue of deprecation to the team. Thank you :)

Hi, The Marketplace version of the Aircraft is the Premium Edition which is FS2024 Native with the additional features that come with 2024 as shown on the IniManager/Store Pages

Hello, As this is Double T's scenery you will have to reach out to them at this email here: Tienvip26842@gmail.com Additionally there is a fix here on FSTO that might work in changing the identifiers. https://flightsim.to/addon/106004/doublet-skbo-runway-fix-for-batc

I've added this for the team.

It's still being worked on :)

I can pass this along to the team, are you able to upload a video of this occurring in the sim when you have the chance, if not I can grab one later. Thank you.

Hi, Do you use any 3rd Party Liveries installed or any other mods related to the aircraft that might be out of date. Usually this occurs when mods or out of date. If not it's possible that something corrupted during the update or install. Let me know if the first option or reinstalling the aircraft helps. Thank you.

I'll take a look into this, it appears my list of things for A340 is increasing :D

Hi, So for the former issue I have noticed this as occurring every so often, I have assumed it to be something that occurs on a route basis and not consistently and chalked it up to an IRL navdata issue, similar to IRL waypoints that cause loops or other weird anomalies which is usually listed in NOTAMS. I'll ask the team about this just to make sure but I can recommend that one verifies the Flight Plan in it's entirety using the PLAN function and scrolling through the Plan with the MCDU to verify there are no discontinuities. As for the second issue, I have noticed this happens when I flying max forward speed possible, they activate but at these altitudes, the weight of the airframe, and the oh so sweet efficiency of 4 CFM-56s, the aircraft executes the climb but spends the next 1000s of miles climbing at less than 50fpm in some cases, usually I'll reduce speed ahead of climb and then accelerate again post climb, or I'll just run the usual 0.83/.84M for cruise so the aircraft can still climb. Outside of that I tend to not run into this issue with step climbs so I wouldn't be to sure after that. If you would like to add a video from YT or Google Drive to the thread I would be more than happy to take a look at it. Thank you :)

Hi, I will pass this information along to the team. We have been seeing reports of inconsistencies in our discord as well which I am working through investigating. Thank you :)

when you say QNH is showing on the FO Side while you are in inHg. The link should allow the user to set each value manually on one and reflected to the others. If you try setting both to the same setting, unchecking the Link options, the recheck and check if this is still occurring?

Hi, The issues is known and logged to the team, I'll run it back past them but no immediate ETA at this time. Thank you.

Hi, Unfortunately not much we can do about that. EGLC is using a custom flattened platform to get around the crazy undulations in the base photogrammetry ground elevation. User and other AI aircraft correctly read the collision model of the custom flattened platform to set objects on top of it. The GSX simobjects however don't respect this custom platform, but instead sets their height as an offset from the base base photogrammetry ground elevation. There is about 1ft of difference in some areas, hence they appear slightly sunken. A GSX profile allows to set custom elevations for the walking passenger models/paths, but not the base simobjects (like the vehicles, staff, stairs etc). TL;DR just a side effect of working around badly deformed base PG elevations that can't be resolved via terraforming. They should only be slightly sunk, not wholly at the stands. If that's happening, then likely some other mod is also affecting the underlying terrain elevation.

You can disable the default EGCC by going into the My Content Menu in the Marketplace Tab from the Main Menu, search for EGCC, and then disable/uninstall the Asobo EGCC that comes with FS2024

Hi, are you able to try a different browser, or this link again. I tested the link myself and was able to send a support ticket. Let me know if this helps.

Hi, usually we don't aim for compatibility between mods or other 3rd party developers when we make our sceneries. I can't recall if we have an option to disable the solar farm. I can ask the team but ultimately if it's duplicated and non-controllable then the solution is to remove the mod/3rdParty or wait for compatibility from the specific 3rd party creator. Thank you

i'll pass this along to the team, thank you. If possible could one of you attach an image or video. Thank you.

We are excited to access the marketplace on PlayStation. Once we have access we'll evaluate what from our catalogue we can bring to PS5. Thank you for your patience :)