All Activity

No, I gave up... it seems to me to be a visual only bug

Aircraft: A350-900 Default Cabin (JA01XJ) v1.2.6 Simulator: FS2024 SU5.1 Navdata Method: Sim Default OFP: I wasn't able to powerup the aircraft. WASM Error: Orange screen in the autopilot module... the only thing displaying something for some reason since the aircraft was cold and dark Specs: Ryzen 5 7500F, 32 GB of RAM at 6000 MT/s, 1TB of Samsung 990 Pro, Radeon RX 9070 16GB of VRAM. (System has operated without issues before and framerate is around 50 FPS in 4k medium-high settings with aircraft) Autosave file: Unavailable from the flight I just loaded, attaching the last ones I had that occurred a few days ago. Observation I had a WASM crash while just loading the aircraft in RJFF gate six using the SamScene3D airport. This is an airport I constantly fly, so I think is unrelated. What I think is related and maybe how the WASM may had been affected is that the previous flight I had swapped to a secondary flight plan to divert to RKPK (Gimhae) due to weather and failed landing attempt at RJFF (Fukuoka). A few minutes later after landing in the alternate (RKPK), I created a new flight plan to the original destination (RJFF) and proceeded as normal. Another thing to note, before this flight, the aircraft had already handled 3 flight plans (2 short legs of 1-2 hours around Japan and 1 long leg of 7.5 hours from Heathrow to Toronto Pearson). The aircraft never presented any symptoms of the WASM deteriorating (as I have experienced other times). Next Steps. Maybe replicate a flight like this to see if that deteriorates the WASM enough to have a crash after a session like this. Below I am attaching the RJTT to RJFF initial planned route and then the one I did to return to RJFF after landing at my alternate from Simbrief and from the flight plan folder of the WASM module of the aircraft. Load the flight plan from RJTT to RJFF as normal. Create the engine out procedure out of RJTT in 1st secondary flight plan. Create the alternate in the 2nd secondary flight plan. Make the flight from RJTT to RJFF as planned until you reach 3000 ft approaching Runway 34R of RJFF. Go around up to 4000 ft 2 minutes after initiating the go around phase, review the secondary flight plans Initially almost swap the current flight plan for the 1st secondary flight plan. Cancel the action. Choose correctly the 2nd secondary flight plan that has the alternate route. Deviate and land at RKPK. Wait around 30 minutes (the time I waited for RJFF weather to be nice). Load the flight plan from RKPK to RJFF Fly it normally and land in RJFF runway 34R. My apologies for not recording the Debug menu... I forgot and now I can't really prove it. Additional Information A few things I want to note on what addons I have: FlyTampa CYYZ SamScene3D RJFF Drzewiecki Design EPRA IniBuilds KMKE ACO Design ROAH I do not have any other airplane or anything else that interfaces with the WASM besides what the default sim has. 1783312043.bin RJTTRJFF_PDF_1783297068.f14cad5e.pdf RKPKRJFF_PDF_1783307661.a4cc3e9c.pdf RJTTRJFF_INA_1783297068.fpl RKPKRJFF_INA_1783307661.fpl

Are you guys still having this problem?

If this is still occurring I'll pass this along to the team, I know it should be fixed for 2024. If a fix is need for 2020 as well let me know

Hello everyone, I hope you're all doing well. I'm having an issue with the default A320neo in Microsoft Flight Simulator 2024, and I was wondering if anyone has experienced the same problem. I create my flight plan on SimBrief, then I start MSFS 2024, load the A320neo, and enter my SimBrief Pilot ID in the aircraft's EFB/FMS to import the flight plan. However, instead of importing the route, I only get the message "Flight Plan Requested", and nothing else happens. The flight plan never loads into the aircraft. I've tried waiting for a while, but it still doesn't import the route. Has anyone else experienced this issue? Is there something I'm missing, or is this a known bug? Any advice or troubleshooting steps would be greatly appreciated. Thank you very much in advance for your help! I'm Italian, so if there's anyone from Italy who has solved this problem, I'd really appreciate your advice as well. Have a great night, and thanks again!

I know this is a wild thought but I think everyone has used the navigraph charts and had WASM issues. I guess my question would be...Does anyone have the same issues using the LIDO charts?

v1.0.5 of iniBuilds New York (KJFK) for MSFS 2024 [Enhanced] has been released. This is a small update to address the missing options for the control panel. This update can be downloaded via the iniManager. v1.0.5Fixed missing options for control panel.

Known issue to the team already :)

The brightness of the volume knobs cannot be adjusted with the integrated lights knob.

The last time it happened was at VerticalSim's KTPA.

AS LLg stated above there are no Cabins available for the A350 on Xbox. Thank you.

Unfortunately there's no cabin on xbox

Hello everyone, I recently purchased the iniBuilds Airbus A350 for Microsoft Flight Simulator 2024 on Xbox Series S, together with 3 airline livery packs. When I tried my first flight, I noticed that the passenger cabin was not loading correctly. The cockpit loads normally, but the passenger cabin appears missing or not fully generated. After waiting and trying again, the aircraft started working better, so I think it could be a loading issue rather than a permanent bug. I am thinking about reinstalling the aircraft to make sure all files were downloaded correctly. Has anyone on Xbox Series S experienced a similar problem with the iniBuilds A350? Do you have any suggestions or solutions? I would also like to know if this is a known issue or if there are any settings that could help with loading the aircraft correctly. Thank you to everyone who can help! I am Italian, so if there is any Italian user or support member who can help, I would really appreciate it. Have a great day and thanks in advance for your help.

I see what you're saying, I'll ask about it.

Chaseplane doesn't work in the beta and that's a dealbreaker for me. Cant fly without it now. I will just hold off flying the A300 for now i guess. Its weird that no other aircraft has ever had that clickspot problem for me. Ever. I wonder what happened.

Will not this for the team. Thank you.

What airport were you at for this? I've noticed this occurs when I fly to default handcrafted which isn't too often as there are more payware airports than not at this point

We are excited to access the marketplace on Playstation. Once we access we'll evaluate what from our catalogue we can bring over. Thank you for your patience and support :)

Hello iniBuilds, I hope you’re doing well. I know that PlayStation 5 support for Microsoft Flight Simulator 2024 is still being rolled out and that you may not yet have full access to the PS5 Marketplace. I was wondering if the A350 is planned or being considered for PlayStation 5 once everything is available. Since the aircraft is already available on Xbox, I was curious if there are any technical challenges or if it’s simply too early to say. Many PlayStation players would love to fly the A350, so any information you can share would be greatly appreciated. Thank you for your amazing work!

Agreed, personally I find it ridiculous about this operations pack that while optional is a waste of resources, people bought a passenger aircraft for a tristar, why do we all of a sudden need "air-to-air refuelling, a strategic freighter, and a medical and humanitarian evacuation" I do have the pmdg 777F so at best I would use the freighter but neither of the other 2 in practice, cool, but I would personally not use (especially the humanitarian one), of course there are people out there that will but at the same time ini while they do aircraft that their dev team like, I understand but instead of doing what the community wishes and to be frank the better variants of the pax l1011 we get this stuff, it's just to say the least disappointing. And that probably includes not even a UNS-1 that was more commonly found later in the aircraft's cycle.

Aircraft: A350-900 Nocabin v1.2.6 Simulator: FS2024 SU5.1 Navdata Method: NAVIGRAPH OFP: Not created or uploaded at this early stage WASM Error: Error FCU WASM crash info displayed. Only FCU panel was orange. Specs: i5-12600K, RTX 4070 Super, 12Gb VRAM , 32Gb RAM, Windows 11 Professional Autosave File: N/A Initial observation: First WASM crash observed with A350. Loaded sim, selected Free Flight then selected LEBL, Gate 217 (MK Studios scenery). No destination airport selected. Everything OK. Selected End Flight then selected EGCC, Gate 12 (Inibuilds scenery) as departure with no destination airport selected. Went into cockpit. Only FCU WASM crash observed. Other gauges all OK. Next steps: Exited sim. Restarted sim and selected EGCC, Gate 12 once more. No WASM crash. Console log.txt

Hi All, Not sure if I'm doing something wrong or whether this is a feature or a bug. I've noticed that when I am climbing, if my altitude in the FCU selection is 15,000 feet or more away from the cruise altitude the aircraft goes to the 'Descent' phase, (on the PERF page of the FMS, the "DES' phase is shown) and because of that, only open climb is available (which I understand is because the aircraft wants to follow a descent path, hence why CLB would not be available). However if I select an altitude within 15,000 feet of the cruise altitude, it goes back to the climb phase as I would expect. I've noticed this a number of times recently and reinstalled the aircraft but it still seems to be happening. Below is a dummy flight to test it with a cruise altitude of FL 350. The first screenshot shows it when FL200 is selected in the FCU and the aircraft in the 'descent' phase and the second has it when FL210 is selected and it defaults correctly to the 'Climb' phase. Could very well be that I've been missing a step in the setup for all my recent A350 flights or perhaps this is how the real aircraft flies but wanted to check. I tried this on the A340 and the aircraft remained in the CLB phase irrespective of the altitude selected which is what I would expect. Thanks for your help! :) FL200 FL210 Selected

Wasn't able to do this this morning as I was walking out the door for work but had 1 freeze and then a wasm crash. Sunday night, flight from VHHH-KATL, 10 hours in and then everything freezes, plane starts flying to northern Canada. I delete the wasm folder, reinstall the aircraft, and then start another flight last night at 2300. Woke up to see that the aircraft isn't moving. Before I walk out the door, I see the orange screens of death. Each display with its own associated code (pfd, mfd, etc...). Idk what else is going on here, I'll try again tonight. Despite this two events, I was able to do long haul flights with no issues for 15 days straight. Aircraft: A350-1000 Simulator: FS2024 Navdata Method: NAVIGRAPH Specs: RTX 5070, 32gb DDR5 RAM Autosave File: N/A

One more for the GSX issues: when approaching a jetway to park, the jetway starts moving towards the plane before the player has even had a chance to park. What's more, this triggers the front door to open, even though the jetway usually attaches to one farther down the aircraft, not the one directly behind the flight deck. This always triggers an ECAM warning.

Figured out the issue - when loading a resave, if the player was in flight, all the doors are opened, which triggers the pressure warnings. So, definitely a problem.