I have a new computer and I was asking myself....

[Sid]

Originally Posted by Feuerfalke

Hi Oktober!

Water=1
Effects=1
3DBridges=1

TypeClouds=1

PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0

~S~ Feuerfalke

Where did you find 3Dbridges and what does it do?

[Feuerfalke]

Originally Posted by Sid

~S~ Feuerfalke

Where did you find 3Dbridges and what does it do?

That's in my ini since the original IL2-days IIRC. I read it somewhere at that time and just copy'n'pasted it into the newer versions. I don't know if it makes any difference at all, but it didn't do any harm either, so I guess that's why it survived.

[Sid]

Ah, thought I didn't recognise it.....thanks for coming back

[TheFamilyMan]

Try setting this in your conf.ini:

ProcessAffinityMask=2

This tells windows to run IL-2 only on core 1. For AMD dual core processors, this can make a considerable difference. I run an ancient 939 4200+ X2 @ 2.64G; if I don't use this setting my display occasionally freezes for a second or so (usually upon encountering a combat situation ), and if something explodes, the FPS goes to down to about 3 for a second or so. Good Luck!

[Feuerfalke]

The problem with "ProcessAffinityMask=2" is, that IL2 was not built to use multiple cores and therefore it can cause stutters to run IL2 on 2 cores. I rather recommend assigning IL2 to one core, Teamspeak, TrackIR and other programs you need, to the second. That solved a lot of microstutters for me, but you should try that one out yourself, as it probably really depends on the system configuration.

[TheFamilyMan]

Originally Posted by Feuerfalke

The problem with "ProcessAffinityMask=2" is, that IL2 was not built to use multiple cores and therefore it can cause stutters to run IL2 on 2 cores. I rather recommend assigning IL2 to one core, Teamspeak, TrackIR and other programs you need, to the second. That solved a lot of microstutters for me, but you should try that one out yourself, as it probably really depends on the system configuration.

There is so much confusion over the use of ProcessAffinityMask. As its name implies, its value is a mask (or more specificly a bit mask), which means the following: each bit of the value specifies a cpu (core) to be used. A value of 1 means only use CPU 0, a value of 2 means only use CPU1, a value of 3 means only use CPU0 & CPU1, a value of 4 means only use CPU2, a value of 5 means only use CPU0 & CPU2, and so on. For more info on what is going on here, do a wikipedia on binary numbers. Enjoy!

Unfortunately, if the affinity mask is not specified (the default for conf.ini), windows will run the program on all available cpus which can cause problems for IL-2.

[Oktoberfest]

Ow..... I don't want to have it so complicated !!!

[Bobby109]

Look at the black death track and see what average fps you get