Can't figure out

[1SgtMajor 1]

I've been doing this flight sim thing for almost 30 years and have never ran into anything like this............SO.....any suggestions etc., would be most helpful.

 

I purchased FSX-SE several months back.....and slowly I've been putting my Flightsim back together again.

 

1st off.............Only FSX-SE on the system on a separate drive  (Drive E:\FSX...........that's the only thing on that solid state drive)

 

Next.....I installed FSX-SE....worked fine....and then started slowly installing scenery or aircraft one at a time....with an install .....fly ....then a reboot..........so it's taken a while to get to where I'm currently at.

 

The only scenery other than stock is Orbx......and I've stuck to regions instead of individual airports etc.  (Central Rookies.....Northern California.....Northern Rookies....Pacific Fjords...Pacific Northwest  England ...Ireland....Northern Ireland....Scotland...Wales...etc.)

 

I have added a few airports  but added FTX Global and FTX Vector also.

 

Aircraft.........Stuck mostly to aircraft I like.....A2A, RealAir, Carenado and Alabeo.......which brings me to the problem.

 

 

I purchased Alabeo D40 last evening.....very nicely done....had a lovely flight last evening and then again this morning.  Later in the day I tried to do a flight in Alabeo R44..........FSX-SE crashed...would not start.  Rebooted and tried again.....same thing.  Rebooted and started with FSX default flight......then tried to switch to the R44.......once again, it crashed.  Rebooted and started with a default flight....and tried the MicroSoft R22.......it crashed. 

 

I tried over and over again and none of my helicopters would initialize...............VERY STRANGE!!!

 

Uninstalled the D40 .........rebooted and tried the R44............Presto......everything worked fine.  In fact........all my aircraft are fine.

 

Re-Installed the D40........started FSX-SE and selected the R44.............No problem..........switched to the D40.............FSX-SE Crashed............Tried several times and I cannot select the D40.

 

Sorry folks..........I'm at a complete loss on this one.....

 

Anyone have any ideas/suggestions?

 

Cheers,

[DaveCT2003 1,820]

I'm not a Steam User (until next week), however I have to assume it has am XML.DLL file.  Have you checked this to see if your latest install munched it, or directed it to a non-correct address for a library?

[1SgtMajor 1]

I'm not a Steam User (until next week), however I have to assume it has am XML.DLL file.  Have you checked this to see if your latest install munched it, or directed it to a non-correct address for a library?

Yes Dave...I did....that's what's odd.....I've spent the better part of the day trying to figure this out etc., and can find no reason for this to be happening.

 

One thing I REALLY like about Steam is you can go to your Lib. files....right click and check properties and have it check the integrity of the game cache....doing this, I found 86 files missing and re-downloaded and installed.  Still, same issue...

 

As mentioned above..... when I install FSX for the first time.....I save the startup file as a "Do Not Touch" file....and I've now reloaded it and started from scratch.  If I can't get if figured out in the next day or so.....guess it will be a remove and start all over again. (smile)

 

I'm hoping someone here might have an idea before going to that extreme. (smile)

 

Thanks for the response Dave....I truly do appreciate it...........but this is starting to look like one of those "Once in a lifetime....who knows what happened.....errors"  (smile)

 

Cheers,

[DaveCT2003 1,820]

There was an update that came out a few days ago, and I've seen posts from a few people who had their files deleted and they had various problems from that.  I believe one fellow said he couldn't get FSX-SE to even boot.

 

Maybe the update had a negative affect on your install?  You can find this information on the main FSX-STEAM webpage.

 

Hope this points you in the right direction and moves you closer to a solution.

 

Would you please be kind enough to let us know how you made out, and if you are able to figure it out can you tell us what actually when wrong and what you did to resolve it?  It would  be a BIG help!

 

Best wishes!

[1SgtMajor 1]

Hmmmm............thought I had it fixed by re-installing what appeared to be 86 missing files...........but I just now tried to open up FSX and take a quick flight and there seemed to be an update with Steam and my FSX is broken once again.  

 

Now.......not sure if that was an actual "update"..........or if by re-installing those 86 files, it triggered something that caused Steam to update my FSX again.....(smile)

 

However, here is what the error report showed.  (I have no idea what any of this means, however, perhaps this might help someone much smarter than me......Smile)

 

Problem signature:

  Problem Event Name: BEX

  Application Name: fsx.exe

  Application Version: 10.0.62615.0

  Application Timestamp: 559f9a9a

  Fault Module Name: hypergauge.dll_unloaded

  Fault Module Version: 0.0.0.0

  Fault Module Timestamp: 5422c998

  Exception Offset: 0e5b735b

  Exception Code: c0000005

  Exception Data: 00000008

  OS Version: 6.1.7601.2.1.0.256.48

  Locale ID: 1033

  Additional Information 1: 7eee

  Additional Information 2: 7eeeeb903d4e7d6426674e8e5ac4d069

  Additional Information 3: e22c

  Additional Information 4: e22c78b11a8cc547d5825b671488137d

 

It's been a long day and my fun meter is pegged out, so I'm off to bed. (smile)

 

BTW...........I see you were a Submariner... and a P3 Sailor!!! (smile)  Spent many years in Avionics what you Navy Folks would call an AE..........so you see.....I'm only smart enough to be very dangerous. (smile)

 

Have a Great Evening!!!

 

Cheers!

[DaveCT2003 1,820]

There was the Public Beta which I believe anyone who booted up during the time frame received, followed by it being removed automatically and then the final version automatically installed. This was two or three separate actions, and if I had to guess one or more of those may have nailed you (reading the FSX-SE webpage it got several other people).  It's easily (and correct) to go back to the last thing YOU did ./ installed / fixed, but given how similar the problems are that others have had I think I'd pursue this on the FSX-SE site.  Please, PLEASE think about sharing what you learn here though.

 

Yeah, retired submariner who had my left wrecked and questioned by career daily after flying with the P-3Cs for several months!  That's where my love of aviation started, especially after my stick time in a Cadillac with 4 large turbo props. Loved every single second of it, and got some great stories out of it all as well!

 

 

Anyway, I wish you the best in getting your problem resolved.  If you fly on VATSIM, think about stopping by our group voice server (see our website for info) and maybe make a flight or two with us.

 

Take care.

[1SgtMajor 1]

Good Morning Dave........I think you're probably correct on the Beta comment.  However, as of last evening, it seems I may have my FSX back to flying normally....provided I don't try to switch aircraft during the session.  Not a perfect solution, however, is currently workable.....but FSX loads very slowly now....but once loaded seems to behave.

 

I too am somewhat retired with a LOT of time on my hands, so I will most likely scrap everything and start again.  Steam makes this VERY easy to do....(smile)....but will take the better part of a week or more to get things back the way I like.  Guess one could call it a "Fall Cleaning." (smile)

 

As far as VATSIM...That's really not my kind of flying.   I rarely fly above 5000 AGL and prefer the Non-controlled airports and airspaces.  My flying is usually with a good cup of coffee while the wife and my handicapped daughter are still fast asleep.  (I still get up pretty early.....can't seem to shake 28+ years of early rising)

 

If I do happen to stumble upon a solution for this problem...rest easy...........I'll be back to post.............Bragging rights are now at stake!! (smile)

 

Most Sincerely,

Steve R.