All Activity

How can it be a longhauler/oceanic plane has no HF radio installed,when Domestic planes like Fenix A320 and PMDG 737 have.

Hi, Like many others I also had WASM issues with the A340 and concentrated around creating custom waypoint and coordinates. After the A340 came on Inibuilds Manager I uninstalled the A340 completely from Marketplace and transfered the purchase to the Inibuilds Manager and installed it from there. I have now 3 times been able to create waypoint and coordinates without any WASM crash, so if you are still getting WASM crashes try to transfer it and install it through the Inibuilds Manager. Best regards Peter Lund

Have had the same problem, was solved with some fresh oil in the engines on the maintenance page on the EFB... Not sure how to disable those maintenance features...

Hi! If the PixelSim Bari Airport (LIBD) isn’t showing in MSFS 2024, first make sure it’s installed in the MSFS 2024 Community folder. Sometimes content placed in old folders isn’t recognized. Clearing your scenery and rolling cache and restarting the sim can also help refresh the airport list. If it still doesn’t appear, check for a PixelSim update that’s compatible with MSFS 2024, as some older or newly released airports may not yet be fully updated.

It is happening in the air through the longhaul travel and also in the airport LGAV. There is no such an issue with other planes like PMDG 737.777 Ifly max or ini A350 A300 and default planes My PC specs are intel 11700k, radeon 6900xt, 32gb ram

Hello everyone, I’d like to ask whether other users are experiencing the same issue regarding limited EFB functionality in VR Mode on MSFS 2024 with the A350-900. When running the simulator in VR Mode, several EFB functions appear to be restricted or non-functional. Affected EFB functions Wheel chocks apply/remove External power connect/disconnect SimBrief import Fuel entry and apply Weight entry and apply Other related EFB interactions Because wheel chocks cannot be removed and fuel cannot be loaded, it becomes impossible to operate the aircraft from the gate. I’d like to ask: Are other users experiencing the same behavior in VR Mode? Is this a known limitation or an unintended issue? Are there any known workarounds or a full solution available? Current system specifications CPU: Ryzen 9 9800X3D RAM: 64 GB GPU: RTX 4090 FE VR : Quest 3 (Virtual Desktop connect with Virtual Desktop) Any feedback or shared experiences would be greatly appreciated. Thank you in advance.

This is the proper technique. The FBW trim system is actively adjusting on climbout so if you yank the stick back, it tends to over compensate and when you release pressure it needs to release the value which cause the crazy pitch fluctuations.

Hi Nick. Can you share you PC specs as well as what airports this is occurring? Without more specific details it sounds like the sim is culling objects, of which lights tend to be the first that are affected.

As with most high-fidelity addons we advise disabling all assistances/collision before loading the aircraft.

Do you have any other bindings setup to toggle parking brake or a keyboard profile that might be causing a conflict?

maybe some connection with the TM. I had this with the TCA which went berserk flying the 350. So I disconnected the USB, then re-connected, and into a different port. No trouble ever since - poss dirty/poor connection. try that..

Yes it does. I have flown other Airbus Aircrafts like the Fenix A320 without any Problems. The Hotas is configured and I also did the configuration within the aircraft. Everything else is working with the Hotas.

Hello all. Would like to know if there is a solution to this problem I’m running into. After selecting Fly the sim stops loading and says aircraft collided with scenery. Doesn’t matter what scenery or where on the airport (gate, ramp, runway). The only solution I have found is to fully uninstall and reinstall. My hope is there is a better solution to having to do a complete reinstall. Thank you for the support. Kevin

ok...just a long shot. Using GSX sometimes causes this, and all that needs to be done is to stop Coutl. OK in your case. Does the thrust increase if you power up?

No I am not using GSX at all.

did you use GSX to push?

Hi all, After pushback the plane(A350) is not moving at all. Parking brake is off, chocks are removed. I am using the airbus thrustmaster without any pedals. I also removed every keybinding related to brakes (just to check). It is still not able to move forward. Do you know how to solve that? Many thanks in advance and fly safe!

You can reproduce the problem even with moving the weather/time bar between night and daytime in msfs

Good evening, On three separate flights conducted with the A300 Premium version, I experienced a freeze during cruise after approximately one hour of flight time. I did not notice any specific triggers. For the second flight, I tested with an empty Community folder. For the third, I deleted the aircraft and its corresponding WASM folder before performing a clean reinstall. No difference was noted. Any advice?

Hi - Both of you were banned for being active members of a piracy discord. Best, Steven

I have encountered this issue only when I pull up rather violently on takeoff. If you pull back slowly, and then keep the nose at 10° or less (as you should) on takeoff, i rarely have this issue. Since the plane usually wants to nose up on takeoff, slight down pressure on the stick helps.

When Ifly in daytime and then it comes night there is no lighting in the cockpit. When I start the flight in nightime the cockpit light are ok.

me too

Hi, I was recently banned from the INI Discord and I’m not sure why. My username is oliverriopel. I’d appreciate it if a moderator could let me know the reason for the ban and whether it’s something I can appeal or clear up. Thanks for your time.

Hello all - Kind of funny, but frustrating all the same. Has anyone experienced issues with the pilot and co-pilot appearing to be floating out over the nose of the aircraft? It seems that switching to exterior view causes this to happen. When I switch back to cockpit view, the co-pilot remains on the nose (dosent help with my landing at all). Any ideas on how to remedy would very much be appreciated!!