Forum Discussion
Alad93 wrote:I can see your point in relation to a faulty HW components but what are the odds that this happened on two completely different configurations?
Actually, pretty high, considering that many system builders offer cheap PSU's for their builds.
But there are other probable causes as well of course.
Point is what Fred_vdp and mcsupersport said, software is never "harming" your pc, it maximal shows weak-points of the used components.
This reminds me of the time a lot of people believes StarCraft II was breaking their PCs when all the game really did was not cap the framerate in menus, causing GPUs to run at 100% usage. This ended up overheating a ton of laptops, also of different brands and models.
if we extend this to Veilguard, I think you can see a similar trigger in at least two areas. First, the shader compilation, which makes the CPU run very hot if you have poor cooling (mine ran at 98°C, which is pushing it). Second is the dynamic resolution, where the game will optionally increase the rendering resolution until it either reaches your set resolution or if your GPU is at 100% usage. For my modest GPU, this means heavy strain in Arlathan forest with constant 100% GPU usage, so I ended up disabling dynamic resolution and running the game at a capped framerate and a fixed upscaling quality to reduce temperatures.
holger1405 wrote:Actually, pretty high, considering that many system builders offer cheap PSU's for their builds.
And they rarely specify which PSU is in it, when this is specifically a component that you don't want to cheap out on. They will display wattage, and nothing more. Same with CPU coolers. You often get stuck with the stock cooling. If it's a third party cooler, you get a cheap one with RGB lights to make it "gaming" tier.