Yikes – thanks for letting me know, I really appreciate it.
Bought the Concorde and took her for her maiden flight. I felt bad for her, there were alarm bells ringing all over. 
I definitely need to read the manual with this bird. Somehow I managed to land her VFR and let me tell you it’s a tiny view from the cockpit ha ha.
Really well done aircraft! Great job to all involved.

Money well spent. Now… to go get that manual. Lol
Wellcome to Concorde experience!!
Your workaround solution worked perfectly on the occasional instances when this non-response issue happened.
Thank you.
That flicking between them seems to work. When i aktivate VOR/LOC on INS and flicking to RAD TRK/HDG also goes off and she turns to Localizer course.
I testet so much but this simple solution just flicking again i never tried. Thanks. CodenameJack also mentioned that earlier but i think i missed that.
After intensive research, I have now been able to successfully complete some ILS approaches in autoland mode. In my case the reason for the irritating behavior of the autopilot was a manipulation of a 3rd party application (PF3) via FSUIPC. This means that even a clean community folder (PMS and TDS GTNxi are special candidates here) does not protect against interference. This will cause problems for many MSFS developers in the future.
Please read my post again. I am climbing at 400 kts from ground level to 28000 ft - the subsonic climb in cold power. Normal rate of climb is 2-3000 fpm (as in previous versions) but in my case the AP reduces the rate of climb to 500fpm. Nothing to do with the supersonic climb or max clb etc.
This has also been an issue in the DC-6 where switching from GPS to LOC on the GNS530 sometimes doesn’t “take” and you need to switch back and forth a few times. I suspect (as mentioned earlier) that this is an “undocumented feature” of the sim autopilot coding and not specific to any aircraft.
Yeah having the same problems with the VLOC ILS system with Concorde. It is so frustrating not to be able to rely on the nav systems. The developers seem to think there is no problem with it and that makes the whole thing worse, you cannot continually do straight in approaches, and flying Concorde is difficult enough at the approach stage without having to flick that switch once that one twice etc and hope you actually intercept the LOC. Sorry but I’m grounding Concorde, and since the developers think it’s ok no problems I guess that’ll be for the foreseeable future.
Feels a bit drastic. If in doubt, just flick the switch a couple of times? That’s what I do on the DC-6. As I said, it’s not aircraft specific, so nothing these devs can do about it.
Yeah they could say there is an issue….moreover this is Concorde, trying to manage CG, Speed, altitude, etc, the last thing you need is a blown ILS and go around….especially when the sales pitch is at new simmers….sorry it’s just not airworthy at this time
There isn’t an issue if you operate the plane as @DEAN01973 has outlined
There is when you press VLOC you want it to work! It works in freeware aircraft in MSFS!
So given these devs can’t fix it, what exactly are you asking them to do?
For me works the ILS with HDG-Track. I push “HDG TRK” (still INS-Switch) to the RWY-heading on the last Fix-points before i except the ILS and then i switch to RAD and when the glideslop start to sink then i set the gearleveler and when the glideslope comes one point for middle, i push the “GLIDE” button! This works for me on a ILS Landing. I found out when you switch first from “INS” to “RAD” and you push after the HDG-TRK and GLIDE then not works the ILS-landing! I will test this with the VOR-LOC button!
The suggested CG in the cockpit and in the engineer’s panel don’t agree with each other. Which one to follow?
Anyone else still having issues with max cruise and autothrottle? The plane easily makes 2.04 but I turn on autothrottle and max cruise and it decelerates to M1.88?
I follow the engineers panel.
To be fair, I am sure many of the users here including myself feel that developers here are among the most helpful and attentive to the user reported issues. Jack goes to the extent of even sharing portions of the source code! Which developer does that?
Dean and Jack even fly and test each of the reported ILS issues personally and share the videos of the system working just fine.
If one reads through all the posts above, all reported issues have been addressed and fixed. Many are due to user’s unfamiliarity with the Concorde’s system. And when not able for whatever reasons, a workaround has been offered.
Is there a problem with the Concorde ILS? No.
Can there be occurrences when the VOR LOC isn’t responsive? Sometimes. But even then it a matter of resetting the RAD / INS which takes hardly 1 second which is nothing compared to the approach procedure.
For me the same! Also in “MACH HOLD”. The throttles goes in idle… I take the autothrottles off and when the cocncorde flying 2.01 mach so i try to adjust the thrust levers so that i maintain the value. I hope, it helps!