I run FSX/FSUIPC4 on a Win7 64-bit system. Home repairs required me to disconnect all devices - Saitek yoke, TQ, and rudder pedals. I tagged them so I could replug them into the same USB ports where they had been. I started FSX and flew the default Cessna with no problem.

 

Then I tested the default 737 and as soon as I started a Free Flight, while parked on the ramp - before I touched any controls - the throttles opened by themselves. To gain control I used the Saitek TQ to open, then close the them. I thought it was just an anomaly.

 

I taxied to active and when I pulled back the yoke... aauughhh - no elevator control - tore up a lot of fence! I restarted FSX and opened FSUIPC4 to see if the axes were assigned correctly and the configuration settings were ok, and found no problem. No reason they should have changed, but I wanted to look.

 

I restarted FSX a few times trying to find a reason for these problems, and for no apparent reason FSX started going into an endless loop while initializing. This symptom is permanent. Maybe a file got corrupted somehow. Can't think of anything else. 

 

I backup my files regularly, so I restored the most previous fsx.exe.  No change. 

 

Since I couldn't get far enough in FSX to check FSUIPC4 settings again, and just in case the fsuipc4 dll or ini files might have gotten damaged somehow, I installed Pete Dowson's newest FSUIPC4 version. Still an endless loop.

 

Any ideas for diagnosing this are eagerly accepted. I have numerous addons so a complete FSX reinstall would be a nightmare, especially since that might not change a thing either. I usually do well at diagnosing problems but this one has me stumped.

 

MH

Only thing i can think of is to backup you FSX.CFG then delete it.

restart fsx and see if that solves it.

I use Acronis and backup the whole of FSX to a cheap 1TB drive.that way any problems i can be up and running 10mins later.

you must also backup your Primary drive because FSX has files on that as well.

well worth the investment.

 

steve

ps have you tried starting fsx without anything plugged in and adding them one by one after it has started.you can do that with USB stuff.

might help to find which one is causing the problem.

Thanks for the fsx.cfg thought. I will definitely try that. I think when FSX doesn't find that file on startup it creates another. I think it lives on the C: drive. I'll try that, although don't know how it could happen after a controlled shutdown, then pulling the plug on the surge protector.

 

I did disconnect all FS devices but problem persists. I've had axis assignment and calibration trouble in the past after plugging devices back into ports in which they weren't initially, so this time I took care and tagged each USB cable with its matching port location.

 

I should have both my system drive and FSX drive fully backed up on a 1TB Seagate external portable device. Do you have a specific FSX file in mind on the system drive?

MH

When you say you are in an "endless loop"  does that mean you can't get past the start up "Splash Screen"?

 

If this is the case, you need to go to My Documents/Flight Simulator X files, open the folder and re-name the Logbook.bin file so FSX can build a new one.  If this is scuessful, you can fix the old logbook file with a fixer program.

If by Splash Screen you mean the very first blue-fade-down-to-white window that says Flight Simulator X and has part of a sectional map on the left and a world map on the right as a "watermark," then yes...  I can't get past that. 

 

I haven't acted on Steve Howlett's suggestion yet, so if backing up/deleting FSX.CFG is a good first step, followed by backing up/deleting Logbook.bin, I'll do those two things. 

 

Sound right?  I want to be v. careful with this.

It can never hurt to back up your files beore doing something.  I think you described the "Splash Screen" very well!

Because this happened when you changed planes or added a new version of FSUIPC I'd make this suggestion.   The dialog box that asks if you want to run/trust a new guage or dll often pops up under the start up screen.  It appears like an endless loop but FSX is just waiting for you to click OK on the hidden window.  If you minimize FSX you will see the pop up. Click it and you will be good to go.

Hi mate

I backup the whole of C:\.for me it's just easier that way.there are 2 or 3 different locations on the C:\ drive that need to be saved so you might as well do all of it.I also use a freeware backup of my emails and bookmarks for Mozilla firefox my web browser.

haven't had any problems doing it this way and if i do have an issue after installing either scenery or addon aircraft .with in 10-15 mins i'm back to a perfect install.

yes if you rename your FSX.cfg file when you start FSX it will build a new one..like tom says you have to go through the Trusted software accepting them, which are not always visible.

 

 

   steve

It can never hurt to back up your files beore doing something.  I think you described the "Splash Screen" very well!

You noticed that I'm detail oriented, eh? Obsessed. Born and raised in the Bay Area. Love the Giants and Niners. Used to really enjoy Montana and Rice play the game.

Because this happened when you changed planes or added a new version of FSUIPC I'd make this suggestion.   The dialog box that asks if you want to run/trust a new guage or dll often pops up under the start up screen.  It appears like an endless loop but FSX is just waiting for you to click OK on the hidden window.  If you minimize FSX you will see the pop up. Click it and you will be good to go.

I don't recall being asked if I want to run/trust anything so maybe there was no hidden window. Anyhow, I made FSX rebuild the fsx.cfg and Logbook.bin files and FSX starts normally. But thanks very much for the input.

I rashly said that everything was back to normal and selected "Mark Solved" for this issue.  Well, that's true, but...  even though FSX now starts for me (for which I'm grateful beyond words), I didn't anticipate just how much work I might have after having FSX rebuild FSX.CFG and Logbook.bin.

 

All the customized Options settings that were probably in FSX.CFG (I haven't looked yet in detail), which I made to accommodate my countless add-ons (graphics, weather, traffic, etc.), went away.  The old FSX.CFG file had much more information in it than the new one, and since it's a text file, first I'm going to restore it to see if it caused my bug.  Even if it's corrupt, I may be able to salvage most settings from it.

 

And the scores of flight records that were in my old Logbook.bin did not propagate to the new file, as I suspected would happen.  You mentioned a fixer program and I would gladly try that. Where can I find it?

 

Here's an oddity.  After rebuilding both files, I lost the ability to make the default C172 begin flights with the ATC winidow active, even though I have that option ticked.  And before the bug, sometimes when I taxied I used Progressive Taxi instead of searching for airport diagrams and switching tasks as I moved along.  FSX now doesn't even display that option (it was #3, after Tune to Tower and Tune to ATIS) once I have taxi clearance.  I do not have Directx 10 ticked so that is not the cause of this bug.  Any ideas on these?

 

MH

You DID save the old FSX.cfg file didn't you?  Take out the new one that FSX built and put your old one back

 

in place.  All of your settings are in there.  Google search "FSX logbook repair tool.

Well yes, of course.  I may be 73 years old, as my pic shows, but I have sense enough to make a backup in this circumstance.  Anyhow, I did restore fsx.cfg and the settings are back to normal.  That points to logbook.bin as the problem.  So I'll google logbook repair tool and give it a go.  Thanks!

Any luck Mud?

 

   steve

http://chicagoflightsfsx.com/modules.php?name=Downloads&d_op=viewdownloaddetails&lid=6

 

 

Just in case!

I've finally gotten home, am getting logbook fixer, and will get started.  charliearon, I have high confidence that this will get me on the road.  steve, does this mean my name is Mud?  Maybe you're not old enough to remember that old saying, eh?

MH