Was born, is living... will die.
I don't know the answer to that. Try our official forums instead (that way other devs will help).
- Decreased weapon accuracy.
- Increased weapon lethality.
- Increased weapon/sight ranges.
- Increased accuracy bonuses against blobs.
- No pop cap.
- No unit caps.
- Some additional content (such as casevacs).
- New territory capture system (although this was removed several patches ago due to an unresolved SCAR conflict).
Details are on our site, under the "Cheat Mode" tab.
I don't understand what you mean. Change the T81 from an MLRS to a single-tube system?
Maybe, we'll see.
Congrats guys. All hail Archaic Entertainment!
But v1.016 was working fine?
If so, re-download and re-extract the v1.017 patch (it was likely interrupted or corrupted the first time).
Are you sure the GBs weren't too close to an enemy strategic point, or that the mortar team wasn't just barraging the area?
This is a known (and annoying) problem.
Could you write up a detailed post in this thread please?
No, not yet. Our SP scripter is currently AWOL.
Not anything to do with MC... have you tried troubleshooting the error online?
For example: Social.msdn.microsoft.com
So far, you're the only person we've heard from who actually liked the beach landing. Most people didn't find it fun. :/
Assuming our singleplayer scripter comes back we may try to make a few more missions. Ideally the next one will be from a PLA perspective, and then we can alternate back and forth to keep the campaign unbiased.
That's a known bug that we couldn't replicate and/or fix (it happens to me, but not any other devs).
The Harrier will be replaced by the Super Cobra eventually, but in the meantime I recommend holding down "Alt" and rotating the camera around it. That always seems to fix the bug on my end.
Any reason you can't update?
Sorry, I meant "bat". Should be two:
- "Modern Combat Launcher.bat"
- "Modern Combat Launcher Cheat Mode.bat"
That's Scarlett Johansson in ship form.
Oops... missed that. :O
It may be the updater trying to connect to our server. You should be able to ignore it without any problems.
If that's not possible though, post a screenshot on our forums so we can see exactly what's wrong.
Instructions are on our site, we'll take another look and see if we can improve them.
The Apache was always intended to be an anti-vehicle unit.
When it was first implemented, its chain gun was essentially just a suppressing weapon that did minimal damage. We buffed it in later patches, although we still wanted to avoid making the Apache too powerful against infantry.
That said, it should be doing more damage than you describe, especially against blobs. Maybe you've just been unlucky?
"Ground team, prepare for touchdown. Be advised... things are about to get a little choppy."
Dead drop. Greenzone. Just some other potential puns I couldn't quite formulate. :/
Então você tem atualmente v1.000, e quiser instalar v1.016?
1. Desinstalar o v1.000 atual. Vá para o seu "Company of Heroes" pasta (por exemplo, o meu é em ""C:\Program Files (x86)\Steam\steamapps\common\Company of Heroes Relaunch") e remova a pasta "ModernCombat" e 5 "ModernCombat.module" arquivos de módulo.
2. Baixe e execute o instalador 1.016.
You mean the HC modes don't show up at all in the victory conditions box?
They weren't removed, so it must be a glitch on your end. try re-extracting the patch and see if that works. If not, then you may need to re-download it.
Do you (and/or your mate) have the same problem when fighting the AI?
If so, then someone's download was probably interrupted or corrupted somehow. Try redownloading and reinstalling the mod (via torrent if your connection is unreliable).
Make a post on our forums:
1. Go to your CoH root folder.
2. Delete any "ModernCombat" folder, or "ModernCombat" .module files.
3. Try running the MSI again.
I believe that's a problem with the new Steam servers, not Modern Combat specifically. :/
Hopefully it'll be fixed with Relic's upcoming patch.
MC really needs a new trailer though; the one embedded above is over two years old and extremely outdated. -_-
Try changing your shader setting to "high". NOT "Ultra" (Ultra utilises DirectX 10, which is incompatible with some of our custom models).
If that still doesn't work then make a post on our site, that way devs more knowledgable than myself will be able to help you out.