All Activity

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

The display map will show at position 0,0 until - Alignment is completed - TK CHG in AUTO or MNL mode from 00 to 01. Both these are necessary to initialize the system. You can then re-center the map to your actual position by clicking the aircraft icon. Because when you spawn on the runway, it automatically aligns the INS to your present position. The map in the center is an INS DISPLAY MAP, its driven by coordinates from INS1, 2 or 3 respectively. Its not a GPS map that is always aware of your position. So when you spawn at a gate, cold and dark, it places the purple dot at 0,0 as it has no known position until the alignment and initialization process is completed as per above.

Looks like the cockpit of the A350.

Hi, SKBO by Double T (purchased through Inibuilds) has runways that don't match MSFS 2024. MSFS 2024 still shows runway 13, while Doube T's version is showing runway 14. How do I fix this? I've tried using various aircrafts and the runways do not match. No ILS runways show up in the MCDU either. Only VORs. Thanks,

When will the A350 family be available for xbox in the msfs2020 marketplace?

Yep. It turned out I had manually typed the path, and there was a typo. D'oh!

The paper printouts are nice, but they are placed at a horribly awkward angle below the EFB. Needs to be either rotated or relocated to a better spot, like next to the MCDUs. For the noise canceling option, instead of having to click through the EFB, a clickspot somewhere in the cockpit that toggles noise canceling on and off would be much more convenient.

What is this?

@iniBuilds Team

Thanks, yes, for instance, the autoprint of the flight plan: how is that supposed to work? Is it when generating a flight plan from the EFB? Same thing with auto-printing takeoff data: nothing happens.

Ok, just to clarify...if the ''POI models' is disabled and I enable the SS3D Sofi stadium it only shows as a crater (no SS3D stadium as it should be). Don't have this issue with 2020 and using SS3D Sofi stadium without issue with inibuilds KLAX.

My inibuilds enhanced FS2024 version just started showing up fully pink. I am not in the SU5.1 beta. I have nothing in community folder except this scenery. I have cleared cache (FS and NVidia). Any suggestions?

I've added this for the team.

I'm looking forward to buying their A350, but the only thing stopping me is the fear that my device won't handle it. I was wondering if I would be able to get a refund later if I provide video clips and proof that it doesn't run well?

Looks like people in the A350 are suffering from this bug as well...

Hello! I wanted to buy the A300 during the most recent iniBuilds Marketplace Creator Sale, however even though the image: showed the A300 as being on sale, the price sadly remained unchanged in the store. :( Also, could you clarify which version of the A300 is currently available on the Marketplace? Is it the dedicated "Premium" edition or the "Compatible" version? Thank you, and have a nice day!

Hmm. Will double check. Maybe the pathway in inimanager is wrong. Ta

I have just respawned and it solwed the problem. It seems it was nothing serious.

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.

Have you spotted there has been an update.

Is it in the library? You should check the content of the community folder.

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 :)