CTBlankenship

VAS, FSUIPC and FSX

Recommended Posts

OOMs seem to be plaguing some people and I just found out how to continuously monitor your VAS through the title bar of FSX using FSUIPC.  I have the registered version of FSUIPC so I am unsure if purchasing that product is necessary to implement this trick.  How to implement:

 

1.  FSX Menu bar | Add-ons | FSUIPC ...

2.  Select the Logging tab

3.  Enter an Offset of 024C (that's a zero)

4.  Enter a Type of S32 from the drop down box

5.  DO NOT check the Hex checkbox

6.  Press OK

 

Now you have a continuous readout of your VAS usage on the FSX title bar.  This suggestion works with people using FSX in windowed mode ... I am unsure about the other option (full screen).

 

ENJOY! 

post-254135-0-65218200-1389275454.jpg

  • Upvote 1

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Hello Charles,  I am a novice compared to the knowledge you have.  Just as a matter of interest I carried out your instructions to the letter in FSUICP and on the top left of the task bar in FSX were the numerals 221460 (fluctuating) in relation to the 737NGX. I also ran on my other monitor the Process Explorer Sysinternals  which gave a reading of 1997908k (fluctuating) both yours and this in tandem. This means nothing to me but maybe you can read into the differences.  No disrespect intended.  Richard Welsh.

Share this post


Link to post

Richard:

 

Sounds to me like the two programs are monitoring the same thing (yea ... I know ... duh) since the values are so similar (enough) ... the question becomes "Which do we trust" ... personally I'm going with FSUIPC as it is the one that starts "dinging" when VAS is running critically low. 

 

The only way to test this is to enlist someone, who is frequently experience OOMs, to install both programs and let us know the values of each when the OOM occurs.  Do we have any volunteers?

 

I personally have never experienced one in my short two years of flying ... maybe this is due to the fact I always used a 64-bit OS which allows all of my other programs (Electronic Flight Bag, ASN, FTX Global, 5 FSDreamTeam airports, IE, Visual Studio 2012, SQL Server Enterprise Manager, StrataFrame, Word ... the list goes on).  

 

I currently have 16GB of RAM (G.Skill PC3 17000, 9-11-11-31, Model F3-2133C9Q-16XL) ... four sticks ... as per NickN's instruction.

Share this post


Link to post

If you check "FS WIndow" it will also be continually visible to full-screen users. Thanks for the tip.

Share this post


Link to post

Here's Ideal Flight 10's take on it:

Stock FSX and Beech King Air 350
FSX Peak VAS: 0.303751168 Gb at start
FSX Peak VAS: 0.778596352 Gb at end flight

Stock FSX and Beech King Air 350 + FSUIPC .dll Unregistered version
FSX Peak VAS: 0.415244288 Gb at start
FSX Peak VAS: 0.896458752 Gb at end flight

Stock FSX and PMDG 777-200LR
FSX Peak VAS: 0.983674880 Gb at start
FSX Peak VAS: 1.620566016 Gb at end flight


(Figures taken from IF10 >augmented flight log.)

Share this post


Link to post

 

 


Do we have any volunteers?

 

My understanding from running it last night was that the FSUIPC data displays available bytes left/available, while Process Explorer displays bytes used.

 

I could be totally wrong.

Share this post


Link to post

Now Kyle ... when have you ever been wrong :P.  Do you have anymore cool videos for me to watch.

 

Thanks to you and Derek for clarifying.

Share this post


Link to post

I found FSX SP2 on Win8(64) triggers the OOM error at around 650Mb remaining.

From IF10's flight log where FSX OOM'd:

"63539837626: FSX Peak VAS: 3.644796928 Gb, 4.294967295 Gb available, 0.650170367 Gb remaining"

The log shows usage increasing with each stage of the sim loading and running so it's easy to monitor VAS used throughout the flight. a warning triggers at around 768Mb to go and shows the current loading.

 

FSUIPC starts pinging around 700Mb to go.
 

Share this post


Link to post

 

 


Now Kyle ... when have you ever been wrong . Do you have anymore cool videos for me to watch.

 

haha - plenty of times, and often very publicly :ph34r:

(Just ask Kevin about my lesson on simulator certification. Even Robert's handed me crow to eat way back when...I think it was about the accuracy of flight directors, where I was spouting rubbish as a newly minted college grad who clearly knew everything...haha)

 

I have another video set up.  I just need to finalize the recording.  Later today, perhaps.

Share this post


Link to post

That is useful information and a unique way of getting it. Very helpful. But who wants to look at a wide green bar during the flight?

 

Michael Cubine

Share this post


Link to post

As an FYI, the FSUIPC "ding" will come on when you have 300MB or less of VAS remaining before OOM.  And yes, the number that you are setting at that offset is displaying bytes left before OOM.

Share this post


Link to post

 

 


But who wants to look at a wide green bar during the flight?

 

Huh?

 

It's displaying the info in the Title bar of the program (for me anyway - I'm running in windowed mode, though).

Share this post


Link to post

FSUIPC shows a number in the window border area and starts pinging and continues pinging after it sees VAS use creep to a high point. It depends on the operating system and the service pack level of FSX, FSXSP2 on Win8(64bit) starts pinging at around 700Mb to go. The IF10 flight log shows VAS use as it creeps up and can be used to find at what point in the sim VAS creeps up the most. The warning message pops up with a ding once (on the green strip) when available VAS has reduced beyond your minimum setting (default 768Mb). The log can be studied after the flight, or the flight can be paused and the log accessed from IF10.

Share this post


Link to post

(for me anyway - I'm running in windowed mode, though).

Kyle

 

I am running full screen as I always do. Since I have never had OOM errors and never disabled any programs to lower VAS, I don't really care how it is presented in windowed or full screen mode. I have no need to use this FSUIPC logging or Process Explorer.

 

Michael Cubine

Share this post


Link to post

I have enabled VAS logging per the instructions, but I get a constant 024C = 0 on the title bar

 

This is when I start up FSX and have the default aircraft in default scenery.

 

I cannot possibly be having 0 VAS left.

 

Any ideas ?

 

Thanks

 

Share this post


Link to post

Thanks Charles, but I can't seem to get a VAS number.  What I get is "monitor IPC:024C (S32) = 0"

 

Nothing but 0 when flying.

 

Any ideas what I'm doing wrong?

 

John

Share this post


Link to post

If both of you are getting 0, then you've either misconfigured something, or FSUIPC's values have changed. It's probably worth looking into their forum, or using a tool dedicated to checking VAS.

Share this post


Link to post

I just found this thread, I've been having some OOM issues with ES Isle Of Man and Guernsey.

So I set up FSUIPC as described above.

Odd results as I fly FSX Gold, 64 bit Win 7, A2A Comanche, ASN, and here's some sample numbers.  Why do they sometimes have a letter in them?

And what do these particular numbers mean?

 

11B9612

1616676

1213412

12D2692

 

Thanks for any help.


Oh, and where can I find the log file?

Share this post


Link to post

I just found this thread, I've been having some OOM issues with ES Isle Of Man and Guernsey.

So I set up FSUIPC as described above.

Odd results as I fly FSX Gold, 64 bit Win 7, A2A Comanche, ASN, and here's some sample numbers.  Why do they sometimes have a letter in them?

And what do these particular numbers mean?

 

11B9612

1616676

1213412

12D2692

 

Thanks for any help.

Oh, and where can I find the log file?

Make sure your Base is set to IPC, Offset to 24C and type is set to S32, also make sure Hex is not checked.

Share this post


Link to post

It is, it's set exactly as you describe.

 

So why the letters?

I see the VAS dropping as I get close to EGNS.

 

And please tell me where I can find the log file?

 

I'm lost when it comes to this stuff.

 

Thank you for your help.

Share this post


Link to post

It is, it's set exactly as you describe.

 

So why the letters?

I see the VAS dropping as I get close to EGNS.

 

And please tell me where I can find the log file?

 

I'm lost when it comes to this stuff.

 

Thank you for your help.

The numbers you posted are HEX numbers that's why there's letters. If hex isn't checked you shouldn't be getting them.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now