xChris93

Any update on this?

@UbaidHas this been checked to confirm it's an isolated issue for this stand? I reinstalled the VDGS last night following the instructions with the issue still re-occurring. Especially suspicious that in the changelog, stands 515 and 516 were modified... which are obviously adjacent to stand 517. Thanks! Chris

Yeah the issue occurred for the same stands even after sim restart - I only tested terminal 5. I uninstalled the previous VDGS version and re-installed but I will try again tonight and report back. Can you guys not check stand 517 to see if it's an isolated problem on my end? Thanks!

Tested on other stands and some were functional... some not. The stand I had an issue with on arrival was stand 517.

Hi, On a return flight this evening from Brussels on vatsim, I noticed that the VDGS wasn't working. I had no issues before the update with functionality. I was using the Fenix A320. Can you please advise on troubleshooting/is this a known bug? Thanks!

I think that I've finally managed to isolate the issue and have a method to reproduce the problem but also resolve it. @Ubaid I'm using the FBW A32NX Dev model. My method was as follows; - Delete rolling cache then exit sim. - Move everything except EGLL scenery within community folder to a temporary folder. - Delete content.xml file and then delete all items within scenery indexes folder. - Run flight sim and rebuild cache then exit. - Move previous community items back in to community folder. - Run sim and should be fixed! However issue reoccurs if content.xml is deleted and rebuilt with all items within community folder (this is likely the issue everyone is having). Thanks and hope this helps anyone else in a similar position! Other than this, the scenery is excellent and with a 3080TI it runs smoothly on my machine. I noticed an fps improvement by also performing the above steps.

Tested with empty community folder and still no ILS on 09 runways 😕 I'm not sure how anybody is getting theirs to work consistently...... I even tried a fresh install of the scenery, deleted content file so many times now lol!

Hi Max, It worked for me once, now that doesn't work... even when populating the LS radio nav page properly. I manually entered 110.3 (ILS 09L/27R) and was unable to pick up the localiser/GS approaching 09 however when crossing 0DME and on 27 side, they both became available. Looking through my community folder I'm struggling to see what could cause conflict. Only potential source could be navigraph data? I'm using the current airac cycle. Thanks for your support!

Yeah I'm also having issues with not being able to capture ILS on 09 runways, working fine when approaching 27. It appears that there is no ILS signal being broadcast towards the west. I've also tried various versions of the A32NX and deleting content.xml without success.

Further to my previous post, after some testing it appears to be an issue/change to the auto population of LOC frequency within the LS Radio Nav page on the A32NX. So advice would be to double check that on approach!

Hi, Tonight I also suffered from no ILS being available for 09L using the most up to date development version A32NX aircraft. Before the flight I also cleared my cache, deleted content.xml and scenery index folder (good practice when installing new scenery). Asobo EGLL is also uninstalled. Luckily it was a clear night and I could fly a visual approach on vatsim, but I was surprised to come across this. Is there a possibility this could be a wider inherent issue with the scenery and needs to be looked at? (based on the reply from Max above where he says its related to a few customers). Is it possible for me to receive support to fix this if not? Thanks!