Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ATR 42/72 -600 updated v. 1.0.36

Featured Replies

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

Anybody else experienced this with the newest version?

Regards, Jan Ast

Win 11 PC | Ryzen 7800 X3D | RTX 5080 | LG 42 C2
Cockpit 😉 | TrackIR 5 | Octavia IFR-1 | Virpil Alpha on WarBRD, Virpil CM3 Throttle, Virpil Sharka Control Panel | Honeycomb Alpha & Bravo | TM TPM Rudder

  • Replies 160
  • Views 38.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • The prop brake seems to confuse a lot of people, and when it is used.     The prop brake needs a few things before the ready light will become available.     The aircraft has to be on th

  • If you’re in Hotel Mode, for a turnaround, then I assume you don’t have a GPU plugged in.    You would start engine one normally, and then we put the condition lever on that engine to Auto to p

  • Try rudder trim.  We rarely use aileron trim in the real thing; usually only if the plane is rigged a bit funny.  Rudder trim is your friend in the ATR.  Always Trimming Rudder.  (And Always Try Reboo

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.

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

So this "bug" is not yet solved.

Regards, Jan Ast

Win 11 PC | Ryzen 7800 X3D | RTX 5080 | LG 42 C2
Cockpit 😉 | TrackIR 5 | Octavia IFR-1 | Virpil Alpha on WarBRD, Virpil CM3 Throttle, Virpil Sharka Control Panel | Honeycomb Alpha & Bravo | TM TPM Rudder

Didn't happen on the one flight I did.

5800X3D. 32 GB RAM. 1TB SATA SSD. 3TB HDD. RX  9070XT.

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.

Richard Chafey

 

i7-8700K @4.8GHz - 32Gb @3200  - ASUS ROG Maximus X Hero - EVGA RTX3090 - 3840x2160 Res - KBSim Gunfighter - Thrustmaster Warthog dual throttles - Crosswind V3 pedals

MSFS 2020, DCS

 

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.

NZFSIM_Signature_257_60.png

 

16 hours ago, tyrodes said:

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

DELETED - Wrong person

Edited by JaseMelbo

Jaseman. Lovin it up here........

Catch us over at MassieSim32 -> https://discord.gg/B4buuHGhcr

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

Jaseman. Lovin it up here........

Catch us over at MassieSim32 -> https://discord.gg/B4buuHGhcr

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).

Intel i9 13900KS @ 5.8GHz - MSI MEG Z790 ACE Gaming - MSI RTX 4090 Suprim X - Corsair 96GB DDR5 6400MHz @ 6600MHz Dominator Titanium RGB - 2x Samsung 2TB 980 Pro + 3x 4TB 990 Pro M.2 SSD Raid 0 - LG 4K 55" OLED C1 - EVGA SuperNOVA 1600 T2 PSU

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.

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

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

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?

Best Regards,

Vaughan Martell  PP-ASEL KDTW

 

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:

spacer.png

 

Edited by mryan75

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.