![]() |
|
Technical threads All discussions about technical issues |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
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
![]() |
#2
|
|||
|
|||
![]()
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. |
#3
|
|||
|
|||
![]()
thax this what i was just looking for!
|
#4
|
|||
|
|||
![]()
Thanks for the post!
Does anybody know what may have changed between the old and the new conf.ini files? ~S~ |
#5
|
||||
|
||||
![]() Quote:
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 ![]() Quote:
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:
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:
![]() The new conf.ini has a lot less parameters, so i guess they simply cleaned up all the unnecessary leftover values. |
#6
|
|||
|
|||
![]()
ah thanks Blackdog_kt, yeah i saved my ini files in separate folders on desktop and on my memory stick
![]() Thanks S! |
#7
|
|||
|
|||
![]()
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?
|
#8
|
||||
|
||||
![]() Quote:
![]()
__________________
I7 intel 920 quade core 6gigs Ram Nvidia Evga GTX 560 2gig overclocked 64Bit Windows 7 Home Premium ![]() |
#9
|
|||
|
|||
![]() Quote:
|
![]() |
|
|