• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated Tom Clayton has offered to post updates on AVSIM forums.

    Thank you for your support.

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