Everything posted by LukeFF
- EFB Chart symbology missing
-
No way to view multiple pages of LIDO charts
Many LIDO charts, such as the Airport Operational Information and SID Procedure Text charts, have multiple pages, but there is no way to navigate between them. You have to use the default EFB to view these sorts of charts.
- Latest Update Feedback – FMS Arrival Issue, Sound Balance, GPWS Volume and Nosewheel Sensitivity
-
BATC nor working properly with A300
Bump just to keep this visible. 🙂 Still an intermittent problem, especially when taking off and being handed off to departure.
-
"Oil temp low" message
Bump - still an issue with 1.0.8.
-
Inibuilds A300 Master WASM Crash Thread v1.0.8 FS24
Setting up STAR for a flight to EIDW when the screens went orange. V.1.0.8 Aircraft: A300 Freighter PW Simulator: FS2024 Version: SU5, iniManager Navdata Method: Navigraph Specs: 9800 X3D, 5090, 64 GB RAM WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11) WASM: Error -239 / ffffff11 [fsdt-msfs-bridge.wasm] fsdt-msfs-bridge: Simconnect Dispatch proc set. WASM: Impossible to get user aircraft [flowmodule.wasm] [FL][ERROR] Failed to get CAMERA STATE from SimVars: -1 WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/A300-600/attachments/inibuilds/Function_Interior_Freighter/panel/inibuilds-A300.wasm is now dirty EDDPEIDW_PDF_1778906271.3ea2187c.pdf
-
Control presets not being loaded on new session
It does seem to be an issue that popped with sim update 5.
-
EI-LDD and B-LDD Livery Issues
The preview images for EI-LDD and B-LDD are reversed: EI-LDD shows it as painted for Air Hong Kong, and B-LDD shows it as painted for ASL. Additionally, the livery for EI-LDD is outdated and does not reflect its current paint scheme, which has been in place for more than a year (i.e., it no longer has the half-white/half-yellow paint scheme).
-
A300 Overhead Clickspots Not Working Properly
Yes, just to add, buttons like the Flight Recorder button on the Ground Control panel are completely unclickable now, no matter how far one zooms in.
-
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
-
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
-
-
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
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:
-
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?
-
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.
-
Control presets not being loaded on new session
Every time I start a new session, I have to choose my control preset because it resets back to the default of NONE every time I load in.
-
LVARS for wiper switches not working
Still an issue after the latest update - none of them work properly.
-
Is KEGE ever going to be updated for 2024?
-
Is KEGE ever going to be updated for 2024?
-
Is KEGE ever going to be updated for 2024?
That's great to hear! The scenery is overall very, very good. The only things I can criticize it on right now are the static aircraft (especially ones that occupy gates at the main terminal; it would be nice if traffic injectors like BATC could place aircraft there instead) and the aforementioned snow inside the terminal. I noticed the PAPI lights on runway 25 are all red when on a stabilized RNAV P approach, but I don't know if that is intentional.