14.11.2009, 15:03
Multi Core Utilization-part 3
NVIDIA Control Panel-Manage 3D Settings Go here. ATI users also go to their Control Panel. Set Threaded Optimization to ON. If it is adjustable, then set it to maximum. Also, look for Mult-core Utilization, or similar name-if there is one, and click it to ON. Fly in IL-2 and see if there is improvement. Keep the settings only if this is clear or your intend to keep your nHancer if you see better results later. More things are coming, so hang tight.
The following in this post only applies with nHancer enthusiasts:
nHancer:
nHancer Control Interface Here you will see the Application box where you click il2set.exe. Next, you will make a profile. By the way, you can change the name of a Profile by standard right clicking on the activated Profile. Click the Compatibility tab. If you decide to use or try OpenGL, then put a check in the box at OpenGL Control. Near it is the Multithreading On box-put a check there. In the same Compatibility box, go to CPU Multicore Support to check the box. ( You will eventually change the processaffinitymask command in the conf.ini file of IL-2 )
Now to force IL-2 to utilize Threaded Optimization in Multicore Support, make an executable profile for both il2fb.exe and il2set.exe. ( Both files will be executables )
_____________________________________________________________________________________________________
The reason for these two executable files in one Profile is this:
Programs such as nHancer do not always activate and process quickly, and this can very from time to time, as most of us know. The il2fb.exe executable file will cause nHancer to activate your Profile that you created and have plenty of time to be ready as the il2set.exe of IL-2 applies its graphics settings. The first executable file prepares the nHancer to handle the second executable file which is the critical one. The second executable file ( il2.set.exe is second ) is the next resort if the system still is not ready after the first executable file ( il2fb.exe is first).
IMPORTANT: Any graphics card interface which allows two executable files could need the above technique of allowing the graphics interface Profile to fully activate to prepare for the il2set.exe file.
The amount of data and settings enforcement causes delays which makes some people think that their graphics settings are never going to work, when really they would work if given the chance. The nHancer therefore has a unique ability which solves this problem of the graphics control panel program not being ready in time. Some nVidia and ATI users have made an understandable mistake by concluding that their settings are impossible. Having a couple of executable files fixed this problem here for me. I tested this and it is true with my computer. Perhaps yours is this way, too.
Look at the symbol near the Executables box. Hold your cursor on the symbol for an explanation. Making an Executable Profile will cause your profile settings in nHancer to be used whenever you open IL-2.
If you want to try different Profiles for each copy of IL-2, then I am recommending the executable file with file path. You create two Profiles with two different names and have each Profile designated toward one IL-2 version by making an executable file with file path that is the same for each Profile.
This could be for comparison purposes such as one as OpenGL Profile and the other for DirectX. The profile settings and changes are saved automatically. When you click on an Executable Profile Name, then the settings will be revealed for that profile in the nHancer Control Panel.
You could have one copy of IL-2 for offline OpenGL settings and another for online DirectX settings, for example, and compare the two to see how you like them. Offline OpenGL could be for IL-2 movies or other visually important usage and the online DirectX could be for online performance.
Of course, if you have a great graphics card, try OpenGL settings to the maximum. If you tried thoroughly to use OpenGL and you are yet to be satisfied, then create a Profile for DirectX and give it a name that distinguishes it.
NVIDIA Control Panel-Manage 3D Settings Go here. ATI users also go to their Control Panel. Set Threaded Optimization to ON. If it is adjustable, then set it to maximum. Also, look for Mult-core Utilization, or similar name-if there is one, and click it to ON. Fly in IL-2 and see if there is improvement. Keep the settings only if this is clear or your intend to keep your nHancer if you see better results later. More things are coming, so hang tight.
The following in this post only applies with nHancer enthusiasts:nHancer:
nHancer Control Interface Here you will see the Application box where you click il2set.exe. Next, you will make a profile. By the way, you can change the name of a Profile by standard right clicking on the activated Profile. Click the Compatibility tab. If you decide to use or try OpenGL, then put a check in the box at OpenGL Control. Near it is the Multithreading On box-put a check there. In the same Compatibility box, go to CPU Multicore Support to check the box. ( You will eventually change the processaffinitymask command in the conf.ini file of IL-2 )
Now to force IL-2 to utilize Threaded Optimization in Multicore Support, make an executable profile for both il2fb.exe and il2set.exe. ( Both files will be executables )
_____________________________________________________________________________________________________
The reason for these two executable files in one Profile is this:
Programs such as nHancer do not always activate and process quickly, and this can very from time to time, as most of us know. The il2fb.exe executable file will cause nHancer to activate your Profile that you created and have plenty of time to be ready as the il2set.exe of IL-2 applies its graphics settings. The first executable file prepares the nHancer to handle the second executable file which is the critical one. The second executable file ( il2.set.exe is second ) is the next resort if the system still is not ready after the first executable file ( il2fb.exe is first).
IMPORTANT: Any graphics card interface which allows two executable files could need the above technique of allowing the graphics interface Profile to fully activate to prepare for the il2set.exe file.
The amount of data and settings enforcement causes delays which makes some people think that their graphics settings are never going to work, when really they would work if given the chance. The nHancer therefore has a unique ability which solves this problem of the graphics control panel program not being ready in time. Some nVidia and ATI users have made an understandable mistake by concluding that their settings are impossible. Having a couple of executable files fixed this problem here for me. I tested this and it is true with my computer. Perhaps yours is this way, too.
Look at the symbol near the Executables box. Hold your cursor on the symbol for an explanation. Making an Executable Profile will cause your profile settings in nHancer to be used whenever you open IL-2.
If you want to try different Profiles for each copy of IL-2, then I am recommending the executable file with file path. You create two Profiles with two different names and have each Profile designated toward one IL-2 version by making an executable file with file path that is the same for each Profile.
This could be for comparison purposes such as one as OpenGL Profile and the other for DirectX. The profile settings and changes are saved automatically. When you click on an Executable Profile Name, then the settings will be revealed for that profile in the nHancer Control Panel.
You could have one copy of IL-2 for offline OpenGL settings and another for online DirectX settings, for example, and compare the two to see how you like them. Offline OpenGL could be for IL-2 movies or other visually important usage and the online DirectX could be for online performance.
Of course, if you have a great graphics card, try OpenGL settings to the maximum. If you tried thoroughly to use OpenGL and you are yet to be satisfied, then create a Profile for DirectX and give it a name that distinguishes it.