ATR 42/72 -600 updated v. 1.0.36

[Paladin2005 443]

I still got the problem with low hyd and elec problems when im in ground idle.

Anybody else experienced this with the newest version?

[tyrodes 29]

2 hours ago, Paladin2005 said:

I still got the problem with low hyd and elec problems when im in ground idle.

Anybody else experienced this with the newest version?

Yes, I did during taxi with a strong tail wind. Otherwise its fine.

[BrammyH 464]

I am getting it also. I thought the problem was on my end,

[Paladin2005 443]

So this "bug" is not yet solved.

[Krakin 5,853]

Didn't happen on the one flight I did.

[RichieFly 738]

12 hours ago, tyrodes said:

Yes, I did during taxi with a strong tail wind. Otherwise its fine.

Good one.

I get low hydraulics sometimes when I'm taxiing and I now I know why. In my case, a 40knot tailwind. Isle of Mann is apparently a windy place.

[Adamski_NZ 967]

19 hours ago, martinboehme said:

As @ATRguy notes above, you should be using rudder trim, not aileron trim. 

Rudder trim does the trick! Many thanks.

[JaseMelbo 391]

16 hours ago, tyrodes said:

Yes, I did during taxi with a strong tail wind. Otherwise its fine.

DELETED - Wrong person

Edited January 22 by JaseMelbo

[JaseMelbo 391]

16 hours ago, tyrodes said:

Yes, I did during taxi with a strong tail wind. Otherwise its fine.

 

18 hours ago, Paladin2005 said:

I still got the problem with low hyd and elec problems when im in ground idle.

Anybody else experienced this with the newest version?

Hi There.  I needed to make sure my Ground Idle position was calibrated correctly with the EFB's Throttle calibration page.  Since I've set the correct values, I no longer have the issue you've described.

Jase

[Dexter1979 101]

Did anyone have any issues when starting MSFS and selecting the ATR - end flight - select another plane - end flight - and select  ATR again.

When I select the ATR the first time no issues but the second time after another flight with another plane I'm getting blank screens in the flightdeck and no animations (levers don't move).

[mryan75 281]

Well unfortunately this issue has not been fixed:

I get incorrect and inconsistent distances from the FAF to the RW waypoint on RNAV approaches every time. Was just flying the RNP11 to TNCC, from the FAF (ELUVA) it is supposed to be 6.0 NM to the RW11 threshold; it was 6.4 NM. Yesterday I flew the RNAV10 approach to TTPP, from the FAF (TALUS) to the RW10 waypoint is supposed to be 5.1 miles, it was 5.8 NM. Same thing at TAPA a few days ago, the distance from the 40THR (which literally means "4.0 NM to the threshold of the runway"), the distance was 4.5 NM.

Just frustrated beyond belief at this. The release notes for this version cryptically said "DME distance calculation issue corrected". Notwithstanding the fact that this aircraft doesn't even have DME, I assumed that this is what they were talking about and had fixed it. Clearly they have not.

So unfortunately for me this is now a VFR-only aircraft. Which effectively renders it completely pointless.

[sd_flyer 6,093]

3 hours ago, mryan75 said:

Well unfortunately this issue has not been fixed:

 

Just frustrated beyond belief at this. The release notes for this version cryptically said "DME distance calculation issue corrected". Notwithstanding the fact that this aircraft doesn't even have DME,

 

Looks like it does 

https://spare-wings.com/atcdme-antenna-prod-161119.html

[vonmar 124]

13 hours ago, mryan75 said:

Well unfortunately this issue has not been fixed:

I get incorrect and inconsistent distances from the FAF to the RW waypoint on RNAV approaches every time. Was just flying the RNP11 to TNCC, from the FAF (ELUVA) it is supposed to be 6.0 NM to the RW11 threshold; it was 6.4 NM. Yesterday I flew the RNAV10 approach to TTPP, from the FAF (TALUS) to the RW10 waypoint is supposed to be 5.1 miles, it was 5.8 NM. Same thing at TAPA a few days ago, the distance from the 40THR (which literally means "4.0 NM to the threshold of the runway"), the distance was 4.5 NM.

Just frustrated beyond belief at this. The release notes for this version cryptically said "DME distance calculation issue corrected". Notwithstanding the fact that this aircraft doesn't even have DME, I assumed that this is what they were talking about and had fixed it. Clearly they have not.

So unfortunately for me this is now a VFR-only aircraft. Which effectively renders it completely pointless.

"Was just flying the RNP11 to TNCC, from the FAF (ELUVA) it is supposed to be 6.0 NM to the RW11 threshold; it was 6.4 NM."

Where did you get a "DME" of 6.0nm from?

[mryan75 281]

11 hours ago, sd_flyer said:

 

Looks like it does 

https://spare-wings.com/atcdme-antenna-prod-161119.html

Seems like it's an option but I can't find DME anywhere in the plane.

[mryan75 281]

 

3 hours ago, vonmar said:

"Was just flying the RNP11 to TNCC, from the FAF (ELUVA) it is supposed to be 6.0 NM to the RW11 threshold; it was 6.4 NM."

Where did you get a "DME" of 6.0nm from?

Here:

 

Edited January 23 by mryan75