ethanjoe89

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.

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

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

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. :-(