MSFS20 ADE20 and VASI

[Ironpot]

Hi Jon,
I'm having trouble with VASI and the 2way edit. In Dev mode, the placements for VASI show but seem to be dropped for ADE. They don't show in ADE as such and appear as only 1 line (the Primary)
I added the 2 Primary and 2 Secondary directly to the XML and built OK. The ADE XML, whilst retaining the statements, appear as blanks in the ADE interface:

But the other statements don't appear to pick up the xml values

 

[scruffyduck]

Ah - its possible they are part of the runway record that I haven't completely coded. I will have to take a look

Thanks Phil

 

[JimBrown]

FYI, I mentioned this in the Alpha 19 pinned thread back in early May. https://www.fsdeveloper.com/forum/threads/alpha-19-released.452236/page-3#post-881985

Just reminding you of that. ;-)

Thanks,
...jim

 

[scruffyduck]

FYI, I mentioned this in the Alpha 19 pinned thread back in early May. https://www.fsdeveloper.com/forum/threads/alpha-19-released.452236/page-3#post-881985

Just reminding you of that. ;-)

Thanks,
...jim

Thanks for the reminder

 

[scruffyduck]

I am looking at this now and I am able to add and save VASI with ADE in the Property Dialog. These VASI stick certainly in the ADE project format (.ad20) However I need to check the impact of two way editing which uses the XML and not the ADE project file format. It is possible that ADE is not reading the XML correctly

 

[connomar]

Ah - its possible they are part of the runway record that I haven't completely coded. I will have to take a look

Thanks Phil

Hi Jon,

I've only just discovered this problem, because I am frequently exporting the XML and then Importing again. - Don't ask why, it's all about using Google Earth Maps for up to date data.-

What I have found is that the Secondary End Vasi record is overwriting the Primary End, leaving the Secondary end set as disabled, though rubbish data showing greyed out. The data is correct in the export, so the problem must occur in the import.

Hopefully this little gem will help you track down the bug.

Many thanks

Martin

 

[connomar]

Hi Jon,

I've only just discovered this problem, because I am frequently exporting the XML and then Importing again. - Don't ask why, it's all about using Google Earth Maps for up to date data.-

What I have found is that the Secondary End Vasi record is overwriting the Primary End, leaving the Secondary end set as disabled, though rubbish data showing greyed out. The data is correct in the export, so the problem must occur in the import.

Hopefully this little gem will help you track down the bug.

Many thanks

Martin

My little Gem seems to have been made out of paste. I lost my runway VASI and lighting data without doing an import, I just don't know exactly when..... yet.

 

[scruffyduck]

This bug has been identified and fixed in the next Hot Fix

 

[connomar]

This bug has been identified and fixed in the next Hot Fix

Hi Jon,

Please can I confirm that Hotfix 3 should have solved the missing VASI and Approach Lighting issue. I Patched Hotfix 2 to 3 and I thought I tested it successfully, but now it is getting lost again. The only new thing I've done is tried the 2-way Developer operation on MSFS. The Version Number Matches your published number v20.21.7997. I was wondering if the fix was in the exe or a dll ?

 

[Ironpot]

I don’t believe it was in HF3 as it was released 23 Nov and Jon said last Monday 29th it would be in the next release. I too still have it being dropped

 

[connomar]

I don’t believe it was in HF3 as it was released 23 Nov and Jon said last Monday 29th it would be in the next release. I too still have it being dropped

Thanks Philip, I should follow the timeline more carefully.

 

[scruffyduck]

It is in HF4 which will be released today

 

[connomar]

It is in HF4 which will be released today

As they say over here "You are the Man"