All Activity

Severe stuttering during take-off and landing when the NVIDIA app is installed. Even though neither the MSFS 2024 game optimisation nor the overlays are enabled. If I uninstall the app, the stuttering during take-off and landing disappears. Once reinstalled, the stuttering returns. Tested in EDDF and OMDBV2 I’m only speaking for myself, as there shouldn’t actually be any connection. But is there a problem with the A380 and the NVIDIA app?

Welcome to Inibuilds patches....!!!

Sorry what do you mean programmed approach i need to planned it in the fms or where?

You can click on this button, next to the oxygen mask. I assume this is a bug, and will be fixed, but it worked for me.

After exhaustive attempts to nail down the correct behaviours for this throttle, it is clear that there is a signal issue in MSFS 2024 from the Winctrl throttle with this V1.0.3 A380 selected in MSFS 2024. Multiple attempts, cleaning the throttle data config, setting axis to 0 to 100%, setting throttle axis as per forum instructions, following the forum instructions to the letter, 4 axis selection vs 2 axis selection, single stroke double shaft in simapp, re-calibrating in simapp, confirming Winctrl firmware is up to date, confirming simapp is up to date, and all points in between end in the same situation. When viewing the Current Axis Value in both throttle axis 0-100% AND throttle axis, the signal will increase when moving to the CL ident, (engine to 69%), then return to the idle signal value (engine at 50%) when moving up to the FLX ident. This occurs before and after calibration. NOTE: when only moving a throttle during a scan to the FLX position, a full signal is registered. Moving to TOGA reduces signal strength back to 50% I currently stream the A380, but tbh, the original download at release was to my PC and the defect appeared then. Uninstall and re-install has zero effect. For reference, every single other aircraft I use with the Winctrl throttle behaves correctly. Fenix, Ini A350, etc, and has done since Fenix release and Ini A350 release. Nil change to my set up. Please ingest the situation here....If I am missing a basic setting change, I would love to understand that.

Just so you know, the METOTS issue still hasnt been fixed since the last updaete (1.0.3), even though mentioned that it is.

Well the crash has been submitted

Yes to both

Thanks it worked for the jetway creation Thanks it worked for the jetway creation. Still not seeing any passangers coming through.

i am using the xbox controller

It seems to be a widespread issue among Xbox users. Which raises the question: If this is not a particular niche issue some unlucky ones are having why on gods green earth was this not detected in testing the update?

Hello, Since updating to v1.0.3 I have been experiencing the following issues, none of which were present in the previous version. 1) Incorrect path drawn by the FMS on arrival/approach Arriving into SCEL via the UMKA6A arrival (SAFEL - UGOLA - AMB25 - PUMAR - TEGEB - FI17L) for the ILS Z RWY 17L, the FMS computed and displayed a path that does not match the published procedure. With NAV engaged and the approach armed, the aircraft followed this incorrect path and deviated from the arrival track instead of flying the published legs towards the 177° final approach course. 2) DIR TO does not recover the route To correct the deviation I performed a DIR TO a waypoint on the approach. After the DIR TO, the aircraft did not track properly to the waypoint and was unable to re-intercept the flight plan route. The recorded ground track shows the aircraft wandering west of the procedure before finally joining final. Expected: the FMS draws and flies the procedure as published, and a DIR TO takes the aircraft directly to the selected waypoint and resumes the flight plan from there. 3) Light states reported incorrectly via SimVars The aircraft is not reporting the exterior light states correctly through the standard SimVars. With the BEACON and STROBE lights switched ON in the cockpit for the whole flight, external applications reading the SimVars see them as OFF. My flight tracker (NewSky) logged Beacon: OFF and Strobe: OFF and penalised the flight with "No BEACON lights for 15886s when required" and "No STROBE lights for 14900s when required", which is essentially the entire flight. Expected: the light SimVars (LIGHT BEACON, LIGHT STROBE, etc.) reflect the actual switch positions in the cockpit, as they did before 1.0.3. Steps to reproduce: 1. Load the A380 v1.0.3 and plan a flight to SCEL with the UMKA6A arrival and ILS Z RWY 17L. 2. Fly the arrival in NAV with managed descent and observe the path drawn on the ND. 3. Perform a DIR TO a waypoint on the approach and observe the aircraft's tracking. 4. With BEACON and STROBE ON, read the light SimVars from any external tool. Attachments: - PFD/ND screenshot during the arrival - Recorded ground track of the approach - Published chart with the expected route - NewSky light log and flight report I can provide more details or run further tests if needed. Thank you.

does plane work with FSUIPC ?

Hello! This is off topic but when can i expect the 1.0.10 update on Xbox?

Hello same for me since 1.0.3 Xbox

Hello same for me

Ahh that could be it, I will test and respond - thank you

Terrain Radar does now work and the update in EFB staill show ver 1.0.1 not 1.0.3 ?

I´m one of the "others"....be calm,is noted,reported,assigned,noticed,booked,since A350...

I needed allmoast 40 try before i got the updated aircraft instaled today. This markedplacesystem its so bad that it is a shame that devs want to suport it at all by using it.

It didn't work on first trial for me. I deactivated and restarted the sim and then activated and restarted the sim, it worked without any issue

From Lead Developer of BBS C-130J regarding WASM crashes... I am extremely happy to be able to finally announce that we now have a pinpoint diagnosis of the random WASM crashes (orange screens) which have afflicted this and other products. As we have long suspected, it is a bug internal to MSFS’s memory allocation system. It affects ALL WASM modules which make any significant allocations and deallocations, however the probability roughly scales with the size and number of allocations. Unfortunately, the particularly extensive systems and feature set of the C-130J - graphics for 16 complex display pages, imagery and terrain database, full TAWS and TCAS simulations, nav database, obstacle database, digital map, more than 200 performance/TOLD tables etc - also made it particularly susceptible to this bug. Asobo has stated that the actual fix may not make it into the sim until SU 8, however there is fortunately a work-around, which will be applied to the C-130J in the next update (ASAP), and to the rest of our wasm-based aircraft as soon as practical. I would like to personally thank all of you for your patience, understanding, and support, and especially those of you who have devoted considerable amounts of time and effort to testing the C-130J, helping us fix this and other issues, giving important feedback, and helping us grow this product into what it is today. Curious if the workaround could be implemented into other aircraft until Asobo resolves this?

I noticed that navigraph charts desktop app was also not loading either and at that point I have discovered I've had a network issue. I restarted network connection and the map buttons are shown once again. However it appears that the map cannot recover from this situation once connectivity is restored.

OIS Enroute map started off fine but after a while map tiles have stopped loading and all map controls are hidden and all I'm left with is a blank screen. EFB charts also exhibit same issue.

Help - I tried to uninstall the A300 which does not appear in the msfs menu and this is what I got - see attachment