• September 28, 2022, 05:08:02 PM
• Welcome, Guest

Pages: [1] 2 3 4 ... 9   Go Down

### AuthorTopic: inside the CONF.INI  (Read 156946 times)

0 Members and 1 Guest are viewing this topic.

#### michel_boonstra1974

• Modder
• member
• Offline
• Posts: 201
• Veteran of the spin and mole expert.
##### inside the CONF.INI
« 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..

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.

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=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"

Receiver of the message "0" (all)

msg1 =
Contents of the message "1"

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

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

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.

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 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

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

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

SoundFlags.reversestereo=0

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

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.

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.

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

Must be 1 to activate Perfect mode.

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
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
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.

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

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
Logged

#### Verhängnis

• Unofficial Heinkel Fan
• Modder
• member
• Offline
• Posts: 1494
##### Re: inside the CONFIG.INI
« Reply #1 on: December 11, 2010, 07:11:31 PM »

Interesting..Nice find.
Logged

#### PO_MAK_249RIP

• CMON U SPURS!
• member
• Offline
• Posts: 1969
##### Re: inside the CONFIG.INI
« Reply #2 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?
Logged
Corsair Carbide case, Intel core i5 4690 3.5ghz with Arctic Cooler, Asus Rock H97 performance, Gainward windforce OC GTX 960 2GB, 8GB Corsair Vengeance 1600mhz, 256GB/500GB Crucial SSDs, Windows 10 64bit.

#### asheshouse

• SAS Team
• member
• Offline
• Posts: 3259
##### Re: inside the CONFIG.INI
« Reply #3 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
Logged

#### Mick

• Modder
• member
• Offline
• Posts: 4774
##### Re: inside the CONFIG.INI
« Reply #4 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
Logged

#### SAS~Storebror

• retired
• SAS Honourable Member
• member
• Offline
• Posts: 21872
• Taking a timeout
##### Re: inside the CONF.INI
« Reply #5 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=32DepthBits=24StencilBits=8
Code: [Select]
[GLPROVIDER]GL=Opengl32.dll
Code: [Select]
[game]TypeClouds=1
Code: [Select]
[Render_OpenGL]TexQual=3TexMipFilter=3TexCompress=0TexFlags.UseDither=0TexFlags.UseAlpha=0TexFlags.UseIndex=0TexFlags.PolygonStipple=1TexFlags.UseClampedSprites=0TexFlags.DrawLandByTriangles=0TexFlags.DisableAPIExtensions=0TexFlags.ARBMultitextureExt=1TexFlags.TexEnvCombineExt=1TexFlags.SecondaryColorExt=1TexFlags.ClipHintExt=1TexFlags.UsePaletteExt=1TexFlags.TexAnisotropicExt=1TexFlags.TexCompressARBExt=0TexFlags.TexEnvCombineDot3=1TexFlags.SeparateSpecular=1HardwareShaders=1Shadows=2Specular=2SpecularLight=2DiffuseLight=2DynamicalLights=1MeshDetail=2VisibilityDistance=3Sky=2Forest=3LandShading=3LandDetails=2LandGeom=3TexLarge=1TexLandQual=3TexLandLarge=1VideoSetupId=17Effects=1ForceShaders1x=0PolygonOffsetFactor=-0.0625PolygonOffsetUnits=-1.0
For AMD cards:
Code: [Select]
TexFlags.UseVertexArrays=0TexFlags.VertexArrayExt=0TexFlags.TexEnvCombine4NV=0TexFlags.DepthClampNV=0TexFlags.TextureShaderNV=0Water=2
For Nvidia cards:
Code: [Select]
TexFlags.UseVertexArrays=1TexFlags.VertexArrayExt=1TexFlags.TexEnvCombine4NV=1TexFlags.DepthClampNV=1TexFlags.TextureShaderNV=1Water=4
For quick copy&paste action, the whole [Render_OpenGL] section for AMD cards:
Code: [Select]
[Render_OpenGL]TexQual=3TexMipFilter=3TexCompress=0TexFlags.UseDither=0TexFlags.UseAlpha=0TexFlags.UseIndex=0TexFlags.PolygonStipple=1TexFlags.UseClampedSprites=0TexFlags.DrawLandByTriangles=0TexFlags.UseVertexArrays=0TexFlags.DisableAPIExtensions=0TexFlags.ARBMultitextureExt=1TexFlags.TexEnvCombineExt=1TexFlags.SecondaryColorExt=1TexFlags.VertexArrayExt=0TexFlags.ClipHintExt=1TexFlags.UsePaletteExt=1TexFlags.TexAnisotropicExt=1TexFlags.TexCompressARBExt=0TexFlags.TexEnvCombine4NV=0TexFlags.TexEnvCombineDot3=1TexFlags.DepthClampNV=0TexFlags.SeparateSpecular=1TexFlags.TextureShaderNV=0HardwareShaders=1Shadows=2Specular=2SpecularLight=2DiffuseLight=2DynamicalLights=1MeshDetail=2VisibilityDistance=3Sky=2Forest=3LandShading=3LandDetails=2LandGeom=3TexLarge=1TexLandQual=3TexLandLarge=1VideoSetupId=17Water=2Effects=1ForceShaders1x=0PolygonOffsetFactor=-0.0625PolygonOffsetUnits=-1.0
And the same thing, whole [Render_OpenGL] section, this time for Nvidia cards:
Code: [Select]
[Render_OpenGL]TexQual=3TexMipFilter=3TexCompress=0TexFlags.UseDither=0TexFlags.UseAlpha=0TexFlags.UseIndex=0TexFlags.PolygonStipple=1TexFlags.UseClampedSprites=0TexFlags.DrawLandByTriangles=0TexFlags.UseVertexArrays=1TexFlags.DisableAPIExtensions=0TexFlags.ARBMultitextureExt=1TexFlags.TexEnvCombineExt=1TexFlags.SecondaryColorExt=1TexFlags.VertexArrayExt=1TexFlags.ClipHintExt=1TexFlags.UsePaletteExt=1TexFlags.TexAnisotropicExt=1TexFlags.TexCompressARBExt=0TexFlags.TexEnvCombine4NV=1TexFlags.TexEnvCombineDot3=1TexFlags.DepthClampNV=1TexFlags.SeparateSpecular=1TexFlags.TextureShaderNV=1HardwareShaders=1Shadows=2Specular=2SpecularLight=2DiffuseLight=2DynamicalLights=1MeshDetail=2VisibilityDistance=3Sky=2Forest=3LandShading=3LandDetails=2LandGeom=3TexLarge=1TexLandQual=3TexLandLarge=1VideoSetupId=17Water=4Effects=1ForceShaders1x=0PolygonOffsetFactor=-0.0625PolygonOffsetUnits=-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
Logged
You live, you learn, you love, you're dead.

#### wingflyr

• Modder
• member
• Offline
• Posts: 215
##### Re: inside the CONF.INI
« Reply #6 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.
Logged

#### LuseKofte

• member
• Offline
• Posts: 6911
##### Re: inside the CONF.INI
« Reply #7 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
Logged

#### SAS~Storebror

• retired
• SAS Honourable Member
• member
• Offline
• Posts: 21872
• Taking a timeout
##### Re: inside the CONF.INI
« Reply #8 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=1This 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:
please set the following two parameters as follows:
Code: [Select]
[Render_OpenGL]TexCompress=2TexFlags.TexCompressARBExt=1This 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
Logged
You live, you learn, you love, you're dead.

#### hguderian

• Modder
• member
• Offline
• Posts: 1130
##### Re: inside the CONF.INI
« Reply #9 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
Logged

#### SAS~Storebror

• retired
• SAS Honourable Member
• member
• Offline
• Posts: 21872
• Taking a timeout
##### Re: inside the CONF.INI
« Reply #10 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
Logged
You live, you learn, you love, you're dead.

#### Silverback

• member
• Offline
• Posts: 146
##### Re: inside the CONF.INI
« Reply #11 on: July 16, 2011, 11:46:55 AM »

Try it and see for yourself, can't hurt.
Logged
Pages: [1] 2 3 4 ... 9   Go Up

Page created in 0.051 seconds with 28 queries.