FTX increases the amount of autogen and introduces custom night lighting, so there is a (moderate) VAS penalty. You can counteract by setting your autogen slider more to the left.

 

I'm pretty sure that the FTX San Francisco area is less demanding, VAS-wise, than the Aerosoft U.S. City SFO. I nearly OOM-ed there just yesterday with a VAS-demanding aircraft and due to my inappropriate settings.

Are any of you experiencing OOM's like crazy with all these ORBX add on?

 

No.

OOM's and ORBX in FSX are possible indeed, due to FSX's 32bit limitations.

But as outlined above in in #31:

The chances of running into an OOM is not  much higher with an ORBX scenery than it is with any other dedicated 3rd party landclass/vector based scenery - and as long as FSX is set up and tuned properly there is really not much to worry about at all regarding that matter.

Are any of you experiencing OOM's like crazy with all these ORBX add on?

 

 

No. In fact, in over 7 years with fsx I have never seen an OOM

 

I had OOMs on every second flight using ORBX products. No OOMs using other scenery. But since Pete Dawson made a "fix" in FSUIPC I get OOM like once per month.. usually when flying NGX over heavy overcast for several hours.

I had OOMs on every second flight using ORBX products. No OOMs using other scenery. But since Pete Dawson made a "fix" in FSUIPC I get OOM like once per month.. usually when flying NGX over heavy overcast for several hours.

And what OOM fix what that be?

And what OOM fix what that be?

I don't know what exactly he did but if you have a registered version of FSUIPC than you have the fix. It's not a magic bullet but it helped me. I can enjoy FSX without constantly fearing it will crash.. like before.

FSUIPC autosave is a workaround, but not a fix.

I don't know what exactly he did but if you have a registered version of FSUIPC than you have the fix. It's not a magic bullet but it helped me. I can enjoy FSX without constantly fearing it will crash.. like before.

 

I think I know what you are talking about but it has nothing to do with OOMS. What you do get with FSUIPC is stabailty and dont ask me how or why but Im in the same boat as you, have barley had a crash since running everything throught the paid version

I think the issue Tomaz is referring to is a change made quite some time ago to help trap spurious G3D.DLL CTDs.  There were a number of specific locations in both Orbx PNW and NRM where I could reproduce these reliably, until the FSUIPC fix came along.  Smooth sailing after.

 

This is not an OOM issue or an OOM fix.

 

As for Orbx scenery and OOM's, I've honestly only had a few in my years running FSX, only one of those was in Orbx territory and I believe it had more to do with the wx (and wx package) I was using than with the specific Orbx area - though of course OOMs are generally a result of cumulative load, and the finger tends to get pointed at the last piece added.

 

BTW, flew from KSBA to KRHV (Santa Barbara to Reid Hillview in the southern Bay area) last night.  Interesting to make the transition from photo (Blue Sky) to an Orbx region.  My initial impressions were very positive, though I haven't gotten to any of the really "good stuff" yet.

 

Scott

Edited February 19, 201412 yr by tttocs

I have FlightBeam KSFO and ImagineSim KSJC and bought ORBX NorCal.  After disabling the two KSFO and two KSJC .bgl files in the ORBX directory, I can say everything looks great!

I have all the ORBX regional profucts, and they are simply amazing!

 

 

I have FlightBeam KSFO and ImagineSim KSJC and bought ORBX NorCal. After disabling the two KSFO and two KSJC .bgl files in the ORBX directory, I can say everything looks great!

I have all the ORBX regional profucts, and they are simply amazing!

 

Luis, you prefer the Orbx KSFO over Flightbeam's? 

Luis, you prefer the Orbx KSFO over Flightbeam's? 

Sorry if I wasn't clear.  I disabled the KSFO and KSJC files that came in the ORBX NorCal package for my FlightBeam KSFO and ImagineSim KSJC to display properly.

 

They blend it very well with the ORBX package. 

 

I'm looking ofrward for the FlightBeam KSFO v2 update too!

The G3D.dll fix is available in the unregistered version of FSUIPC already.

 

But it can't deal with OOMs ...

I don't know what exactly he did but if you have a registered version of FSUIPC than you have the fix. It's not a magic bullet but it helped me. I can enjoy FSX without constantly fearing it will crash.. like before.

 

I watched my VAS using FSUIPC but P3DV2.1 crashed OOM anyways with 400 MB left...why?

I think the issue Tomaz is referring to is a change made quite some time ago to help trap spurious G3D.DLL CTDs.  There were a number of specific locations in both Orbx PNW and NRM where I could reproduce these reliably, until the FSUIPC fix came along.  Smooth sailing after.

 

This is not an OOM issue or an OOM fix.

 

Oh, man, I mixed up OOM and G3D errors, I do apologize for the confusion!

 

 

Sorry if I wasn't clear. I disabled the KSFO and KSJC files that came in the ORBX NorCal package for my FlightBeam KSFO and ImagineSim KSJC to display properly.

 

Ohhhh...had me wondering.  That would have been a stunning statement.  Flightbeam's work is wonderful.