Official Fulqrum Publishing forum - How to patch the sim and update your .ini files (if you have the old ones).

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)

- Technical threads (http://forum.fulqrumpublishing.com/forumdisplay.php?f=191)

- - How to patch the sim and update your .ini files (if you have the old ones). (http://forum.fulqrumpublishing.com/showthread.php?t=23971)

How to patch the sim and update your .ini files (if you have the old ones).

I spend most of my time testing stuff instead of actually flying the sim and i occasionally come up with some worthwhile stuff that might be beneficial to others.

I got a lot of positive reaction about this subject when posting it on another thread, along with fears that it will get buried among other posts, so i took the liberty of re-posting it here on its own thread.

You can also find it hosted on airwarfare.com and i thank Gamekeeper for copying whatever posts of mine he finds useful over there, as the more visible some fixes are the more typing time it saves me (i don't have to retype every solution as much if more people know about it) to actually fly instead of just test things out :-P

First of all, a small note on the issue of the .ini files: If you have download your copy from Steam after the previous official patch was applied (around the end of May i think it was), then most probably you have the new configuration files. If you have installed the sim earlier than May or had Steam apply at least one official patch before the June 21st beta patch, then it's possible that your installation has the old config files.

You can just uninstall and download the whole thing again from Steam if you find the instructions confusing, but they are pretty simple and they will save you time (and bandwidth, if you are not on a unlimited bandwidth ISP package).

So, let's get to it then!

This is the Install, Patching, Repair & Backup section of Airwarfare.com where you can also find other useful guides: http://airwarfare.com/sow/index.php?...=66&Itemid=156

And this is my original post:

Quote:

Originally Posted by Blackdog_kt (Post 300307)

Just had a very small test and will keep flying during the night to see if there's any gameplay-issue improvements (Ju88 gyrocompass, bomb release joystick buttons working from bombardier's seat, etc).

I got my first launcher.exe crash today but i fixed it simply by restarting the sim, it plays the same as before (smooth on mostly medium settings on my 2 year old PC:i7 920, Ati 4890 1GB and 3GB of RAM, win7 64 bit) and everything looks good in regards to FPS, i even bumped one of my low settings to medium.

I also had to get the new .ini files (i didn't do it in the previous patch) that do away with a lot of redundant fields. I prefer to get everything in a working order first so i can actually test stuff, instead of having preventable errors give me "false alarms". There is by now a standard routine i do and every patch has been an improvement for me.

First, how to get the new .ini files (the configuration files). If you have only recently downloaded your copy from Steam you probably don't need to do this, i had mine installed early though so i had to change them:

1) Launch the sim, go to controls and select "save as", then tell it to save an .ini file somewhere you can easily find it. I had actually done this a long time ago, saving a "mycontrols.ini" file in my documents folder.

2) Go to documents\1c softclub folder and move the files conf.ini, confs.ini, confuser.ini to a backup folder.

3) Do the same for the files of the same name in steam\steamapps\common\IL-2 sturmovik cliffs of dover, moving them to their own backup folder.

4) Run the steam file verification tool . This will spot you are missing the .ini files (since you moved them to another location) and download the new ones. I have opened and compared the old and new files and their structure is different, so i can confirm this will give you the new files without having to mess with steam cloud settings, just keep the cloud thing off altogether.

5) Probably all your settings have now been reset. Go to controls and load the .ini file containing your previously saved control bindings, then click on the apply button. In my case it happened to keep them stored anyway. My realism settings and graphics options had also been reset so i had to reselect them and i think my transparent on-screen windows also changed so i'll have to customize them again. All in all it's less than 5 minutes of work for a cleaner, leaner config file structure so it's worth it.

I don't know if all this affects single-player career progress but i think it doesn't: i accidentally skipped a mission once and i manually edited another file to revert back to the previous "step" in the campaign but it was a completely different file, so i don't think campaign progress has been affected.

6) EXIT THE SIM. This is probably why i got a launcher crash the first time around (i had just applied the beta patch too, further complicating things) i didn't exit after changing graphics options and tried to fly a mission right away. Next time i just changed settings, restarted the sim and all was fine. It's generally a good habit to restart the sim when changing graphics options.

To get the beta patch up and running:

1) Assuming you have up to date .ini files keep reading, otherwise follow the above routine first.

2) Even if you have current .ini files, make sure you are as close to a stock installation as possible. I run with no mods (i am waiting for the SDK first) so it's relatively easy. I just backup anything i might want to keep or fear i might lose (mainly my controls settings), then run the Steam file verification tool.

3) Extract the beta patch file into the main game folder (steam\steamapps\common\IL-2 sturmovik cliffs of dover) and let it over-write anything it asks you to.

4) Go to documents\1c softclub\cache, select everything under that folder and delete it. This forces the sim to rebuild the shader cache and will prevent problems with graphic glitches and/or FPS that may be caused by running a newer version with cached shaders of a previous version.

Please do this before claiming visual bugs, reduced performance, etc, as it helps A LOT: i've never had degraded performance ever, every new patch is smoother than the last and i'm running a two year old PC.

This cache clean-up happens automatically when you install a live, official patch from Steam but i'm not sure if it happens with beta patches, so i do it manually just to be sure.

5) Start flying :-P

When the patch goes live on Steam:
1) Either revert to the previous version by using the file verification tool, or just patch on top of the beta one.

2) Clear your cache

3) Go flying :cool:

I hope it helps some of the people having problems, it's been immensely helpful for me so i thought i'd pass it on.

Important Edit: Whatever you can test OFFLINE, do so. It's perfectly possible to join a server running a previous version when you are running a newer version beta patch and this will give you all sorts of glitches. You might be able to join but that doesn't mean the two versions are always compatible with each other. Luthier himself said so in one of the previous updates. So, test the aircraft behavior offline and when you go online to test multiplayer specific issues, make sure the server is also running the same version as you are.

Bug reports from multiplayer are pretty much worthless if the server and client are not running the same version. It's also why i don't go online yet, i spend most of my time not flying/playing the sim but testing, bug-hunting and compiling a FAQ for when the US release happens to help get people up to speed fast, so i don't want to have all kinds of "false alarms" caused by incompatible versions and/or mods when trying to see what works, what doesn't and how i can work around any remaining issues.

I would urge everyone who is having problems to try this out. I'm not claiming it will work for everyone, but a couple users already reported better results and so i guess it's no harm to try it.

It is also useful for another reason that TUSA/TX-Gunslinger pointed out: if we follow a more or less standardized way of updating our sim, it's much more probable that our individual installations will be on the same page.

This makes for a greater commonality among the user base and eliminating problems that might simply be setup/installation issues and not directly problems of the underlying code. For example, a lot of bugs (especially display/graphics bugs) and even launcher.exe crashes can be prevented by forcing a rebuild of the shader cache when updating to a new version.

If we can prevent these bugs we can not only enjoy a better simming experience, but we can also spot the true bugs in an easier manner and report them to the developer team for fixing.

Feel free to try this out, copy it on your fansite, sticky it, etc: the more visibility it has the less likely it is i'll have to retype it sometime down the road when another user is having troubles with updating or getting preventable bugs :-P

Hope it gets at least some people who are facing problems up and running ;)

Hi Blackdog_kt,

thank you very much for these very important notes. I have done as you suggested.
My fault is/was that i never updated the ini files in the steam application.

I have done it every time in 1C folder.

Thank you again

Cheers

LC

Hi Blackdog_kt

Im going to give this a whirl, i am getting some stutters after installing this patch so hopefully if i do it this way, it will help:cool:. Do i need to have my steam cloud on to get the patch from steam or do's it still work without?

Thanks S!

This is a peice of great advice, I have been through the files and they are quite different from previous ones, only problem I am having with this and the last patch is I cant save or load my controller settings, so I have to keep redoing them :confused:

Nice post, reposted on syndicate forum too, hopefully it has sorted out my crossfire issues, so far so good. Also it seems processaffinity has gone from the conf.ini file and is incorporated in the main core as I still get all four cores being used.

In game when you set up your controls there is an option to save them, this then creates a control file in your documents section for COD which you can backup elsewhere and just copy back when you upgrade.

thax this what i was just looking for!

Thanks for the post!

Does anybody know what may have changed between the old and the new conf.ini files?

~S~

Quote:

Originally Posted by meplay (Post 300434)

You don't need to keep Steam cloud enabled. As soon as the patch is beyond the beta stage it will get incremented with a new version number and will be out on steam for automatic download.

If you have automatic updates enabled you will get a notification in the steam interface and it will begin downloading. If you prefer to keep the updates off, once the patch is released you can right-click on your CoD icon in steam and go to properties, there you can set auto-updates to on and let it update and then set it to off again.

What the clouds does is transfer settings between your currently used pC and steam, it doesn't have anything to do with patching. The initial .ini files are in your game folder, then they get copied over to the documents\1c softclub folder upon installation/first run of the sim and whatever you edit gets saved there (or in both, not really sure).

What the cloud does is upload a copy of them to steam and if you fire up the sim from a different PC with the same account and cloud enabled, it's supposed to download your .ini files so you are up and running fast.

The confusion comes from the fact that i don't really know which set of .ini files it uploads to steam and which set takes precedence (eg, people have enabled the cloud only to have steam overwrite their configs with new, blank files). So i just keep it off and do it the old fashioned way: copy anything i might need to a separate backup folder.

In any case though patching is not tied to the cloud, so if you find the description of what it does confusing you can keep it turned off and not care about it :grin:

Quote:

Originally Posted by Tiger27 (Post 300436)

This is an issue with the latest beta patch and already brought to the developers' attention. People report that going to the "plane" menu from the main loading screen and setting loadouts there works: they can be properly saved and selected for the flight during the mission pre-flight screens.

However, something got broken in the "player plane" menu which alters your personal loadouts, this is found on the map pre-flight screen right before you spawn. People report it works in multiplayer though.

The temporary workaround is to save loadouts in the plane menu and assign them to your entire flight for offline flying.

Quote:

Originally Posted by Blackrat (Post 300458)

Yep, the affinity mask setting was withdrawn.

Also, the ability to save just the keybindings and controls is very useful. My one main worry was that my personalized mycontrols.ini file would be incompatible with the new conf.ini, but thankfully it worked just fine and i didn't have to remap everything from scratch.

Quote:

Originally Posted by 335th_GRAthos (Post 300468)

Thanks for the post!

Does anybody know what may have changed between the old and the new conf.ini files?

~S~

There were a lot of legacy parameters in the initial config files that were not really used by the sim, leftovers from previous builds during development and so on. At least that's what Luthier said when the sim was initially released and that's why he told us it's possible to horribly break the sim if we just went around and started changing values :-P
The new conf.ini has a lot less parameters, so i guess they simply cleaned up all the unnecessary leftover values.

ah thanks Blackdog_kt, yeah i saved my ini files in separate folders on desktop and on my memory stick :) so im just going to leave my steam cloud turned off

Thanks

S!

So if I don't download the beta patch and wait for Steam to be updated, do I still need to delete the old ini. files or will Steam do it automatically?

I'd like to add another few small items to Blackdog's excellent list. There is nothing in the checklist that I personally have not been doing - I love his list because it is coherent and one of the only pieces of structured guidance for beta patch setup that exists in our forums here.

I have installed and tested each of the release and beta patches since the beginning - saving and documenting results for each iteration. There have been many improvments since the beginning - but overall frame rates on my system when properly configured average around 42 fps - with min in low 20's - max in the mid 90's.

I got home late last night, so I was quite tired when I ran down the "Blackdogs Checklist". On my first TBD track benchmark - my average frame rate was around 21 fps. After checking my Catalyst, Game settings, configs and system to ensure all settings were consistent with my standard testing. I re-ran the benchmark after rebooting my system. Low frame rates again!

I gave up, went to bed and realized after I woke up, that I'd forgotten to clean out my 1C Softclub/Cache directory. Stupid me. Cleaned the cache, restarted CoD then ran TBD track for the bench. Crap! Back to 21 fps again. Went to work.

After I came home, I restarted my system - checked everything again - recleaned the cache. Still 20-21 fps. Restarted CoD and ran a second time and BANG 42 fps!

Why? **The 1C Softclub\cache has to rebuild itself after you delete the files. So CoD has to be run at least 1 time and closed again for this to happen.

Here are some additional steps:

1. Delete all files in /My Documents/1C SoftClub/il-2 sturmovik cliffs of dover/cache
2. Start CoD
3. Playback "The Black Death" track - you can stop it after a few seconds.
4. Exit CoD
5. Restart CoD
6. Conduct testing

While I'm on this point, maybe it's good that I add this part.

1. Play "The Black Death" Track once all the way through, looking for anomalies or bugs - but don't use this benchmark.
2. Keep the benchmarks from the second and subequent playbacks, and report them together.

Why? On the first track playback, the track is loaded from disk to RAM. You'll find the second playback much more stable than the first (if you conduct enough benchmarks to be statistically significant), because of the random access loadup.

This way, random access storage is removed from the equation, and we are isolating the CPU/RAM/Video sections of each system. This makes the FPS results, much more comparable and non-dependent on the variables of storage, thus giving a better picture of cross-platform relationships and dependencies.

You can always report the first load, sometimes I do - but I keep these results separated.

In summary, if your not making multiple, full track benchmarks and not saving results to files, your results may not be all that usable, and most importantly - you can't see what is really occuring in your system, patch-to-patch.

S!

Gunny

Useful extra bits of info there Gunslinger ;)

I don't usually benchmark in the true sense of the word (i just fly some missions and see how things go over a variety of terrain) because tracks recorded on previous versions might give different results on newer ones (like it was in IL2) but it's good to know anyway in case i decide to start doing so.

Quote:

Originally Posted by timholt (Post 300846)

So if I don't download the beta patch and wait for Steam to be updated, do I still need to delete the old ini. files or will Steam do it automatically?

Unless they incorporate this step in the automatic patching process you will still have to do it yourself.

However, this is a one-time deal unless they decide to change the .ini files again, which i doubt will happen soon...maybe in the future when new features get enabled they will just add new parameters, but i guess the basic structure will remain the same for now.

In other words, it's not something you need to do every time you download a new patch, just once if you had an early version of the sim initially installed on your PC.

EDIT:

I misunderstood (or should I say I'm being a wally!), you have to launch Clod and it creates the missing ini files in the 1Csoftclub folder ( I thought steam did it!). I will leave the question intact in case someone else has the same problem.

Thanks Blackdog_kt, may be you can help me suss why this doesn't work for me. I must be doing something wrong but can't see what.

I checked my ini files and they are dated March and April 15. (I disabled cloud as I had it enabled), moved the ini files to back up folders on my desktop, ran the verify cache option and Steam downloaded exact copies back into the Steam directory but none into the MyDocs installation folder.

:confused:

Can sombody be kind enough to post his conf.ini (new version)?

Mz conf.ini is sacred, I do not dare to let anyone (e.g. Steam) touch it thus I will do the update manually.

Thanks in advance!

~S~

Quote:

Originally Posted by Blackdog_kt (Post 300565)

Quote:
Originally Posted by Tiger27 View Post
This is a peice of great advice, I have been through the files and they are quite different from previous ones, only problem I am having with this and the last patch is I cant save or load my controller settings, so I have to keep redoing them
This is an issue with the latest beta patch and already brought to the developers' attention. People report that going to the "plane" menu from the main loading screen and setting loadouts there works: they can be properly saved and selected for the flight during the mission pre-flight screens.

However, something got broken in the "player plane" menu which alters your personal loadouts, this is found on the map pre-flight screen right before you spawn. People report it works in multiplayer though.

The temporary workaround is to save loadouts in the plane menu and assign them to your entire flight for offline flying.

Thanks for the advice, but in my case it is the controls config menu where I cant save, so I cant backup or load my saved control file, although the apply button works thankfully, strange because I have reloaded everything and it is still there, but I dont know of anyone else with this problem, as it is I just redo my controls each patch, it's a pain but doesnt take to long.

Quote:

Originally Posted by 335th_GRAthos (Post 302429)

Can sombody be kind enough to post his conf.ini (new version)?

Mz conf.ini is sacred, I do not dare to let anyone (e.g. Steam) touch it thus I will do the update manually.

No problem GRAthos, this is the one Clod created after following Blackdog_Kt instructions. Apart from epilepsy flag and my screen res its a virgin...:grin:

I'm doing the same as you and will use it to modify my original Conf file then replace it.

[BOB]
EpilepsyFilter=0

[window]
DepthBits =24
StencilBits=8
DrawIfNotFocused=0
SaveAspect=0
Render=D3D10_0
width=1280
height=1024
posLeft=0
posTop=0
ColourBits=32
FullScreen=1
ChangeScreenRes=0
Frequency=60

[NET]
speed=100000
localPort=27015
serverName=My Server
serverDescription=IL-2 Sturmovik: Cliffs of Dover
serverInfo1=
serverInfo2=
serverInfo3=
serverInfo4=
VAC=1
maxPlayers=255
socksEnable=0
socksHost=
socksPort=1080
socksUser=
socksPwd=

[Console]
IP=20001
UseStartLog=1
WRAP=1
PAUSE=1
HISTORY=1024
HISTORYCMD=1024
PAGE=20
LOG=0
LOGTIME=0
LOAD=console.cmd
SAVE=console.cmd
LOGFILE=log.txt
LOGKEEP=0

[rts]
; 0 - not use, 1 - show cursor and not capture, 2 - not show

cursor, and capture
mouseUse=2
; 0 - not use, 1 - use if hardware exist
joyUse=1
; 0 - not use, 1 - use if hardware exist
trackIRUse=1

[rts_mouse]
SensitivityX=1.0
SensitivityY=1.0
SensitivityZ=1.0
Invert=0
SwapButtons = 0

[rts_joystick]
FF=1

[core]
RandSeed = 0
TexQual=3
TexFlags.PolygonStipple=0
Shadows=0
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=1
LandShading=1
LandDetails=1
Sky=3
Forest=2
VisibilityDistance=3
LandGeom=2
DrawCollisions=1
Water=-1
Effects=1
EffFlags.Light=1
EffFlags.SpriteRender=0
Grass=-1
CordEffect=1
UseFog=0
UseLandCube=1
UseLandConnectedObject=1
LinearObjectManager=1
Roads=-1
Sun=1
Clouds=1
EffFlags.LightSpritesProj=1
ShadowMapSize=5
TexFlags.AsyncLoad=1
TexFlags.ShowTexture=0
SimpleMesh.SWTransform=0
SimpleMesh.QuadTreeClip=1
SimpleMesh.InstancingHW=1
EffFlags.LightContextSprites=1
CloudsFlags.Detailed=1
TexFlags.CreateHDR=1
Decals=1
EffFlags.SWLight=0
TexFlags.CockpitOnePass=0
MegaTexture=0
TexFlags.Reflection=0
RenderTargetQual=3
MSAA=0
MeshStatics=1
MeshStaticsDetail=2
SimpleMesh.QTNoCompose=0
MeshFirstLod=0
MeshShowLod=0
SpawnHumans=0
TexFlags.SSAO=0
TexFlags.VSync=1
TexFlags.FastTransparency=1

[sound]
SoundUse=1
DebugSound=0
SoundEngine=1
Speakers=1
Placement=0
SoundFlags.reversestereo=0
RadioFlags.Enabled=1
RadioEngine=2
MusicVolume=14
ObjectVolume=7
MusState.takeoff=1
MusState.inflight=1
MusState.crash=1
MusFlags.play=1
MasterVolume=14
Attenuation=7
SoundMode=0
SamplingRate=0
NumChannels=2
SoundExt.occlusions=1
SoundFlags.hardware=1
SoundFlags.streams=1
SoundFlags.duplex=1
SoundExt.acoustics=1
SoundExt.volumefx=1
SoundFlags.voicemgr=1
SoundFlags.static=1
VoiceVolume=8
Channels=1
SoundFlags.bugscorrect=0
SoundExt.extrender=0
SoundSetupId=8
ActivationLevel=0.02
Preemphasis=0.8
RadioLatency=0.5
AGC=1
PTTMode=1
RadioFlags.PTTMode=0
RadioFlags.PlayClicks=1
ActLevel=9
MicLevel=10
SoundFlags.UseRadioChatter=0
SoundFlags.AutoActivation=0
SoundFlags.forceEAX1=0
speakers=1
vgMaster=7
vgVoice=7
vgMusic=7

Thanks SEE ! :D

~S~

Quote:

4) Run the steam file verification tool . This will spot you are missing the .ini files (since you moved them to another location) and download the new ones. I have opened and compared the old and new files and their structure is different, so i can confirm this will give you the new files without having to mess with steam cloud settings, just keep the cloud thing off altogether.

I've looked in Steam but cannot find this. Help!:confused: