ISSUE DESCRIPTION
Description of the issue:
Found another career mission sending to out-of-service runway. Mission was Ferry Flight in a Vision Jet from LFAP to LFFN RWY 10/28. Arrived at airport and runway marked with giant X’s.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
n/a
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
This is one of those situations where the runway has been shortened and only the formerly usable parts are marked with X’s in real life. There’s a shorter segment that is still open. I’m not sure if that’s temporary or not. Either way, the AI doesn’t understand the difference so it detects and renders it as a wholly closed runway.
Well, I was landing on RWY 10 so I noticed the X’s and the shorter strip farther along. The short strip doesn’t have X’s in it, so I floated down over the X’s until I got to the short strip you mentioned…and as soon as the wheels touched down, I was penalized for leaving a runway without announcing I was going to taxi.
Unfortunately, MSFS recognizes the no-longer-functional part of the runway as “valid for landing” in-game, and the IRL short runway as “not runway”.
You can see in the screenshot I’m facing the old RWY 28. This is because I landed on the short, unmarked strip and turned around.
I guess Asobo doesn’t need to invalidate the whole airport? They just need to go in and somehow flag the X’d out section as “not runway” and the newer unmarked strip as “actual runway”.
