Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SAS~Storebror]

Dear all,

Let us introduce a tiny little tool called

"FUMS" - "F*ck Up My System" - A Process Management Tool.

Download Link (Mediafire):FUMS 1.3

This tool will help you running BoS (and other apps if you like) smoother and stick to the official dev team recommendations (e.g. run your PC in "High Performance" mode) without leaving your system in an undersired state if you happen to do other things than playing IL-2 (which, much to our surprise, sometimes is reported to happen).

Using FUMS you can automatically adjust the following things:

• Change Priority of Processes as soon as they appear
• Change the Processor Affinity of Processes (the CPU Cores they are running on) as soon as they appear
• Automatically adjust your PC's Power Plan when a given Process Starts or Exits

FUMS consists of 3 files: The Executable (FUMS.exe), a pdb file for debugging, and the settings file (FUMS.ini).
FUMS needs admin privileges and it needs .Net Framework 3.5 or later to be installed on your PC (you likely have that already).
That's not because we're nasty at you, it's just because otherwise you won't have access to the settings FUMS is meant to adjust.

Installation:
Extract the 3 files to a folder of your choice, open FUMS.ini in a Text Editor and adjust settings to your needs, save FUMS.ini, run FUMS.exe.

FUMS runs in "Tray Icon" mode per default.
When you double-click on FUMS' Tray Icon (lower right tray area, click the up-arrow if the icon is blanked out), FUMS' window opens up.
In order to terminate FUMS, right-click on it's icon and choose "Exit".

The FUMS configuration is not really self-explaining, but the ini file contains sufficient information.
Don't mess around with things you don't understand. FUMS is called FUMS for a reason.

Sample conf.ini that runs IL-2 Battle of Stalingrad with dev-recommended settings, including lowest priority for Steam (if your game is Steam based - if not, doesn't matter) and "High Performance" Power Plan Setting:

Code: [Select]

; FUMS - Fuck Up My System
; A Process Management Tool


; All settings in this file will apply instantly when the file is being saved,
; there's no need to restart FUMS to apply changes.


; The [Common] Section contains application specific settings which are not
; related to any process
; UpdateInterval sets the interval (in Milliseconds) for scanning the List of active
; Processes for matches with the list below

[Common]
UpdateInterval=100


; The [Priority] Section holds the desired priorities for certain processes.
; Each setting consists of
; <process name>=<priority level>
; Where <process name> is the name of the process as listed in the Windows Task Manager's
; "Details" tab, and <priority level> is one of the following:
; -2 = Idle
; -1 = Below Normal
;  0 = Normal
;  1 = Above Normal
;  2 = High
;  3 = Critical ("Real Time")

[Priority]
IL-2.exe=1
SteamService.exe=-2
steamwebhelper.exe=-2
Steam.exe=-2


; The [Affinity] Section holds the desired processor affinities for certain processes.
; Each setting consists of
; <process name>=<affinity mask>
; Where <process name> is the name of the process as listed in the Windows Task Manager's
; "Details" tab, and <affinity mask> is a binary mask reflecting the cores the process
; should run on. If you are not familiar with affinity masks, we recommend to use
; the "ProcessAffinityMask" tool to calculate the matching mask:
; https://www.sas1946.com/main/index.php/topic,32520.0.html
;
; An Affinity Mask of "255" for instance means "first 8 cores", because
; 255 = 0xFF = 0b11111111
; Which either means 8 physical cores or 4 physical cores plus 4 hyperthreading cores.
;
; An Affinity Mask of "-1" means "use all cores", which is the windows default behaviour.

[Affinity]
IL-2.exe=-1


; The [PowerPlan] Section holds the desired processor affinities for certain processes.
; Each setting consists of
; <process name>=<power plan>
; Where <process name> is the name of the process as listed in the Windows Task Manager's
; "Details" tab, and <power plan> is one of the following:
; 0 = Power Saver
; 1 = Balanced
; 2 = High Performance
; If the last process of this list exits, the Power Plan will be reset to the default
; value it has been on before the first process of this list started.

[PowerPlan]
IL-2.exe=2

Mike

[SAS~Storebror]

Oh by the way... FUMS sources are available on our Superschool Subversion Repository
It's written in C# using Visual Studio 2017 if you are keen to know... Express Edition should do (don't ask me, but theoretically it should).


Mike

[SAS~Storebror]

FUMS 1.1 has been uploaded and is available in first post.

Changes:

• Added Option to Autostart FUMS when Windows Starts
  (Tick Checkbox at the bottom of FUMS window to activate Autostart)
• Fixed an issue where Process Name Dictionaries were case sensitive, resulting in Exceptions thrown when case mismatch between configuration settings and existing process happened.
• Performance Enhancements and Simplifications in Process Matching Rules
• Fixed an issue where configuration file changes would trigger the file to be reparsed twice

Mike

[hello]

hmm... Link? 

[SAS~Storebror]

Lol, no idea how that happened, but now the link is there.
Thanks for the heads up!


Mike

[gerula]

Awesome work Mike!!!! It does help a lot. My game loads up twice as fast as before, and runs without any problems, on line, off line.
 You rock.

[hello]

Thanks very much, giving it a go now

[SAS~Storebror]

Update in first post: FUMS 1.2 has been released.
We're not BETA testing anymore, this version is stable.

Changes:
* Autostart function has been adjusted, Scheduled Task starts with 30 seconds delay now to give the Taskbar/Tray a chance to come up before FUMS start.
* Tooltip Text for Tray Icon has been adjusted.

Please note that due to limitations in XP's Task Scheduler, you need to have Windows Vista or later (7, 8, 10) to use FUMS.


Mike

[Flying H]

I have a major problem with this!

Code: [Select]

System.NullReferenceException: Objektreferensen har inte angetts till en instans av ett objekt.
   vid FUMS.FUMS.CheckProcesses() i U:\sources\VS2k17\C#\FUMS\FUMS\FUMS.cs:rad 310
   vid System.Windows.Forms.Timer.OnTick(EventArgs e)
   vid System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   vid System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)I get the options to ignore or proceed, clicking proceed repeats the exeption over and over.
Started as admin.
Any clue on what to do?
Specs: W10 updated all the way, i5-2500K, 16G mem, GTX 960, (what more do you need to know?)

[SAS~Storebror]

Thanks for the feedback.
Looks like you have a custom powerplan active or you have enabled the (hidden) ultimate powerplan.
And it turns out that FUMS didn't take that into account yet, so please find an updated version 1.3 in the first post now that should solve this issue.


Mike

[Flying H]

THX a million! That solved my hickups!

[UberDemon]

So would you say your program goes up to...  eleven?