wow, very nice report. Excellent! I do the job now over 20 years, but I have never seen such a good and detailed report - what an effort! Much appreciated …
I guess, I can´t be answer in such detail as you made and I hope, that the answer doesn´t sound “to easy”. You describe a bug in the sim. As you have described, when you enter the STAR in the worldmap, you see the correct sequence and the correct path … but in the moment, where you change the approach from automatic to as an example to the ILS 01L, you will also see, that the path mess immediately.
I assume, ASOBO uses the same logic in the worldmap as for all other FMC/S and Garmins. Because as you also figured out, it´s independent which aircraft you use, or where you enter your flight (worldmap or directly in the aircrafts). My assumption (I can´t really verify it) is that the bug is the conjunction between the different parts of a STAR and the connection to the Approach. There are special rules and here I guess, there is somewhere a limitation in the sim at the moment (or a bug, I don´t know).
But all in all, it´s not a navdata issue - because you see, that one part (the STAR) is coded correctly, when you plan it in the worldmap. How this can be work see you with the “WorkingTitle CJ4 mod”. The devs don´t use the internal FMC function - they had developed it by their own and the result is as expected - here the RIPAM3L arrival with the ILS01L approach. At least the flightpath shows the correct way and the autopilot follows the legs perfect … worth to try …
But back to your issue:
Only ASOBO can fix this - the data seems to be ok (when I use the CJ4 as reference which uses the same data as in the worldmap, in the A320X, in the 787, G1000/3000 …).
Sorry, I hope this answer is detailed and understandable enough. When not, please hesitate to ask/contact us again please. In the meantime, thanks for this great report and your effort to create it.
Happy flying …