• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FS2004 Broken DOF

Messages
1,043
Country
us-northcarolina
DOF not in support topic so i'm posting here.

No matter what I click on I get this:

async


Grrrr...too small, can't read it.
Anyway it says, 'It seems that some area locations are wrong'.
As in? What would that mean?
It didn't do that a couple days ago.

Please Jon fix it :D
 
Wut :eek: don't you bring a catastrophe on me. Knock on wood, my 10th installation of Windows 7 has been stable for more than a month...phew.
 
Well it means that the program ran through your scenery.cfg file and could not find the file locations for the areas specified.

So technically DOF is probably not broken ;) It is doing its best to tell you it can't find some scenery areas specified in the scenery.cfg you pointed it at :)

Did you change the location of your active scenery.cfg or perhaps change the setting as shown in DOF?
 
So technically DOF is probably not broken ;)
Technically it's not broken but practically it's not working, JK :D

Since I did so much library clean up let me check what I could have forgotten to set, reset, preset or even deset.

Did you change the location of your active scenery.cfg?
If I had then DOF couldn't have

Well it means that the program ran through your scenery.cfg file and could not find the file locations for the areas specified.

Haha.
 
Jon, DOF is complaining of not finding SomePath\Scenery\Scenery. In other words it's looking for a scenery folder inside of a scenery folder.
Any idea why?
 
Jon, DOF is complaining of not finding SomePath\Scenery\Scenery. In other words it's looking for a scenery folder inside of a scenery folder.
Any idea why?

Yes - it found it in scenery.cfg. As far as I recall DOF does not invent any paths for itself but reads what is in the scenery.cfg. Open the one it is reading with notepad or similar and look for that path. Be aware that scenery.cfg does get shortened paths it they are in the FS folder setup. You will see full paths if the scenery is elsewhere (on another drive for example)
 
That explains my mistake then. I registered the Scenery folders of sceneries instead of the scenery folder itself. That doesn't sound right LOL.
I.e.: W88\Scenery instead of just W88.
 
I corrected the situation but now I'm unsure of what's going on.
If I click on Find in DOF should I see a progress bar or some kind of indication the program is searching and if it doesn't find any duplicate should I get a message or not?
Atm I click on Find and nothing happens.
 
I corrected the situation but now I'm unsure of what's going on.
If I click on Find in DOF should I see a progress bar or some kind of indication the program is searching and if it doesn't find any duplicate should I get a message or not?
Atm I click on Find and nothing happens.

Well yes you should see a progress bar. But the Find button looks for your FS installation. Use the Scan button to search for duplicates.

Bizarre and unexpected as it is :) - everything we have covered so far in this thread is in the Operational Notes pdf file ;)
 
:rotfl: Ok fine I admit it, staying up all night is not good at my age anymore LOL.
I am publicly humiliated :eek:

No need..... my skills at writing documentation are pretty poor so it is just nice when I realize that for once I did cover most of the bases.....:D

I am sure you are familiar with RTFM :D
 
Yeah I know RTFM but hey I'm a guy so what do you expect, I won't read the manual until something is broken. Manuals are for women aren't they :D
Fortunately there isn't one of those around.

My accounting teacher had RTDQ written on the board before every test.
Read The Damn Questions.
 
Hey Jon, I know very little about checksums. I know what they are, I've read how they are calculated (and forgot) but can 2 files have the same checksum?

DOF is reporting a bunch of similar checksum for default objects compared to downloaded libraries, i.e.:
asias\scenery\ob9asia0.bgl compared to default_terminals_ss_v2.bgl.

It's also reporting default scenries being duplicated in the same folder with different GUID such as namw\scenery\la.bgl.

Am I going to be sent back to the help file :D
 
Hey Jon, I know very little about checksums. I know what they are, I've read how they are calculated (and forgot) but can 2 files have the same checksum?

DOF is reporting a bunch of similar checksum for default objects compared to downloaded libraries, i.e.:
asias\scenery\ob9asia0.bgl compared to default_terminals_ss_v2.bgl.

It's also reporting default scenries being duplicated in the same folder with different GUID such as namw\scenery\la.bgl.

Am I going to be sent back to the help file :D

It probably is in the operational notes but I am feeling in a good mood today :)

Two files can have the same checksum. It means they are byte identical. In this context it means that the same model is present in more than one bgl file. They may have the same GUID or they may be different. However if you display them in FS they will look identical because they are identical.

If I remember correctly Sidney extracted a lot of objects out of stock files and placed them in new libraries. This file probably comes from the early days of EZ-Scenery. It is very possible that the stock objects are locked because their placement code is in the same file as the model. By extracting them into a new library with a new GUID Sidney has made them available to many users.

This just underlines the complexity of the whole model business. It also points to why using DOF is not trivial. Certainly there is no point or value in trying to avoid this particular duplicate.
 
It probably is in the operational notes but I am feeling in a good mood today :)

Phew, close call...but I avoided the dog's house ;)

Thanks for your explanation, makes sense.

I don't understand though, why it's reporting la.bgl being duplicated in the same folder (default folder) with different GUID.
 
Phew, close call...but I avoided the dog's house ;)

Thanks for your explanation, makes sense.

I don't understand though, why it's reporting la.bgl being duplicated in the same folder (default folder) with different GUID.

because even MS duplicated objects..........................
 
Back
Top