richboy2307

As mentioned above, we have been trying but don't have any viable workaround at the moment for what appears to be a platform-level bug with how its rendering the clickspots. Should we find one that works, it will be pushed via an update but barring that it remains an issue that needs addressing sim-side. Thanks!

A known issue since SU5 Beta, please see:

Now you can. Try on v1.0.9. If you do happen to get a crash, please follow this guide to report the CRASH variables as well.

What is WASM?The WebAssembly Module (WASM) is a container for running programmes written in other langauges (eg C/C++) that is then converted to native code ahead of time (as DLLs) during first launch (WASM Compilation). This helps improve performance for subsequent uses but causes longer load times on first launch. his also improves security of the sim and portability of projects across PC / Consoles. In case of issues, only the WASM crashes instead of the rest of the sim along side with it. This is why the sim and some functions may continue to work, however other systems and displays that use WASM on the aircraft become unresponsive or "freeze" in place with a red warning screen. So what to do in case of WASM crash?Do not close the sim/restart flight immediately Verify the WASM error message & crash LVARs Report the WASM error message & crash LVARs with reproduction steps using the guide below. Verify WASM Crash in SimStep 1. Enable Developer Mode FS24 Settings > General > Advanced Options FS20 Options > General Options > Developers Step 2. Enable the Console by pressing "~" key on your keyboard or using the Dev Toolbar at the top of the screen Step 3. Filter the Console by ❌Error messages only by clicking on ⚠️Warning and ℹ️Messages to disable them (remove blue box border around them). Step 4. Type 'WASM' in the search box. Find the WASM Error and Copy the message. Also take a screenshot of this console window for making a report. Step 5. Check the new CRASH LVARs via the Behaviours Menu. Also take a screenshot of this for making a report. Accessing Behaviours Menu FS24 Via the DevMode toolbar at the top, select Tools > Behaviours and navigate to the Variables tab. Uncheck "Only Show Variables get/set....". Type 'CRASH' in the search box and expand their name to display the values. Report WASM Crash on ForumStep 6. Paste the WASM Error message, screenshot of the Console and INI_CRASH LVARs obtained in Step 4 and Step 5 above into a forum post/discord message/ support ticket WASM Crash Report. Step 7. Take note of what you pressed or things you did, just before you noticed this crash happen. Step 8. Verify if you are able to repeat the crash by following those same steps. Step 9. Please provide the following information Aircraft: A300 PW Freighter Simulator: FS2024 Navdata Method: SIM DEFAULT or NAVIGRAPH BASE OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes WASM Error: The error you copied in Step 4 above Crash Variables: The variables you screenshotted in Step 5 above Specs: CPU, GPU and RAM of your system. Step 10. Include on your report a Screenshot / Video showing what you pressed/did just before the crash happened to give us more clues. Screenshot of the Crash Variables Steps on how to reproduce the crash so that we can try ourselves with debugging tools to identify the cause of crash. These types of WASM crashes are heavily dependent on the actions taken just before the issue occurs. Detailed reports of the exact steps leading up to the crash are extremely helpful, as if we’re able to reproduce the issue internally using the same sequence, our team can investigate, debug, and resolve it much more effectively.

This would be useful yes, along with exactly the airport at which you tried and with what approach. Normally if you're in ALT mode already, arming LOC then ILS should properly set the aircraft up for a GS intercept from below.

Try these: L:OVH_CPT_WIPER and L:OVH_FO_WIPER 0 = OFF, 1 = SLOW, 2 = FAST I dont have Axis and Ohs but checked via SPAD and both seem to be working. Yes they do work. The DEACT sticker is referring to the rain repellent switches, not the wipers themselves. Their clickspot however is currently affected by a platform level bug since SU5 beta that incorrectly scales the clickspots of certain types of XML interactions. The same was reported on A310 and taken by Asobo as a sim bug - basically the click spot boundaries have become too small / scale incorrectly with zoom levels, resolutions etc. In these instances the clickspot will always be exactly at the center of the switch. Move closer or zoom in if you're having troubles for the time being. You can confirm this by enabling Developer Mode > Tools > Behaviours > Debug > Interactions. You'll note that the interaction shows, and works as intended but the hitbox seemingly de-scales wrongly when the debug is disabled.

The display map will show at position 0,0 until Alignment is completed , AND MSU Mode Select knob is set to NAV, AND Execution of TK CHG in AUTO or MNL mode from 00 to 01. All of these are necessary to initialize the system. You can then re-center the map to your actual position by clicking the aircraft icon. Because when you spawn on the runway, it automatically aligns the INS to your present position. The map in the center is an INS DISPLAY MAP, its driven by coordinates from INS1, 2 or 3 respectively. Its not a GPS map that is always aware of your position. So when you spawn at a gate, cold and dark, it places the purple dot at 0,0 as it has no known position until the alignment and initialization process is completed as per above.

Once we get more clarity on the PS5 Marketplace and it's process we'll be able to say more but yes, we intend to support the platform with our addons. There is no ETA but I'm sure we'll make an announcement once that happens. Stay tuned to our socials or newsletter which you can sign up for at the bottom of our store page: https://inibuilds.com/

Hi, Ensure you're logged in to the same account where you purchased the addon. Click on My Products from the toolbar on the left. Select the Scenery tab and ensure no status, simulator or search filters are selected. You should see your purchased PHNL copy there if the order was paid for successfully. If not, please reach out to Direct Support with reference to your order# and use the same email as your registered account. https://inibuilds.com/pages/contact Note, much of the team is currently attending FSExpo so expect some delay in responses as they travel to return to office in the coming week. Thanks!

Hey That is the plan but expect more finalised information closer to release. And yes it is safe to expect special Emirates liveries. They're truly the airline synonymous with A380 after all with that enormous fleet!

That is the plan yes, but we can't say for certain until final testing on the platform of release candidate. The A380 is still in active development currently. Expect more information closer to release :)

Thanks, those features were deemed beyond the scope of this product line and the price is reflective of that. However we note the suggestion for future development. As for the A380, expect features on par with the A350 at the very least, if not more :) Thanks!

Hi @heyado7018 Thanks for your video. We tried reproducing your issue but no luck across the team or testers. See attached video of my personal attempt. We suspect the issue could be one of A keybind conflict - check all keybinds pertaining to Mixture, Fuel or Ignition. Alternatively try with just mouse and keyboard connected to rule this out. An assist conflict - ensure automixture is disabled under Settings > Assistances as it can affect availability of fuel An addon conflict - you tried running Tristar with a renamed (assuming empty) community folder so less likely in this particular instance. Let us know if any of the above suggestions work? Thanks 2026-06-09 01-31-02.mp4

Yes the physical probe equipment on the engine may be the similar, and what they can physically measure will be equivalent but the computers that process this data before being shown to the flight crew are nowhere near the same. As far as the Tristar is concerned, all the available resources show that it cannot and will not show any indications lower than 1.0. Even if the actual pressure maybe lower than that, it will remain at 1.0 indicated at the very lowest. That being said, descent FLT IDLE readings are typically around 1.05-1.15 range depending on atmospheric conditions so I don't see any cause for alarm.

Hi, No even at IDLE when stationary, a running engine can't give an EPR below 1.0 - which indicates that the total exhaust pressure precisely matches the ambient intake pressure. A flight idle of ~1.100 is pretty typical.