All Activity

I appreciate you taking the time to give me all of this information. That's unfortunate that doesn't help, I'll pass all of this along to the team, thank you and sorry for the inconvenience.

Yeah, that was the first thing I tried (deleting WASM and RollingCache); unfortunately it didn't help. I also tried uninstalling and reinstalling the A300 in the iniManager (clearing WASM and RollingCache at the same time), with no luck.

There's no way to have the doors open while sitting inside ? I have many other helicopters where you can do that... and the shift C works fine to walk around with door still open . Not understanding why that can't be implemented.

Given the later information, it is possible that the aircraft didn't initialize properly upon loading or is corrupted in some way, you can try a full reinstall or clearing the WASM so that the aircraft can recompile itself upon loading. Instructions for the later can be found below

OK, so I tried loading in the plane again, and after fiddling with the angles a bit I was finally able to get these buttons and switches to "reliably" (relatively speaking) activate - but the clickspots are very tiny and finicky. While zoomed in very close with the controls in question centered, I was able - with quite a bit of patient "hunting' with the cursor - to find the spot where it would change to a hand and show the control name tooltip, and click on it there. I imagine it'd be somewhat harder to do in the air with turbulence (especially for the anti-ice controls), but this is at least a start. I'll have to try a full flight later when I'm home from work. My bigger concern is that something is clearly going wrong; it's certainly not supposed to be this wonky. It doesn't seem to be this way for others in my VA or people making YouTube videos flying the plane. For example, in this A330Driver YouTube video, he can easily activate buttons/switches on the overhead panel without having to hunt for clickspots: https://www.youtube.com/watch?v=K1mIKaSoUwI (see for example 6:45, where he turns on the ATS and yaw damper switches).

Hi, Sorry for the inconvenience, I will push this issue to the team.

This still not solved (at least on Xbox) 🙁🙁🙁 Terrible product support for that price, guys!!!

I'll see if I can get a clip (it might be a couple days), but in the meantime - I can confirm this is happening from essentially all angles. The pushbuttons on the overhead panel consistently show the hand cursor (and are clickable) only when I'm pointing at the very center of the button. The ones circled in my screenshot that don't work at all are equally nonresponsive from all angles (apart from the one time I got lucky and got Pitch Trim 1 to engage). I'm not doing anything weird or unusual with cameras or angles, and I don't have any mods installed that mess with cameras or physics. I'm just flying the plane from the left seat like normal, and using Shift+WASD and the mouse to turn/move my head to see the overhead panel - same as most players do (e.g. in online video tutorials).

Hi, I will pass this along to the team.

Hi, If this is a livery from the IniManager have you checked that it's been updated, another user had a similar issue on the SAS liveries and that resolved the issue seen here. Let me know if this works, thank you.

Hi, Thank you for this imagery, is there anyway I could get you to record a small clip, sometimes click spots are wonky at certain angles, regardless of that fact it will help pinpoint for the devs where click spots can be improved from a user's perspective since everyone positions themselves differently. I will pass this along to the team, thank you.

Thanks for the feedback, I'll pass it along to the team.

Hello, Understand this has been forwarded to the team to fix. In the meantime, is there another way I can download the airport (already purchased) since it's not possible via iniManager? Thank you!

Hello, I have tried it, This is my Volanta track taxiing down Juliet to RWY07R I have 0 deviations on the taxiway

Hi, see attached screenshot. The Name of the aircraft on right hand side seems a little bit screwed up. Could you fix this by any time soon? Thanks in advance!

Ok hold on, let me tell you what I did so far. Created a folder D:\2024\Addons\iniBuilds Went into the Sim Paths in the iniManager and setup a default path (via auto scan) where my community folder resides a second path containing the stuff from iniBuilds Now if I install Wolf's Fang airport for example, I get to choose where to install it. I'll just select the second inibuilds folder. Now I have this I like my stuff being ordered and well sorted. If I move the installed Wolfs Fang into the airports folder, the iniManager does not recognize it anymore as "installed". I think you can see my point here. It does not help to install all the stuff (aircraft, airports, liveries) into ONE single folder. What's the purpose of the SimPaths in the iniManager then if I put all my stuff into one folder? Next example (A340) Now, in order to see and update the aircraft in the iniManager, I would need to add the path above to my sim paths in the iniManager. That's fine if you have a couple of aircraft/liveries. But this also means that I need to add every single folder of every single aircraft as a custom path in the manager. Why?

Hello, Using words like hate is abit much, can I suggest keeping your tone more constructive. Also, thank you for your feedback, are you talking from experience as a A350 pilot IRL? Kindest

I keep getting D-ATIS updates for my departure airport. I turned it on, but the option to turn it off is greyed out after clicking on it to cancel. Steps to recreate is to ask D-ATIS to keep updating for dep airport, in my case MMMX. Then turn it off after a while.

Just bought the A300-600R Premium for MSFS24 the other day (along with the A340, which so far has been working perfectly, for what it's worth). Really cool plane, and I'm liking the new features/improvements compared to the older A310-300 included with MSFS24; but I'm having trouble getting several of the button and switch clickspots on the overhead panel to work. Several of these are critical to flight, so this has unfortunately rendered the plane unflyable for me. First off, all of the overhead panel pushbuttons (for instance, all the fuel pump controls) have really tiny clickspots: the "hand" pointer (I'm using Legacy cockpit interaction mode, which, per my understanding, is the preferred mode for iniBuilds airliners) only shows up as clickable when I point to the very middle of the button. This is something I noticed with the A310-300 as well, but didn't think as much of it there since I know it's an older plane that hasn't been fully updated for 2024 (and in general is running much older code). However, I was surprised to see this also the case in the A300. Talking to other simmers who also fly the A300 on a virtual airline Discord I'm part of, it doesn't sound like any of them are experiencing this clickspot issue in the A300. In the A310, the tiny clickspots are annoying but livable, since all the buttons and switches at least work. However, in the A300, several groups of critical controls (circled in the attached screenshot) appear to have their clickspots so glitched that I can't successfully click on them at all. I occasionally can get a hand pointer to very briefly appear when mousing over the toggle switches, and once I managed to get Pitch Trim 1 to switch on after spamming a lot of clicks in the vicinity; but I've been unable to reproduce that one-off success. Obviously, this is a big problem since the plane cannot fly without these being turned on (or at least should not; I didn't try it, the ECAM warnings were enough to convince me of that ;-) ). Several other button groups near these (e.g. the anti-ice controls) seem to have the same problem, but I haven't investigated them as closely since they weren't critical to getting the plane started up. Does anyone know what's going on, and how to fix this? The fact that others in my VA didn't have the same issue - and that it's suspiciously similar to what I think(?) is a known issue with the older A310 - is making me wondering if somehow my sim is getting assets confused between the two planes. I saw the warning in the iniManager that says "to avoid any unexpected conflicts you must delete the previous install of A300 prior to updating". I never owned the pre-Premium A300, so I figured this didn't apply to me; but since I did just fly the A310 a few days ago (once as a trial run before buying the A300 to see if I'd like it), it has me suspicious. This is just a wild guess though, so I could be completely wrong. Just in case, I tried deleting my rolling cache as well as the A310's folder in StreamedPackages, but it didn't help. I looked in MSFS's Marketplace -> My Library to see if I could just disable the A310 entirely, but it says it cannot be disabled (presumably because it's part of the base MSFS24 install). For reference, I am on the current version 1.0.5 (Sep 23, 2025) of the A300-600R Premium, according to the iniManager. Thanks in advance - I'd really love to have this plane working! It looks like a lot of fun, and I think it's one I'll end up flying a lot (love these old-but-still-automated birds). I don't want to have to refund it, but currently I don't know what to do since it's unflyable due to this issue. :-(

Hello, many other classic aircraft in this simulator have the paper flight bag and I just find it a bit silly to be honest, like a trend that gets dug into for no reason or benefit to a user other than cool and never use it again (but of course this is different in this case) like flushable toilets and stuff which is a plain waste of development time and instead should be put into stuff that matters. I'm all for the atmosphere of a classic aircraft but a paper flight bag seems a bit odd, but this is more than likely only going to be me. If it was an extremely old laptop or just an EFB I think it would be reasonable, but if it's done it's done. I hope this sets a new bar for inibuilds aircraft and while nobody could be able to deduce every single system working in this aircraft simply cause it's glass. I hope it is study level and even though being a completely different aircraft doesn't suffer from modelling issues or flight model issues (especially the latter, that are present on all airbus aircraft) that are refused to fix with certain excuses.

I've found a way to disable it; simply turn off CFD in MSFS2024.

Hello, I recently purchased the A340 and unfortunately I am experiencing the same problem as others have reported. I am playing on PC using an Xbox controller. As a test, I created a new profile and assigned only the rudder, leaving all other functions unassigned. However, the steering still reverses during takeoff. If anyone has a solution to this issue, I would greatly appreciate it. It’s really disappointing to buy an aircraft and then not be able to fly it properly. 🤬

As the main point states, how do I turn this off? Thank you.

I can confirm no noise / ghost input during taxi. It happens in WF Scenery VHHH when taxing westbound on Taxiway H/J, it happens in other places too but Hong Kong is the one that I remember most clearly. Please try.

Hi, after updating, WASM cleaned, I could not trasfer the existing custom autosaves anymore. It keeps only 5 of 40 in the folder and deleting 35 after starting the flight. Even the 5 in the folder are not visibel in the OIS. Did an all new download from Manager, to avoid corrupted files, new installation in MSFS with cleaned WASM - did not help. Rolling back to previous Version solved the issue for me - it works again. Any help/solutions with the current Version?