New Beta

[Randall 82]

11.55 is available.

[Janov 2,383]

The gist of this update is (official release notes will follow, I am sure) that the latest global airports are integrated into the sim... if you get "can not find runway" at an airport when using the GPS, chances are that your navigational data needs to be updated.

Cheers, Jan

 

[alexcolka 183]

Great! Will this be the final X-Plane 11 version?

[Janov 2,383]

7 minutes ago, alexcolka said:

Great! Will this be the final X-Plane 11 version?

That is a question for Laminar Research officials to answer.

My personal estimate would be: Barring any discovery of showstopping bugs with V11.55 - yes.

[Paul Deluca 164]

This is great. Good news!!!!! Thanks Randall

[Randall 82]

Also, Ben’s related post:

https://developer.x-plane.com/author/bsupnik/
 

[Greazer 1,320]

Interesting.  So this is the reason for the common Vulkan CTD issues?  Looks like the person blaming the users and their overclocks needs to apologize.

[GoranM 3,762]

Oh Greazer. You still don’t get it. 
Overclocking would crash the previous version due to specific issues with Vulkan. This was confirmed by Laminar. This has now been fixed for the current update. So overclocking should now be fine. 
I hope this resolved your issues. 

Edited June 18, 2021 by GoranM

[Greazer 1,320]

1 hour ago, GoranM said:

This has now been fixed for the current update. So overclocking should now be fine.

 As per notes, it was due to 3rd party plugins using the new “instancing” drawing APIs.  Not overclocking.

[GoranM 3,762]

I’m not going to continue pointless debates where you’re asking for apologies. Laminar said in a previous blog post to not overclock because it may contribute to crashes through vulkan. Want an apology?  Ask them for it. 

[Greazer 1,320]

Sorry Goran, the problem was bad code by 3rd party guys 😂

[GoranM 3,762]

Ok. Laminar issued an update that fixed every single developers bad code.  The bad code which was throwing up a Vulkan device loss error. 
Thanks for clearing it up. 
🤦‍♂️

Edited June 18, 2021 by GoranM

[Brian Mackie 123]

A period of silence from GoranM and Greazer would be much appreciated. These two have a habit of hijacking threads, starting personal arguments,  and ruining the discussion for the rest of us.

Edited June 18, 2021 by Brian Mackie

[Greazer 1,320]

At the end of the day if the update fixes the dreaded CTD's then Vulkan version is much better for it.

[mSparks 2,086]

2 hours ago, Greazer said:

At the end of the day if the update fixes the dreaded CTD's

only if you have plugins using the new instancing api, and only then if they actually tripped it.

I never got a recreate on this (although by the sounds of it AutoATC should have been affected)

However, this is yet another memory corruption bug fixed (potentially several), CTDs are the best possible outcome for memory corruption, the most likely outcome of mem corruption is unprogrammed behavior, like say a bunch of buttons in the cockpit stopping working or terrain failing to render - and different for everybody.

Its these that make developing this stuff hard, and why 3PDs should avoid low level languages like C/C++ if at all and whenever possible.

Edited June 18, 2021 by mSparks