Issues with 11.50b10

[jelder]

These are probably xplane induced errors in the latest beta, but thought I would report that the TBM seems to be crashing b10, here are a few lines from my log file:

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1811: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1812: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1813: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1901: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1902: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1903: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1905: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1913: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\2004: Access is denied.

2020-06-04 22:19:35 TBM900[helpers.c:1123]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\2005: Access is denied.

and then at the bottom:

2020-06-04 22:20:11 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FF632195AE7 D:\X-Plane 11\X-Plane.exe+0000000001075AE7 ()
1 00007FF631578A04 D:\X-Plane 11\X-Plane.exe+0000000000458A04 ()
2 0000000000000100 D:\X-Plane 11\X-Plane.exe+0000000000000100 ()
3 0000000000000100 D:\X-Plane 11\X-Plane.exe+0000000000000100 ()
4 0000009672FFF488 D:\X-Plane 11\X-Plane.exe+0000009672FFF488 ()
 

 

Jim

[Goran_M]

According to Ben Supnik, beta 10 has some confirmed issues with it, so we'll ignore this one.

[Marius_B]

Hi,

I also experience some issues, since the Beta 10

The GPS approaches are working fine (both LPV and LNAV+V), but no ILS approach is working in the TBM, the green indicator is selected, but no CDI an, of course, no capturing the localizer.

The glideslope works, but it can be used only for reference in manual flying.

Another issue that I noticed is that the autopilot does not stop at the assigned altitude, both VS and FLC, after it reaches the altitude, it is a fight with the elevator trim.

 

I tried both the Experimental Flight model and the standard model.

 

Thank you

[okidokki]

@Marius_B, your screen shot shows that AP is in ROL and PITCH mode, so it won't follow the ILS down.

I have observed this behaviour every now and then when ILS gets activated (if I remember correctly, even on 11.41, in fact I haven't tried Beta10 yet). AP switches from NAV/APR to ROL/PITCH with APR button remaining activated. Solution is simple: just activate NAV and APR again.

It's always good to double check if the AP is in the correct state.

[Marius_B]

Hi,

It was in manual flying, because it was not displaying the CDI, so I had to land manually.

Even so, the CDI should have appeared, so I could use it as guidance (the ILS frequency was correct, I even set it in the both NAV radios)., but even the name was not appearing at the side of the frequency 

I tried the same approach with the Cirrus and the Cessna, the CDI appears and works fine.

Also, as I said if I choose RNAV, the GPS approaches are working, both LPV and LNAV+V

Edited June 7, 2020 by Marius_B

[Marius_B]

@okidokki

Hi Okidokki,

 

I tried to apply the hint you gave me but, unfortunately, I had no luck! I tried the same flight, with a very simple flight plan, took off from the airport that I know very well, go to the nearest VOR, then activate the approach and try to get back to the airport.

 

The moment I activate the Approach, the AP is following the fixes, both LNAV and VNAV, the issue starts at the FAF, the PFD changes to Localizer, it is not tracking anymore the lateral navigation, it just goes in a circle. I tried many times to deselect NAV and APR and select again, I also disconnected the AP and activate again, no luck. The ROL is continuously displayed, I cannot do anything but disable the AP and land visually. At this airport it is no problem, it is my home airport and I can land without issues, but I am trying to practice for the bad meteo conditions. I really do not know if I m doing anything wrong, I flown the Hotstart TBM for hundreds of hours, I had no issue like this. It happened a few times to have failures, or ILS approaches which were not working, but I assumed that they are part of the 'fun', as normal failures.

In this case, I check the maintenance, there is no fault indicated, the plane is as new :-)

Also, the same procedure, in the Cirrus or the C172 works fine, the ILS approaches are OK, automatic or manual, this is why I wonder if there is anything that it is out of the normal

I tried now the same approach with the Aerobask DR401 and it works well, I stayed on the AP, 'riding' the GS until the minimums....

Thanks

Edited June 7, 2020 by Marius_B

[PeterForsgard]

On 6/6/2020 at 6:35 PM, Marius_B said:

Hi,

I also experience some issues, since the Beta 10

The GPS approaches are working fine (both LPV and LNAV+V), but no ILS approach is working in the TBM, the green indicator is selected, but no CDI an, of course, no capturing the localizer.

The glideslope works, but it can be used only for reference in manual flying.

Another issue that I noticed is that the autopilot does not stop at the assigned altitude, both VS and FLC, after it reaches the altitude, it is a fight with the elevator trim.

 

I tried both the Experimental Flight model and the standard model.

 

Thank you

I have the same issue. ILS approach doesn’t seem to work in 11.50b10. 
Flew to EKCH and ESSV today and had the same problem. Had to land manually with no Localizer information. 
Did you figure out a solution?

[Marius_B]

Hi Peter,

 

Unfortunately, not yet!

I tried everything I could think of, Experimental Flight Model, Standard one, Vulkan drivers and OpenGL, I created a new airframe, still the same behavior. I thought that maybe the radios failed, but in the Maintenance page all is like New....

At least a bit of relief is that I am not alone.

Maybe Goran will see our posts and he might suggest a possible solution.

Edited June 8, 2020 by Marius_B

[skiselkov]

When you report problems include ALL the reproduction steps. What airport? What runway? What approach were you flying? Where were you located? With what you have told me so far, I really have nothing to go on

Edited June 8, 2020 by skiselkov

[PeterForsgard]

11 minutes ago, skiselkov said:

When you report problems include ALL the reproduction steps. What airport? What runway? What approach were you flying? Where were you located? With what you have told me so far, I really have nothing to go on

I flew to two different airports. EKCH and ESSV,

EKCH: After vectors I tried to get established on ILS DME RWY 22R approach.

ESSV: After vectors ILS Z rwy 21.

I switched to LOC but couldn't see CDI.

I got the glideslope but the aircraft couldn't catch it so I could only use it as information for the manual land.

This started in X-plane 11.50b10. I flew many ILS approaches in 11.50b9 without issues.

[Marius_B]

Hi @skiselkov,

I am trying the following plan;

LROP (Romania Otopeni) towards the FLR VOR, then ILS08R approach (vectors)

When I activate the approach, it follows the GPS points (OBELA) both LNAV and VNAV, when it switches to FAF FF08R, CDI commutes to ILS and no more tracking, the plane does not follow anymore the direction, no VNAV, the ILS does not show the LSI, only the GS is working and I have to land manually.

 

Please let me know what other details are useful, I will send them all to you!

I love the plane, it is the best ever simulated, I enjoy a lot the Synthetic Vision, I know that it is your 'baby'! 

This lockdown I took the TBM around the world, I really enjoyed flying it in all the beautiful places! 

I am attaching a photo from 'visiting' Tarbes, Daher factory 

Thank you and the team for this amazing plane!

[skiselkov]

Thanks for the quick responses guys, will investigate.

[Marius_B]

We must thank you! 

[PeterForsgard]

I reverted to 11.50b9 but I still have the same ILS issue.

Tried ESSV again, no CDI.

Then I flew to ESGG and got vectors for ILS rwy 21 approach. Again the same issue.

Marius_B: Do you have AIRAC 2006?

[Marius_B]

I do not have a Navigraph subscription, so it is the default cycle.

Attached you have the initial screen of the MFD

 

[Marius_B]

In any case, the RNAV approaches work fine. So, for the time being, you can continue to fly and select the GPS approaches, not the ILS ones.

Let's hope that Saso will give us some good news!

[Felipe Mendes]

Indeed, there is no more ILS approaches on 11.50 Beta 10. I could confirm this today. SBCY airport, ILS-X RWY 35 procedure, there is no localizer (ILS frequency was tuned, the CDI was auto switched by LOC, but the LOC needle is gone). The glideslope is present, but the AP do not follow it anymore, by pressing the APR button. It was doing fine on beta 9, did this approach many times before.

Regards,

Felipe.

[Marius_B]

Anyhow, at least until the ILS approaches will be 'attended', I think that we should practice more the RNAV approaches, considering that they will, in a not so distant future, and taking advantage on the technology advancements, become more and more utilized. Hopefully, one day, the LPV approaches will be used even for autolanding....  

RNAV_QFacts_final_06122012.pdf

[Rossco]

I did a flight yesterday & also noticed the ILS wasn't working on NAV 1 however I did find that NAV 2 appeared to be tuned in & showing both glide slope & Loc.. I was hand flying by that stage so not sure if the AP would have tracked correctly. 

Haven't had a chance to get back & see if this was a one off for the NAV 2 to be tuned for the approach & not the NAV 1.

[Marius_B]

I tried both NAV radios, I set the frequency in both and tried to switch between them, same issue

Anyhow, as I said, the RNAV approaches work fine, so it is a good chance to practice them! 

Edited June 10, 2020 by Marius_B

[chuckv]

I had the same issue. Are you using Navigaph for Xplane 11.5 and above? This seemed to be the issue for me. If I use Navigraph data for 11.4 with 11.5b10 it works just fine.

[chuckv]

As a follow up. The default G1000 (in the C172) works just fine with the newer Navigraph data. It seems that just the TBM does not like the 11.5 Navigraph data.

[PeterForsgard]

I have manually installed AIRAC 2006 cycle.  

Then I reverted to 11.50b9 and had the same issue. I left the navdata untouched so it could be the problem.

Marius_B no not use Navigraph data and still have the ILS problem.

But if you look at Marius_B:s screenshot you can see that the Obstacle database seems to be new. So 11.50b10 could have messed up the navdata in some way.

I'll try to use the navdata from beta 9.

[Marius_B]

I can confirm that the other aircraft having G1000 are OK, tried C172 and the DR401

[Marius_B]

Also, the issue seems to be only when the G1000 switches from the GPS to the ILS localizer. If I select any RNAV approach, no matter if LPV or LNAV+V, it goes smooth, follows the simulated glideslope and path up to the baro minimums