Sorry about the delay in replying.
I was wondering how you managed to use an aircraft that required real world Navdata in the FMC/CDU to get a route to SPIM (arrival).
I built the route manually using enroute chart and PFPX data. SPIM came up as not available in route builder.
This (full route in the FMC/CDU) is all part of preflight ops in the flight sim and real world (FMC/CDU ORIGIN / DEST on the RTE page).
Yes it is, and sometimes it is necessary to manually build the route. I manually built the route on the FMS in the CDU RTE page. I used SPIM for the destination; the reason for all my troubles. You can manually build a route in an FMS using fixes and airways without putting any departure or destination airports. The airport entries only provide departure and arrival navigation data, to string along to the enroute data.
If the ICAO for any airport in the flight sim world is changed where will all the AI aircraft go?
Good question, and I have no answer for that.
I flew flight plan :
SPRU - SPJC Garmin GTN750 AIRAC (1803) SID/STAR ILS15 APPR
No problems arriving at P3Dv4.4 SPIM
That was my mistake, I did not use SPJC, I used SPIM as my destination and why I had no arrivals info.
In the sim the AIRAC will have the correct ICAO SPJC code, but the addon scenery index will have SPIM. That had a drastic effect on the Prosim737 presentation on the CDU. Prosim737 builds its database from the scenery index of P3D, and the airport was coded SPIM. Prosim737 now had two different data (codes) for the same airport, the AIRAC data had SPJC for navigation and P3D scenery index data for the airport had SPIM. If I use SPIM for destination in the RTE page I'll get runway and gate info, but no navigation data. If I use SPJC I get no airport data (no such code in scenery index), but I will get navigation. I used SPIM, so no nav data at the time, my scenery was SPIM so I used SPIM.
I solved the problem by copying and editing the copy's BGL ICAO code to SPJC, then adding that new BGL to my addons scenery folder. I now have two identical scenery (addons) one as SPIM (to coincide with P3D's default airport and have priority over it), the other as SPJC to allow Prosim737 database to build on that code and provide airport data on the FMS.
If I did not do that, by just renaming the code of the addon would cause the default airport to also be visible on the external visual and create ghosting as the two airports are clearly different and not aligned with each other.
I hope this satisfies you curiosity.