1 hour ago, hvw said:

Which hotfix, Bob? I didn't see one available after v1.0.5.139 update.

The last one that was released 2 days ago. 

 

35 minutes ago, Bobsk8 said:

The last one that was released 2 days ago. 

 

<scratching head> I only got the update to version 1.0.5.139, no hotfix. Perhaps this hotfix was included in the update as I downloaded that update quite some time after it was released.

@Aamir I can accept the 'Too Steep Message' as I understand it is just a message. My flight plans are also compiled by Simbrief, and I stick to the proper descent procedures, so they only reason I brought this up was because I saw some other users that were having the same issue.

That said, do you have any info on the overheating brake issue that I have experienced on every flight since the latest Fenix A320 update when using GSX? I read all the release notes from the update, and I saw where this brake issue was supposed to have been addressed, but I am getting it on every flight now with the Fenix A320, right after pushback is complete. It then takes over 15 minutes for them to cool down enough for the warning to go away and allow a takeoff without the warning sounds. I do NOT use any time compression, ever, and I do not slew my aircraft around or use the GSX editor. I simply load aircrew, passengers and baggage through GSX, do all my preflight for the A320, request pushback, and then I get the brakes overheat warning. 

Any insiight into this issue would be appreciated, and I appreciate all teh work you and your team have done so far on this enjoyable sim aircraft.

38 minutes ago, hvw said:

<scratching head> I only got the update to version 1.0.5.139, no hotfix. Perhaps this hotfix was included in the update as I downloaded that update quite some time after it was released.

There is no hotfix. The latest version is 1.0.5.139. 

1 minute ago, sniper31 said:

@Aamir I can accept the 'Too Steep Message' as I understand it is just a message. My flight plans are also compiled by Simbrief, and I stick to the proper descent procedures, so they only reason I brought this up was because I saw some other users that were having the same issue.

That said, do you have any info on the overheating brake issue that I have experienced on every flight since the latest Fenix A320 update when using GSX? I read all the release notes from the update, and I saw where this brake issue was supposed to have been addressed, but I am getting it on every flight now with the Fenix A320, right after pushback is complete. It then takes over 15 minutes for them to cool down enough for the warning to go away and allow a takeoff without the warning sounds. I do NOT use any time compression, ever, and I do not slew my aircraft around or use the GSX editor. I simply load aircrew, passengers and baggage through GSX, do all my preflight for the A320, request pushback, and then I get the brakes overheat warning. 

Any insiight into this issue would be appreciated, and I appreciate all teh work you and your team have done so far on this enjoyable sim aircraft.

Umberto was in this thread earlier giving us some more explanation on this, so we will amend it once again. We have disabled the brake temperature simulation when we're told pushback is occuring, but there seem to be exceptions to that case where other variables are triggered to 1 and we need to disable the brake temperature modelling also. We will add this. 

For now, instead of waiting 15 minutes for the overheated brakes - head into MCDU MENU > MAINT > FAILURES, hit the CLR button on your MCDU and select the line with Brake Temperatures.

It will clear the high brake temps instantly. 

5 minutes ago, sniper31 said:

@Aamir I can accept the 'Too Steep Message' as I understand it is just a message. My flight plans are also compiled by Simbrief, and I stick to the proper descent procedures, so they only reason I brought this up was because I saw some other users that were having the same issue.

That said, do you have any info on the overheating brake issue that I have experienced on every flight since the latest Fenix A320 update when using GSX? I read all the release notes from the update, and I saw where this brake issue was supposed to have been addressed, but I am getting it on every flight now with the Fenix A320, right after pushback is complete. It then takes over 15 minutes for them to cool down enough for the warning to go away and allow a takeoff without the warning sounds. I do NOT use any time compression, ever, and I do not slew my aircraft around or use the GSX editor. I simply load aircrew, passengers and baggage through GSX, do all my preflight for the A320, request pushback, and then I get the brakes overheat warning. 

Any insiight into this issue would be appreciated, and I appreciate all teh work you and your team have done so far on this enjoyable sim aircraft.

Sounds like a GSX issue. I don't use GSX, just have FS 2 CREW pushback app, and have never seen hot brakes, unless I really stomp on the brakes because I overshot he touchdown point. 

 

8 minutes ago, Aamir said:

There is no hotfix. The latest version is 1.0.5.139.

Thank you, Aamir.

9 minutes ago, Aamir said:

For now, instead of waiting 15 minutes for the overheated brakes - head into MCDU MENU > MAINT > FAILURES, hit the CLR button on your MCDU and select the line with Brake Temperatures.

It will clear the high brake temps instantly. 

Okay Aamir, I can do that. Appreciate the answer and clarification 🙂 

1 minute ago, sniper31 said:

Okay Aamir, I can do that. Appreciate the answer and clarification 🙂 

Not a problem, sorry for the inconvenience!

19 hours ago, sniper31 said:

@Aamir I can accept the 'Too Steep Message' as I understand it is just a message. My flight plans are also compiled by Simbrief, and I stick to the proper descent procedures, so they only reason I brought this up was because I saw some other users that were having the same issue.

That said, do you have any info on the overheating brake issue that I have experienced on every flight since the latest Fenix A320 update when using GSX? I read all the release notes from the update, and I saw where this brake issue was supposed to have been addressed, but I am getting it on every flight now with the Fenix A320, right after pushback is complete. It then takes over 15 minutes for them to cool down enough for the warning to go away and allow a takeoff without the warning sounds. I do NOT use any time compression, ever, and I do not slew my aircraft around or use the GSX editor. I simply load aircrew, passengers and baggage through GSX, do all my preflight for the A320, request pushback, and then I get the brakes overheat warning. 

Any insiight into this issue would be appreciated, and I appreciate all teh work you and your team have done so far on this enjoyable sim aircraft.

@sniper31 I'm experiencing the same problem that you describe, GSX pushback is causing hot brakes after the latest update.

Same problem with hot brake and I can’t clear the problem 

need to maintain gear down time to descend temperature after TO

 

20 hours ago, Bobsk8 said:

Sounds like a GSX issue. I don't use GSX, just have FS 2 CREW pushback app, and have never seen hot brakes, unless I really stomp on the brakes because I overshot he touchdown point. 

 

http://www.fsdreamteam.com/forum/index.php/topic,27800.msg182032.html#msg182032

I do not have GSX and there is definitely some sort of spurious interaction (using Fenix Pushback).  Push normally, start #2. Stop push and set brakes.  When starting #1 the a/c moves backward requiring another press of the STOP button to cease movement.  Repeatable.

HTH- C

Am i the only one that thinks it hasn't gotten brighter after the update?  Is there something that needs to be turned on?  To me it looks the same.  Everything else is good though!

On 10/27/2022 at 2:15 AM, RALF9636 said:

I already noticed that before the latest update.

When flying manually on climbout and reducing the rate of climb the autothrust is not reducing thrust to maintain the target speed, it stays at full climb thrust and keeps accelerating.

It works fine with autopilot on though.

 

You need to describe what exactly happened. It's your job to pitch for speed when flying manually. Were you leveling off? 

Hmmm can't seem to engage the autopilot after take off with this patch.  Hands off all controls but pressing the autopilot does nothing.  Haven't had this issue before.