Hi all,

I have noticed that after installing the scenery of VOZ1.8, the data base are not correctly read, as one of the file.bgl shows up ahead of the actual AFCAD. what I mean by that, is there is a file for TWY that is ahead of the actual AFCAD of YSSY.

when I open AFCAD or or AFX I can see the TWY is highlighted and the real AFCAD is second, that result, when running maker RNWY and the DB of FSCommander, the real data is not read. If I rename the TWY. bgl to org for example the data is scanned properly. so my question is how can I lower the priority of the file TWY to go under the AFCAD, so It can be scanned properly. When I open AFCAD I see the TWY as 1 the AFCAD as 2 and the default as 3 in the priority. so I need to switch the 1 and 2.

Hope I explained my issue properly.

Thanks for any help

Regards

Hani

The simple fix would be to move VOZ AF2 Scenery above VOZ Scenery in the Scenery Library.

 

This might fix your FSCommander problem, but might also screw up the scenery in the sim.

 

You could also create a new scenery layer below VOZ AF2 Scenery and move the taxi sign .bgl to that area. There is an exclude for the default signs that you might want to move also as it may cause problems if it has higher priority than the new taxi sign .bgl.

 

regards,

Joe

Hope I explained my issue properly.

 

The TWY.bgl is most likely a 'stub' airport containing new taxiway sign data. Problem is FSCommander sees it first and since there is no runway info FSCommander fails. Quick fix; remove TWY from FS9 and run FSCommander, then put TWY back in its original location. The best permanent fix would be if AFX is capable, import TWY into to the opened YSSY airport file, save and compile, then remove TWY.bgl from FS9. That fixes the duplicate problem that FSCommander sees. By the way the file TWY or a file by any other name of similar construction is / was a common way to correct or add taxiway signs to a airport. That said, as you see, there are certain drawbacks.

 

Since you are familiar with AFX and if AFX can not import files (I don't have AFX so I don't know.) You could use Airport Design Editor (free ware) to do what needs to be done.

 

http://www.fsdeveloper.com/forum/downloads.php?do=file&id=99

 

or

 

http://www.airportdesigneditor.co.uk/ade_003.htm

 

I hope this helps, if not we'll try again!

 

Regards,

Mel

To explain what Mel stated, which should work, ADE works on a project basis. Only when the project is finished (and saved for further editing) you then compile and save the .bgl. This will combine the two files when you import each using in ADE File\Import from .bgl for the TWR and AF2_ file by browsing to them.

 

Here is the file menu with what you can use highlighted.

 

 

 

Open Airport is for opening an existing project file .ad2 or .ad3.

Open Airport from Bgl is for initializing the project with an existing airport type .bgl such as your AF2_. (If you use it again it will close the project based on a prompt answer and load the new airport .bgl.

Import Bgl you can try using with the TWR.bgl file to bring it in without closing the project.

 

Save Airport As lets you name the project file.

Save Airport saves the project using the current project name and path.

 

Compile Airport creates the .bgl from the project.

 

For further work always open the project because it has specific code internal to ADE which is not passed to the compiled .bgl and if you reopen from the .bgl that will not be in there.

 

ADE has two classes of compiling discrepancies. One is a caution error and the other is a warning that the compile will fail and a box will point to the code. It is best to run the fault finder first in the project and scroll through the list. Some faults will cause only cautions and others will cause compile failures. If scenery has code that lies outside of limits in the Microsoft FS9 bgl compiler SDK allowance limits you will get a caution or an outright fail notice. Cautions allow compiling but Warnings do not. Cautions are open links, etc. Failures cause a compile shutdown. For example, those communications that have frequencies outside of the allowed VHF range (UHF like 274) in the COMs list will cause a Warning and the compiler will fail. Two many parking codes at a gate will cause a caution that some may be excluded. The problems are shown as you click on the items in the fault finder list if I recall correctly.

 

I bring this out because when you Import the TWR .bgl there may be conflicts with global deletion statements.

 

Just try and see what you get in the combined project. Just remember to Import the Airport AF2_ .bgl first and the just Import Bgl for the TWR file. Then run your various lists and make sure all is there.

I was thinking along the lines of Mel and Ron and wanted to test a couple thing before suggesting them.

 

There is a file in ...\VOZ Scenery\scenery named VOZ_Robs_YSSY_TWY_Signs.bgl and it shows up in Afcad2. After looking at that file I am not sure what it is this file is supposed to do.

 

After disabling that file I looked around YSSY and everything looks fine in terms of taxiways signs. There is no shortage of them, they are definitely not default and I do not see any duplication of signs or signs out of place that would indicate the default signs are still there.

 

I opened AF2_VOZ_YSSY.bgl (found in ...\VOZ AF2 Scenery) in ADE9 and it contains taxi signs which indicates it was not made with Afcad2.21. I remember seeing, in the early days of AFX and ADE, people who renamed files with the AF2 prefix so end-users would know what they were.

 

It is possible that VOZ_Robs_YSSY_TWY_Signs.bgl was left over from an earlier version of VOZ and is no longer needed.

 

Before going to all the work suggested by Mel and Ron (which I don't think will work in this case anyway) I would disable VOZ_Robs_YSSY_TWY_Signs.bgl and test.

 

I think that will fix the issue without any adverse effects.

 

regards,

Joe

 

[edit]

AF2_VOZ_YSSY.bgl contains 332 taxi signs, VOZ_Robs_YSSY_TWY_Signs.bgl contains 15.

 

I checked 5 of the 15 and they were duplicated in the 332.

[/edit]

Hi All,

Thank you so much for your very much detailed explanation, what I end up doing, was as Joe suggested, as the other option will need from me some time to digest, witch I will, as i need to understand a bit mor about compiling BGL. Foe now by disabaling the TWY. bgl witch is what Joe named, made FS commander to read the correct info for the RNWY. I don't know what that file of TWY is doing, as by removing it every this is still 100%, perhaps it's a left over as Joe suggested.

For now all is fine and I am a happy flyer. Ronzie and Mel, I have to understand your process as I have the same issue in CYYZ where there is a Sign.bgl that is always higher in priority over the AFCAD, so I will look at your method to try to fix it.

Thanks so much to all, much appreciated.

Regars

Hani

I would like to take the time the thank both Ron and Joe for their insight and clearer (than mine) way of looking at the problem. I don't have VOZ and that definitely hindered my point of view.

 

Best regards to all,

Mel

Sorry that file was recreated as a dummy file but for some reason it must have been left out and the old file kept in......

 

Just a heads up While we wait for the Flytampa Version of YSSY to be completed I have done a few updates to the scenery since my Avsim release but have only uploaded them to, http://aussiex.org/forum/index.php?/files/category/16-voz-downloads-fs9/

 

In one of the downloads I do advise to remove that TWY Bgl as it is not required.

 

Regards

 

Flukey

Thank you so much Flukey, much appreciated.

I will download the new version.

Best regards

Hani