I have a question,....

 

do all the add-on programs that run in conjunction with FSX (EZdock,OPUS,Accu-Feel, etc...) run WITHIN and the SPACE of FSX's V.A.S.?

 

or...do they run within the normal memory pool not associated and reserved for FSX?

 

I have dumbed down my cloud rez, my plane skin rez, and my water setting to MID high, and still get an O.O.M and CTD episode with FSX.

 

I have not dumbed down any of my graphics settings, for to do so, would negate and make redundant the purchase of such as FSXG. I get 30 FPS at full graphics usage, so that is not a problem...but that I run out of VAS still is.

 

Also one final questions for the FSX enlightened, if you switch out your view (for instance you are in the cockpit and sweep your view left and right, and/or switch to out-of-plane (spot) and then back into the cockpit for let's say about 20-30 times in one half hour...would that also consume VAS, your SWITCHING OF VIEWS?

 

I'm just trying to get a handle on my O.O.M issue, for I'm having a ball with FSGX and wish to keep using FSX and not drop the whole sim in user frustration.

 

Any comments on the above questions from the forum would help...

--------------------------------------------------------------------------------------------------------------

 

Mitch

As far as Opus goes, no it does not eat up your Vas, but depending what textures you are using, like Rex HD clouds would. Opus runs in it's own memory space.

Ezydok, runs within EXE.xml and dll.xml, so I would think that it does run in fsx memeory space. I have gained also about 5fps in heavy airports by removing ezydok.

I don't use accufeel anymore, as I found it too buggy, so I am unsure what sort of foot print it has.

 

Since moving to DX10, I have had no OOM's.

 

Generally, if an add-on runs as an .exe file, it will run within its own process space, and not directly impact FSX VAS. This is the case with Opus. However, if the current weather conditions are such that Opus injects multiple layers of heavy clouds, those cloud graphics definitely will impact VAS, since they are generated within FSX itself.

 

Not sure about accu-feel or EZDock.

 

Add-ons that are loaded as DLLs do run within the main FSX process, and impact VAS.

Ezdok is its own process and runs in its own address space. Accufeel is a dll module that is loaded within FSX address space. Accufeel is so small, that the overall impact to memory is negligible.

Another is that .dll and .exe addons can both become clients of simconnect and register for notification of events and receive data structures, which eats into FSX.

Thank you all, for your comments.  They were most helpful.  So, it would seem that depending on what you are running in a nutshell, is going for the most part to inject VAS reservation and consumption....

 

Opus doesn't, but on the other hand what it injects can and will eat into the VAS 'whole'.

 

I'm starting to see what an FSX user can be up against...and again, thank you all for your responses.

 

FSX is a rockin' simulator, and I could only wish that Microsoft stepped back in, and if only did one thing, re-released the franchise in a 64 bit variant, for this plaguing problem for those that want all features at 100 percent, would simply go away with modern equipment and a ample memory pool. That's all they would have to do...and probably 90 percent of all 32 bit users, would pay $79.00 again to convert to a 64 bit FSX base.   Sigh......  Instead of Flight, they could have put their resources into that, and made $$$$ in the process.....

 

I hope at some time in the near future, a Microsoft executive 'catches' that...and sees there is money, merely in a base-product 64 bit refresh!

Interesting note on AccuFeel. In my previous installation it run without problems, but with this new setup I had to uninstall it as it crashed the sim. What kind of problems have you encountered?

Interesting note on AccuFeel. In my previous installation it run without problems, but with this new setup I had to uninstall it as it crashed the sim. What kind of problems have you encountered?

Well, I have always had about a 20-30 minute flight time, before my inevitable OOM and following CTD.  I usually get a back-ground 'chime' sound that I have identified as W7 'advising' me that I am running low--to exhaustion of VAS for my (FSX) running program. If I  ignore from the first 'chime' sound, I am parked on my desktop about 5 minutes afterward.

 

I run OPUS, EZCA, ACCUFEEL, SHADE, and A.I. Smooth (this prevents A.I. interference with my flight and approaches, etc) and that's about it. I just did a flight without anything other than FSX itself, and my only first chime came with my first SPOT VIEW attempt. I wonder if running FSXG, (no HYBRID mode engaged...) and all FSX graphic sliders at full 100 percent just overwhelms the VAS when you go to SPOT VIEW?!?!?  

 

All of the aforementioned programs run with no faults, other than perhaps getting me closer to that OOM and 'bye, bye...see ya...' CTD.

 

No matter, a total bummer and frustration in the extreme....

 

I hope you sort out your personal headache FSX issues. Good luck!

Sesquashtoo, the chime is FSUIPC warning about FSX VAS being at 3,8 Ghz if I remember correctly.

 

Does anyone know if and how I can make FSX load without certain DLL's in DLL.XML?

 

Does anyone know if and how I can make FSX load without certain DLL's in DLL.XML?

 

You can edit your dll.xml or exe.xml like this:

	<Launch.Addon>
		<Disabled>False</Disabled>
		<ManualLoad>True</ManualLoad>
		<Name>CumulusXDll!</Name>
		<Path>E:\FltSimProgs\FSX\CumulusX\Modules\CumulusX!\CumulusXDll.dll</Path>
		<DllStartName>DLLStart</DllStartName>
		<DllStopName>DLLStop</DllStopName>
	</Launch.Addon>

The key being the "ManualLoad" entry.  This will cause a popup for the dll when you start fsx allowing you to load (or not) the dll.

 

scott s.

.

Great Scott, thank you sir!

 

 

I have dumbed down my cloud rez, my plane skin rez, and my water setting to MID high, and still get an O.O.M and CTD episode with FSX.

 

That's surprising Mitch cause on my old C2D rig that was on XP 32bit with 2GB of RAM and a 1GB video card I routinely ran the all of the PMDG birds, AS2012, EZdok, sometimes Accufeel, plus all the normal stuff like GEX, UTX, 80 or so addon airports and WOAI and never once in 5 years of running that system had an OOM.

 

The only thing I didn't do was run any texture that was over 1024X1024 in size. Any addon I would purchase whether it was an environment addon like REX or FEX or an airport or scenery addon, the first thing I would do is make sure any texture that was installed from those said addons was in DXT format and no larger that 1024X1024. If I found anything larger than that size texture or in a format other than DXT, the first thing I would do is convert it to 1024 and DXT format and of course add mip maps if they weren't included.

 

I can say that even when running pretty much every slider to the right not always gave good FPS in some situations and when switching views with that rig sometime resulted in taking a few seconds for textures to load, I never once had an OOM.

 

In your case its really hard to say whats going on if you keep getting OOMs. I just recently built a new rig to catch up with the times and using the same formula as I did on my old rig concerning textures, I have yet to OOM in almost 100 hours of test flights using all my same addons.