Ok here are actually two bugs, but the one I'm focusing on is in the title,
I've noticed that when having your units selected, and giving them an attack move order into the enemy base now causes them to continue firing on the enemy's HQ even when it has been destroyed, below are two examples from the same game session (on the map Road to Kharkov)
As you can see (and hopefully trust me on it) my units (most noticeably my tanks) are shooting on the destroyed enemy's HQ, where I had to then force them to attack the enemy's other buildings instead of using attack move. This may just be a bug on this new map but I doubt that would be the case.
And then, a smaller problem which is not such a big deal, I noticed that when selecting fix locations under custom game this same map, Road to Kharkov, has it's starting locations incorrect, as it would seem enemies would be starting right next to each other. (Almost hoped that would be the case as that might have been a bit interesting until Relic fixes it lol) But this issue is just on the create custom game screen, like I said not such a big deal.
|
In our troubleshooting and searching forums, there is no further replies to these problems since Relic backs up that the beta driver fixes the issue, end of story.
My friend got hold of a second hand Radeon 4750 or something like that for only (in US terms, 10 dollars), and the problem is now gone. The crashing issue is with the 2, 3 and 4 series Radeon cards, however with his 4 series card the game now works fine, which leads me to believe something the game needs (maybe direct X version) is just not supported with the 3 series, otherwise I don't know. - you can try forcing the game to run on direct X 10 from within steam and see if that helps, that is something we have not tried. (assuming the game runs on direct X 11 and nothing else)
So from my side I am sorry to say (or at least think), that this problem will likely never be addressed or looked further in to (as it is a big problem if the game cannot be played but it's advertised that it should be playable on such and such a configuration yet nothing has been done about it thus far). Best your friend can do is get a cheap 4 series or 5 series card, assuming your friend also runs on a 3 series at least? Or go Nvidia I guess.
And the updating after crashing is annoying when it happens over and over as in your friends case, I think this is just a "check, make sure" small download to ensure all files are fine. |
Recently (Somewhere in the past week) my CoH2 started crashing to the desktop with Bug Splat Reports coming up and my display driver stating it recovered from a crash. This happens sometimes when booting up CoH2 and sometimes just before entering a map after it loaded. I know this was a known issue with the 2,3 and 4 series Radeon cards while playing on a map, but my card is a HD 5870, and this has never happened before.
This is very annoying and I have tried reverting back to older drivers, which at first seem to fix the issue, but seemingly only for one session of playing, which after that it would then either crash at boot up or after loading a map again.
Would be nice to have advice on this issue? What am I missing here? Did something change in the game itself from patches etc? As I know I have not changed anything on my computer and this just randomly started happening. |
so it is overclocking programme for dummies?
I wonder why would someone make it, people without overclocking knowledge and overclock = burning their rig
It is not an overclocking program. It simply switches services and/or background programs off to your specification while playing a game, which saves up resources to be used for the game instead of for the OS or otherwise. So it frees up ram and CPU usage. I might add it does this automatically every time you enter a game that you added to it's list, and switches all services and programs back on again after you quit the game.
I have been using it for a while now and it definitely makes a difference to loading times in games, and obviously should help with FPS, have not really looked into that.
This program should not be of any use to people with high end pc's though. |
Update to my original post here,
My v2 P4 got abandoned, I recaptured it myself, the P4 was now skirted but back at v1. Therefore it is the crew that vets and not the tank itself, the skirting that stays is at most just a skin/visual "bug". If this was without a doubt not the case for others here, then I agree it's a major bug, but for me it was not a problem/bug. |
Well, about vet, maybe it could be so as I'm not sure about that.
But, about the armoured skirts, I also saw it happen, my v2 P4 got abandoned and captured and the skirts stayed on, I took no special concern of this as the armoured skirts is just a skin upgrade, it does not have to be directly linked to an actual armour upgrade, so I just assumed the tank reverted back to v1 just the skin stayed the same for no apparent reason, which is not such a big deal as it does not happen a lot anyway. |
This happens to anyone who experienced a game crash before, after relaunching the game it does a quick "update", however I think this might just be a "let's quickly check to see if everything is in order" - "repair". Can be annoying but not too much since it only takes like a few minutes and how many times does the game crash in the long run anyway. |
Was playing the campaign, when I kept hearing that my HQ keeps being under attack and whenever I go look there were no enemy forces there... until I waited, and noticed that my ally, the 69th Army Rifle Division, did not take kindly to Order 227, as they were always trying to kill the Commissar whenever I called in Conscripts. I guess not all Soviet forces took Stalin's orders to heart lol.
|
First of all I apologize if this has been officially discussed somewhere on here, but for what it's worth, I like to reinforce the exposure of the following problem:
My friend owns as Radeon HD3870, he is able to play the game on medium settings without lag, but even when turning all settings to low the following always happens:
Start a skirmish or multilayer map, game crashes within a minute or two of game play..
Then, the solution, the Radeon beta driver 13.4 for HD 2,3 and 4 series experiencing this crash problem in COH2, well, now his able to play a skirmish map for about 7 to 10 minutes before it crashes EVERY TIME. Funny note: winter snow maps works perfectly fine for him no problem. Just summer maps that always crash.
Anyone finding a solution to this problem somehow please inform, as it would seem that AMD is now happy with the beta supposedly solving the problem. Does the newest COH2 update maybe fix this? As I have not yet spoken to him since after the update I just noticed some Nvidia driver fixes on the patch notes but nothing pointing directly to Radeon related problems. Any help would be appreciated as we really enjoyed playing COH1 together and now since this happened he just decided to hell with COH2 (at least until it got fixed.)
Things we tried so far without success:
Declocking the card a bit (reason for this is my own card (5870) pretty much use to crash on every game until I declocked it just a slight bit and everything worked fine ever since)
Overclocking a bit
Overclocking a lot
Making sure DirectX is up to date
Tried previous and current beta drivers for card
Using game booster to significantly free up resources
Running the game in compatibility mode for Windows 7 (he has Windows 8 installed)
Played around with different graphics settings in game as well as turning v sync on and off.
So the conclusion is definitively that this is not a performance issue but a somehow incompatible driver issue (which is obvious I know) - but never hurts to try different things to maybe solve it. |
I've never seen those faces before
Ha I believe you |