Thread Closed

IL-2 Guide for Computers, Benchmarking, Optimizing, Tweaking
#30

Benchmarking Preparation Phase

Both ATI and nVIDIA users can benefit from reading this, though the focus is mainly on nVIDIA/nHancer at this point. More ATI focused information is found further in this topic. Big Grin

#2 Multicore Utilization

Now, you should have il2set.exe as the Executable file with its file path in the Executables box (This is named and appears in the Executables box when you click the il2set.exe, or other designated profile name, in the Application box of nHancer.). This file path should have been set in the Executable to the il2set.exe file in the IL-2 version that you want to enhance.

Click the profile name in the Application box to begin making settings. Click the Compatibility tab of the box for optimization (right side of the interface in my nHancer). Scroll down Compatibility and check the box for:

CPU Multi Core support
Note that if you run in OpenGL, then this is enforced automatically. If you run DirectX, then this setting only is enforced if you have also previously checked the box Profile can be activated manually and actually do activate the Profile manually.

Open or explore your main IL-2 folder. Seek your conf.ini file. Open it and go to the ;processaffinitymask= command line. Delete the ; to uncomment it, if you want your Operating System to choose where processing is to take place among multiple cores. Note that no matter what you do, the OS can place processing of IL-2 where it needs it. Really, the best we can do is request our preference and it will try to comply if it can. My IL-2 used to run in only the default first core. Now the simulation runs in both cores, the way I want it, with processaffinitymask=3. Windows Task Manager Resource Monitor (CPU Usage section) absolutey confirms this-no disputing it. This in turn allows my CPU cores to run full throttle, so to speak, with all the threads that it needs in two cores. It never goes below 18 threads and sometimes runs in the mid-20s of threads. Once, it was at 28 threads! That's a huge improvement over the 1 to 3 threads before I began using nHancer. Windows Task Manager Resource Monitor proves this.

#3 Multi Threaded Utilization
A single thread is an area of a CPU that performs processing and its associated input and output path. A CPU can perform, in some cases, upto hundreds of threads at a time. IL-2 comes with default 1 to a few threads capability. Everybody reading this can increase the threads above the default and see noticable improvements. The nHancer has a convenient way of explaining the method and using it with IL-2.

Multi Threading in OpenGL
Your nHancer program will enforce multi threading. I feel for you about this getting repetitive, however, Windows Task Manager Resource Monitor reveals that this is true.

Make sure to have your profile designated by clicking the name of your profile in the Application box. In the nHancer interface to the right, click the Compatibility tab. Scroll to OpenGL Control. With this feature, as the name indicates, you begin to take control of OpenGL features in regard to IL-2. Put a check in the box for Multi threading ON. I also have Error reporting Enabled, nearby-while you are there.

Multi Threading in DirectX
This will occur if you enable Prerendered Frames. The graphics frames will be sent to the CPU for preprocessing before being sent to the GPU for final processing. For the CPU to do this, it will automatically open more threads to accomplish the tasks that you command. Yes, Windows Task Manager Resource Monitor proves it to be happening. All this is done at the speed of electricity, so don't worry about any lag from this.

Click on the Optimizations tab at the right of the nHancer interface and scroll to Prerender Limit. I set mine to 8, but if you have a less capable PC than mine, then try a lower number at first. You can easily increase it later.
Thread Closed


Messages In This Thread

Forum Jump:


Users browsing this thread: 5 Guest(s)