PS4-lancering

Jmog>
mens de få Europæere der er begyndt at få deres maskiner (retailere der "kom til" at sende dem) har fået "Made in Japan"-modeller.

Belønning for at være det største Playstation marked hermed bekræftet ;-)

Beano>
Hvorfor? Er de i bedre kvalitet?

Jmog>
Og dejligt at se, der stadig er så mange mennesker, der vil have en rigtig konsol fremfor kun at spille på mobil og tablet.

Beano>
Live lige nu...

http://www.engadget.com/2013/11/22/twitch-tv-late-night-tv-broadcast/

Det er ret vildt!

Naiera>
Jeg havde ellers håbet at NFS skulle være godt, køre godt og se pænt ud :(

But does Need for Speed: Rivals actually pin down that promised 30fps? The answer is yes, and it does so with v-sync engaged too - but there is a caveat. You'll notice during the frame-rate analysis above that the line holds at an unerring average of 30fps, making just a single exceptional drop to 25fps while bursting through a complex dock area. It's undeniably a rock-solid frame-rate - but while a 30 frames-per-second average sounds good on paper, the practical reality is that motion still suffers from a perceived judder effect at points.

But why? Simply put, smooth 30fps games rely on a single unique frame being followed by a single duplicate frame, repeated over and over to give an even sense of motion from a console's typical 60Hz signal. The alternating order of these frames is crucial, but in Rivals' case we see stretches of play where two unique frames will be trailed by two duplicates - averaging out at the same overall frame-rate, but creating a discernible stuttering to camera motions as they whips past. This is one of the reasons why we are currently working on adding consistency graphs to our performance analysis videos (here's a sample of how it will look once complete). Frame-rate is an average, judder is a split-second phenomenon and in the case of Rivals, it has a fundamental impact on the look and feel of the game.

Investigating further, we boot up Battlefield 4 on PC where the phenomenon is easy to replicate in the very same engine with a forced 30fps cap (via the command line: GameTime.MaxVariableFps 30). Again, the same jerky motion is experienced as a result of a string of unique frames being rendered, followed by a likewise number of duplicates to compensate - highlighting this as a possible quirk of Frostbite 3 engine itself. It's not a deal-breaker for Need for Speed: Rivals' playability on either system, but the game's ability to produce a consistent 30fps isn't being best served with this setup, and for some the sensation feels like it's dropping to as low as 20fps.

"The explanation for the frame-pacing is a bug in our settings, Even though the gameplay code is configured to run the game at 30Hz, the present interval of the renderer is incorrectly set to 1, which means that the renderer can present a frame at any multiple of 1/60 seconds. This will be fixed in an upcoming patch."

Hanky>
Hvorfor helvede låse PC-udgaven til 30 fps
...EA T_T

Beano>
Mere uskyldigt...