Came Across a Couple of VAS display Tools

[Rogen]

Came Across a Couple of VAS display Tools

So, there I was looking for a method to display the VAS usage of FSX what with FSX being a 32 bit program and limited to a 4 GB "VAS" window of memory.

I was using the Microsoft sysinternals "Process Monitor" tool, however the tool, while accurate, was more of an entire system tool and was a little cumbersome.

There was also FSUIPC that with a crafted data entry would display the VAS usage in a green bar on the sim screen, not really what I was after though.

So with a little further searching I came across the two below applications.

progectFly Tools and VAS monitor.
https://steamcommunity.com/sharedfiles/filedetails/?id=1388569114
Both connect to either FSX or P3D via FSUIPC and both do the job and come with a few pros and cons.

VAS monitor, while displaying VAS usage just fine, it is a .Net Click Once launched application. This means it launches from the authors web page and will typically be blocked by anti malware tools unless whitelisted. However it is fast to start, does the job well enough and includes a FPS counter and a configurable point at when it's VAS warning alarm is triggered.

progectFly Tools, was an item I read about however the links all pointed to a web site that now is used for selling shoes... A bit of further searching and version 1.0.1.0 was found for download and testing carried out. This tool looks a little prettier and serves a few additional items of which FPS is not one of, nor does it have a configurable VAS usage warning, although it does warn in a voice.

It's also small and runs from a single executable, so no need for click once web launches.

Both sit outside of FSX/P3D and would typically sit to the side on another monitor and function with the free version of FSUIPC.

Download links:
FSUIPC: https://forum.simflight.com/topic/80977-updated-modules/
VAS monitor: http://spilfred.com/VASMonitor/publish.htm
progectFly Tools: http://projectfly-client.software.informer.com/

Also if you need to be monitoring your VAS, you've probably grown beyound FSX-SE and it might be time to look at the 64 bit version of what FSX could have become -> P3D v4

Cheers

[galax17]

Thanks.

[TextRich]

Nice finds Rogen. I still like FSUIPC displaying my VAS in the window's title bar out of the way and only visible when I am curious enough to look up at it.

[Rogen]

Originally posted by BF Bullpup:

I still like FSUIPC displaying my VAS in the window's title bar out of the way and only visible when I am curious enough to look up at it.

Ah, the thing is I prefer no borders, title bars ect. and run a full screen borderless window along with hiding the task bar so as to maximise the full use of my screen and additional monitors.

All the benifits of running full screen and yet also maintain a usable second/third monitor for ASN, G-Plan/Little Nav Map and various other bits and pieces such as a VAS monitor :-)

https://github.com/Codeusa/Borderless-Gaming/releases

Also available as a Steam purchase.
https://store.steampowered.com/app/388080
Cheers

[Rogen]

Also just a couple of notes.

FSX-SE opens multiple windows as it gradually opens while the user is preparing to fly.

This tends to lead to Borderless gaming doing funny things while FSX-SE is opening and to help combat that I use a regex to detect the window title I want to full screen. Regex is a language used for detecting and pulling apart text strings.

For example:
Borderless detects the main FSX-SE window on my machine as having a title of..

Monitor IPC:024C (S32) = <seven numbers>

And to detect it I use the following regex.

^((Monitor IPC:024C \(S32\) = )\d*?.*?)$

Essentually it means look for the text without the numbers playing a part as the numbers change each time.

Once the main window has been detected and full screened I then pause Borderless Gaming's automatic processing.

For myself the result is FSX-SE in a full screen 1920 x 1080 with the task bar hidden and opening on my monitor of choice, something I otherwise couldn't control when I switched to Steve's DX10 fixer.

Cheers