I was dead set on getting a PS4 but literally everyone of my friends is going Xbone so I may have to go that way.
I have this. Plus, the fact that GT6 seems to be even more boring (and may not be on PS4) while Forza has got even better sort of makes me lean away from getting both like I did this generation.
no, no, no, no.
They give you a Veyron (fastest internet around), but if you over do it on the mileage they limit the speed to 50% or thereabouts for a few hours.
A Veyron at half speed is still considerably faster than a snail (ADSL) at full speed.
I don't see why they wouldn't actually.
If you can still purchase stuff through your we browser like you can now then it should be on your download list which is tied to your account and not a particular console.
I have this. Plus, the fact that GT6 seems to be even more boring (and may not be on PS4) while Forza has got even better sort of makes me lean away from getting both like I did this generation.
or I could keep using my BT fibre and may not hit a 100 (75mb I get) but I wont get a 50% reduction in speed if I travel too far
From memory I think you need to download about 3.5gb in an hour to get throttled now on 100mb.
That's not going to happen during your average gaming session.
Edit: Actually it's 4.5gb down and 1.45gb to 1.8gb up (depending on package) for throttling.
i moved from bt to sky after 4 years plus of waiting for my exchange to get llu'd so at least im not being reamed by bt anymore. hopefully they will hook up with both sky and bt as it means good pings all around for multiplayer hopefully.
Apparently the biggest 4 ISP's in England are BT, Sky, TalkTalk and Virgin. You'd have thought Sony would have gone for those 4 first
Got confirmation from amazon for release date delivery D:
Got confirmation from amazon for release date delivery D:
On a classical system you have a RAM pool and a VRAM pool that are physically speperated. Copying data from one pool to the other creates latency. The GPU is very good ad hiding latency. What it needs most is high bandwidth. The CPU on the other hand is extremely sensitive to latency. The CPU needs extremely low latency to work efficiently. Copying data from the RAM (CPU) to the VRAM (GPU) creates latency, but that's okay for the GPU. Copying data from RAM (CPU) to VRAM (GPU) and back to the RAM (CPU) creates even more latency. It's too much for the CPU. The copying alone takes longer than the computation wich makes this roundtrip highly ineffective.
Xbox360 and older APUs have a unified RAM. This means that the RAM is no longer physically seperated, but even though it's the same RAM chips, the system still distincts between memory partition for the differenct processors. You still need to copy the data between CPU partition and GPU partition, but this will be much more efficient than copying it between physically seperated pools. But it's still too much latency for a CPU, GPU, CPU roundtrip.
PS4 will have hUMA wich means that you no longer need a distinction between CPU partition and GPU partition. Both processors can use the same pieces of data at the same time. You don't need to copy stuff and this allows for completely new algorithms that utilize CPU and GPU at the same time. This is interesting since a GPU is very strong, but extremely dumb. A CPU is extremely smart, but very weak. Since you can utilize both processors at the same time for a single task you have a system that is extremely smart and extremely strong at the same time.
It will allow for an extreme boost for many, many algorithms and parts of algorithms. On top of that it will allow for completely new classes of algorithms. This is a game changer.
Even with the integration of GPUs and CPUs into the same chip, GPGPU is quite awkward for software developers. The CPU and GPU have their own pools of memory. Physically, these might use the same chips on the motherboard (as most integrated GPUs carve off a portion of system memory for their own purposes). From a software perspective, however, these are completely separate.
This means that whenever a CPU program wants to do some computation on the GPU, it has to copy all the data from the CPU's memory into the GPU's memory. When the GPU computation is finished, all the data has to be copied back. This need to copy back and forth wastes time and makes it difficult to mix and match code that runs on the CPU and code that runs on the GPU.
The need to copy data also means that the GPU can't use the same data structures that the CPU is using. While the exact terminology varies from programming language to programming language, CPU data structures make extensive use of pointers: essentially, memory addresses that refer (or, indeed, point) to other pieces of data. These structures can't simply be copied into GPU memory, because CPU pointers refer to locations in CPU memory. Since GPU memory is separate, these locations would be all wrong when copied.
hUMA is the way AMD proposes to solve this problem. With hUMA, the CPU and GPU share a single memory space. The GPU can directly access CPU memory addresses, allowing it to both read and write data that the CPU is also reading and writing.
hUMA is a cache coherent system, meaning that the CPU and GPU will always see a consistent view of data in memory. If one processor makes a change then the other processor will see that changed data, even if the old value was being cached.