The Last OOM?

In less than 24 hours, Lockheed Martin will release the highly anticipated and very long overdue 64 bit version of Prepar3D version 4.  With this release, will we finally see an end to the out of memory issues we’ve all experienced with FSX and every version of P3D?  Have we experienced the last OOM?  Can we once and for all stop worrying about how much (or how little) VAS we have?  Are those little ding, ding, ding noises just as we are on final approach after an extremely long-haul flight going to be a thing of the past?  I darn well hope so….

If you are an FSX or P3D user and don’t know what the acronyms of OOM or VAS stand for, or you haven’t encountered those ding, ding, ding sounds just before you are rudely presented with the error that says “Too Bad, Too Sad…we don’t care that you’ve just spent 12 hours flying and are in the final 5 minutes of flight, but you’ve run out of memory and we’re about to ruin your fun”, then I suggested you read this post.

Taking the Plunge

Sure…I might as well!    While I owe a review of Dovetail Games brand new Flight Sim World FSW (and I’ll get that done soon), in a nutshell I don’t believe (at this time) there is any chance I’ll spend a great deal of time in FSW.  Reason being is lack of 3rd party aircraft, scenery and such.  I don’t see FSUIPC making its way to FSW anytime soon and without that, it really limits just how much fun I can have in the sim.  NOTE:  I said it will lack how much fun I will have.  Your mileage may vary depending on what you want from a flight sim.

But yes…I do plan to purchase P3D v4.  But I’m also doing so knowing it will be some time before some of my favorite add-ons will be made available.  Some developers will have content ready on day 1, others will have their content after the first few weeks etc. etc.  From what I’ve read, much of the add-ons I currently own will not require a repurchase to obtain the P3D version 4 installers.  This is great news…but it’s more or less the commitment that many of these developers made when we all began speculating about a 64 bit version.

By the way, I have been flying lately as I’ve been playing around with both FSW and enjoying flights in P3D v3.4.  I experienced what will hopefully be one of my last OOM crashes on Sunday when I was flying from KDFW to KMEM.  Just within about two minutes after landing (thankfully) the system just said..”Nope…you’re done” it has used up 100% of the available 4 GB of VAS which is the dreadful limitation of 32 bit applications we’ve all been dealing with.  It was a great flight other than that.

My Future in Flight Sim

All things being equal, in the past 6 months I’ve been using P3D v3.4, X-Plane 11 and Dovetail Games new Flight Sim World.  As I’ve stated many times, I have a large dollar investment in FSX/P3D, so much so that I really can’t afford to seriously look at X-Plane as being a full replacement  and still be able to enjoy the hobby in the same fashion.  I have many years of experience with the Microsoft Flight Sim family of products and still find the X-Plane way of doing things about as difficult as trying to hammer a nail into the wall using only my forehead.

You can expect to read my first impressions on the 64 bit version of Prepar3D version 4 in the coming days/weeks.  I might even record my thoughts and make it available on my YouTube channel.  Stay tuned…

Until next time…

Happy Flying!!!

Jerry

An issue solved

As I mentioned in an earlier blog post, I packed away my flight sim computer and other gear (yoke, pedals, GoFlight hardware modules) in early January 2012.  Prior to this timeframe, I hadn’t spent much time flying since July/August 2011.  However, at this time (and even in January 2012) my FSX machine ran just fine. 

Since my FXS machine had been packed away between January and September of this year, I had a number of Microsoft updates to apply to the machine, along with updates to my antivirus programs.  Also, specific to FSX I had several updates to apply for various scenery and other add-ons. 

From almost minute one, FSX was unstable and I experienced many CTD’s or crash to desktop issues.  Many of these were experienced when clicking menus within FSX.  But FSX would also crash when starting up as well as when going to an airport (FSX default or otherwise) via the menu.  The odd part of this was I new I had applied the fix to resolve CTD’s when clicking menus just after I built the new machine two years ago.  Of course I’m talking about the uiautomationcore.dll fix.  This impacts users running FSX on Windows 7 64 bit machines.  If you want more information on this fix, please read this.

Anyway, I was pulling my hair out trying to figure out what was wrong.  I was very close to just biting the bullet and performing a full system rebuild on my machine.  Then on one of my Africa flights I experienced a CTD and decided to do a little more research on the specific error.  The error pointed to g3d.dll.  I used Google to search and found a blog post on the Avsim Forums which pointed to the fault being with FSUIPC.  I hadn’t thought about checking to see if an update to FSUIPC was available since my long hiatus. 

I applied the most recent version of FSUIPC and ran some tests.  Since applying the update, I’ve spent another 4-6 hours on the machine flying, clicking menus and just about anything else I can think of.  The machine is stable and I’ve experienced no CTD’s. 

I hope this information might help someone else. 

Until next time…

Happy Flying!!!

JT

GrizzlyBearSims

5 User(s) Online Join Server
  • MEE6
  • Midnight_Hobbit/ElrodJr
  • p...
  • MonitoRSS
  • PistolpackerWV