All Activity

Yep. I’ve reported this numerous times. Sad to see it back.

Bug is still present!!!!!!!! 1.2.1

pdfcoffee.com_a350-ata-33-pdf-free.pdf

In the attached screenshots, you can see that currently power is supplied to the aircraft through the the Batteries (DC), and the static inverter (AC), however the emergency cabin lighting is still completely off even with the cockpit switch in the on position (the same is true when the cockpit switch is in the arm position). This bug isn't immersion-breaking by any means, but it would be much appreciated if this could be fixed, as this system is one of the most important emergency systems on the aircraft and is actually not directly connected to the aircraft's electrical system, but is powered by 8 batteries located above each door, which are charged by the aircraft's electrical system, however in case of a total loss of electrical power, the emergency lighting system is able to be powered for at least thirty minutes by each battery pack. I'll attach a pdf guide to the lighting system of the A350, if you're looking for the emergency exit lighting system, it's on page 56.

Hi, I will take this information and pass it on to the team. Thank you.

Dear Ini, Another couple of updates to the IniManager client and I must ask again when the updates notifications will be fixed for products that have two separated versions for MSFS2020 and MSFS2024... If it is installed only in one of those simulators the notification mark stays green even though there's an update. For example, if I didn't read your Discord channel updates and I only checked the main page of IniManager I would never know there's an update available for Stansted and I run the older version: The green mark says everything is fine, there's no update available, I'm running the latest version. However, double clicking on the product card takes me to the addon page which shows me there actually is an update! I own over 60 airport addons on your store and really I don't have time to regularly go through most of them and double click each product, check its page if there's an update, then click back and scroll back where I was and go to the next one. For this reason I prefer buying products on different stores if they're not exclusive. Can you finally fix this??

Same problem in MSFS2024 version. I hope they can update soon!

You Sir, are amazing. I have a beefy system so the A300 ran OK for me, just not great. And certainly worse than the compatible version. This fix however is simply brilliant. Absolutely silky smooth performance now, not a stutter in sight, even panning around inside and outside at DFW. Can't thank you enough for finding and posting this.

I'll pass this along to the team, thank you.

Can you link the A340 Thread for me please and I will get it noted for the team as well, thank you.

Thank you for this, I will push this along to the team as one of them should be able to double check since I haven't seen it on my end.

I second this. More up to date livery packs need to be compiled and sent to the 2024 Marketplace for console users.

While these updates have helped some, there are still absolutely glaring issues. Time compression is still not integrated and if you try to use it, the fuel burn remains at 1x so you land overweight. Inverted switches are still present. LNAV and VNAV are jank, which to the A300-600s hardware timeframe may or may not be accurate. Either way, this “premium” product despite having a couple patches over the last 12 months still feels like abandonware.

This is on PC. I've included two screenshots here. #1, notice the Block is 84.5, the FOB is 37.3, the Trip is 23.2, the DEST is 14.1, and the EXTRA is 48. Block-FOB is 84.5-37.3=47.2, which is just about 48. The DEST fuel is correct. Simbrief estimated me at about 13.5 at landing. I have no idea where it's getting the TRIP of 23.2. Should be 70.4. Obviously it knows that, since BLOCK-DEST=70.4. The second screenshot I've loaded more fuel, FOB is 37.5. BLOCK-FOB is now 47.0. EXTRA has decreased by .3. Trip has gone up by .2 (!?).

Okay, this is what I'm seeing. I uninstalled and reinstalled Nool, confirmed the Asobo EGSS is disabled, and confirmed my settings in the app. This is still what I'm seeing (it looks like untextured letters and numbers):

@IniJamirAny chance this can get forwarded, as well as the other thread for the a340 that is the same topic, thanks

Strange because on A340-300 it’s working fine.

Terrain data has never worked or rather is simply not available on Xbox.

Yes, ILS details automatically populating now.

Not possible to select any first occurring SID in the dropdown menu.

Yep actually works which is surprising to me why that would be the case but helps as a workaround in the meantime. I do hope they do fix it soon for the people who don’t have that add on. I haven’t had a problem with the SIDS not working.

I've got to amend my statement about not having this issue with other airports... while most airports seem fine, I got this issue (interestingly not with 100% of all signs but some of them) at the MSFS2024 World Update EDJA and EDVK airports too.

Hi! Love the this new addon! However, i am expiriencing an issue where some of the gatesways are missing. I have attempted to reinstall the addon via inimanager. I have to load the aiport without GSX profile too. The gates just dont appear. It also seems like i dont have any static aircraft, even though it is checked in Inimanager. What could be causing this? Im expiriencing this in msfs2024. I dont have any other EGCC sceneries installed in my community folder.

No idea how to help but just another +1 on this so the devs are aware this is not an isolated issue. I've put the A300 back in the hangar (MSFS2024 SU4) - unflyable. All other a/c fine in the sim except for the usual, occasional MS2024 CTD (which so far is fixed by dumping my rolling cache after every session). Can't get through a single flight without something breaking (usually engine bleeds fail mysteriously in cruise and I lose pressurization or autopilot disconnects and fails for no reason with switches frozen in the off position - or both). Too bad, such a great product when it worked. Best all

Still don’t seem to have sorted the autopilot not picking up NAV and going to waypoint after takeoff - always having to do a direct to. So, other than spinning fan blades what else has been updated (and broken)?