![]() |
|
Technical threads All discussions about technical issues |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
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. |
#2
|
|||
|
|||
![]()
thax this what i was just looking for!
|
#3
|
|||
|
|||
![]()
Thanks for the post!
Does anybody know what may have changed between the old and the new conf.ini files? ~S~ |
#4
|
||||
|
||||
![]() 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. |
#5
|
|||
|
|||
![]()
ah thanks Blackdog_kt, yeah i saved my ini files in separate folders on desktop and on my memory stick
![]() Thanks S! |
#6
|
|||
|
|||
![]()
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?
|
#7
|
||||
|
||||
![]()
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
__________________
Intel i7-3930K @ 4.00 MHz - ASUS Rampage IV EVGA 3072MB VRAM GTX 580 16GB RAM - Windows 7/64 Warthog and U2Nxt Cougar under t.a.r.g.e.t |
#8
|
||||
|
||||
![]() Quote:
![]()
__________________
I7 intel 920 quade core 6gigs Ram Nvidia Evga GTX 560 2gig overclocked 64Bit Windows 7 Home Premium ![]() |
#9
|
|||
|
|||
![]() Quote:
|
![]() |
|
|