10 minutes ago, Maxis said:

Looking at your signature (You're on an AMD GPU) I think you would be best served by starting the Fenix app then unselecting the display sync check box AND SELECTING

the alternate display mode. (Which from my understanding is the display mode that was default in Block one) Which worked out the box for AMD graphics cards.

Unselecting display sync alone did not fix the issue completely. Selecting the Alternate display mode did and also allows me to use Afterburner/RTSS and AMD's driver based frame gen which i use simultaneously on every flight.

Thanks. I have now turned Display sync off, which at first did not solve the CTDs. I have now updated all of my system drivers inkl. the Realtek sound drivers and I was now able to start a flight. I just left Barcelona for Palermo. Let's see how things go. Keeping fingers crossed.

3 hours ago, pmplayer said:

@Aamir Beautiful update to me,  especially related to fluid and performance !

yep, second that. performance is just great

6 hours ago, Bobsk8 said:

POLOsim who apparently is a ATPL. posted the same thing I did, so I guess he doesn't know what he is talking about either???

I think Polosim may have been referring to an autoland not being permissable / practiced under CAT1.

The discussion was around you telling Capt.Piett that he hadn't done an autoland - when there was an image just above your post, showing his Fenix just above the ground, with CAT1 and "Flare" annunciated.   In other words, clearly doing an autoland!

How ever it may be in the real A320, in the Fenix you can certainly perform an autoland with Cat 1 annunciated.

13 minutes ago, JYW said:

I think Polosim may have been referring to an autoland not being permissable / practiced under CAT1.

The discussion was around you telling Capt.Piett that he hadn't done an autoland - when there was an image just above your post, showing his Fenix just above the ground, with CAT1 and "Flare" annunciated.   In other words, clearly doing an autoland!

How ever it may be in the real A320, in the Fenix you can certainly perform an autoland with Cat 1 annunciated.

I think that is possible to do the same thing with the B737, as someone already told, it's technically possible to autoland in CAT1. And I can autoland everywhere in MSFS20 with the Fenix and the FBW (but I don't know how it's realistic or not),

Edited March 13, 20242 yr by Claudius_

22 minutes ago, JYW said:

The discussion was around you telling Capt.Piett that he hadn't done an autoland - when there was an image just above your post, showing his Fenix just above the ground, with CAT1 and "Flare" annunciated.   In other words, clearly doing an autoland!

No, "Flare" has nothing to do with autoland, it shows regularly on manual landings. It just means the automatic nose down mode on the Airbus has been enabled (to simulate a flare).

7 hours ago, Bobsk8 said:

It appears , that prior to my post, POLOsim who apparently is a ATPL. posted the same thing I did, so I guess he doesn't know what he is talking about either??? Why didn't you quote his post and insult him? 

 

You're right @Bobsk8, I guess I did blow off a bit too much steam at you. I just got increasingly frustrated as I could have testified in Supreme Court that I did an autoland 🙂

@polosim you seem quite knowledgeable, so I find it a bit baffling that you didn't notice LAND and FLARE on the FMA in my screenshots. Do you disagree with what @Fiorentoni mentioned i.e. that it is in fact *possible* to autoland the FENIX (the virtual rendition of the real aircraft) despite FMA announcing"CAT1"? I mean, the virtual air traffic controllers at Heathrow would certainly not applaud you for doing so. But I think that's a bit besides the point. 

Edited March 13, 20242 yr by Cpt_Piett

25 minutes ago, Claudius_ said:

possible to do the same thing with the B737

 

8 minutes ago, Cpt_Piett said:

I mean, the virtual air traffic controllers at Heathrow would certainly not applaud you for doing so.

😁  Legal or not legal that is the question !???

This discussion reminds me of when I was getting my B737 200 rating equipped with SP77 autopilot and the instructor demonstrated to us in the full motion simulator how in case of extreme emergency the SP77 was capable of performing a CAT III "autoland" in an ILS approach. It wasn't the most subtle landing, but we definitely saved the airplane and the passengers. An experience that gave us confidence in the magnificent aircraft but that we would not like to experience in real life.

48 minutes ago, Cpt_Piett said:

You're right @Bobsk8, I guess I did blow off a bit too much steam at you. I just got increasingly frustrated as I could have testified in Supreme Court that I did an autoland 🙂

@polosim you seem quite knowledgeable, so I find it a bit baffling that you didn't notice LAND and FLARE on the FMA in my screenshots. Do you disagree with what @Fiorentoni mentioned i.e. that it is in fact *possible* to autoland the FENIX (the virtual rendition of the real aircraft) despite FMA announcing"CAT1"? I mean, the virtual air traffic controllers at Heathrow would certainly not applaud you for doing so. But I think that's a bit besides the point. 

I see flare all the time  on an ILS approach in the A 320, with only one AP engaged. I think that is the computer signaling that it is time to flare. 

51 minutes ago, Bobsk8 said:

with only one AP engaged. I think that is the computer signaling that it is time to flare. 

True it’s. You will see FLARE on FMA even with both AP OFF but FD ON, (manual landing) which would be indicating that the FLARE mode is active.
 

FLARE MODE
When the aircraft passes 50 ft RA, the THS is frozen and the normal flight mode changes to flare mode as the aircraft descends to land. Flare mode is essentially a direct stick-to-elevator relationship (with some damping provided by the load factor and the pitch rate feedbacks). The system memorizes the aircraft's attitude at 50 ft, and it becomes the initial reference for pitch attitude control. As the aircraft descends through 30 ft, the system begins to reduce the pitch attitude to -2 °nose down over a period of 8 s. Consequently, to flare the aircraft, a gentle nose-up action by the pilot is required.

8 minutes ago, polosim said:

True it’s. You will see FLARE on FMA even with both AP OFF but FD ON, (manual landing) which would be indicating that the FLARE mode is active.
 

FLARE MODE
When the aircraft passes 50 ft RA, the THS is frozen and the normal flight mode changes to flare mode as the aircraft descends to land. Flare mode is essentially a direct stick-to-elevator relationship (with some damping provided by the load factor and the pitch rate feedbacks). The system memorizes the aircraft's attitude at 50 ft, and it becomes the initial reference for pitch attitude control. As the aircraft descends through 30 ft, the system begins to reduce the pitch attitude to -2 °nose down over a period of 8 s. Consequently, to flare the aircraft, a gentle nose-up action by the pilot is required.

OK, so it isn't just a message, it is actually the aircraft signaling that it is doing something to the pitch. 

1 hour ago, Bobsk8 said:

I see flare all the time  on an ILS approach in the A 320, with only one AP engaged. I think that is the computer signaling that it is time to flare. 

I'm thinking it very well could be. Can't remember if FMA shows the same during normal landings vs autolands. And again, sorry for coming across too strong at you. Initially I think I replied to your comment that "you're probably right" or something. I believe you've got many more hours in the Fenix than I do, so I didn't have any reason not to believe you. 

But then, as more people commented, my belief that I actually did an autoland was reinforced. Man, this is giving me a headache!

I'd like to get to the bottom of this though. How should we resolve it? Should I do a quick video recording demonstrating an autoland with FMA announcing CAT1? Of course, I run the risk of being wrong, which would be quite embarrasing! 

EDIT: I mean, when you've got AP1+2 connected and DO NOT disconnect before touchdown, AND the bird adequately flares - you've just done an autoland, right? Sigh. This discussion does nothing good for my blood pressure...

Edited March 13, 20242 yr by Cpt_Piett

17 minutes ago, Cpt_Piett said:

I'm thinking it very well could be. Can't remember if FMA shows the same during normal landings vs autolands. And again, sorry for coming across too strong at you. Initially I think I replied to your comment that "you're probably right" or something. I believe you've got many more hours in the Fenix than I do, so I didn't have any reason not to believe you. 

But then, as more people commented, my belief that I actually did an autoland was reinforced. Man, this is giving me a headache!

I'd like to get to the bottom of this though. How should we resolve it? Should I do a quick video recording demonstrating an autoland with FMA announcing CAT1? Of course, I run the risk of being wrong, which would be quite embarrasing! 

EDIT: I mean, when you've got AP1+2 connected and DO NOT disconnect before touchdown, AND the bird adequately flares - you've just done an autoland, right? Sigh. This discussion does nothing good for my blood pressure...

The FMA should show "LAND" on final approach if all conditions for an autoland are met. As for the rest, it might just be a Fenix bug, showing CAT1 when you've entered a baro altitude (because they thought that's what triggers it).

First flight with V2B2, overall a great job but I do have one question/issue.  The expected trip wind was a 16 mph tail wind but when I attempted to upload "TL016" to the TRIP WIND field in INIT-B, received a message in the scratchpad that the value is "INVALID.....".  This is the syntax I have been using, has this changed ?  I still see five dashes for expected no. of characters.

8 hours ago, Aamir said:

A support ticket with a general description as above and your logs attached is a good place to start

It seems as if an update to various system drivers (incl. the Realtek driver) together with turning off the display sync did the trick. No more crashes. Looking forward now to doing a couple of flights!

Edited March 13, 20242 yr by carlito777

29 minutes ago, zachlog said:

First flight with V2B2, overall a great job but I do have one question/issue.  The expected trip wind was a 16 mph tail wind but when I attempted to upload "TL016" to the TRIP WIND field in INIT-B, received a message in the scratchpad that the value is "INVALID.....".  This is the syntax I have been using, has this changed ?  I still see five dashes for expected no. of characters.

Per the real aircraft's if you just up link the wind it gets rid of the trip wind.