Patch Notes 01.000.300
Patch Notes 01.000.300
LAS-99 Quasar Cannon - Increased recharge time by 5 seconds
This is a nerf right, the time now takes 5 seconds longer to become ready?
Yeah, when I need to use a reload it’s usually cause shit hit the fan. But ammo isn’t that hard to find it anything.
That quasar cool down is going to hurt for drop ships though
The steam patch notes are lacking some details from the discord patch notes. check out Enemy Patrol
: : : Stratagems
Enemies Balancing adjustments have been made to
Enemy Patrols We unintendedly had non-linear scaling of the patrol spawns so they didn’t spawn as often as they should have when less than 4 players. The intention is that 1 player has 1/4th of the patrols compared to 4 players, but it used to be that they had 1/6th.
🎮 Gameplay
It's there...
Crash fixes
Scout strider Riders now less vulnerable to explosions
Aw man that sounds like a huge nerf to the Scorcher and Eruptor. Being able to kill the scouts by shooting them in the front with explosive weapons made them so much more manageable.
Thank you for pointing this out.
Looks like grenade bowling is still on the menu.
For now, the most effective method to preventing this issue is to limit core clocks on NV31 to about 2500 MHz.
I believe this is under the known issues for Adrenalin
In my case it manifested as a graphics driver crash. This would bring down anything that was using the GPU: the game, discord, Windows DWM.
Someone on SC`s forums did a bunch of research and eventually suggested the clock limit, which has solved all my SC, HD2, R&C issues and most of my War Thunder issues (though that one still silently deletes itself from RAM occasionally, but I think that’s just War Thunder).
Here’s the post, if you’re interested: robertsspaceindustries.com/…/high-end-amd-gpu-cra…
Sorry, I take a bunch of acronyms for granted. TDR = timeout detection / recovery.
Did the bug report tool suggest there was a timeout in each of those cases?
I forget, it’s been a while. I want to say yes, but the screen would freeze for several seconds before the GPU driver reset in my case, so that seems like a legitimate timeout to me. I had tried increasing the timeout in the past to fix these issues, before I found this method.
While testing I did confirm using OpenHardwareMonitor that the GPU core frequency would spike above 3100Mhz before crashing, as the thread describes. Setting the max to 2550 seems to prevent this happening.