Not necessarily, if you direct to a waypoint from the flightplan then yes. If you manually insert a waypoint instead of selecting a waypoint from the flightplan then no.
I insert STARs in the MCDU, sitting at the gate or on cruise, and find that there are “legs” sticking out of the new route. I have to go in and delete the stray WPs manually. So idk.
After the FWB update that features Simbrief functionality it is possible to get a new route from cockpit as long as you generate a new flight from SimBrief - there is no way as yet to load earlier FPs or save new ones from cockpit. But creating a new one with Simbrief is so fantastically easy. (And I delete the SID and STAR as these so often get weird when applying them in flight. And not possible to delete when in flight.)
Are you in VFR or IFR? If IFR, did you select ILS approach, and press LS and APPR buttons when at the approach phase?
If VFR, select VS and insert a descending ratio. Or…disengage AP and reduces engine power to reduce altitude or put the nose down manually (if you are really close, down landing gear, give some flaps and speedbrake to reduces speed and altitude faster)
Sometimes, departure and arrival runway in simbrief is different to in game ATC which one should I follow?
When input arrival runway, if that runway does not have any frequency (ILS, RNAV…), MCDU would not display runway to select, so what should I do at that time?
And sometimes, SID and STAR in simbrief is different to in game SID and STAR, for example runway 11 in KMGE have STAR WRGNZ1 in simbrief but in game it was WRGNZ3, is there any reason for that?
I think no planning service can really predict the runway. If they do have info, it can for sure be overrode by local ATC. Many people don’t put the SID or STAR in until they get weather from the actual airport.
As for runways without RNAV or ILS, I assume it is just done by VOR navigation and by hand so maybe there’s nothing to show in the FMS.
I think the problem with assigning STAR is that the ATC tends to be too late in giving you the runway assignment. They don’t give you the STAR at all, but only the approach, VIA transition waypoint. And since the navdata in the sim has the STAR to be a fixed pattern, having an entry waypoint all the way down to the runway. By the time the ATC give you the runway assignment, you’re already passed the first waypoint in your STAR, so when you select the STAR, it backtracks you because you have to go through the “first waypoint” that you already passed before.
It sucks, that’s for sure, but that’s why I just put my whole flight plan from SIDs and STARs, and the approach from the beginning. So far, I’m always landing with the right wind direction, never changes away from where I want it to. But maybe that’s just because of luck.
To descend : Set the new altitude in the AP. Turn ON the VS. Use the thumbwheel to “decrease” vertical speed. The vertical speed bug should go negative. The heading bug will return to zero when the descent altitude is reached. The VS button will go off and ALT button will be on.
Maybe I’m being obtuse [and having re-read your post I am obtuse] but I use MSFS for assigning the STAR ie in the drop downs think there marked green with the ILS marked purple. ATC tend generally to get me down in most cases in time for the STAR but occasionally there late. Out of interest what do you use for inserting your stars into your route if you don’t use MSFS or perhaps you do?
If the diamonds aren’t showing up, it is probably because the frequency of the ILS beam has not been automatically entered in the nav radio. They occasionally do not self populate, mostly with add-on sceneries.