• 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 we will post updates on AVSIM forums.

    Thank you for your support.

FSX SE Wont Work

D

DaleRFU

Members +
Hi all,

The other day I wanted to launch my FSX SE and it fired up with the splash screen as usual but I won't go any further than that. Normally it bring the menu up in about 10 seconds but now I can leave it for half an hour and still nothing happens. I then decided to remove it from my system and reinstall it and still the same issue occurs. Has anyone got any ideas as to why this is happenings and what could be the issue? I'm starting to get withdrawal symptoms. I'm running my FSX SE on Windows 10.

Kind Regards
Dale
 
The symptom sounds like a corrupt logbook too me.
Go to your "Documents\Flight Simulator X Files" folder and delete "Logbook.BIN"
see if that fixes it.
 
You can also see if Steam loaded. With me Steam sometimes does not open completely, and then I get the same situation as what you describe.
 
Dangerous Beans said:
The symptom sounds like a corrupt logbook too me.
Go to your "Documents\Flight Simulator X Files" folder and delete "Logbook.BIN"
see if that fixes it.
Click to expand...

I can't believe this was the cause, something so simple. Wish I had asked before I erased everything. Big thanks
 
You must log in or register to reply here.
Back
Top