Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
The point of the AVX instruction set was to allow developers a means to more efficiently utilize calculation heavy CPU tasks. That's exactly what shader compilation is. It's a type of code compilation, which is a CPU specific task.
On top of that, animation and frame management are also CPU tasks. Draw distance and LOD (Level of Detail) settings are also CPU specific tasks. CPUs suck at raster processing. You know the stuff of drawing and rendering a 2D or 3D image. But telling the game engine or the GPU what detail to load if XYZ object is at ZYX location in the 3D or 2D space is CPU because it's logic calculations.
Gaming is evolving to use 8 core and 16 thread designs now. Single threaded CPU calculations in games only provides a limited range of power. You can only process so many tasks at a time on single core (two threads max so technically only 2 tasks). This is pretty archaic and since CPUs have been designed with 8 cores for the last 10 years now, consumers were getting shafted by developers for the past decade for underutilizing CPU hardware.
This game is still in beta and we are the testers. We all need to learn from this and do not buy future games on release, or until we have seen genuine user reviews.
but it was funny. xD i reckon, dude just never heard his rig at full stress load. so what?!?
and well... it's a big boi laptop. i'm used to shader compiling in unreal engine development. it's getting a lil louder then idle, but is not a big deal. i render and do all sort of graphics stuff on it too, i'm used to it. noise is my friend. :) i never thermal throttled before, tho. that was a first for me too. and... the whole thing runs just for a couple of minutes. if your hardware can't endure that full load stress you specced and built it wrong. once done the menu runs at 30-40% now. on my rig. pretty damn chill.
Yeah I actually got scared xD. But I just hate crazy ports that just fks up your computer, I've had computers getting destroyed in the past from bad games, I know it's a real phenomena, so I kinda have PTSD. Bluescreens and unexpected shutdowns of your computer can destroy especially HDD's, and sudden temperture spikes and fans going 100% when not been tested 100% for a while can cause malefunction in the fans, that can happen days or weeks afterwards and you forget what the cause was, that's why it's important for games to be in tuned with computers, or your computer will go all over the place. I hate ♥♥♥♥♥♥ ports.
it's not a crazy port. it's a software like anything else. ofc it uses your hardware to it's full capabilities, if it's needed. an old cpu gonna be busy. and ofc produce a lot of heat because of the watts it consumes. if your cooling can't keep up you done something wrong while putting the parts together or building it. games don't destroy computers. faulty or low quality components give up under stress. that is what kills it, not the software. if you are all scared about loosing a fan or two. you should not switch on the computer at all.
Today, on modern hardware, any BSODs and system shutdowns are due to a lack of proper optimizations on the system itself. Of course, repeatedly shutting down for power related reasons is definitely not good on hardware in general though. Always good to make sure your PSU has 150W of spare head room from all your hardware you're running. 250W extra if you're on a 3080, 3080 Ti, 3090, or 3090 Ti in case of transient spikes.
If your system is being damaged by these workloads, it's a result of inefficient cooling or power issues. Some kind of other actual hardware problem. Inefficient cooling leads to thermal issues. Inefficient power sources can lead to voltage and power problems. Mismatching motherboard and CPUs can also result in issues (too high end of a CPU for a lower end motherboard for example). These are end user configuration problems.
Not to say the game doesn't have its own issues, but what you're describing isn't software/game related. The game is merely just a trigger point making the underlying problem show itself.
i'm not fanboying. i'm just not a tech illiterate. this game does not hurt your hardware. it's stressing it, but the cpu itself got so many safety measures it can literally not die from it. i got a laptop cpu 4600H that is similar to your 10400f. i'm roasting it around 80-90 if it goes all the way in the game. but i know it can deal with it. Tjunction is 105C where it thermal throttles. i thermal throttled my gpu a couple days/weeks ago. that peaks at roughly 90. still not an issue tho. it just throttled. i let it cool and finished the chapter and moved on 1 hour later. wth. no big deal. i for sure know the limit now, i can push it to. that's about hardware.