Originally Posted by [/B
Blackdog_kt;332226]I've got a suggestion to make this thread more useful and it's actually one very simple thing: let's stick to what the patch is supposed to be fixing and test that first, instead of testing our own "favorite" issue regardless of whether it's supposed to be fixed or not.
Radio commands, AA, the Spitfire's prop and various other issues are
a) well known and documented on the sticky thread started by Insuber and
b) not part of what they worked on for this patch, so it's no use reporting them in this thread
This is a beta patch and that simply means "we tried to fix features A,B and C, please test and tell us if A, B and C work now".
The Ju88's gyrocompass is my own pet peeve but i won't report it. Why? Because it's already a known issue and it wasn't supposed to be part of this patch.
Please, let's read the changelog and test the items mentioned there:
- New graphics: Are there any artifacts/corruption and under which circumstances and what PC configuration? Examples are the people who posted here about the red-out artifacts, the horizon lines and so on, perfectly good case of testing what's supposed to be tested.
- New sounds: Are there any sound glitches? Do the sounds play correctly? Doesn't matter if we think it should be louder or softer or whatever for now, the question is does it work or does it play back a garbled mess?
-New bombsights: Are they working as they said they would?
-Ground handling physics: Any difference when testing previously suspect issues with the new beta patch? For example, the spinning aircraft upon spawn, or the Blenheim's tendency to yaw way too much to the right on take off?
Well, i tested two of these items and i'm very glad to say that the patch seems to be doing what it says on the label: the Blenheim can now be kept under control during take-off much easier just by stepping on the rudder and its bombsight works correctly (i just came back from completing an attack on an airfield bombing from 8000ft and it worked like a charm, bombs bang in the middle of the runway intersection).
Let's try to test the other stuff on the changelog so that they can wrap these issues up and move on the next ones, don't you guys agree? ;-)
Finally some important technical guidelines for testing.
Possible version mismatch: Going online with a beta patch is possible, but if the server you are flying on isn't running the same version, you can get all sorts of glitches.
These can't be classified as legitimate bugs because they might simply be caused by flying a different version than the server. If you spot a bug while flying online, try to replicate offline too before reporting it.
Clear your cache and defrag the game folder:
After applying the patch go to documents\1c softclub\il-2 sturmovik cliffs of dover\cache
You'll see a bunch of file in there and another folder named "shaders". Go into shaders and delete all files in there, but don't delete the folder too. Now go back one level back to the cache folder. Delete all files in there too (remember, except the shaders folder).
Open steam, right click on CoD's icon, select properties and click on the "local files" tab. Now click on "defragment cache files" (this is not the same cache we just deleted in the documents folder, it's steam's way of referring to your actual game folder).
What does all this do?
The steam defrag does just that, it defragments the game files so that they are in continuous or adjacent blocks (or both), making it easier (and faster) for your hard disk to read them without having to look all over the place.
As for the cache, the game generates some data and stores them in those folders under your documents folder, so that it doesn't have to calculate everything from scratch whenever you fly, thus saving some processing power and gaining some performance.
However, if the way a bunch of graphics related stuff is calculated has changed and that data conforms to the old standard, there is a potential for glitches. Clearing those files forces the game to rebuild that data according to the new graphics algorithms.
The first time you run the sim after clearing the cache you'll notice it takes longer to load the menu, it's because it's rebuilding that data. Let it finish and as soon as you are in the menu exit the sim. Run it for a second time and you'll now see that it loads much faster (since the data is now generated by the previous run). No go ahead, fly and test what's in the changelog ;-)
|
