• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WCCftech: Memory allocation problem with GTX 970 [UPDATE] PCPer: NVidia response

Page 39 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Clearly that isn't what was said. Why you have to take things out of context is beyond me.
Would you like to explain what was taken out of context? Nvidia has made a statement wrt 970, and suggested that it is working as designed, so what is out of context? The ram? Well, their driver is already working around the segmented memory problem, by avoiding the .5gb as whenever that portion of vram is accessed, it makes one cringe, to say the least. By the way, if Nvidia can make a mistake and enrichen themselves, their shareholders, this poor sod can make a mistake which earns him nothing. May be you could show him just as much understanding as you're willing to show Nvidia.
 
It appears that the GTX 970 is working as intended.

https://twitter.com/NVIDIAGeForce/status/560881138869497856

So apparently the GTX 970 was deliberately designed to cause hitching and stuttering when accessing its last 500MB of VRAM.

Nothing more to see here, I guess.



First of all, this article is old news. Second of all, I think we are done with this lengthy dead horse beaten discussion. I am tired of the arguing and back and forth.


-Rvenger
 
Status
Not open for further replies.
Back
Top