I had a look at your airport XML and I can see no glaring discrepancies. It appears you use the DevMode editor and select default values for ILS effective range. The one difference I notice, is my own DME and Glideslope ranges are much, much greater.
<Ils lat="10.93810487147290" lon="114.07946867425618" alt="3.04754704423249" end="PRIMARY" range="
50017.00000000000000" ident="IABC" magvar="0.300000" heading="30.38500022888184" frequency="108.55000000000000" width="5.200000" name="CAT II ILS/DME 03" backCourse="TRUE">
<Dme lat="10.93031027923380" lon="114.07582494904693" alt="3.05064512789249" range="
92631100.69526401162148"/>
<GlideSlope lat="10.92334853611178" lon="114.07168300147505" alt="3.00807329453528" pitch="3.000000" range="
92631100.69526401162148"/>
</Ils>
I know I wanted a larger range than the 5k meters default, but I don't remember selecting a value that high. Nevertheless, it does work, so it is something to try.
Hi, thanks for your feedback, I wanted to ask you if you can also see your custom ILS by removing it from the Navigraph Community.
I do not use Navigraph, everything is default, except my work. This airport does not appear in the default airport list, therefore anything added would be local to this machine. I use "Little Navmap" to track my AI vehicles, it reads local scenery libraries and it shows the ILS feather. If the airport is not loaded, Little Navmap shows only the island airport from Openstreetmap, with no ILS.