Bitcoin Forum
May 05, 2024, 08:45:40 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Why underclock video memory?  (Read 5586 times)
burningrave101
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
July 08, 2011, 03:58:53 AM
 #21

Any time you enter a new cell in a game the textures needed are loaded into VRAM for that cell. This is why your VRAM usage goes up with the use of high-res texture packs. It is also why your VRAM usage goes up with the use of Anti-Aliasing and Anisotropic Filtering which is applied to those textures present in the VRAM.
1714898740
Hero Member
*
Offline Offline

Posts: 1714898740

View Profile Personal Message (Offline)

Ignore
1714898740
Reply with quote  #2

1714898740
Report to moderator
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
fascistmuffin
Newbie
*
Offline Offline

Activity: 56
Merit: 0



View Profile
July 08, 2011, 05:15:49 AM
 #22

Read the wikipedia entry again.  It has the word 'may' in it.  Just because it's capable of different things doesn't mean it is used for those things. 

I really don't want to bring this down to the personal insult level, but seriously, RESEARCH before posting nonsense. You're more stubborn than talking to a brick wall. There's nothing bad about being wrong about something, buts it's bad when you continue to try to spread misinformation even though many are weighing in.

I doubt you even googled VRAM usage, since I found many results that I looked at before posting that explained what VRAM is used for these days.
JoelKatz
Legendary
*
Offline Offline

Activity: 1596
Merit: 1012


Democracy is vulnerable to a 51% attack.


View Profile WWW
July 08, 2011, 05:37:53 AM
 #23

Do I really think they put 1GB on graphics cards to hold 117 frames?  YES.  How else are you going to get smooth framerates?  In Rift I get 40 - 60 FPS.  In PlanetSide I get 100+. In EQ2 I get 30 - 50.
For the love of god! Think, man! If they rendered more than a few frames ahead, the lag when you tried to move would be intolerable.  No modern game renders more than 3 frames ahead.

Quote
If the rendered frames had to compete with textures then your computer would grind to a halt.
No, because thankfully they have GPUs with fast local memory that are designed from the ground up to do *exactly* that.

Quote
I run LOTRO with Hi-Rez textures.  That folder ALONE is over 11GB.  That very fact makes it impossible to store textures on the VRAM.
It also makes it impossible to fit the textures in system memory. On modern systems, the video card memory and the system memory are of the same order of magnitude. Games load those textures they need for a particular region onto the video card. They pick the texture resolution (and in some cases, use compression) based on the available RAM on the video card.

Quote
Since it would have to pick and choose what textures it needs, it would have to call them from the hard drive, to system RAM and finally the VRAM.  That's idiotic.
Why? That's actually remarkably efficient. The hard drive controller can write directly into system RAM. And the GPU can read directly from system RAM. This keeps the CPU out of the loop.

Quote
Especially when it makes far more sense to only send the textures you need for a given frame.
You have to be crazy. There is no way you want to be doing anything per-texture, per-frame except on hardware 100% designed for exactly that purpose, which would be the GPU and its fast, local memory.

I am an employee of Ripple. Follow me on Twitter @JoelKatz
1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!