VOR bug stays visible when ADIRU is unaligned and shows the direction which should be hidden as when the ADIRU is no longer aligned/ON it should no longer receive information from the heading of the VOR

It would be great if the development team could address this in a future update, making the VNAV speed adjust dynamically based on the actual conditions during takeoff, as it does in the real aircraft.

I hope this feedback helps improve the accuracy and overall realism of the T7v2. Thank you!

1. Nosegear / Main landing gear collapse (I want this as I cannot find a way to make my gears completely collapse)

2. Volcanic ash messing up engine performance / causing them to fail BUT have the probability to still provide some electrical power as in one instance, British airways 009, when all engines failed they didnt loose their instruments.

3. EFB Failure possibility

4. Engine separation visualization if possible (Ripped part of pylon / wing / damage to wing etc)

Log copy.txt

During cruise on a longer flight, the aircraft experienced a severe freeze affecting avionics, flight controls, and external model rendering. The issue resulted in loss of control and corrupted visual elements inside and outside the cockpit.

Description

Approximately 3 hours into the flight (my second flight using this aircraft), the airplane suddenly entered a shallow left bank, followed by a rapid descent. At the same time, the avionics appeared to freeze and did not reflect the aircraft’s changing attitude or descent.

I attempted to correct the situation using the flight controls, but the controls were unresponsive. The cockpit displays and systems appeared mostly frozen and were not updating normally.

When switching to the external view, the aircraft model appeared heavily corrupted. Parts of the aircraft did not load correctly, and some elements appeared visually broken. Additionally, the throttle pedestal inside the cockpit became transparent.

Unfortunately, I was unable to get the logs from when this happened, but I was recording the flight. If this happens again, I will add the log.

https://youtu.be/xONDmuv_KlI

The correct droop degrees of flaperons and ailerons are attached.

I know for sure on 737NG/MAX using ALT INTV button on this case will only change VNAV ALT to VNAV SPD, only 2nd press will start to delete altitude constraint on LEGS page. Read though the FCOM and both type are not clear on explaining this point (but they phase sort differently),

So I'm not sure if it's the correct 777 behaivor or not.

Today I made a flight from EDDF to KJFK with the freighter 777. Close to Gander I tested a diversion to Gander airport. I was around 15 miles before turning final and suddenly the whole systems became unresponsive. Everything was freezed and I could not even deactivate the autopilot and fly the plane manually. The EFB was also completely freezed. From the outside the plane looked like completely messed up, the livery was upside down. Not sure what triggered that bug?
Many thanks for looking into.

Kind regards

Log.txt

Log.txt

Taken from a guide made bag a real 777 pilot. Right now, CARGO FWD A/C shows when it’s not supposed to, ENG SHUTDOWN doesn’t show, and PACK L and PACK R is a little weird. He didn’t mention anything in the stream about it, but even when external air conditioning is not connected, the messages still appear. Also the TCAS status message doesn’t appear.

Hope that this can be tuned up. It’s already pretty solid, but would love to have it perfect

I’ve been testing over the last few days during different flights and there’s definitely an issue with the brake logic. The good news is that I’ve managed to reproduce it consistently, and it’s quite simple:

When you load the aircraft and taxi for departure, or perform a rejected takeoff, the brakes behave correctly and heat up as they should. The same happens if you load one of the predefined situations, like 10 miles on final or something similar. The problem is with long flights. I couldn’t tell you the exact duration for this to happen, but it happens on any long haul you do. For some reason it’s as if the brakes bug out during cruise once they reach 0º again, and then they stay frozen there at that temperature. At first I thought it was my fault, since I’m using a LUA script so that when I brake with the right foot, the same input is replicated on the left brake, as you haven’t added the new wheelbrake axis yet (add this, please 🥺). But I tested it thoroughly and it’s not the cause of the problem, since I did several rejected takeoffs using it and the brakes heated up perfectly. The problem, as I said, happens after a long flight.

I just landed at ZSPD with autobrake 2, disconnected it after a few meters by slamming the brakes to the fullest to make the first fast exit, and the brakes stayed at 0º during the 10 minutes it took me to reach the gate, plus the extra time I waited there to see if anything happened. I hope you can take a look at this, because there’s definitely a bug there. If you need a log, I can provide it the next time I do a flight, but as I said, it’s easily reproducible, you’ll probably be able to see it yourself.

Thank you beforehand!

Log.txt

I completely reinstalled the FlightFactor B777 V2, but my two problems persist (see attached image and log file). The first problem is white "spots" on the screens in the pedestal, and the second is a SASL error message that causes XP-12 to crash whenever I try to change settings, such as selecting a different engine.

I would be very grateful for any help with this fantastic aircraft.

Regards

Log.txt

I can’t attach any images because of file size restrictions

To recreate start engines, shut down enter replay mode, exit and it should do it

During rotation in sim

Airborne in sim

In v2.5.12, the main gear taxi cam lighting is too dim, as it should illuminate the rear of the engine nacelle, flap fairings, and main gear. The nose gear lighting looks fine in comparison.

I have reset and made sure there are no failures at all.