Special Aircraft Service

The SAS Factory - Tech Help, Ancient Mods etc. => Tech Help : Using Mods => Tech Help (other than BAT or IL-2 Great Battles) => Using Mods Tutorials => Topic started by: michel_boonstra1974 on October 15, 2010, 05:40:17 AM

Title: inside the CONF.INI
Post by: michel_boonstra1974 on October 15, 2010, 05:40:17 AM
I was tweaking my config.ini a bit and found an interesting config.ini explanation. Thought this might of use to some one.

** edit - sorry about only bold letters further down, but despite re-editing I am unable to change them back to standard for some strange reason..

EDIT by StG77_HaDes:
I re-edited it. I think it should be OK. And it also deserves to become sticky ;)

[il2]

describes game

title=Il2-Sturmovik Forgotten Battles
describes game

hotkeys=HotKey game
this determines whether the game uses hotkeys that are assigned in control section of hardware section of game setup

[window]
this describes how windows displays the game on screen

width=1024
resolution width in pixels set in display properties settings tab in windows

height=768
resolution height in pixels set in display properties settings tab in windows

LCD native resolution not included as an option in FB/AEP/PF Enter your screen values here and Save and start your game.... (if you later open the IL-2 Setup and close it by clicking OK it will change the resolution to 640x480 16bit, unless you change it to something else via this IL-2 Setup.) You will need the following values as well

change SaveAspect=0

ChangeScreenRes=1

EnableResize=0

ColourBits=32
resolution colour set in display properties settings tab in windows. Can be 16 or 32

DepthBits=24
Z buffer usage can be 16 or 24

StencilBits=0
Set in driver section of Il2FB hardware setup. Can be 0 or 8

All the above deal with image quality. The higher the numbers for width and height then the more pixels will be used in the same area therefore the image will be more detailed. The larger the number of bits then the more detail there is per pixel so better image quality

ChangeScreenRes=1
allows the screen resolution to be changed in game. Can be 0 or 1

FullScreen=1
forces display to be full screen and not in a window. Can be 0 or 1

DrawIfNotFocused=0
setting to 1 allows watching the IL2 window in the background, while Alt-Tabbing out of the game. Quite useful for playing co-ops - if you crash and wait for the next mission to start, you can put IL-2 in the background and keep an eye on the mission progress, but at the same time start ranting about "my fav plane is porked" on the forums.

EnableResize=0
Enables user to change window size. can be 0 or 1
must be 0 to allow lcds to fill screen

EnableClose=1

SaveAspect=1

Forces 4:3 picture aspect. Can be 0 or 1
Change SaveAspect=1 to SaveAspect=0 will remove some small black bars at the top and bottom of the screen you get without it on lcds

Use3Renders=0
Allows use of up to 3 screens. Can be 0 or 1

[GLPROVIDER]
This section comments on what 3D drivers you are using

GL=Opengl32.dll
It will either be openGL or Direct X depending on what you picked during setup.

[GLPROVIDERS]
Changed by running setup from start-programs-ubi-il2sturmovich-setup

Open GL=Opengl32.dll

DirectX=dx8wrap.dll


[NET]
This section deals with your settings for connecting to the internet

speed=25000
for multiplayer games.

routeChannels=0

serverChannels=31
serverchannels indicates max allowable number of players

localPort=21000
port 21000 this will have to be enabled in your firewall to allow you to connect to web

remotePort=21000
This is Server's port that you connect. Hyper Lobby detects it automatically.

SkinDownload=1
SkinDownload= 1 allows skins to be used. 0 does not

serverName=
Name of own server

serverDescription=
Own description of server

remoteHost=
IP Internet address of the remote computer that one connects to

localHost=
IP internet address of the local computer that one connects to

socksHost=

checkServerTimeSpeed=1
Compares master clock of server and client

checkClientTimeSpeed=0

checkTimeSpeedDifference=0.05

Maximum difference of the master clock permitted (Maximum is 5%)
Note spelling of differense is correct

checkTimeSpeedInterval=5
Maximum difference of the master clock permitted (Maximum is seconds)

checkruntime=

In order to set the client-side verification parameters you will need to manually edit here
checkRuntime=0-no check is made (default);
checkRuntime=1-quick check;
checkRuntime=2-comprehensive check.

[MaxLag]

farMaxLagTime=10.0

nearMaxLagTime=2.0

cheaterWarningDelay=5.0
Time until you are cheating warning

cheaterWarningNum=-1
Number of warnings until player is kicked. If at -1 autokick is deactivated.


[chat]
region=(dx=0.6925,dy=0.071666665,x=0.0,y=0.0) Position and size of chat window

msg0 =
Contents of the message "0"

adr0=ALL
Receiver of the message "0" (all)

msg1 =
Contents of the message "1"

adr1=MY ARMY
Receiver of the message "1" (own side)

autoLogDetail =
On-Line Stat Messages

The server hosting an on-line game may set the ‘level of detail’ of the server auto-generated stat messages. The level is set in the conf.ini file in the Il-2 folder, in section [chat], in the autoLogDetail key.Ex.:[chat]
autoLogDetail = 3

You can set the key to the following options:0 - disables all stat messages.1 - only player-vs-player kill messages are displayed.2 - displays player-vs-player, and AI-vs-player kill messages.3 - a lot of chit-chatting.

[game]
In game settings

Arcade=0
when at 1 changes display to show balloon speech from aircraft and arrow bullet strikes etc. Can be 1 or 0

HighGore=0
when at 1 changes display to show gore effects on a limited number of planes Can be 1 or 0
This feature has been dsabled in recent versions of the game

mapPadX=0.6689453
mapPadX and mapPadY are position coordinates for the inflight map, they're nothing to do with padlock.They are a measure in fractions of full screen width from left of screen (mapPadX) and height from the top of the screen (mapPadY) for the top left corner of the map.

mapPadY=-0.046875

viewSet=32
Snap view -Even number. Pan view Odd number.

Intro=0
when at 1 runs intro movie at game launch

NoSubTitles=0
(Subtitles for pilots' voices; 1 = none, 0 = all) At top of screen

SubTitlesLines=3
Number of lines for sub-titles

NoChatter=0
(Radio chatter; 1 = none, 0 = all) To hear pilots voices

NoHudLog=0

HUD text messages and warnings; 1 = none, 0 = all At side of screen

NoLensFlare=0
(Lens flare effects; 1 = none, 0 = all)

iconTypes=3 allows user to change what is displayed in icons when enabled these are available from key bind in control section.

Icon Settings: You can change your icon types and distances by typing these variables in console in game the command syntax is: mp_dotrange [FRIENDLY|FOE] [DEFAULT] [COLOR] [DOT ] [RANGE ] [TYPE ] [ID ] [NAME ]

FRIENDLY or FOE keywords define which party the following parameters apply to the aircraft of the viewer's army, or the aircraft of the hostile armies.

The following keys define the distance at which the appropriate icon is enabled:

COLOR: The distance at which icons take the color of the inbound plane’s army. Icons farther away will be drawn in grey.

DOT: The distance at which the “dot” plane marker becomes visible.

RANGE: The distance at which the distance measurement appears in the icon.

TYPE: The distance at which the airplane model or model family becomes visible.

ID: The distance at which the tactical number is visible.

NAME: The distance at which the aircraft’s pilot name is visible (if it is driven by a human pilot).

mp_dotrange DEFAULT restores the Pacific Fighters predefined icon setup.

mp_dotrange run without parameters prints the current icon setup ranges (which may be issued by both client and server).

e.g mp_dotrange FRIENDLY COLOR 0.1 DOT 15 RANGE 5 TYPE 0.1 ID 0.1 NAME 2.5

This will give you friendly info at Aircraft dot at 15km range at 5km Pilot name 2.5km all other at 100metres

eventlog=eventlog.lst

describes where eventlog is written=n to is enabled

eventlogkeep=0

0 when 0, every mission overwrites the event log file, so it contains the last mission only. when 1, it writes an eventlog continuously, keeping log for all missions you fly

3dgunners=1

For 3d gunners in PF will effect frame rate =0 turns them off

Typeclouds=
TypeClouds=0 - standard clouds
TypeClouds=1 - improved quality clouds

[HotKey game]
describes keys assigned during play

PrintScreen=
ScreenShot

P=pause

Pause=pause

[HotKey gui]

Escape=activate
This line needs to be in config to end missions, For some reason, this line very often disappears when patching is done.

[HookViewFly Config]
this section is how your view moves in external view

timeFirstStep=2.0

Time until aircraft passes camera

deltaZ=10.0
Angle of camera to aircraft

[HookView]
The camera origins are fixed but the distances you may be able to change for the [Hook View] and [Hook View Fly] sections

MouseLeft=Len

[HookView Config]


AzimutSpeed=0.1

TangageSpeed=0.1

LenSpeed=1.0

MinLen=1.0
(closest distance from a given object while in camera view)

DefaultLen=20.0
(Default distance from object when using external views)

MaxLen=3000.0

(Max distance from camera you can zoom out, I have mine set to 50000 which is 50km. Nice for finding stuff if you die!)

Speed=6
(speed of mouse zoom and pan, higher is faster)

[HotKey builder]

these are key assignments when using the mission builder


[MouseXYZ]
This section concerns the variables for mouse control
The mouse is generally used as a viewing device either in game or when viewing tracks

[HotKey Console]

This section deals with console . There is a console help section in forums at www.airwarfare.com (http://www.airwarfare.com) for full list of commands. In the console you can change most of the config parameters while in game.

Shift Tab=Activate
The console is where you can type commands to the game. In this default setting you press shift +tab to show console

[Console]
The console is where you can type commands to the game.
In the default key setting you press shift +tab to show console

The most common use is fps START SHOW to display FPS

In the console you can change most of the config parameters while in the game.

HISTORY=1024
Number of lines permitted in console

HISTORYCMD=1024

LOAD=console.cmd

SAVE=console.cmd

LOG=0
Here logs are disabled but you can save them by setting to 1 if you wish the console will then be saved to a text file for you to view later.

LOGTIME=0

LOGFILE=log.lst

LOGKEEP=0

[sound]
This section deals with sound settings in game most are determined in the in game hardware setup sound section

SoundUse=1

SoundEngine=1

Speakers=1

0=Default 1=Headphones 2=Desktop speakers 3=Quadraphonic 4=Surround

Placement=0
0=Default 1=Small 2=Narrow 3=Wide

SoundFlags.reversestereo=0

RadioFlags.Enabled=1

RadioEngine=2
Radio volume

MusicVolume=8
Music volume

ObjectVolume=14
Object volume

MusState.takeoff=1
Takeoff music can be 1 or 0

MusState.inflight=1
Inflight music can be 1 or 0

MusState.crash=1
Crash music can be 1 or 0

MasterVolume=12

Main volume

NumChannels=2
0=Default 1=8 2=16 Best for quality vs. performance 3=32 Beware of performance hit!

[rts]
This section is for input controls for mouse and joystick

;ProcessAffinityMask=1

IL-2 supports two processors using the ProcessAffinityMask in the conf.ini. There's little documentation from Maddox Games about how you're supposed to use it, though.

ProcessAffinityMask=1 Core1 (default) or
ProcessAffinityMask=2 Core2 or
ProcessAffinityMask=3 Core1+2

You must remove the semicolon in order to run this command Basically tells IL-2 which core(s)to run on. There appears to be no consensus that running IL-2 on two cores shows any tangible difference.
One more thing to add. With the Semicolon in place you essentially have the same as:
ProcessAffinityMask=0 which also uses both cores so it's the same as =3.

EDIT BY StG77_HaDeS
Actually you HAVE to set game to use Only 1 core to have better FPS and considerable LESS stuttering.

mouseUse=2

joyUse=1
can be 1 or 0

trackIRUse=1
TrackIR is a piece of hardware that moves view when you move your head. This line also has to be in file if you use niewview a program that helps you get better control of your hat switch

DisableIME=0

locale=
Set menu and HUD message language to other than English, e.g., German (de) or Russian (ru) or Hungarian (hu)

[rts_mouse]


SensitivityX=1.0
the higher the value the more sensitive movement in x axis

SensitivityY=1.0
the higher the value the more sensitive movement in y axis

Invert=0
Inverts mouse movement

SensitivityZ=1.0
the higher the value the more sensitive movement in z axis

[rts_joystick]
Joystick settings are found in hardware setup in game See Tully's Joystick section for full instructions on setting up your joystick.

X=0 1 4 9 16 25 36 49 64 81 100 0
Each axis has 12 entries. The first is the dead zone ( 0 to 50) the last is filtering ( 0 to 100)

Y=0 1 4 9 16 25 36 49 64 81 100 0

If all values set to 100, IL-2 software does not do any "curving"

[Render_DirectX]
This section is for your video card and how its features are used in the game.
Most use OPENGL as the game was optimized for this so all comments are in this section.
See Video card section in IL2 optimization guide for explanation of terms

[Render_OpenGL]
This section is for your video card and how its features are used in the game.
See Video card section in IL2 optimization guide for explanation of terms

As Far as I Know the Text variables are all set in hardware setup program and depend on your card.

TexQual=3
3= normal
2= reduced by factor of 2
1= reduced by factor of 4 0 = reduced by factor of 8.
Only need to reduce for older graphics cards of 16mb or less.

TexMipFilter=1
0=None
1=Bilinear (fastest)
2=Trilinear (Improves quality with little sacrifice in speed)
3=anisotrophic (Best quality but slower)

TexCompress=2
0=No compression best quality
1=16bit conversion
2=S3TC compression, best Performance. with little worse texture quality

TexFlags.UseDither=1

TexFlags.UseAlpha=0

TexFlags.UseIndex=0

TexFlags.PolygonStipple=1

TexFlags.UseClampedSprites=0

TexFlags.DrawLandByTriangles=1

TexFlags.UseVertexArrays=1

TexFlags.DisableAPIExtensions=0

TexFlags.ARBMultitextureExt=1

TexFlags.TexEnvCombineExt=1

TexFlags.SecondaryColorExt=1

TexFlags.VertexArrayExt=1

TexFlags.ClipHintExt=0

TexFlags.UsePaletteExt=0

TexFlags.TexAnisotropicExt=0

TexFlags.TexCompressARBExt=1
must be activated if S3TC compression is used

TexFlags.TexEnvCombine4NV=1

TexFlags.TexEnvCombineDot3=1

TexFlags.DepthClampNV=1

TexFlags.SeparateSpecular=1

TexFlags.TextureShaderNV=1

HardwareShaders=0
Must be 1 to activate Perfect mode.

Shadows=1

The lower the value in this section the less detailed these appear but game runs faster e.g
If you suspect trees or forests may cause the frame rate to drop, try lowering the Forestparameter in the conf.ini to 1, or even 0 (that would make forest appear in less detail, but render faster).

The only ones I have adjusted are water, Forest and Effects.

Specular=2

SpecularLight=2

DiffuseLight=2

DynamicalLights=1

MeshDetail=2

VisibilityDistance=2

Sky=2
Forest=1
LandShading=2
LandDetails=2

LandGeom=2
TexLarge=0 High-resolution airplane textures (0/1)
0= low resolution, fewer memory needs, faster
1= quality, improves textures more memory need, slower

TexLandQual=3
TexLandLarge=0 High-resolution land textures (0/1) 0= low resolution, fewer memory needs, faster 1= quality, improves textures more memory need, slower

VideoSetupId=15

0 - Safe Settings
1 - Default Settings
2 - Maximum Settings
3 - NVidia GeForce 6800/6600/FX/4/3
4 - NVidia GeForce 5200..5900 - 1.x Shaders
5 - NVidia GeForce 4MX
6 - NVidia GeForce 2 GTS/MX/256
7 - NVidia Riva TNT2
8 - ATI Radeon X800/9800/9700/9600/9500
9 - ATI Radeon 8500/9000
10 - ATI Radeon
11 - Intel 915/925 (GMA900)
12 - Kyro II
13 - Matrox G400
14 - 3dfx Voodoo 3
15 - 3dfx Voodoo 5
16 - S3 Savage 4
17 – Custom

Water=1
To select water rendering mode please modify the Water section in the file conf.ini in the [Render_OpenGL] section (Water = 1 by default).

Water = 0 - Water with flat geometry (fastest).

Water = 1 - Water with flat geometry (fast).

Water = 2 - This mode is visually similar to water = 3 but it runs on ATI cards 9800, X800, X1800 and later models.

Water = 3 - Fast render mode with Vertex Shaders 3.0 (NVIDIA 6600 and later models)

Water = 4 - Better quality mode with Vertex Shaders 3.0 (NVIDIA 6800 and later models)

Reminder:
ATI 9500 and higher supports modes: 0, 1, 2.
NVIDIA 6600 and later models support: 0, 1, 2, 3, 4.
NVIDIA cards before the 6xxx series support: 0, 1, 2 (2 is not recommended).

Effects=1
To minimize effects settings, use Effects = 0 (effects without shadows).
Effects=2, ([Render_OpenGL] section of conf.ini) test mode for improved effects lighting. This mode required 3.0+ MHz CPU.

ForceShaders1x=0

If on older cards try to use ForceShaders1x = 1 it's helpful for GeForce FX 5200, 5600, 5700 cards. Not needed for newer cards

Clouds rendering

In order to see higher quality clouds you will need to manually edit the conf.ini file located in your main game folder before launching the game. Open the file with a text editor, find the [game] section and in the TypeClouds= line write in either 0 or 1, then save the file.

TypeClouds=0
standard clouds

TypeClouds=1
improved quality clouds

Note:
When playing online the player will see the cloud type set by the server, and not as individually set in their conf.ini. This is done to ensure all players see the same tactical situation in the air regardless of their settings.

PolygonOffsetFactor=-0.15
If you experience flickering airfields when viewed from high altitude, add these two lines into the OpenGL section to fix the issue

PolygonOffsetUnits=-3.0

[DGen]
Not added by default used to alter settings for offline play

NoBadWeather=1

Can be set to zero or one, one meaning you never get bad weather

MissionDistance=50

Can be set to from 10 to 200 Kilometers, depends on the map and targets available. It is not guaranteed that there will be suitable targets in this distance

NoAirfieldHighlight=1
Set to one to zero. Zero meaning you'll have AAA/flak unit at some unused airbases

RandomFlights=0
Can be set to 0 to 5 Random flights are flights not related to your mission, both friendly and enemy are just incidental you may or may not see these flights, they might not get close enough. Default or not having the line in conf.ini is average (3). Can affect frame rates.

MaxFLAK=5

Can be set to 0 to 100, default or not having the line in conf.ini is 10. Can affect frame rates. Affects the amount of flak generated from your airfield to target, so can affect frame rates very much.

AirIntensity=Low
Settings are low, medium and high. Default or not having the line in conf.ini is medium. Sets the number of flights, enemy and friendly, that are related to your mission. On low setting, there will be no random flights and it will override the "RandomFlights=" setting in that case, ( see above ). Can dramatically affect frame rates.

GroundIntensity=Low
Settings are low, medium or high. On low, you'll only have ground objects around target or active airfields. Default is medium (or not having the line in conf.ini ) and there will also be extra objects around your flight route, besides target area and active airfields. High gives you extra targets of opportunity to and from your home field. Can dramatically affect frame rates.

Maxbomberskill=1
Settings are 0, 1, 2 and 3, ( for rookie, average, veteran and ace ) and default or not having this line in conf.ini, the AI bomber gunners will be kind of random or depend on other settings like CampaignAI=. This limits the entire bomber skill ( not just the gunners ) to a lower level if preferred, so you can attack bombers more easily if you limit it to a low setting. It affects only enemy AI for bombers, not friendly. Unfortunately, this does nothing for transport aircraft, such as LI-2, C-47 or JU-52, so be careful around those and don't assume they will be limited like the bombers if you set this to a low setting!!! Sometimes FW-200 Condor can also sometimes be assigned as a transport plane in some maps, so watch it!!!!

CampaignMissions=Hard
Settings are easy, normal or hard. Default or not having the line in conf.ini is normal. This changes the scripts ( ops files, I.E. - ops41-E.dat, where "E", means easy ) files in the Dgen folder used to generate missions. Affects the number of enemy planes encoutered as opposed to the number of friendly planes in your group/s. For example, set on easy, you might have a mission generated which gives you four fighters on your side with four bombers, and two enemy fighters will later show up to intercept your bombers. The very same mission on hard might give you only two fighters on your side, maybe the same number of bombers to escort, but you'll run into four enemy fighters to deal with!! This balances out so it does not affect frame rate much, if at all.

CampaignAI=Hard
Settings are easy, normal or hard. Default or not having the line in conf.ini is normal. Increases enemy and friendly AI by a factor of one. Low increases friendly AI level higher while lowering enemy AI level. High does the opposite. Normal gives you a more even match of AI strength."

CampaignLength=Short
VeryShort, Short, Medium, Long, VeryLong (VeryLong is default)

CampaignDifficulty
CampaignDifficulty=Easy
CampaignDifficulty=Hard
Easy settings will add one level to all friendly groups and decrease enemy experience

OperationVictory=100

In Pacific Fighters dynamic campaigns the player's actions influence the outcome of individual operations as well as the whole war. The system works by assigning a static number of points to each target destroyed, and calculating a total number of points for each side. If your side destroys enemy targets, points are added to your side's tally. If your side's targets are destroyed by the enemy, the points are subtracted from your side's tally..Each side is assigned a predetermined number of points which in each operation means a historical outcome (victory or defeat). If the operation's tally does not match the historical outcome, an alternative briefing is triggered which may mean a defeat for the side that historically won, or vice versa.For example, if you want mission outcome to always be historical, you can set the parameters to unachievable high values, such as:

OperationDefeat=-100
OperationVictory=3000
WarVictory=1000
OperationDefeat=-3000
WarDefeat=-1000
WarVictory=30000
WarDefeat=-30000

Default value for an operation outcome is 100 points (added if it's a victory, subtracted if it's a defeat). War outcome's value is 1,000 points By reducing the numbers you can make your contributions matter much more in the overall war effort.

The following point values are used
Carrier = 100 points
Other ship = 20 points
Plane = 5 points
Tank = 3 points
All other targets = 1 point
The tallies are recalculated after each mission, and they're checked at the end of each operation.

UseParachutes
Japanese have chutes from start of war
Title: Re: inside the CONFIG.INI
Post by: Verhängnis on December 11, 2010, 07:11:31 PM
Interesting..Nice find.
Title: Re: inside the CONFIG.INI
Post by: PO_MAK_249RIP on December 16, 2010, 02:21:09 AM
This has been around a while but its always useful to repost for the newer guys. It used to be on an older site which I think is now no more?
Title: Re: inside the CONFIG.INI
Post by: asheshouse on December 16, 2010, 02:25:27 AM
There is a detailed guide to the conf.ini at Mission4Today
http://mission4today.com/index.php?name=Knowledge_Base&cat=7
Title: Re: inside the CONFIG.INI
Post by: Mick on December 17, 2010, 01:50:32 AM
Could somebody tell us who is right ? The version we've always read or that one ?

Just FYI this part is wrong:
Code::

TexMipFilter=1
0=Bilinear (fastest)
1=Trilinear (Improves quality with little sacrifice in speed)
2=anisotrophic (Best quality but slower)


The correct version would be:
Code::

TexMipFilter=1
0=none
1=bilinear
2=trilinear
3=anisoptropic

source : http://mission4today.com/index.php?name=Knowledge_Base&cat=7
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on July 15, 2011, 01:32:29 AM
Just for reference, these are the required settings for absolutely maxed out graphics in IL-2:

Please check the sections and settings as described below, usually all mentioned parameters should be in your conf.ini already, so you just have to change them accordingly.

All type of cards:

Code: [Select]
[window]
ColourBits=32
DepthBits=24
StencilBits=8
Code: [Select]
[GLPROVIDER]
GL=Opengl32.dll
Code: [Select]
[game]
TypeClouds=1
Code: [Select]
[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=1
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.ClipHintExt=1
TexFlags.UsePaletteExt=1
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=0

TexFlags.TexEnvCombineDot3=1
TexFlags.SeparateSpecular=1

HardwareShaders=1

Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=3
LandShading=3
LandDetails=2

LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Effects=1
ForceShaders1x=0
PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-1.0

For ATI cards:
Code: [Select]
TexFlags.UseVertexArrays=0
TexFlags.VertexArrayExt=0
TexFlags.TexEnvCombine4NV=0
TexFlags.DepthClampNV=0
TexFlags.TextureShaderNV=0
Water=2

For Nvidia cards:
Code: [Select]
TexFlags.UseVertexArrays=1
TexFlags.VertexArrayExt=1
TexFlags.TexEnvCombine4NV=1
TexFlags.DepthClampNV=1
TexFlags.TextureShaderNV=1
Water=4

For quick copy&paste action, the whole [Render_OpenGL] section for ATI cards:
Code: [Select]
[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=1
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.UseVertexArrays=0
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=0
TexFlags.ClipHintExt=1
TexFlags.UsePaletteExt=1
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=0

TexFlags.TexEnvCombine4NV=0
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=0
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=0

HardwareShaders=1

Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=3
LandShading=3
LandDetails=2

LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Water=2
Effects=1
ForceShaders1x=0
PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-1.0

And the same thing, whole [Render_OpenGL] section, this time for Nvidia cards:
Code: [Select]
[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=1
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.UseVertexArrays=1
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=1
TexFlags.ClipHintExt=1
TexFlags.UsePaletteExt=1
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=0

TexFlags.TexEnvCombine4NV=1
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=1
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=1

HardwareShaders=1

Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=3
LandShading=3
LandDetails=2

LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Water=4
Effects=1
ForceShaders1x=0
PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-1.0

Note: You can try "Effects=2" if you feel lucky, but it's prone to cause stutters and different errors if your hardware can't handle it. Additionally it causes issues with effects mods like "Plutonium Effects Mod". Be warned - in case of trouble, just set "Effects=1" as listed above.

Hope that helps.
Best regards - Mike
Title: Re: inside the CONF.INI
Post by: wingflyr on July 15, 2011, 12:14:21 PM
quote Storebror
Just for reference, these are the required settings for absolutely maxed out graphics in IL-2:

Awesome settings, Mike,
 just awesome. Thanks for this. Worked very well with my card, again thanks for doing this. Cheers M8. Wingflyr.
Title: Re: inside the CONF.INI
Post by: LuseKofte on July 15, 2011, 01:33:11 PM
Storebror you had a setting in one of the texflag to stop game freeze when bomb drop
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on July 16, 2011, 12:44:07 AM
Thanks for mentioning this Le0ne.

Now we're stepping apart from maxed out settings...
In case your game freezes/crashes when dropping big bombs, set this parameter as follows:
Code: [Select]
[Render_OpenGL]
TexFlags.UseClampedSprites=1
This will limit the number of sprites/objects being rendered simultaneously at a given time and thus solves issues where there are just too many objects (here: explosion effects) to be rendered to fit to your system limits.

In case you get the famous "Paratrooper Error" message on mission start:
"Mission loading failed: Mesh3do/humans/Paratroopers/Russia/mono.sim not created"
please set the following two parameters as follows:
Code: [Select]
[Render_OpenGL]
TexCompress=2
TexFlags.TexCompressARBExt=1
This will compress textures before transferring them to your graphics card memory and thus solves issues where the amount of textures exceeds the hardware limits of your graphics card's memory.

Best regards - Mike
Title: Re: inside the CONF.INI
Post by: hguderian on July 16, 2011, 07:04:27 AM
Hi!
If I'm not wrong "Typeclouds=" goes under the config's [game] section and have only two values:
TypeClouds=0 - standard clouds
TypeClouds=1 - improved quality clouds

Also I know that effects= must be set to 0 or 1 cause a value like 2 can cause stutters/slowdown and freezes.

Cheers
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on July 16, 2011, 10:37:33 AM
You're right about the TypeClouds setting, this was my mistake. Thanks for the heads up, I've changed the above post accordingly.
For Effects=2 setting a warning has been added, however it should work well on current mid-range hardware as long as no conflicting mods are installed.

Best regards - Mike
Title: Re: inside the CONF.INI
Post by: Silverback on July 16, 2011, 11:46:55 AM
Try it and see for yourself, can't hurt.
Title: Re: inside the CONF.INI
Post by: Whiskey_Sierra_972 on July 27, 2011, 05:20:30 AM
The best setting I ever tried!!!!

Thanks for them Mike!!!

All the best!

walter
Title: Re: inside the CONF.INI
Post by: pdittrich on September 17, 2011, 02:40:36 PM
absolutely maxed out graphics
"beware", he means what he says.
i tried them, and for a second, i enjoyed wonderful pictures... then a black screen. i "thought" my rig was alright, but that was unhandelable for it.
i lol'd, tuned some stuff down, now it works - waaaay better than before, a big thanks to all who contributed to this thread.
Title: Re: inside the CONF.INI
Post by: Wildchild on September 24, 2011, 12:21:02 PM
Thanks Storebor, will try these out when I get home  ;D
Title: Re: inside the CONF.INI
Post by: Wildchild on September 26, 2011, 02:32:06 PM
Only one question... Whats the fix for stuttering over cities?
Title: Re: inside the CONF.INI
Post by: CWMV on September 26, 2011, 02:35:49 PM
Don't fly over cities.
Buy better hardware.
Decrease graphics settings.
Title: Re: inside the CONF.INI
Post by: jt189 on September 26, 2011, 03:58:15 PM
Now what if wildchild can not afford the high end hardware that most of us have some of the hardware cost up to 4 figures and beyond.
Title: Re: inside the CONF.INI
Post by: CWMV on September 26, 2011, 04:14:23 PM
Then turn the graphics settings down.
It may also help to run plutonium effects if he's not already. Way better performance over stock. Helped me.
Perhaps an expert like Storebror can recommend another solution.

Forgive my brevity, posting from phone.
Title: Re: inside the CONF.INI
Post by: Knochenlutscher on September 26, 2011, 04:32:47 PM
Wildchild, don't try to run these maxed out ultra settings, it's Post no.999 for that topic.
please read through Hades recommended Thread for optimum Settings, not maxed out.
http://ultrapack.tuttovola.org/index.php/topic,2.0.html
Depending on your hardware of course, if you stick with NVIDIA try NVIDIAINSPECTOR instead NHANCER (outdated!), lets you
set AFR3 too.
Once you understood and tried what he said it's easy to find a strutter-free solution.
I did too, only had maxed out, until I switched 1-2 things a bit down.
It's not a MOD thing, but a conf.ini tweaking, it took me 7 months to find my personal optimum settings there.
Those that have good gfx and less strutters. I can have strutters with or without Ceasium Mods if I try some settings.
Title: Re: inside the CONF.INI
Post by: Wildchild on September 26, 2011, 05:26:31 PM
Wildchild, don't try to run these maxed out ultra settings, it's Post no.999 for that topic.
please read through Hades recommended Thread for optimum Settings, not maxed out.
http://ultrapack.tuttovola.org/index.php/topic,2.0.html
Depending on your hardware of course, if you stick with NVIDIA try NVIDIAINSPECTOR instead NHANCER (outdated!), lets you
set AFR3 too.
Once you understood and tried what he said it's easy to find a strutter-free solution.
I did too, only had maxed out, until I switched 1-2 things a bit down.
It's not a MOD thing, but a conf.ini tweaking, it took me 7 months to find my personal optimum settings there.
Those that have good gfx and less strutters. I can have strutters with or without Ceasium Mods if I try some settings.

Thanks, I'll try those tonight. I love the effects, but what I really notice is the changes in the ground, none in the plane or anything elts

(I do love the updated trees alot!!!!)
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on September 27, 2011, 01:21:28 AM
what I really notice is the changes in the ground, none in the plane
Yes that's true, the conf.ini settings mostly apply to ground objects, apart from some obvious texture settings which would affect planes too. If you like to have sweet looking planes, try to fine-tune your graphics card settings either in Nvidia control panel, ATI catalyst control center or the like, e.g. raising the anti aliasing and anisotropic filter settings will increase the overall quality ingame alot. All of this requires enough GPU power of course.

The particular issue of stuttering over big cities in turn is a CPU load issue for sure (at least 99% sure).

Bottom line: You can't teach an old dog new tricks. If your CPU and/or GPU can't handle the game on max settings, you either have to reduce the settings or buy new hardware. There really ain't no way around that, trust me, I've tried it for years and ended up in doing a major hardware upgrade myself.

Best regards - Mike
Title: Re: inside the CONF.INI
Post by: MANYSH on September 27, 2011, 02:16:28 AM
Very simply you can save your CPU :) I have worst PC ever ,and stuttering was very bad on my PC

What you need to do:

1 Make another partition on you hard drive
2 Install another operating System on  partition with you create ( Use win XP. don't try vista, win 7! )
3 Remove all not needed services, and applications from your Win XP
4 Install drivers, and java
5 Install Il-2
6 Configure Nvidia profiler ( im sure very similar soft you will find for ATI ) , turn all settings off, keep anti-aliasing 2X -4X check how this affect your game.
7 Configure Swap file for win XP
8 Configure config.ini

After that,I save about 30% CPU power, you may say is not much, but it really help for stuttering and all problems . Use this operating System only for Il-2 for safety reasons :)
BTW you may buy Win XP cheap from eBay

Regards
Title: Re: inside the CONF.INI
Post by: Wildchild on September 29, 2011, 07:18:32 PM
Mixed two of the settings, now i got a big forest and nice city without stuttering ;)
Title: Re: inside the CONF.INI
Post by: KG3_V on December 22, 2011, 05:20:22 AM
Can somebody look maybe over my grafic settings in the ini ? I have a good system, quadcore @3,4 GHZ, 4 GB Ram, Win7-64, GTX 580, and still have a lot of stutter when lot of planes are burning or bomb runs. I use the merged Plutonium/FxRevplution Mod for 4.1 (in DBW 1.6)


Code: [Select]
[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=0
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=1
TexFlags.UseVertexArrays=1
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=1
TexFlags.ClipHintExt=0
TexFlags.UsePaletteExt=0
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=0

TexFlags.TexEnvCombine4NV=1
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=1
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=1

HardwareShaders=1

Shadows=1
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=2
LandShading=3
LandDetails=2

LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17

ForceShaders1x=0
PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-1.0
Water=4
Effects=0
Title: Re: inside the CONF.INI
Post by: gianluca on December 22, 2011, 08:11:40 AM
Hi, have you checked you are running the game having set the right core affinity? one core only is the best but I also discovered that enabling this through conf.ini did not work and had to use task manager....
Gianluca
Title: Re: inside the CONF.INI
Post by: santobr on December 22, 2011, 08:34:05 AM
Try this:
TexFlags.DrawLandByTriangles=0
TexFlags.ClipHintExt=1
TexFlags.UsePaletteExt=1
Forest=3
Effects=1



santobr.
Title: Re: inside the CONF.INI
Post by: KG3_V on December 22, 2011, 02:45:46 PM
Thanks !
It really seem to run better now

But still missing smoke trails when to much explosion, but I believe this was a engine problem
Title: Re: inside the CONF.INI
Post by: santobr on December 22, 2011, 03:16:41 PM
Yes, it is.
Some smoke effects can produce a lot of particles, when the number of particles shown in the screen reaches the limit of the engine of IL-2, a group of them will disapear and even some textures on airplanes like glass or propellers could disapear too.
Take a look at this video:
http://www.youtube.com/watch?v=OOrm5__8af0


santobr.
Title: Re: inside the CONF.INI
Post by: LuseKofte on July 13, 2012, 04:05:23 PM
I got this shadowa flickering using Gurners effects on the side of the smoke, the shadows blink continiously. I am sure it has nothing to do with the mod but my conf.ini settings.

HardwareShaders=1

Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=3
LandShading=2  it was 3 but when I change it to 2 the blinking was gone. What exactly does this regulate is it the landscape shadows?
LandDetails=2

LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Water=4
Effects=2
ForceShaders1x=0
PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0
Title: Re: inside the CONF.INI
Post by: razor1uk on August 03, 2012, 11:28:41 AM
Most likely a 3D representation of shadow from the point of view from the lighting source - would involve a lot of CPU/GPU power - and so flikering as it is actively adjusted to your 'screens' position relative to ground and lighting angles etc... where as shadpws 2 might just apply simpler 'shadow' method.
Title: Re: inside the CONF.INI
Post by: ntz on September 20, 2013, 07:36:25 PM
hello, i'd like to call for some help :) ..

well, say I have exactly those settings (except with effects=1) and everything is in stock 4.12.1m abolutely smooth and cool, but in 4.11.1m + HSFX 6.0.17 i have lower fps and tearing sometimes when flying above city or big ground combat group .. I've heard that HSFX replaced some textures by more quality one or so, not sure .. i have 1024MB of dedicated RAM memory and relatively good cpu and gfx ..

What would you please start with from these "maxed" settings to put lower to increase FPS ? I have nvidia GT230M and i7-QMxxx (mobile quadcore) ?

just take a look for reference here http://www.sas1946.com/main/index.php/topic,9756.msg185327.html#msg185327 .. i have these settings ..

summary:

settings above are pretty fine in stock 4.12.1m but tearing and with fewer FPS when stock 4.11.1m + hsfx 6.0.17

regards, ntz
Title: Re: inside the CONF.INI
Post by: Mick on September 21, 2013, 01:49:20 AM
I got this shadowa flickering using Gurners effects on the side of the smoke, the shadows blink continiously. I am sure it has nothing to do with the mod but my conf.ini settings.

... yep, I had that very same shadows flickering until I changed Effects=2   >>> to =1 ...  ;)
Title: Re: inside the CONF.INI
Post by: Balker on September 22, 2013, 10:50:21 PM
Look at the "rings" I have around the moon:

(http://www.sas1946.com/images/imageshit/img42/8397/hyrm.jpg)

Can I fix this setting the conf.ini?
I have a ATI Radeon HD 4800.

Thx!
Title: Re: inside the CONF.INI
Post by: ntz on September 25, 2013, 10:40:14 AM
you can't fix this ..
Title: Re: inside the CONF.INI
Post by: Balker on September 25, 2013, 11:31:43 AM
you can't fix this ..

And that is because...:)

Title: Re: inside the CONF.INI
Post by: santobr on September 25, 2013, 07:08:28 PM
I don't know if these will make any difference, but check these settings in your conf.ini:
Code: [Select]
TexFlags.SecondaryColorExt=1
TexFlags.UsePaletteExt=0



santobr.
Title: Re: inside the CONF.INI
Post by: ntz on September 26, 2013, 05:59:29 AM
well, it's because textures of sky are not generated on fly and they are not in range 3x 0xFF (RGB) but in much shorter range .. and also i'm tending to suppose, that it's intentional like that ;) .. well, i'm NOT gfx expert, perhaps someone more proficient will reply it .. also it higly depends on your display device and its brightness
Title: Re: inside the CONF.INI
Post by: Balker on September 27, 2013, 01:07:19 PM
Thanxs  ;)
Title: Re: inside the CONF.INI
Post by: JosefK on October 01, 2013, 06:52:30 AM
Hi everyone,

can someone write me here, best working Render_OpenGL configuration for my PC, I have VGA GeForce 9600 GT (512MB), RAM 4GB,
CPU X4 640 (3.01 GHZ) ?

Thanks!
Title: Re: inside the CONF.INI
Post by: ntz on October 01, 2013, 01:42:07 PM
everything you need is written up at the first page of this thread
Title: Re: inside the CONF.INI
Post by: FNRennier on October 01, 2013, 02:29:40 PM
michel_boonstra1974,
Very good, yes it is a good help to better understand the config.ini, thank you!  ;D
Title: Re: inside the CONF.INI
Post by: Goanna on January 08, 2014, 08:56:58 PM
Hi gents,
I'm always scouring the net for the latest and greatest info on the conf.ini file, discovered the quoted bit below in one conf.ini of an ATI user. I've never seen these lines before, anyone know what they are/do?

Cheers

Goanna

Quote
FogLow=1
FogHaze=4

Link to source;
http://69thvirtualfightergroup.com/phpBB3/viewtopic.php?f=15&t=5481&sid=a909293b0dac526a0dbf3048e00e9227
Title: Re: inside the CONF.INI
Post by: Mick on January 09, 2014, 02:11:21 AM
... never seen these two lines before ...  ???

At first I thought they were part of a weather mod, but then they should be part of a [Mods] section that is absent from the guy's conf.ini ...  :(

Of course no need to be a mod guru to guess that the first line deals with the altitude of fog, and the second line with the thickness of it ...  ;)
Title: Re: inside the CONF.INI
Post by: marcost on January 09, 2014, 02:53:34 PM
Hi that sounds familiar - I came across the foghaze parameter on another thread recently. I hadn't heard of it either:

http://www.sas1946.com/main/index.php/topic,15180.288.html


Regards,

M
Title: Re: inside the CONF.INI
Post by: Goanna on January 09, 2014, 03:59:47 PM
Thanks Mick & Marcost, interestingly the guy who posted his conf.ini in the link I posted claims that his conf.ini is from a "vanilla" version of the game.

Cheers

G
Title: Re: inside the CONF.INI
Post by: hguderian on January 09, 2014, 04:33:23 PM
Take a look here!

http://www.sas1946.com/main/index.php/topic,18906.msg205908.html#msg205908 (http://www.sas1946.com/main/index.php/topic,18906.msg205908.html#msg205908)

Cheers
Title: Re: inside the CONF.INI
Post by: David Prosser on May 06, 2014, 08:38:07 PM


Thanks, this information was really useful.

cheers

David
Title: Re: inside the CONF.INI
Post by: harpia on February 05, 2015, 03:45:43 PM
Thank Storebror, the IL2 graphic was wonderful, thanks again!:)) ;) ;) ;) ;D ;D ;D
Title: Re: inside the CONF.INI
Post by: LucShep on February 05, 2015, 04:09:32 PM
A must read for any user of IL2.
Many thanks for this thread.  :)
Title: Re: inside the CONF.INI
Post by: vpmedia on February 05, 2015, 10:32:02 PM
I've found this useful when I started playing this game:

Quote
IL-2 setup explained

Driver Tab
Provider: OpenGL or DirextX. OpenGL will most often give the best performance, especially on Nvidia cards, but try both and see which one gives better performance. OpenGL requires a dedicated graphics card, will not work with onboard graphics and some laptop cards.

"Full Screen" mode is the standard way to play the game and will often give the best performance/stability.

If you run widescreen in the conf ini use:
EnableResize=0
SaveAspect=0

Video Mode: Choosing lower resolutions and color modes will greatly increase framerate and lower memory usage. 32-bit color is needed to enable "Perfect" mode graphics.

"Use Stencil Buffer" enables translucent shadows (instead of full black shadows) and is required to enable "Perfect" mode graphics. For a slight performance boost, turn this setting off.

Video Tab
Texture Mipmap Filter: Simply put, this setting affects how sharp a texture may look when viewed from large angles or distances. Anisotropic offers the best image quality at a usually heavy performance loss (only folks with good video cards should use this), and bilinear filtering offers the best performance at a still acceptable texture quality. Trilinear is a tiny bit better than bilinear (it smoothes the transitions between mipmap levels) and the performance hit is very minimal depending on your video card. I reccomend bilinear but it is up to personal taste and your hardware.

Texture Compression: This setting can greatly reduce the memory load and increase framerate by compressing textures. S3TC gives the highest compression ratio and may cause some minor artifacts like little squares on water but it can greatly help or eliminate stuttering (16bit has a smaller compression ratio and less performance boost but also a bit less artifacts). I reccomend S3TC compression.

"Use Dither" helps eliminate the ugly color "banding" when running the game in 16-bit color mode. Has no effect in 32-bit color mode. Reccomended on in 16-bit color mode and can be turned off if running with 32-bit color.

"Use Vertex Arrays" gives faster performance without image quality loss because it allows vertices to be used in groups (arrays) instead of individually. Turn this on.

"Polygon Stipple" is a way of emulating or faking translucent shadows when the stencil buffer is turned off. It does this by creating a "dotted" effect that looks translucent (not unlike the stubble of incoming facial hair). Turn this off for a small performance boost. If stencil buffer and polygon stipple are both turned off, you'll get completely black shadows which isn't much of a drawback.

"Multitexture" affects all multitexturing used in the game, most notably, some water effects, and the very high clouds that are textured to appear more "chunky." Without multitexture, these clouds are smooth white instead of textured. Highly reccomended to leave this on but turning off yeilds performance boost.

"Combine" allows more advanced multitexturing effects. For example, the murky water effect near edges of rivers to simulate shallow depth uses this extension. Turning off gives small performance boost but I reccomend to leave it on.

Turning off "Secondary Color" creates graphic anomalies during fog. For example, nearby forests may not appear to be "fogged out" while everythng else is. This may give a performance boost when turned off but I reccomend it to be left on.

"Vertex Array Extension" allows the use of vertex arrays as explained above. Reccomended on.

"Clip Hint" tells the driver that clip volume clipping for primitives is not neccesary. Basically, it tells the driver not to worry about something the game doesn't do anyway. Minor performance increase when checked (about 1 fps). Reccomended on.

"Use Palette" uses paletted textures instead of full color textures. This can save memory with little to no image quality loss. About 1 fps increase when checked. Reccomended on.

"Texture Anisotropic Extension" should be checked if you selected anisotropic as your mipmap filter. Otherise, uncheck it.

"Texture Compress ARB Extension" should be checked if you're using S3TC for texture compression. Otherwise, uncheck it.

Sound Tab
Playback Channels: The number of channels sound can be played through. Fewer channels give better performance. 8, 16, and 32 are your options but 16 is pretty much the minimum or else sounds may cut out when firing the weapons on a plane with many guns. I reccomend 16 channels.

Speaker Type: Self-explanitory, select your setup.

"Reverse Stereo" should only be checked if your left/right sounds are reversed.

3D Engine Mode: Affects sound engine quality/features. Settings are self-explanitory. I reccomend the minimal mode though I notice very little quality differences between the modes.

Sampling Rate: Affects the sound quality (clarity), lower gives better performance. It's up to personal preference but I reccomend 22050 for low to mid range PC's.

"Audio Enhancements and Hardware Acceleration" enables the use of hardware for sound and uses more sound features/effects. Some people report an increase in framerate when this is turned on (Audigy 2 for example) and others report a decrease (Turtle Beach Santa Cruz, some Soundblasters). You should test which setting gives best performance on your card.

(http://euro_wdwmkr.tripod.com/g42.gif)

(source: http://forums.ubi.com/showthread.php/480194-IL-2-Setup-Explained)

I added some info to the 'driver tab' section.
Title: Re: inside the CONF.INI
Post by: Crazy G on October 17, 2015, 03:02:15 PM
S!

What these settings do? UIColor=0 and UIDetail=0

Thanks,
Title: Re: inside the CONF.INI
Post by: CzechTexan on October 31, 2015, 01:34:38 PM
Thanks Boonstra, Storbror, and all others who added input for the conf.ini
I've been wondering how I can get rid of the haze in the atmosphere and the settings here seemed to fix it.
Title: Re: inside the CONF.INI
Post by: KevinHoggard on November 06, 2015, 02:13:57 PM
Have a question regarding the Video Setup ID, I'm running a NVIDIA® GeForce® GTX745 Graphics with 4GB of Discrete Video Memory.

Currently have VideoSetupID=17 - Is this correct for my video card?
Title: Re: inside the CONF.INI
Post by: Epervier on November 06, 2015, 02:23:48 PM
Yes !
This is the best solution!
Title: Re: inside the CONF.INI
Post by: KevinHoggard on November 06, 2015, 02:26:58 PM
Thank you
Title: Re: inside the CONF.INI
Post by: Crazy G on November 23, 2015, 09:23:23 AM
UIColor=0
Changes user Interface Color. Can be 0 to 5

0 - Blue
1 - Grey
2 -
3 -
4 -
5 - Clear/Opaque

UIDetail=0
Changes User Interface Detail. Can be 0 to 5

0 -
1 -
2 -
3 -
4 -
5 -

UIBackground=rnd
This is the background image. There are 5 options available

en - English/American Image
ru - Russian Image
de - German Image
jp - Japanese Image
rnd - Random Image of the four above.

UIColor, UIDetail, and UIBackground can be set using the User Interface in the Setup area of the sim.
Setup>Misc Settings>User Interface

Use3RendersUI=0
Title: Re: inside the CONF.INI
Post by: rruff on November 26, 2015, 09:55:45 AM
Have a question regarding the Video Setup ID, I'm running a NVIDIA® GeForce® GTX745 Graphics with 4GB of Discrete Video Memory.

Currently have VideoSetupID=17 - Is this correct for my video card?

You also want to make sure to use Nvidia Inspector to include AA settings for the game. Gets rid of the jaggies around the edges and looks much better!
Title: Re: inside the CONF.INI
Post by: spartan18a on November 27, 2015, 09:57:41 AM
It seems that I see the objects much later than my squadron mates. For example last night, we were crossing the English Channel and when someone said the French coast was at 12 o´clock, I couldn´t see anything. It took some minutes until I saw it myself.
I have an Nvidia GTX 970 Gaming G1. Why can´t I see the objects as soon as the rest??  o_O

Thanks

[Render_OpenGL]
TexQual=3
TexMipFilter=1
TexCompress=0
TexFlags.UseDither=1
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=1
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=1
TexFlags.UseVertexArrays=1
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=1
TexFlags.ClipHintExt=0
TexFlags.UsePaletteExt=0
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=1

TexFlags.TexEnvCombine4NV=1
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=1
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=1

HardwareShaders=1

Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=2
LandShading=3
LandDetails=2

LandGeom=2
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Water=4
Effects=2
ForceShaders1x=0

PolygonOffsetFactor=-1.00
PolygonOffsetUnits=-10.0
Title: Re: inside the CONF.INI
Post by: PA_Willy on November 27, 2015, 10:52:59 AM
aGAIN:

LandGeom=2 --> 3
Title: Re: inside the CONF.INI
Post by: spartan18a on November 27, 2015, 01:07:18 PM
Thanks buddy, I didn't see your other answer in our forum. I wasn't at home. :)
But now surely more people was helped by you  ;)
Title: Re: inside the CONF.INI
Post by: rruff on November 29, 2015, 10:02:57 AM
It seems that I see the objects much later than my squadron mates. For example last night, we were crossing the English Channel and when someone said the French coast was at 12 o´clock, I couldn´t see anything. It took some minutes until I saw it myself.
I have an Nvidia GTX 970 Gaming G1. Why can´t I see the objects as soon as the rest??

Make sure you are using the highest settings in conf.ini and also use Nvidia Inspector to improve AF (anisotropic filtering) and AA (anti aliasing). Search for it on this forum. The higher end Nvidia cards also have something called Dynamic Super Resolution. That may be better than jacking up the AA.
Title: Re: inside the CONF.INI
Post by: b9flyer on May 21, 2016, 11:08:50 AM
Storebror, I've used your conf.ini update - what an unbelievable change to the aircraft et al. I can even access Hamm66s Lancaster campaign which wouldn't load before.

Another brilliant job by the team - many thanks.
Title: Re: inside the CONF.INI
Post by: adambegg on August 07, 2017, 05:17:55 AM
Is it possible for Il-2 to ignore the conf.ini?  Currently whenever I start it it uses the settings in the "Il-2 Settings" program, and then if I try to change the resolution in-game the whole thing crashes as soon as I try to exit the video settings.

Does this sound familiar to anyone?
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on August 07, 2017, 05:46:25 AM
IL-2 will not and cannot ignore the conf.ini.
It can happen however that it cannot write settings back to conf.ini, e.g. when your game is installed inside the "Program Files" folder tree and you don't run IL-2 with administrative rights.
Furthermore there are situations when the ingame resolution change fails, e.g. sometimes when you try to switch between scaled fullscreen and unscaled windowed modes.

Either case, the logfile would tell us more.

Best regards - Mike
Title: Re: inside the CONF.INI
Post by: adambegg on August 09, 2017, 03:19:01 AM
Oh yes, of course.  I re-installed Il-2 for the first time in quite a while and totally forgot about moving it out of program files.  My bad.

Thanks for the reminder!
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on August 09, 2017, 03:22:01 AM
Happens to all of us, glad you got it sorted :)

Cheers!
Mike
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on November 08, 2017, 04:01:30 AM
For the sake of completeness, in case you happen to be bound to use you CPU's integrated "Intel HD" graphics (whatever version of Intel HD you have), you will not get happy with using OpenGL as the Intel drivers are buggy, so you have to switch to DirectX.

Switching to DirectX means that you have no access to the so called "Perfect Mode" like OpenGL users do.
Your game will look worse than it does for users with a dedicated graphics card.
CPU integrated Intel HD graphics are not designed for gaming.
Just saying...

In order to switch to DirectX, please edit your conf.ini file as follows:

Code: [Select]
[window]
ColourBits=32
DepthBits=24
StencilBits=8
Code: [Select]
[GLPROVIDER]
GL=dx8wrap.dll
Code: [Select]
[game]
TypeClouds=1

Now comes the most important section for DirectX users, "Render_DirectX".
While I don't have such thing like "recommended" settings, these are settings tested by myself, working well on an Intel Core i5-3210M laptop with Intel HD 4000 graphics:
Code: [Select]
[Render_DirectX]
TexQual=3
TexMipFilter=1
TexCompress=2
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=1
TexFlags.PolygonStipple=1
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.UseVertexArrays=1
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=1
TexFlags.ClipHintExt=1
TexFlags.UsePaletteExt=1
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=1

TexFlags.TexEnvCombine4NV=1
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=1
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=1

HardwareShaders=0

Shadows=1
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=2
LandShading=0
LandDetails=2

LandGeom=2
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Water=2
Effects=1
ForceShaders1x=0
PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0

Hope that helps.
Best regards - Mike
Title: Re: inside the CONF.INI
Post by: KG3_V on November 20, 2017, 10:22:43 AM
I also need some advice for graphic settings
if i change the graphics ingame the game crashes

I tested the Midway map and there are some kind of green patches around the islands . i havnt played il2 for a long time so maybe its normal. also far moutains in some maps really look ugly

GC is a GTX 970

Must i use open gl or dx ?
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on November 20, 2017, 11:04:27 AM
Green patches around islands indicate that your PC is using the CPU's integrated graphics in OpenGL mode.
Make sure you really use your GTX 970 with IL-2.
Perfect settings have been discussed on page 2 of this thread.
I'm using a GTX 970 myself. It works.

Best regards - Mike
Title: Re: inside the CONF.INI
Post by: KG3_V on November 20, 2017, 11:40:55 AM
how do i change the gpu ??
Title: Re: inside the CONF.INI
Post by: KG3_V on November 20, 2017, 12:03:11 PM
It looks like this now

https://imgur.com/a/M8UNW
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on November 20, 2017, 10:22:45 PM
Atolls with green patches, what's wrong with that?
(https://s2.postimg.cc/wxtphzld5/atoll_in_maldives.jpg)

The 109 image looks like your Nvidia Settings could use some fine tuning to give better anti aliasing results.
These have been my settings on the 970 before I switched to a G-Sync Monitor:

Anisotropic Filtering =16x
Antialiasing - FXAA = Off
Antialiasing - Gamma Correction = On
Antialiasing - Mode = Override any application settings
Antialiasing-Setting = 8x
Antialiasing-Transparency = 2x (Supersample)
CUDS - GPUs = Use global setting (All)
Maximum pre-rendered frames = Use 3D Application settings
Multi-display/mixed GPU acceleration = Single display performance mode
Power management mode = Prefer Maximum Performance
Multi-Frame Sampled AA (MFAA) = On
Texture filtering - Anisotropic sample optimization = Off
Texture filtering - Negative LOD bias = Allow
Texture filtering - Quality = High quality
Texture filtering - Trilinear optimization = Off
Threaded optimization = Auto
Triple Buffering = On
Vertical sync = Fast

Best regards - Mike
Title: Re: inside the CONF.INI
Post by: KG3_V on November 21, 2017, 03:01:35 AM
Thank you, will try it now
the Screenshot from where after change settings, the green dots before look much brighter and "comic like

i have changed the opengl cpu in the nvidia control center to gtx 970, i hope this forces the game to use the card

in the normal Il2 config program i have selected the highest Nvidia card available in the settings
Title: Re: inside the CONF.INI
Post by: KG3_V on November 21, 2017, 01:39:30 PM
Everything works now but i have still one problem, somekind of strange looking sky, which even hurts the eyes. its hard to explain but it feels like watching a 3d movie without the glasses. i have tried the optional default skys but the problems is also there
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on November 21, 2017, 10:19:58 PM
Screenshot?
Title: Re: inside the CONF.INI
Post by: KG3_V on November 22, 2017, 05:19:37 AM
https://imgur.com/a/vnrtj
Title: Re: inside the CONF.INI
Post by: Mick on November 22, 2017, 05:44:27 AM
... may be I urgently need to go and see an ophtalmologist, but I can't see anything wrong in your sky screens ...  o_O
Title: Re: inside the CONF.INI
Post by: KG3_V on November 22, 2017, 06:19:30 AM
It is hard to explain. the somehow look weird to me. the colours or something really hurt the eyes on some maps. maybe it is this way. the only way i can explained it is that for it is the same feeling of taking of the googles during a 3d movie
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on November 22, 2017, 06:44:10 AM
Monitor trouble?
The skies look just fine.
Title: Re: inside the CONF.INI
Post by: taraboulba on March 31, 2018, 12:30:55 AM
Hello Everybody!

I was looking to improve my graphics, then I made a search and I found this incredible thread. All I needed is there from conf.ini to graphic card tuning.
As usual on SAS, it's clear, detailed and kindly explained!
Thanks, thanks a lot to all contributors!

Best regards,
Tara

Title: Re: inside the CONF.INI
Post by: KG3_V on June 29, 2018, 03:51:39 AM
I am now back playing. the only problem i seem to have is a lot of sudden pop up of buildings and trees. maybe it was always this way, i dont remember. i used the settings for ultra in the config ini for nvidia cards
Title: Re: inside the CONF.INI
Post by: j.vandeinsen on August 15, 2018, 06:49:37 AM
Hi,

I just wanted to post a quick thank you for this. Because i am rather new to this game and all the modding that comes with it. But you guys are posting some great stuff that really got me going.
Hell, there is not a problem that i could not fix with the information provided.

So thank you guys ever so much for the time, effort and clear explanations.

It is much appreciated.
 
Title: Re: inside the CONF.INI
Post by: Kiwi on December 01, 2018, 05:54:08 PM
Is there particular setting that is really CPU intensive?
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on December 02, 2018, 01:24:05 AM
No.
Title: Re: inside the CONF.INI
Post by: Blaubaer on January 27, 2019, 12:53:47 PM
Quote
[game]
...
viewSet=32
Snap view -Even number. Pan view Odd number.
...
I did not understand what the parameter does. Can anyone explain it to me?

Regards, Michael
Title: Re: inside the CONF.INI
Post by: macgiver on January 27, 2019, 01:17:47 PM
I did not understand what the parameter does. Can anyone explain it to me?

Look at your "SNAP VIEW" and "PAN VIEW" commands, try "Toggle Snap/Pan View" (F9 by default) and you will see the difference.
Title: Re: inside the CONF.INI
Post by: Blaubaer on January 27, 2019, 02:34:24 PM
 "Toggle Snap/Pan View" - nothing changes while toggling. Nothing to be seen.  :(
Title: Re: inside the CONF.INI
Post by: macgiver on January 27, 2019, 03:29:57 PM
These are commands for switching views with the keyboard, if for example you look up in SNAP mode when you press the button the view moves in programmed direction and when you release it returns to the central view (forward). If you switch to PAN mode when you press the button for example "pan view up" view rises 45° and stays in this position, if you press again view go up next 45° and stay looking at the vertical (90°), to look forward again, you have to press "center view" button. We could say that SNAP is for quick glances like in combat and PAN to control the sky during normal flight. This is already history, I think that today everyone flies with "Track" or emulate mouse with hat or change the view with hat...
Title: Re: inside the CONF.INI
Post by: Blaubaer on January 27, 2019, 03:36:24 PM
Quote
today everyone flies with "Track" or
Like me.
What does viewset= mean to me then?

Title: Re: inside the CONF.INI
Post by: macgiver on January 27, 2019, 04:01:03 PM
For me that's what I said in this thread: https://www.sas1946.com/main/index.php/topic,60398.msg665767.html#msg665767 (https://www.sas1946.com/main/index.php/topic,60398.msg665767.html#msg665767)
Title: Re: inside the CONF.INI
Post by: Sebtoombs on October 02, 2020, 09:36:58 AM
Thank you really helpful post all round!
Title: Re: inside the CONF.INI
Post by: 221teddy on May 23, 2021, 12:45:24 PM
Just for reference, these are the required settings for absolutely maxed out graphics in IL-2:

Please check the sections and settings as described below, usually all mentioned parameters should be in your conf.ini already, so you just have to change them accordingly.

All type of cards:

..............


Hi SAS~Storebror,

this recommendation in post #5 is now 10 years old. Therefore my question: are these recomendations still valid, up to date, and comprehensive for the current mods like VP mod or BAT mod? Or are there  new developments/new features (e.g. effects=2) to be considered in order to improve further the graphical quality? I think this information or a new summary table might also be interesting for other IL-2 dummies like me.

Teddy
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on May 24, 2021, 01:00:11 AM
It's still valid.
Title: Re: inside the CONF.INI
Post by: 221teddy on May 28, 2021, 11:27:59 AM
What's the impact of "effects=2" in the [RenderOpenGL] part of the conf.ini onto the graphic's quality? My impression is: no impact at all. But the impact onto the fps rate may be severe when it comes to scenes limited not by the GPU but by the CPU performance (multiple heavy explosions, severe smoke and fire etc.). Can someone comment on this?

Teddy
Title: Re: inside the CONF.INI
Post by: SAS~Storebror on May 28, 2021, 10:41:35 PM
In scenes where you don't see no impact, there is no performance impact either.
If there is a performance impact (and yes, there is... mainly when there's lots of smoke around), then there is a visual quality difference as well, but honestly it's not worth it.
From my own experience, the single thing I notice most between effects=1 and effects=2 is the presence and/or quality of smoke shadows.

]cheers[
Mike