All Activity
- Today
-
EG8240 changed their profile photo
-
MCDU Export on external hardware
In the following file (of course the drive may vary too, depending how your system is setup): C:\Users\[youraccount]\AppData\Local\MobiFlight\MobiFlight Connector\Scripts\ScriptMappings.json Change the following line: "AircraftIdSnippet": "A300", To: "AircraftIdSnippet": "a300", I reported the solution to Mobiflight a good while ago but it hasn't so far been included in update. NB: If you update Mobiflight, and they haven't included the fix yet, you have to do the edit again. Edit: it will of course have the errors reported above. I'm really hoping Inibuilds would take a look at this.
-
[1.0.6] N1 gauge needle vs digital readout mismatch
Hi, this is a known issue which is still being addressed, thank you :)
-
Air Data Switch
Hi, Would you consider adding a little more functionality to the Air Data Switch? I believe when selected the associated FD should be removed and the PFD message BKUP ALT/SPD with the degraded amber = should appear. Kind regards
-
DeeResi joined the community
-
anıl5435 joined the community
-
[1.0.6] N1 gauge needle vs digital readout mismatch
-
cantfindagoodusername joined the community
-
Removing animated pilot
Oh yeah I don't think the Captain is possible to remove
-
Overspeed protection
That works , thanks
-
FMGC DES Mode
Thanks Ill try it again with the latest release
-
Removing animated pilot
Hi, Thanks for taking time to reply, It was an attempt to remove the captain avatar that I wished to do since I fly it in the RHS. But I'm not sure if this is possible? Thanks
-
samuraicabuloso joined the community
-
Leonardosd joined the community
-
Wrong Version of A300 Showing as Installed
Alright, in case the team asks: I had iniManager scan for my 2024 installation (and 2020, which came up blank, so I left that field empty). After that, I had the app install the A300 directly into my Community folder, and... same issue. ☹️ It will initally show the 2024 Premium version as correctly installed, but upon reloading the app, it all goes sideways and shows the Compatible version as the only one installed. The Manifest file does show 1.0.8 as being installed.
-
Wrong Version of A300 Showing as Installed
Thanks, going to try something else here in the meantime.
-
Wrong Version of A300 Showing as Installed
I'll ask the team for more advice, you could try restarting the PC and then running the Manager in Admin mode and see if that makes a difference
-
Wrong Version of A300 Showing as Installed
-
Wrong Version of A300 Showing as Installed
No, sorry, I typed too soon. I deleted everything I had installed from the iniManager in the addons linker folder and started from fresh. I set the sim path to the same folder in addons linker for both 2020 and 2024, to see what would happen. Unfortunately, it's the same problem - even after reinstalling the Premium version, it shows the compatible one as installed. This is my manifest.json file contents: clearly 1.0.8: So at this point I'm stumped.
-
Wrong Version of A300 Showing as Installed
And in sim is it showing 1.0.8 now or still .7?
-
Wrong Version of A300 Showing as Installed
-
-
大魔王小小怪 joined the community
-
Wrong Version of A300 Showing as Installed
So I'm guessing there is a compatibility issue with the Addons Linker app?
-
Wrong Version of A300 Showing as Installed
Yeah, you beat me to saying you don't have to make it the same as mine as your file setup is designed for aircraft inside of the Addon Linker and not the Sim itself
-
Wrong Version of A300 Showing as Installed
And that actually made the problem worse, since I can't now enable or disable the A300 from Addons Linker.
-
Wrong Version of A300 Showing as Installed
Nope, didn't work. :( This is what I'm seeing now: the Compatible version is both Installed and Uninstalled. My sim paths looks like this:
-
The INS Drift issue isn't what it seems. They DO drift, but are self-correcting upon any WPT entry - Video Evidence
Should be fixed in 1.0.6 but please check and let us know. The issue was already identified before it was reported here :)
-
Wrong Version of A300 Showing as Installed
Hi, this is how I have it set up. I have just one sim path, the default one. Anything there that isn't right? I have one folder in Addons Linker for 2020-only addons from ini and another for ones installed for 2024. EDIT: ah, so I see what might be going on here: I need to create a second path group and set them up similar to yours?
-
Control presets not being loaded on new session
Hi, I'm not to sure that this is aircraft related unfortunately as I have this issue myself with every airplane I fly from the iFlyMAX to the Fenix and our own Airbusses. I haven't checked the FS Forums but I've had this since SU4 so I just assume it's one of those things I just get to live with xD
- Yesterday
-
Wrong Version of A300 Showing as Installed
Hi, in the IniManager Settings select Sim Paths and then in there if your path groups are enabled which I assume they are since you use addon linker. Disable it if it isn't already. Let me know if this helps. The way I have addon linker set up requires that I disable the Sim Paths shown in the top right of the second photo since my sceneries are externally loaded and my aircraft in the community folder, whenever I update I have to disable the simpaths in order for the aircraft to update
-
Wrong Version of A300 Showing as Installed
I tried one more time - I "installed" the Premium version again. It downloaded all the files, installed them, and then it showed as Installed. I then exited and reloaded the iniManager app and, same thing as above - it shows Compatible as being installed and Premium as not - even though the version number is 1.08.
-
Wrong Version of A300 Showing as Installed
I own the Premium version of the A300; however, every time I update it, it ends up showing the Compatible version as installed. Even though I uninstalled the version shown as Compatible and installed the Premium version, it keeps showing this wrong version. This doesn't make any sense because in Addons Linker, it shows Premium version 1.08 as installed, and nothing about the 1.15 version of the compatible version being installed.