buzz456 wrote:Somebody more knowledgeable than me needs to explain why 32 bit can only use so much ram and 64 can access all of what's on your machine. That seems to be what unleashed my setup to make everything run like a movie with no jerkiness.
Well I started programming in 1977 as a kid, so it's meaning is second nature to me. But I know less technical types get confused and there is no reason for them to feel dumb cuz it is a little complicated and yet it's not. I'm gonna kinda make a layman's example that shows the CONCEPT, but really isn't accurate when it comes to the formula of bits. This is simply made for you to say..ok..I kinda get it.
Remember multiplication tables? They traditionally are 12 x 12 grid charts. Let's just say for the sake of this example, that table is only gonna be 9 x 9. That's a SINGLE figure example. It's max number it can come up with is 81. BUT... if you make a table that goes to TWO figures, it's max would be 99 x 99 which equals 9,801. By doubling the figure places, you don't get a result number that is double that of the single place figure but actually exponentially higher. In this case it's a max number that is 121 times as big then you can achieve by only multiplying single digit numbers.
Computers store stuff in RAM, but it must be broken up into little cubby-holes called memory addresses. Think of RAM as a city and it's memory addresses are individual houses in that city. Think of Windows as the post office that both delivers and retrieves mail from those addresses. 32-bit post offices would only recognize about 4GB worth of houses. It doesn't see the houses beyond that. But with a 64-bit post office it can recognize exponentially more houses.... or addresses.
I know it's a ridiculous example, but I used it to demonstrate the CONCEPT for the layman. THEN there's THEORETICAL maximum memory addressing Vs. ACTUAL which is an even more complicated can of worms that's not needed to go into here.
Just go to wiki here....
http://en.wikipedia.org/wiki/64-bit_computing
and here...
http://en.wikipedia.org/wiki/Memory_address
If you want to dive head first into actual nuts and bolts of it.
Hope that helped somewhat.
I can't do that with my new 560Ti. I changed the AA to FXAA + 8xMSAA and texture filtering to 8x and get good frame rates but I still see some moire in the switches. It still runs way better than my trusty old 8800GT.
