Was born, is living... will die.
It's been a while, sorry about that. :P
Exactly which setting did you change? What did you change it to?
Change your graphics shader setting to "high".
We had some sweeping changes planned; if they go ahead then an infantry-only mode is a possibility.
Why Type 56s? They're completely outdated (one of the things about MC that always annoyed me), especially for standardised front-line professional troops.
With my skillset? Not unless you want recoloured Chinese or US troops. :P
Could you make a post on our forums?
Include your "warnings.log" file, found here: "Documents\My Games\Company of Heroes Relaunch\warnings.log"
Make sure you copy the warnings.log directly after a game during which this error happened, as each time you play the file will be overwritten.
I replied, but I need more info. It's probably something simple like the anim_states.
Good gameplay requires that every unit be specialised in their own way though. For example, if every unit can combat vehicles in some way (especially in HC where even something like an AT4 usually means instant death) then the player has no reason to build dedicated anti-armour units like Tank Hunters.
Seriously mate, thankyou for holding the fort and helping out others all this time. You are, without a doubt, our most dedicated fan.
They're entirely separate and don't affect the base game. You can have as many mods installed as you like.
It'd be nice, but unfortunately that just isn't possible. Not by a long shot.
Didn't see this post until now, but I just want to add my condolences. Something like this hits hard. It's great to see just how supportive the CoH community is.
We'll need to check this out then.
Apparently the opacity of the images was to blame.
Any unit/ability icons that I created in Paint.NET had hidden properties that caused them to be rendered completely transparent by the game.
Maybe the newer framework causes them to be rendered properly?
University exams. Annoying third year ones.
The next few weeks are essentially going to be an academic Wipeout course.
Believe me, there are real-life reasons behind every delay. And don't forget that everyone still on the dev team has already given this mod years of their life...
More often than you update it.
No time anymore mate. We'll hopefully get to update after the uni exam period.
Thankyou very much. Enjoy. :)
Thanks a lot for the info, we'll check it out. It's been hard for us to test as nobody on the team can replicate it.
AAMC has already put these up on our forums. If you find any more could you add them to the list there?
Never mind the comment above then, posted it before scrolling down. :P
It's a known problem (the .msi installer doesn't work properly). We hope to release a new version soon that will fix all this... it should've been out a month ago but we've been bogged down by uni studies and other real-life obligations.
You need to make a shortcut to the .bat files in the ModernCombat folder, e.g:
"C:\Program Files (x86)\Steam\steamapps\common\Company of Heroes Relaunch\ModernCombat\Modern Combat Launcher.bat"
I'm assuming you haven't tried that and just linked straight to RelicCOH.exe?
Did you download and install the latest patches?
Only the UI aspects are handled by RGDs. Not the actual asset itself.
Skins are handled by a model's RGO and RGM IIRC. The Stryker's would be in "Data\art\Models\Races\amer\vehicles\Stryker".
However the system is pretty complex, with different skins and states being applied under various conditions that you'd need OE to manipulate. I personally don't know exactly how it works.
It's a dual-system mod, with both a regular damage system and a more realistic "hardcore" damage system.
The M110 will be back eventually, but not as a default sniper weapon.
And they look similar because they are similar. :P
*most recent "scarlog" file
Can you make a post on our forums and post the contents of your warnings.log file?
The warnings.log should be in "Documents\My Games\Company of Heroes Relaunch".
If you can, also go into "Documents\My Games\Company of Heroes Relaunch\LogFiles", find the most "scarlog" file and post that up too. Make sure it's from straight after a game during which this bug occurred.