Left CDU - INVALID NAME - At boot up
-
Known issue. It’s being addressed
Brian
https://www.flyaka.com
Alaska Adventures -
Known issue. It’s being addressed
@dadgametime That's very interesting, since I've never seen it before. Who else is fixing bugs in Starship for me?
EDIT: I have left my original line of questioning below in case this doesn't work, but please ignore it unless we have to come back to this topic.
After a much more careful look at the code, I suspect this is caused by a user waypoint that was previously saved with an invalid name. I'm not sure how this would happen, but a user waypoint consisting of two characters, with the first being a number (ex. "6Y") could do it. If you don't have a lot of saved user waypoints that you care about, you could try purging your user waypoints with the "ERASE ALL USER WPTS" option in the "FMSSFP" menu. If this doesn't work, I can take up the issue with you through Just Flight Support (I saw your ticket) to get to the bottom of this.
Original thinking...
I just looked at the code, and there are only a handful of things that can trigger this message. I assume you are importing a flight plan from the world map, 2024 EFB, or some 3rd party application. Is that correct? I could start by saying that this is not currently supported in Starship, but since I'm working on that support right now, I'm more curious what causes it before the CDU even initializes.
If you are importing a flight plan, could you send me the list of waypoints that triggered this message? Preferably not just the approach name, etc., but the actual list of ICAOS that was injected into the simulator, if this is possible.
-
@dadgametime That's very interesting, since I've never seen it before. Who else is fixing bugs in Starship for me?
EDIT: I have left my original line of questioning below in case this doesn't work, but please ignore it unless we have to come back to this topic.
After a much more careful look at the code, I suspect this is caused by a user waypoint that was previously saved with an invalid name. I'm not sure how this would happen, but a user waypoint consisting of two characters, with the first being a number (ex. "6Y") could do it. If you don't have a lot of saved user waypoints that you care about, you could try purging your user waypoints with the "ERASE ALL USER WPTS" option in the "FMSSFP" menu. If this doesn't work, I can take up the issue with you through Just Flight Support (I saw your ticket) to get to the bottom of this.
Original thinking...
I just looked at the code, and there are only a handful of things that can trigger this message. I assume you are importing a flight plan from the world map, 2024 EFB, or some 3rd party application. Is that correct? I could start by saying that this is not currently supported in Starship, but since I'm working on that support right now, I'm more curious what causes it before the CDU even initializes.
If you are importing a flight plan, could you send me the list of waypoints that triggered this message? Preferably not just the approach name, etc., but the actual list of ICAOS that was injected into the simulator, if this is possible.
@Black-Square Spot on Nick, purging the user waypoints sorted it (I've not been importing flight plans since day 2).
Thanks
James -
Thanks for confirming that. I've made the error message more clear for future troubleshooting. I've found that MSFS 2024 creates all sorts of user defined waypoints with name collisions, while MSFS 2020 didn't do this unless you explicitly created one yourself...
