[ Closed ] v.3.0 beta 1, 2, 3, 4, 5, 6 public tests (Page 6 of 13)

With Beta 3:
On ND, the distance on top right needs to be a decimal (like 2.3 NM). For the moment it's rounded to 2 Nm.
Otherwise, we cannot shoot some approaches as the distance is not accurate enough.

On arrival, no transition nor Initial Approach Fix selection possible (it was working on A330 v2)
I checked on LFBD > VOR23 > ROYAN8L (STAR)
We should have some transitions, such as ETPAR

TA ONLY not displayed anymore on the ND during take-off phase (as it was in v2)

Any possibility to set an ALTN airport in FMC?

Thank you for your hard work!

But Where?

Hi

After entering Flight plan do you fill INI pages 1 and 2 ? That way you wil have altitude .
and afterwards PERF page ? Filling speeds (just click on left key in front of them) you shall get announcement at TO .

If you already do that , this means it is a bug as in V3.2 this worked fine .

jcdp

Oh I have an issue when rainwindows on (MCDU menu on)

All liveries
Framerate: with Texture Q> Maximum Visual or lower  Eff>High or Lower  (no changes at all)

• Overhead >33->53

• Outside 28->36

• default forward <20- >33 with rain window on

• default forward <20- >33 with rain window off

Just tried a flight with the beta: I've tried Dubai (OMDB) to Muskat (OOMS) with this route:

OMDB 30R ANVI3F ANVIX L223 TARDI N629 MUSUK MUSU1V 08L (my flightplan told me to fly this route at FL250)

The following things happened that seemed odd:

- Upon programming the arrival in the flight management system I received an error code in red stating something about 08L missing leg;

- After programming the route on the init. page my cruise altitude was reduced to FL210 (maybe because of trip length (218NM) vs weight (take-off weight was 177887 kg)

- When I started the engines and moved the starter switch to the start/ign postion the EPR indicators started spinning wild. When the engine is started this normalized to correct reading.

- After I reached my cruise altitude of FL210 I wanted to check if I could reset my cruise altitude in the Flight Management System to FL250. When I opened the INIT page and wanted to dial in FL250 I had a CTD.

Attached are the log.txt and fmgs.dmp file from my X-Plane11 directory immediately after the CTD. I've filmed the entire flight, so if it helps I can transfer the video to the developers.

...

You might publish your flight on this site. It will be a opportunity for us beta tester to see what is working and where the problems are. But we have also to know what is your hard- and software (plugins) configuration - write it in your Profile (up on the blue line)

Приветствую, Евгений!

Самолет сдувает боковым ветром. На скриншоте показано как это выглядит.
Самолет сдувает после прохода точки, потом при приближении к следующей точке возвращается на траекторию - потом все повторяется, особенно заметно, когда точки расположены близко друг к другу при достаточно сильном боковом ветре, в моем случае это примерно 40 узлов боковой ветер и 5 миль между точками.

Hi !

A330B3:  From EDNY to LOWI:

Route: EDNY SID BEMKI Y326 XEBIX STAR LOWI

best regards,

Thomas

Hi Jar

This version is very good! Its a big jump forward. Thanks very much. The only main problem i'm having is with fuel predictions. Its quite messed up (shows sometimes more at destination left that having right now). And the fuel flow seems like 25% too low. I could fly OMDB-KLAX without any problem, what is not realistic. It would be great if you could fix the fuel flow to more realistic values.

No you are not alone. Same for me. Thousands of warnings.....

Best regards,

Thomas

Loaded airplane fine but as reported multiple times in this topic, the MCDU does not allow proper programming of arrivals and transitions for arrival runways.  Will someone in admin acknowledge that this is being reviewed/looked at?  Thanks in advance.

just tried inputting a coroute and got a out of memory error and CTD  with beta 3