• 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

  • 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

tech support

T

tigisfat

Guest
After a few emails back and forth with PMDG, they cut me off and told me that it wasn't their product's fault that FSX was crashing.

I could be wrong, but I'm pretty sure after analyzing the Flytampa Grenadines files structure that it was the PMDG MD-11 that destroyed my FSX and prevents it from loading. Flytampa Grenadines has only a basic scenery file structure, there are no core modifications. If you screw that up, FSX just won't load it and will give you an error upon loadup, saying that it can't find the textures. PMDG's only idea was to uninstall the MD-11 and delete the FSX.CFG and DLL.XML, then try everything again.

I just finished running the FSX repair function, and I get the error even faster now.


I'm assuming unless one of our SOH wizards has any last-minute saves for me, that my last option is a complete reinstall. For the last few days I've been gathering passwords and registration keys from around my computer, but we're talking about years and years of flawless FSX and hundreds of payware products. Surely I won't be able to come by all of it, and I'm hoping as much as possible can be saved simply by copying folders.

Sure I can back up gauges, textures, effects, sim objects and other stuff. But if there's nothing else I can do I'd like any advice you can give about preserving my modifications as well as possible, especially my most advanced ones that surely aren't as simple as saving folders. Can I keep my logbook?
 
If it's a problem with FSX simply not starting, the first two things I would check are for a corrupt set of Saved Flight files and/or a corrupt Logbook file. Both instances will keep FSX from starting.

Corrupt Flight Files Senerio:
Delete every file in your My Documents\Flight Simulator X Files folder except your logbook.bin file. Then try a restart.

Corrupt Logbook Scenerio:
In the same folder as above, rename or move your logbook out of the folder. Keep a copy of the logbook.bin file. That is your logbook record and if it turns out to be the problem, that can be fixed with a logbook editor tool. Once you've got logbook.bin file saved and out of the way try a restart.

FAC
 
If it's a problem with FSX simply not starting, the first two things I would check are for a corrupt set of Saved Flight files and/or a corrupt Logbook file. Both instances will keep FSX from starting.

Corrupt Flight Files Senerio:
Delete every file in your My Documents\Flight Simulator X Files folder except your logbook.bin file. Then try a restart.

Corrupt Logbook Scenerio:
In the same folder as above, rename or move your logbook out of the folder. Keep a copy of the logbook.bin file. That is your logbook record and if it turns out to be the problem, that can be fixed with a logbook editor tool. Once you've got logbook.bin file saved and out of the way try a restart.

FAC

Are you sure that's the right place for the logbook? I can't find it in there, and opening my logbook works just fine.
 
With XP and now W7, that's where my log book file has been. The logbook.bin file is the actual flight hours and logging. The second part of the log records are your rewards and badges. Those are located in the "GrantedRewards.BIN" file that is located in the same folder as the FSX.cfg file. What I don't know is if Vista used the same location.

It's strange that your saying that there is no logbook.bin file in your "My Documents\Flight Simulator X Files" folder. I wonder if that may be part of the problem.

Even if you accidently deleted the logbook.bin file in there, FSX would automatically create a new one in that folder the next time you started FSX.

FAC
 
With XP and now W7, that's where my log book file has been. The logbook.bin file is the actual flight hours and logging. The second pert of the log records are your rewards and badges. Those are located in the "GrantedRewards.BIN" file that is located in the same folder as the FSX.cfg file.

It's strange that your saying that there is no logbook.bin file in your "My Documents\Flight Simulator X Files" folder. I wonder if that may be part of the problem.

FAC
hmm. When I dump my .CFG and DLL.XML files, it will start but won't allow me to load a mission or go to the free flight menu without crashing.

When I go to my logbook, everything appears to be functioning.
 
You'll be my hero if this fixes everything.

I did run the FSX repair function, and for some reason the logbook file isn't in my FSX documents and the editor can't find it.

Any suggestions?

Why wouldn't FSX repair make a new logbook?
 
I'm not to sure that the repair option would consider a missing logbook.bin file a problem that needs to be fixed.

When you first install FSX, I am pretty sure that there is no actual logbook.bin file installed. It gets created the first time you start up FSX.

I would do a search of your hard drive looking for the logbook.bin file. It must be there somewhere or I wouldn't think it would be viewable. If you do find it, I would try just moving it back in the "My Documents\Flight Simulator X Files" folder where it belongs.

When your looking at your logbook do you mean from within FSX or using one of the logbook editors available?

FAC
 
I'm not to sure that the repair option would consider a missing logbook.bin file a problem that needs to be fixed.

When you first install FSX, I am pretty sure that there is no actual logbook.bin file installed. It gets created the first time you start up FSX.

I would do a search of your hard drive looking for the logbook.bin file. It must be there somewhere or I wouldn't think it would be viewable. If you do find it, I would try just moving it back in the "My Documents\Flight Simulator X Files" folder where it belongs.

When your looking at your logbook do you mean from within FSX or using one of the logbook editors available?

FAC
There's a search running right now.

I mmeant to say that I can see it from within FSX. I can get to my pilot records menu and everything appears to work okay.

The editor is what I was trying to bring it up with. I can't find it while searching the FSX documents folder.
 
Well, after a million searches it finally found it. It's saying there's nothing wrong with my logbook, unfortunately.

FSX still crashed on startup.
 
Have you completely uninstalled the MD-11 and the scenery?

If it were me I'd download both again, look at what files are going to go where (i.e. don't autoinstall) and have a peek around those folders, see whether there's any residual mess that the uninstall didn't take care of, rebuild the CFG and see what happens.
 
Did you make a note of where the search said the logbook file was located?

FAC

no, I copied it, saved a copy in my backup folders then pasted another copy into the FSX Documents folder.
 
2885382748_7875b97d90_o.jpg
 
I've never done that. Do you know how?

Hi tigisfat,

Click on the windows start icon bottom left of the screen and type 'system restore' in the search programs and files window. Click on System Restore and follow the instructions to restore your system files and programs to an earlier date and time.

While Windows restores your PC to an earlier time, close your eyes and repeat 'there's no place like home' until you arrive back where you were :salute:

Hope it goes OK
 
Hi tigisfat,

Click on the windows start icon bottom left of the screen and type 'system restore' in the search programs and files window. Click on System Restore and follow the instructions to restore your system files and programs to an earlier date and time.

While Windows restores your PC to an earlier time, close your eyes and repeat 'there's no place like home' until you arrive back where you were :salute:

Hope it goes OK

Do I get to pick the date and time?
 
Do I get to pick the date and time?

It won't restore most files, just so you know. I don't imagine the system restore will do anything whatsoever.

And you will be able to pick from a range of dates and times. Your system constantly creates automatically system restore 'points' - i.e. snapshots of your system, that it can return to when you need it to. You can also create them manually.

But as I said chances are it won't sort out whatever file it is that's gone walkabout. For example, in some instances, if I save a word document onto my desktop, then do a system restore to before the document was even created, it will still be there.

Whether the file will be changed or not depends on the information your PC is backing up every time it creates a restore point. On my PC it is set to system settings only - i.e. registry files. All the basics only. Even if I did a system restore to 3 years before I even bought FSX the program and all the add-ons would stay on my PC and work perfectly.
 
Tigisfat, I am sorry to read about your problems. Fortunately for me my version of said product has worked flawlessly and has caused no issues. However there is something to be said about customer service or lack of customer service. Since I am a newbie here and I do not want to make it seem as if I have an axe to grind or anything but this trend towards poor customer service is the reason FSD will never see another dime of my money ever again. I hope in the end you can work though this issue and things can return to normal. Good luck. :)
 
Back
Top