• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

D-Day install problems

Steven190

Charter Member 2016
I downloaded the D-Day addon, not I get error messages upon start up.

The messages are the program can not find areas 135,136,137,138 and 139.

I have looked for these and I can not find what it is looking for. has anyone any idea as to were these files are and how to fix them?
 
I could be wrong, but I think the problem lies here:

It ALSO includes the (first) Defense and Attack phases of Courseulles-sur-Mer. This part of the Juno sector, called Mike Beach, was assigned to the Winnipeg Rifles of Canada. I have included this first module (of many to follow) so you will have the basic folder structure of your D-Day Project already in place after installation. All subsequent freeware modules of the D-Day Project will be loaded into these folders and no further entries in the scenery.cfg are necessary.

Apparently it adds folders to the scenery.cfg for later modules, but right now those folders are still empty, so it is looking for scenery that has been added to to .cfg but isn't really there yet.
Kind of sloppy way to do things, in my opinion.
 
It may be that there is a slash (\) missing in your scenery.config file between ‘Flight Simulator X’ and the rest of the filename of each of the missing sceneries. That was a problem that I had. I think Francois gave the solution (I could never have thought of this myself).<o:p></o:p>
 
This was what I was looking for, I will look into this. It has been driving me nuts with these messages.

Thanks
 
The (\) were missing. I replaced the \.

Unfortunately that did not cure the problem. The messages still come up upon startup. I am at a lost as to what is going on here.

Thanks for the help
 
I could be wrong, but I think the problem lies here:

It ALSO includes the (first) Defense and Attack phases of Courseulles-sur-Mer. This part of the Juno sector, called Mike Beach, was assigned to the Winnipeg Rifles of Canada. I have included this first module (of many to follow) so you will have the basic folder structure of your D-Day Project already in place after installation. All subsequent freeware modules of the D-Day Project will be loaded into these folders and no further entries in the scenery.cfg are necessary.

Apparently it adds folders to the scenery.cfg for later modules, but right now those folders are still empty, so it is looking for scenery that has been added to to .cfg but isn't really there yet.
Kind of sloppy way to do things, in my opinion.

I am going to delete these entries to see what happens. Of course I will back up the complete file
 
Back
Top