B747-8f

You‘re absolutely welcome

Waypoints on a SID ( such as e.g. DF526, DF527, etc ) would just be inserted as a normal waypoint. Floating waypoints on a SID ( such as „when passing ALT xyz turn left…“ ) would need to be flown raw data anyway. T/C and T/D would not be entered on the INS anyway, they are calculated manually and thence be related to a waypoints ( distance inbound/outbound of a waypoint ). Navigraph charts is not an option in VR, as it costs performance and breaks the immersion.

For the purists amongst us, who like to insert each and every waypoint manually into the INS ( just as real flight crews did ) it would be of great benefit if there would be an option to manually number the Waypoints on the OFP. This would aid in assigning the Waypoints to their slot-numbers in the INS. For instance such as a manually placeable circled number next to the waypoints on the OFP ( like selectable „stickers“ numbered from 1 to 9 ). Best regards

One example: Selected speed is 250 and your actual speed is 300. In this case the yellow ball must on the „fast“ ( F ) side of the indicator.

Hello Jamir, thank‘s for your reply. I think a video is not required. The fast/slow indicator just acts inverted: it shows „slow“ when you‘re too fast and vice versa. Just to clarify: it‘s not a command instrument that would show „slow“, when you need to slow down. It just shows a state that you‘re in, thus it shows „slow“ when you are too slow and „fast“ when you are too fast Best regards

Hello Team, I‘d appreciate if you could add an option to increase the crew-volume ( F/O and F/E ). Thank you

Hello Team, whilst I feel that you‘ve done well on the visuals and sounds, the Autopilot/Flightguidance leaves a lot to be desired. Two of the most disruptive and most obvious shortcomings are: 1.) ALT CAP / HOLD is completely unreliable. The A/P busts the selected Altitude ( especially when it tries to capture the Altitude during turns ) by up to 700ft, which would be a significant LEVEL/ALT Bust in real life. Furthermore, what happens when Flaps are extended, the A/P will start to allow a climb from the selected and captured Altitude at a considerable rate, busting the selected Altitude again by up to 700ft. 2.) The fast/slow indicator on the ADI is inverted. Come on people, this must have been obvious during testing. For sure a plane with potential, but for the time being it‘s to be left in the Hangar, as the A/P is simply too unreliable, especially in an online ATC-Environment.

It‘s early days, yes, but rest assured: they won‘t fix it as they failed to fix the incorrect cockpit-geometry on the A300-600 ( after several attempts of mine to make it clear ) as well. Especially in VR it‘s a vast dealbreaker!

One year later and still the same issue? Shouldn‘t be too hard to modify…

Thank you very much indeed! I‘m on VR ( Varjo Aero ) I should mention and maybe this is the cause. I‘ve cranked up the brightness of my headset to maximum, but that didn‘t fix the problem. I‘ve been on a flight yesterday with bright sunlight. All P/B lights, not only on the overhead, but also on main panel & pedestal, were so dim that they were almost unvisible. Also the numbers on the COM / ILS / VOR / ADF selector were almost unreadable. Same is true for the EFB, although it was cranked up to 100% brightness. Best regards

Same here ( A306 MSFS ). According to real world FCOM it is however indeed possible in the real A300/310. Format is e.g. xxxx.xN/xxxxx.xE. Really curious why this isn‘t modelled. Best regards.

Given the fact that I‘ve also tried a TORA of 6.000m, it should be clear that there‘s no conflict with the MATOW. A fully loaded A300 would of course be able to safely depart from a virtual 6.000m RWY. This wirh pretty much ISA conditions. If not, it couldn‘t operate longrage out of EDDF with it‘s 4.000m TORA. And of course it did ( DLH ). But still with a virtual TORA of 6.000m the EFB provide valid T/O data.

Hello all, I'm new to this forum and I'd like to ask if this forum is supposed to be a peer to peer forum only, or if the developer is reading threads in this forum as well. Put in other words: where to report observations/bugs/etc to the developer. In this forum or via a support ticket? Thank you and best regards, Toto

Hello Team, just did my first longhaul flight with the A300 from EDDH to CYUL. During preflight, the EFB did not accept the actual T/O weight of 171.4tons, although this is the the max allowed TOW according to your Manual and the Simbrief profile. I've tried everything, I've even set a TORA of 6.000meters, however, the EFB would not accept any weight above 170.0tons. It always replied with "cannot provide safe data". So, it seems that the EFB's max TOW is 170tons instead of 171.4tons. Best regards, Toto