Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
Mid/High what are those words you speak of ? I play on the max settings of everything again I am not having issues other than the memory leak and I am able to continue to play with no issues other than the heat gen which is countered by my cooling system.. I am just saying if the game isn't meant to be played on ultra whats the point ? Also I am just agreeing with the OP since its true.. just because he doesn't have zero point generator isn't my problem.
Is this a leak or is the program requesting allocation of a lot of memory due to optimization. When you ask an engineer how often do you have memory leaks in your programs I respond with, "almost never". RAII is way too good at keeping these things from happening to heap, files, sockets, or mutexes. RAII uses constructors and destructors, so you never have to include operators like new, or delete or locking/unlocking mutex so it manages memory for you. There are always exceptions, I am very bad at explaining things (why I do not train people) but in short it is rare or intentional. Memory management in C++ is not too bad, for the most part.
Segfaults are more common, I have this issue especially when i interface with low level code, OS API's or other low level libraries, they tend to have a sh*t load of pointers and poor type safety, if you're lucky you only have to deal with one or the other. I am never lucky.
second, the black screens and the fans cycling up could be a problem with your i guess (4080 nvidia) graphics card, because its a common problem amongst this cards.
I dont have any of this problem whilst playing on max settings (7900xtx)
maybe uninstall your graphic cards drivers and do a fresh install
Games can't kill hardware.
Bad hardware setup, or faulty hardware is what kills hardware.
When a game pushes a computer to hard, the computer safeguard to prevent damage, ie thermal throttle etc, assuming ofc you haven't been overclocking beyond stable limits.
and if you happen to have 13 or 14th Gen Intel CPU, that's probably your problem right there, as out the box they are pushing themselves too hard to point of fatal stability issues, Intel is aware this and trying to do damage control without taking real responsibility right now.
Or if you have RTX 4090 you might have a failing power connector due to the melting 12v plug issue with Nvidia top end card.
If you claim to have built the computer yourself you should be ashamed to not have a good understanding of how computer hardware works instead of blaming the Dev's.
There is no memory leak, did you try to monitor virtual and private bytes on the process U01-Win64-shipping ? Did you make a dump and check it is Visual Studio? Probably not. How about Nsight/VisualProfiler or CodeXL depending on your gpu?
Well, I did.
Games can kill Hardware, alas the Hardware was faulty before. Again a Nvidia Problem, a while ago, as the uncapped FPS menu in New World caused some 3090 to brick themselves. I dont understand how people still buying Nvidia cards for high prices, that tend to destroy themselves in a collective suicide while simply doing what they were made for.
Also we will never know if you even owned the game to begin with. So it kinda seems you just want to bash the devs. They've put in actual work fixing the most glaring issues players have had, and issued the patches very quickly. So I wouldn't really blame the devs at all.
So far I've had like 2 crashes in my 110+ hours of gametime. One caused by myself for alt-tabbing too much quickly. My fault that one. Other one was after 5+ hour session.
For the record:
i7-10700k (stock)
32 GB ram
RTX3080TI
New World didn't brick the 3090's, it highlighted a flaw in the 3090 itself.
Not every 3090 got bricked, not every GPU got bricked, if the flaw was the game it wouldn't of been limited to specific brands of 3090's
I missed this initially
Nvidia put out statement while back regarding Unreal 5 "Out of Video Memory" is not a Nvidia issue, its Intel 13th and 14th Gen problem,.
The fix is to stop using any overclocks, stop using motherboard defaults.
In Bios switch to "Intel Baseline Profile" (bios might need updating maybe.)
This will downclock your CPU and you lose some performance, but its the only fix.
If you don't do it then you going see this problem again and again, and it could potentially kill your CPU eventually.
So unless you want dead PC I'd take this very seriously, and again, this has nothing to do with the game Dev's, its a Intel flaw that's been discovered recently, they clocking too high at stock and is highly unstable.
Various source's
https://www.youtube.com/watch?v=HIubZYwBfPc&ab_channel=JayzTwoCents
https://www.youtube.com/watch?v=OdF5erDRO-c&t=719s&ab_channel=HardwareUnboxed
https://www.youtube.com/watch?v=si4DTxFUUvM&t=14s&ab_channel=GamersNexus
Hopefully it helps that OP I suspected it was because of overclocking.
SO i will call BS on everything you mentioned and that you are nothing more than a spammer looking for attention.
i have 2 computers 3600 AMD with a 5700XT and aa 5950x and 6900xt and both run it totally fine.
i know others running the game on a R9 290 at 40fps, so i call 100% BS on your attention seeking claims.
go play helldivers or COD you clowns pocket