D-Day install problems
Results 1 to 9 of 9

Thread: D-Day install problems

  1. #1

    D-Day install problems

    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?

  2. #2
    Any one have an idea as to a fix?

  3. #3
    Where did you get the file from and what's the name, I can see if I can figure it out.
    Windows 10 Pro 64 bit
    Asus P8Z68 M
    Intel i7-2700
    16 GB of Ram
    GeForce GTX 550 Ti

  4. #4
    I got the addon here; http://fsclassics.com/free-stuff/free-stuff/

    Probably should buy the program to see if it cures the problem. If you have any idea as to what to do I would be appreciated.

    Thanks

  5. #5
    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.

  6. #6
    SOH-CM-2023
    Join Date
    Jun 2005
    Location
    Netherlands
    Age
    65
    Posts
    1,232
    Blog Entries
    1
    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></o>

  7. #7
    This was what I was looking for, I will look into this. It has been driving me nuts with these messages.

    Thanks

  8. #8
    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

  9. #9
    Quote Originally Posted by Astoroth View Post
    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

Members who have read this thread: 0

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •