KBJC incorrectly referred to as "Detroit Metro"

This airport is in the Denver area, so of course it’s not Detroit.

1 Like

Hi @Bahnzo3217 ,

Moved to User Support Hub User Support Hub > ATC, Traffic & NAVAIDs since this issue has already been reported and closed with the following comment “Marked as Won’t Fix at this time.”:

Also, when reporting an issue in the Bug Reporting Hub please don’t delete the provided template :+1:.

I reported it AGAIN, because there’s no reason this bug shouldn’t be fixed. This is a popular field in a large metropolitan area.

And the template had no relevance to this bug. It’s a simple report, why require someone to fill out all that? :-1:

2 Likes

The form gathers the necessary information to cover most potential defect reports. Otherwise, you get one liner posts that don’t even enable peer users, let alone Triage Ingestion to repro, which is Step 2 to validate a defect report.

Step 1 of course is always disable all Add-Ons, Community or External.

Along with @CasualClick’s comment, it may be that the data in the template is automatically imported into a SQL database. No data = no import.

This has been a problem that has persisted for 4 years now. Think of this more as a reminder it still exists. Seriously, there’s no excuse for it being marked as “won’t fix”. That’s crazy…

1 Like

MSFS2020 fixed the “Detroit” reference, but in MSFS 2024 the issue is back and KBJC has other problems.

The airport is no longer referred to as “Jeffco Airport”, it’s “Rocky Mountain Metropolitain Airport”. Its shorthand is “Metro”, as in:

Ground: Metro Ground (not Detroit Metro Ground)
Tower: Metro Tower (not Detroit Metro Tower)
ATIS: Metro Tower Information (not Jeffco ATIS)

Hopefully these items are an easy fix. The ATC interactions are hot garbage right now with these issues.

Many of the issues they fixed are back in 2024 because they forked from an older version and never bothered to pull all the fixes from 2020 because of course they didn’t. Likely they made so many code changes some dev say “nah F that”. Probably lied to a product person and said it was impossible just because they didn’t want to do it.

Junior dev: “Should we look at all these 2020 changes and merge them into the 2024 build before we get too far?”

Management: “Naaaaaaahhhhhh”

throws junior dev out window