Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Autopilot101]

Has the CUP WAW module ever been optimized? I stopped updating CUP on the WAW part12 and MME part10 due awful FPS issues and I was wondering if it was worth checking since playing with 16 FPS isnt exactly comfortable, compared to the 25 FPS HSFX give me on the same conditions.

[sniperton]

1. Yes, it has been optimized, and you have some extra JSGME options to customize effects and reduce the demand on your computer;
2. Considering the greatly increased amount of content (maps, planes, objects) compared to HSFX, that 40% FPS loss is proportional.
3. 25 FPS in HSFX is just not normal. You either have a much weaker rig than mine (what I don't believe), or your system is not optimized. Reduce resolution and/or effect settings until you have a stable 40+ FPS in HSFX.
4. On low-end PCs (like mine) running WAW with reduced planesets ('lightened air.ini') makes wonders. You can create one for PTO, one for MTO, one for ETO, and switch between them via JSGME.

[Autopilot101]

1-2 I'll try updating it then, though I dont have much hope for good fps.
3- During the missions I get mostly 40fps or so, but the smoke effects after the explosions cripple the fps with both, the default effects and the ones included in HSFX. Other than that its pretty stable.
4- About the lightened air.ini, I've seen it stickied but it was outdated. I've tried to make some changes on my own but I dont remember if it caused a CTD or if the improvement was minimal. Maybe I should try it again once I download the updates.

As for my PC, the processor is a FX 6100 OC'd to 3.8GHz and the GPU is a Radeon HD 6850. Sadly this processor isn't very good at single core processing, so this game suffers from it. Before someone suggest to try without OC, I've done it already. Thanks for the reply sniperton.

[Chupacabras84]

4- About the lightened air.ini, I've seen it stickied but it was outdated.

Its not outdated per se, in short, lightened air.ini reduces number of aircrafts loaded and with that comes improved performance.
Now why its stuck at WaW part 8? Because with number of objects in WaW 8, its pretty much reached limit of how many planes you can have while still keeping performance like its a stock game, at least on my PC (This thing is PC dependant apparently).

After WaW part 8, there are too many objects added to make this ini work, therefore, if you udpate WaW past part 8 you wont get any performance gains with lightened air.ini.
At some point I was hoping to get back to it and see what else I can do to make performance better past  WaW 8 but currently i am very busy and dont have time.

[sniperton]

@Chupa, following your idea I made a small utility which makes air.ini customization a little bit easier.

It's uploaded to mission4today: http://www.mission4today.com/index.php?name=Downloads3&file=details&id=2292

@Autopilot, my rig is much weaker than yours; give it a try with these settings:

Code: [Select]

[il2]
title=Il2-Sturmovik Forgotten Battles
hotkeys=HotKey game
;p optimized CUP

[window]
width=1600
height=900
;width=1280
;height=720
ColourBits=32
DepthBits=24
StencilBits=8
ChangeScreenRes=1
FullScreen=1
DrawIfNotFocused=0
EnableResize=0
EnableClose=0
SaveAspect=0
Use3Renders=0
EnableClose=0
WideScreenFoV=1
UIColor=4
UIDetail=0
UIBackground=rnd
Use3RendersUI=0

...

[Render_OpenGL]
TexQual=3
TexMipFilter=2
TexCompress=2
TexFlags.UseDither=0
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=0
TexFlags.UseClampedSprites=1
TexFlags.DrawLandByTriangles=1
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=0
TexFlags.TexCompressARBExt=1

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

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

LandGeom=2
TexLarge=1
TexLandQual=2
TexLandLarge=0

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

[Chupacabras84]

which makes air.ini customization a little bit easier.

Good idea, although for me notepad++ is still faster and more convenient, mainly because I took fairly automated way when creating and modifying air.ini files.

If you want to improve it, one of the thing you can add are presets to enable/disable planes by country/year/prototypes/training/etc.
Shift+click/Ctrl+Click highlighting to bulk enable disable planes.

[sniperton]

If you want to improve it, one of the thing you can add are presets to enable/disable planes by country/year/prototypes/training/etc.

It's on my list, but I'm reluctant to hand-create an additional plane database to make it work properly. Possibly I'll implement it as a side-feature into my DCG database editor tool in a way that if you create a 3rd party campaign with a reduced planeset, it will also create a corresponding air.ini as JSGME mod.

[Chupacabras84]

I'm reluctant to hand-create an additional plane database to make it work properly.

Probably the easiest and fastest thing but it requires some knowledge of notepad++ and open office because it uses automatic procedure to create the list of aircraft's you want fast and easy.

Can you share src of your prog?
Wanna see how you went about it maybe I could try and mess with it if I find a free minute.

[sniperton]

What I mean is that for such 'automatic' presets I need availability dates for each country that had the plane in service; these data cannot be taken out from either air.ini or plane.properties. So the problem is that someone first has to create those presets (as you did with #8 and as I do for myself for #20), then their 'implementation' is rather easy: the 'reload JSGME mod' function is exactly for that purpose.

One thing I can do is to add slots for alternate air.inis, so that if the program starts with some air_#.inis available in its folder, those files also pop up as options on startup. But that would be not much different than reloading a JSGME mod folder.

Anyway, if you wish, I can upload or send you over the free pascal source files (though it may take a bit of time to put in comments to make clear what does what)

[Chupacabras84]

Anyway, if you wish, I can upload or send you over the free pascal source files (though it may take a bit of time to put in comments to make clear what does what)

Sure, there is no haste so take it easy 

[Autopilot101]

@Sniperton: Tried the settings you posted with both mods, for comparison purposes. CUP got no real FPS difference, stuck with 16fps. HSFX went from 25-26 to 27-28. Im using the 109 N4 single mission as benchmark without moving the camera at all nor taking off, just adjusting the FOV to 85. It seems like something quick enough for testing.

@Chupacabras: I remember you posted something like that on the sticky thread. Anyway, tested WaW part8 with the lightened air.ini. On the previously mentioned mission, the FPS went from 16 to 17-18. The result is rather underwhelming.

[JG7_X_Man]

Has the CUP WAW module ever been optimized? I stopped updating CUP on the WAW part12 and MME part10 due awful FPS issues and I was wondering if it was worth checking since playing with 16 FPS isnt exactly comfortable, compared to the 25 FPS HSFX give me on the same conditions.

I had this exact same issue as well - imagine my dissolution with my system getting 15 fps:

I7-4790K 4.0GHz OC'ed @ 2.7GHz (Water 3.0 Ultimate cooler)+ Nvidia GTX 970 + 1TB SSD (dedicated to IL-2)+Win 7 SP1 (OS installed on 500GB SSD)

So it turns out, not following the CUP install instructions correctly (which included a clean install) killed my FPS - even with my system. Following the instructions to the "T" got me up to my regular 60 FPS pre-CUP install.

Because I have the space I opted for the individual WaW, and JTW install so I don't know how well the "lightened air.ini" works