rsherhod
05-14-2010, 11:28 AM
I've just started playing Men of War, and for some reason I can't even get past the first armoured car in the first mission!
It's not that I'm getting killed (although that did happen a few times), it just that when I do kill it, nothing happens.
I must have tried it a hundred times to make sure I'm not just doing something stupid, and I've watched a few video walkthroughs of that engagement and followed it precisely. Even down to using exactly the same guy to kill the bloody thing.
I've seen what should happen; it goes boom, and they all rush forward and say "He won't be driving around any more" or something. For me they do rush forward, but no one says anything and nothing else happens.
Unlike in the videos the 'Destroy the German armoured vehicle' objective doesn't flash up as completed, as it should, and resolutely stays as my one and only listed objective.
Technical info:
It's a direct2drive copy, with their most recent patch installed.
Oh and it runs fine on moderately high settings.
It must be a scripting bug; albeit one that no one else seems to have ever had (no relevant google results).
Maybe reinstalling without the patch would help.
It's not that I'm getting killed (although that did happen a few times), it just that when I do kill it, nothing happens.
I must have tried it a hundred times to make sure I'm not just doing something stupid, and I've watched a few video walkthroughs of that engagement and followed it precisely. Even down to using exactly the same guy to kill the bloody thing.
I've seen what should happen; it goes boom, and they all rush forward and say "He won't be driving around any more" or something. For me they do rush forward, but no one says anything and nothing else happens.
Unlike in the videos the 'Destroy the German armoured vehicle' objective doesn't flash up as completed, as it should, and resolutely stays as my one and only listed objective.
Technical info:
It's a direct2drive copy, with their most recent patch installed.
Oh and it runs fine on moderately high settings.
It must be a scripting bug; albeit one that no one else seems to have ever had (no relevant google results).
Maybe reinstalling without the patch would help.