Oh it is.I do the same.
Desktop Outlook is pure hell.
Starfield seems perform very badly with AMD CPUs, almost like they used crippling Intel compiler. So much for AMD sponsored title.Starfield is probably not representative for most future games, but DF found that on Intel both HT and E-cores caused performance degradation (12900K). On AMD however (3600) it scaled as its supposed to with more threads (SMT on). I think I'll be just fine with avoiding the whole b.L/heterogenous thing for the next generation too...
Yep. So much for AMD sponsored title. Forget the performance woes for a while. Now this...Starfield seems perform very badly with AMD CPUs, almost like they used crippling Intel compiler. So much for AMD sponsored title.
Would be interesting to see where exactly is the bottleneck for AMD systems.
If they sponsor, it's in their best interest to make sure it just works!Why would AMD have to do the work FOR THE DEVELOPERS?
Note that there is precedent. Back during the golden age of twimtbp, when it seemed like nearly every game participated, the reason so many game devs signed up to the program wasn't payments of money (only major aaa titles got that), but access to nVidia QA, which was very competent and would test the game on all reasonably current nV cards using all reasonably modern cpus. For many smaller studios, this was too good of a deal to pass up.Why would AMD have to do the work FOR THE DEVELOPERS?
From the source you quote and presumably read:
However, there have also been a few cases of the game causing reboots on Intel machines as well. For one, the player who tipped us off about this issue was playing the game on an Core i7 13700k with a RTX 4090 GPU.
I've got an i7 13700k with a 4090 and have similar reboot crashes to what's being described. The first happened when Barrett gave me the watch, and the second is when I talk to a certain NPC in New Atlantis who asks me to get her a coffee from TerraBrew. That one seems to be reproducible. I also had another crash on the first planet Kreet when walking around, possibly from panning my view too quickly.
PcWorld & NeoWin articles say it clearly. Check'em out...From the source you quote and presumably read:
From the Reddit thread that the artcile quotes as thread:
View attachment 85623
So the game consistently crashes on 13700K, 12700K and 8700K.
@SiliconFly did you do a minimal reading of either the press articles or the Reddit thread?
Yeah, NeoWin got tipped by someone who has these crashes on a 13700K.PcWorld & NeoWin articles say it clearly. Check'em out...
I've got an i7 13700k with a 4090 and have similar reboot crashes to what's being described. The first happened when Barrett gave me the watch, and the second is when I talk to a certain NPC in New Atlantis who asks me to get her a coffee from TerraBrew. That one seems to be reproducible. I also had another crash on the first planet Kreet when walking around, possibly from panning my view too quickly.
So basically the game has issues on both AMD and Intel CPUs since the thread OP is on an AMD mobile system...Yeah, NeoWin got tipped by someone who has these crashes on a 13700K.
It's right there, in the article. And both articles have one source of information, the reddit thread in which a number of people with Intel CPUs report having crashes as well.
Has to be GPU drivers correct? If CPU is stable, user mode code won't crash CPU and the whole system.From the source you quote and presumably read:
From the Reddit thread that the article quotes as source:
View attachment 85623
So the game consistently crashes on 13700K, 12700K and 8700K.
@SiliconFly did you do a minimal reading of either the press articles or the Reddit thread?
A friend of mine found this idk if this is relevant...Has to be GPU drivers correct? If CPU is stable, user mode code won't crash APU and the whole system.
Could these be from console optimizations?A friend of mine found this idk if this is relevant...
Very damning indeed!A friend of mine found this idk if this is relevant...
Not really. Went thru the reddit. Looks like PCWorld & NeoWin have done a pretty thorough analysis. Majority of the cpus are predominantly Ryzen (with a few Intel cpus in the mix).So basically the game has issues on both AMD and Intel CPUs since the thread OP is on an AMD mobile system...
We don't actually know since anecdotal evidence is insufficient in number to derive an actual distribution. In other words, give it up.Not really. Went thru the reddit. Looks like PCWorld & NeoWin have done a pretty thorough analysis. Majority of the cpus are predominantly Ryzen (with a few Intel cpus in the mix).
Should we? Maybe we should inform PCWorld & NeoWin about this.We don't actually know since anecdotal evidence is insufficient in number to derive an actual distribution. In other words, give it up.
Neowin's source is - reddit. That bastion of reliable data. Bzzzt, wrong answer, thank you for playing, but please stop.Should we? Maybe we should inform PCWorld & NeoWin about this.
Neowin's source is - reddit. That bastion of reliable data. Bzzzt, wrong answer, thank you for playing, but please stop.
Based on Geekbench numbers, a single GNR thread is about 4x faster than Stoney multi-core.You know what I want to see? A benchmark face off between Granite Ridge and Stoney Ridge. Call it the "Rocky Ridge Race" or something.
Granite Ridge would probably be, what, 8X faster on multithreaded code?
Starfield seems perform very badly with AMD CPUs, almost like they used crippling Intel compiler. So much for AMD sponsored title.
Would be interesting to see where exactly is the bottleneck for AMD systems.
If they sponsor, it's in their best interest to make sure it just works!
PcWorld & NeoWin articles say it clearly. Check'em out...
Not really. Went thru the reddit. Looks like PCWorld & NeoWin have done a pretty thorough analysis. Majority of the cpus are predominantly Ryzen (with a few Intel cpus in the mix).
Should we? Maybe we should inform PCWorld & NeoWin about this.