- Messages
- 34,854
- Country
New Build to test this problem
Download here:
http://www.scruffyduck.co.uk/files/sde_build_2634.zip
Things to note:
this build is intended to be used to test the scanner problem
Install it away from any existing SDE installs
Set you FS and BglComp Folders. Also set the units to make sure that you have a full settings.xml file.
Open the scanner and click Scan as before. Note that you will get a progress bar that should run twice. The first is the default scenery folder and the second is your addon scenery folder. After the second run of the progress bar it will close and the scan button will stay greyed for a while. This is when the tree of objects is being transferred to the window. It is slow.
Finally you will get the scan button back and the the tree (or not!).
Click on View Log. There is going to be a lot of stuff in there. Here is some information to help interpret it.
Note I have scanned an FS9 installation but that should not make any difference and you should see similar stuff for FSX
There are two section headers in caps that signify which folder is being scanned. An entry like this
signifies that a file has airports in it and they have been extracted
An entry like this:
signifies a file that has no airport data in it (should only turn up after SDE starts scanning the Addon Folder
An entry like this:
signifies that SDE found a bgl that is not BglComp based (should only turn up in the Addon Folder section and is related to FS9 files)
At the end you should see something like this
SDE processed 235 files in the Addon Scenery Folder Tree and had 23769 airports to put into the tree. The tree got built!
You numbers may be different.
If you see anything else the it might signify the problem Also if the run stops short somewhere it might show us the file (or maybe the one before it) that is the problem
Download here:
http://www.scruffyduck.co.uk/files/sde_build_2634.zip
Things to note:
this build is intended to be used to test the scanner problem
Install it away from any existing SDE installs
Set you FS and BglComp Folders. Also set the units to make sure that you have a full settings.xml file.
Open the scanner and click Scan as before. Note that you will get a progress bar that should run twice. The first is the default scenery folder and the second is your addon scenery folder. After the second run of the progress bar it will close and the scan button will stay greyed for a while. This is when the tree of objects is being transferred to the window. It is slow.
Finally you will get the scan button back and the the tree (or not!).
Click on View Log. There is going to be a lot of stuff in there. Here is some information to help interpret it.
Note I have scanned an FS9 installation but that should not make any difference and you should see similar stuff for FSX
There are two section headers in caps that signify which folder is being scanned. An entry like this
D:\Program Files\Microsoft Games\FS9\scenery\Same\scenery\ap923260.BGL
Decompiler Output...
. 34472 646 10 ... NameList
Name List Extracted
signifies that a file has airports in it and they have been extracted
An entry like this:
D:\Program Files\Microsoft Games\FS9\addon scenery\static objects library\scenery\ez-extra-objects-1.bgl
Decompiler Output..
signifies a file that has no airport data in it (should only turn up after SDE starts scanning the Addon Folder
An entry like this:
D:\Program Files\Microsoft Games\FS9\addon scenery\LF2 - Madisonville\scenery\LF2_VTPL.BGL
Decompiler Output...
BGL ID 1 not correct
signifies that SDE found a bgl that is not BglComp based (should only turn up in the Addon Folder section and is related to FS9 files)
At the end you should see something like this
Processed 235 files
Building Tree with 23769 entries
Tree Built
SDE processed 235 files in the Addon Scenery Folder Tree and had 23769 airports to put into the tree. The tree got built!
You numbers may be different.
If you see anything else the it might signify the problem Also if the run stops short somewhere it might show us the file (or maybe the one before it) that is the problem