It seems the problem is the flight model. If you try to break M1 at 40k by hitting max AB, you can see the AoA keeps going up (very strange right?) and the plane stuck at .99. From what I can tell, the engine is driving a pitch-up rotation alone the center. This should not happen in a real jet. Other planes I own does not have this issue.
2 Likes
Where is it stated that it’s not planned for Xbox?
Very interesting and great job finding the root cause. I agree it should not be like that at all.
On their Facebook page in one of their comments. The plan is to cut out all pages that currently have no function on Xbox, and right now the enlargement feature isn’t working so that will probably go too.
i have written about this a few times… there is an issue with the flight model. People say you can break M1 by pitching down. Not realistic. The airplane should easily go through M1 in level flight.
Long overdue reply. I am on Xbox. Thanks! I don’t use Facebook so never saw that message. I think it is a good thing to cut unused things since the hardware (at least on the series S which I use) is limited.
1 Like
So i have had this problem for a while where the MFD seems to be bugged, i only get the right side of the four screens and they appear to the left of the display. it also takes very long to load. Does anybody know if you can do anything to fix this problem? i allready reinstalled the add on but that didn’t work. i waited for an update with the hope it would get fixed but it still happens after the newest update.
Start your engine. The generator will fully power up your avionics (full display)
Yep, the delay in getting the full display was changed in the last update to make it more realistic.
1 Like
Cosmetic weapons are now officially available on Xbox for the F-35 with the latest update…
1 Like
Is anyone having a strange pull to the left bug on the F-35? Since the update, my plane wants to veer off the runway to the left during taxi and takeoff. While in flight, it also wants to bank and veer to the left after the initial takeoff. It’s doing this with the weapons loadout (maybe) as I haven’t flown it or taxii’ed it without the weapons loadout.
I can’t figure out what the issue is. All planes in the game are taxiing and turning normally in the air. I don’t have a stick drift problem.
Series X.
Edit: Sorry I think it’s veering and banking towards the right, because I have to hold down the left trigger slightly to keep it in a straight line during taxi and takeoff. Same with the analogue stick, I have to constantly readjust to keep the wings level and prevent it from banking automatically to the right.
Extremely frustrating! Is anyone having a similar issue? All plans taxiing and flying normally. No issues with my controller.
Does anyone know why only part of my route shows up in the map in the plane? I created a flight plan in MSFS 2024 using https://planner.flightsimulator.com/ and could see the route in the EFB, but only part of it was showing on the map in the plane. Part of the route had overlapping waypoints, so I’m not sure if that was the issue.
Thanks
pic of flight plan Imgur: The magic of the Internet
The F-35 is not fully compatible with MSFS 2024, it’s certainly not a native 2024 aircraft so probably that’s the reason.
Thanks. I thought I read that the plane was compatible with 2024, so I guess I just assumed everything would work.
It is compatible, I’ve used it in 2024 but I guess those web-based flight plans, EFB and import features would require native 2024 planes to work. I think it’s best just to try creating flight plans on the in-game world map (something I haven’t tried yet as it requires a mouse).
Since the latest update, the F35 is no more showing up in the loading screen, when all my other planes do. I’m on 2024/SU2 beta. Did a few reinstalls and all files seems to be in the right place. I have the Tornado, MB339, the Tomcat and all carriers working well. Just no luck with the F35. Anybody a clue what could cause this?
I had something similar. I had previously changed the installed packages location in UserCfg.opt and found the update had reset it to its default value. It is typically the last line in the file and will say something like:
InstalledPackagesPath “C:\Users\xxxxxxxx\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages”.
I had to:
- Uninstall “F35 Lightning II Microsoft Flight Simulator for Microsoft Flight Simulator 2024” using “Add or remove programs”
- Update the InstalledPackagesPath setting. You can either edit the config file directly or change it from within FS. From the main menu select FS Store, My Library, then click the small configuration cog just to the right of the search bar on the right-hand side.
- Reinstall the F35 package
You might also have to tidy up/remove the content of the original …\LocalCache\Packages\StreamedPackages folder as the content may be orphaned having moved the installation path.
No issues here at all. Neither in the public/beta SU2 build nor in the current SU3 build.
Are you still having issues? If you are, try deleting reserved space and activating your products again. You can also download them now.
The issue seems to be gone with SU3. I had the same happen with taogs Alouette II. They showed up after the update. However, I cant save new joystick-profiles now. Hope this is also temporary issue. Its one of my favorite features in 2024.
Hello, first off, I want to say I love the plane; however, there is another addon for the Sepecat Jaguar, which in 2024 has real working weapons, however, they don’t do any visible damage, but you can see it explode. And I am wondering about the possibility that we can one day do that with the F-35 as well? I understand if it’s not possible because of the classified nature of the plane but it would be a cool feature.