Catastrophic runaway STEP in LIPX Verona Villafranca Runaway 22

NOTAM: Catastrophic runaway STEP in LIPX Verona Villafranca Runaway 22

Have you reported it to zendesk? The developers do not read all in this forum and advice to report it to zendesk.

You can click the zendesk link in the top of this page (and every other page in the forum) or at the link i paste here:
https://flightsimulator.zendesk.com/hc/en-us/requests/new

Hope they fix this and all the other ‘broken’ runways.

Sure; I put also a post here in order to advice other pilots…is a NOTAM
:ice_hockey: :ski: :joy: :joy: :joy: :ski: :ice_hockey:

2 Likes

Very similar to the problem reported here:

https://forums.flightsimulator.com/t/broken-terrain-at-cywg/308362/6

https://forums.flightsimulator.com/t/anyone-else-getting-blue-streaks-across-runway-when-you-land-causing-you-to-crash/294839/8

https://forums.flightsimulator.com/t/do-lots-of-airports-have-runway-issues-that-cause-absurd-crashes/306356/4

https://forums.flightsimulator.com/t/broken-runway-eddc/290644

https://forums.flightsimulator.com/t/airport-runways-in-photogrammetry-broken/302437/3

These appear to rendering bugs possibly related to photogrammetry. They are not consistent - you can often taxi the same runway at low/medium speed and never see one of these cracks. You might also land perfectly on that same runway two or three times in a row before you see it again. Given the several various reports in different places around the forums, the best approach is probably to file Zendesk reports complete with screenshots, videos and any supporting details like your approach speed, aircraft type, etc.

I don’t believe that’s accurate because these cracks are rendering issues, not problems with the runways themselves. Read these links - these problems are random and may occur on one landing then not appear the next three times in a row, then appear again …

My personal guess is that they are caused by something like a thread priority issue or something involving corrupted or incomplete cached photogrammetry data, given the fact that several people have reported that turning off photogrammetry removes the problem entirely.

looks like the San Andreas Fault. :joy:

Ok…after the crash caused by the “runaway step” I reloaded the situation by starting from takeoff from 22 and moving ahead very slow until i saw the step and took the screenshots…later I will restart MSFS and try again and again.

yes… this is what happen often and also @LameLefty already mentioned : other users doesnt have these issue. Just try to delete delete the Cache…

In any case it seems to me that AFTER updates some wrong graphical issues are on scenery.
E.g.: at Venice Lido San Nicolò (LIPV) I saw some cubes and “pyramids” as terrain that i dont remember during past flights.
Good luck

like this ?

https://forums.flightsimulator.com/t/strange-geo-domes-at-all-airports/302678/2

hopefully you are not also such a user which permanently fly with the dev-mode :joy:

And then is also this thread:
https://forums.flightsimulator.com/t/hilfe-habe-merkwurdige-grafische-fehler-help-have-strange-graphical-errors/308060

But what you reported first, should be other kind of issue…

Hi MrMooreySJ

Please, ask before posting, please.
I’m NOT in developer mode.

And also I forgot that after landing before step-crash one FORKLIFT is on the runaway.
Bye

I asked whether your reported

are

This bug hit me tonight after an almost 4 hour flight into KSFO runway 28R. Hit the first crack right at touchdown or so, bounced, touched down again and started decelerating, Then I hit another crack, slewed off the runway and “You struck an object and caused catastrophic damage …” or words to that effect.

sigh

I have this bug in verona (lipx), bologna (lipe) and latina (lirl). It only happens if you arrive at the airport from afar. However, if you take off from these airports and land it does not happen.

You can see the break in the screenshot:

This appears to be resolved.