16.02.2010, 18:25
Hi, bro
An interesting coincidence is that I have planned to add screen captures later. This was actually planned in my Flowchart several months ago. Not only will I include instructional screen captures, I will add a few in flight ones to demonstrate what I achieve with certain settings. For example, I will highlight water, trees, and antialiasing, since these are among the more common issues in IL-2 user minds. With the screens will be explanation of what I do to achieve this.
One of the things that I want to include is a shot with 3D forests, clean antialiasing lines, and many other facets in a particular shot that I have in mind. The scene is not perfect, but close with acceptable FPS.
The il2fb.exe is enough when an nHancer user has a simple system and maybe a couple IL-2 versions. The il2setup.exe comes in to use when a guy wants to use different Setup instructions for the same version of IL-2. In this case you would use a an Executable file with File Path to connect directly to the IL-2 version in question. This will open the door to use different Profiles for the same IL-2 version.
For example, lets say a person uses HSFX. User has a UP 2.0 and a FusionPack, as well. Okay, one can experiment with different settings of his HSFX version in an easy to understand way. Wanting to compare DirectX with OpenGL, user would make a Profile with Executable File Path for each. User would name the DirectX Profile accordingly, perhaps even indicating that it is intended for the HSFX in the name of it. He would do the same for the OpenGL Profile.
One reason for using the il2setup.exe is to target the file for over ride in a direct way. Among several reasons for the name DirectX is the shorter file paths and direct connection to setup settings. The Windows are DirectX favorable, though OpenGL is included. Getting the best image will be the use of OpenGL but the data is being worked around various issues to achieve this. The best performance will generally be achieved with DirectX which will simplify paths and data cache to achieve better performance, in some ways at the sacrifice of image compared to OpenGL.
All these issues have been resolved in DirectX 11, and Storm of War will maximize these utilities.
Unfortunately, IL-2 was never a perfect match with recent graphics cards, and drivers in particular. The nHancer solves most of these issues for the nVidia owner, but it sometimes requires specifying commands in very certain terms in order to be sure to effect graphics settings in a clear way.
Thank you for your comments and suggestions. I am considering these issues and will procede in an orderly way. Hopefully, I do not sound too much like logical Mr. Spock! :lol:
Everything here is a Work In Progress.
An interesting coincidence is that I have planned to add screen captures later. This was actually planned in my Flowchart several months ago. Not only will I include instructional screen captures, I will add a few in flight ones to demonstrate what I achieve with certain settings. For example, I will highlight water, trees, and antialiasing, since these are among the more common issues in IL-2 user minds. With the screens will be explanation of what I do to achieve this.
One of the things that I want to include is a shot with 3D forests, clean antialiasing lines, and many other facets in a particular shot that I have in mind. The scene is not perfect, but close with acceptable FPS.
The il2fb.exe is enough when an nHancer user has a simple system and maybe a couple IL-2 versions. The il2setup.exe comes in to use when a guy wants to use different Setup instructions for the same version of IL-2. In this case you would use a an Executable file with File Path to connect directly to the IL-2 version in question. This will open the door to use different Profiles for the same IL-2 version.
For example, lets say a person uses HSFX. User has a UP 2.0 and a FusionPack, as well. Okay, one can experiment with different settings of his HSFX version in an easy to understand way. Wanting to compare DirectX with OpenGL, user would make a Profile with Executable File Path for each. User would name the DirectX Profile accordingly, perhaps even indicating that it is intended for the HSFX in the name of it. He would do the same for the OpenGL Profile.
One reason for using the il2setup.exe is to target the file for over ride in a direct way. Among several reasons for the name DirectX is the shorter file paths and direct connection to setup settings. The Windows are DirectX favorable, though OpenGL is included. Getting the best image will be the use of OpenGL but the data is being worked around various issues to achieve this. The best performance will generally be achieved with DirectX which will simplify paths and data cache to achieve better performance, in some ways at the sacrifice of image compared to OpenGL.
All these issues have been resolved in DirectX 11, and Storm of War will maximize these utilities.
Unfortunately, IL-2 was never a perfect match with recent graphics cards, and drivers in particular. The nHancer solves most of these issues for the nVidia owner, but it sometimes requires specifying commands in very certain terms in order to be sure to effect graphics settings in a clear way.
Thank you for your comments and suggestions. I am considering these issues and will procede in an orderly way. Hopefully, I do not sound too much like logical Mr. Spock! :lol:
Everything here is a Work In Progress.