• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

Digital Foundry vs Mario Kart 8

dark10x

Digital Foundry pixel pusher
Maybe they did notice the dropped frame in QA and the developers decided it had no effect on gameplay? I mean, how many people can see a single dropped frame with the naked eye and then be bothered by it? That part of it being something they "could not unsee" struck me as a little much.
It's due to the nature of displays. With g-sync this wouldn't be noticeable but in normal 60 hz displays it's very obvious. I noticed it within seconds of first loading up the game. It persists throughout normal play.

It's akin to the issue with the Gameboy Player on GC. That was due to refresh rate differences between TVs and the gba but it resulted in a noticeable skip inset intervals during play. Very distracting.

It's very bothersome to my eyes and it was worth noting as it's a very strange issue for a Nintendo game.
 

nib95

Banned
Correct me if I'm wrong, but the point of DF highlighting a drop of just 1fps is not that you'd feel the frame rate difference itself, but the judder it may cause as a result of it breaking sync with your sets refresh rate?
 

Kysen

Member
Just goes to show that the wiiu is already at its limit (devs words not mine) and to achieve a 60fps update AA is the first casualty.
 
wonder if the frame drop is a bug/oversight or an actual performance thing.

Pretty interesting, I honestly don´t think that it is out of the question to see a performance improving patch down the road
no pun intended
.

59 ->60 fps seems like such a small jump.
 

Papercuts

fired zero bullets in the orphanage.
Just goes to show that the wiiu is already at its limit (devs words not mine) and to achieve a 60fps update AA is the first casualty.

They just focused on different things, here it seems to be lighting.

2rt2vMk.jpg


The four tires, lights on the track, headlights, etc. are all dynamic.

The 59fps thing seems to be a bug as the article details it's only present when CPU controlled people are in the race. So 12 player online races should be 60fps anyway, and there were no drops regardless of what was happening.
 

CTLance

Member
A repeated frame exactly every 64 frames? How very odd. Could that be intentional? I mean, it's not some off number, but 64 being 0100 0000b (2^6) sounds like someone implemented some sort of counter. Which begs the question, why, and is it intentional or a bug? Also, what happens when the entire engine basically doesn't render anything during that last frame? Is the entire engine stalled, including game logic, or is just the graphics part in disarray? Is it some kind of overflow? Lag compensation? What is it?

Dammit, now I'm curious.
 

Mithos

Member
I haven't noticed any stuttering on any 60fps MK8 footage I've seen and I really wish I don't notice it because I've clicked on this thread now.

I noticed the 60fps -> 59fps "thing" in the youtube video on DF homepage, but then again that's how youtube videos almost always looks for me.
 
That nintendo magazine link from above is from 2013. The eurogamer article says april 2014.

They reported 1080p so close to the release date people thought it was set in stone, and because it came from eurogamer who are known for their performance analysises and not some Nintendo exclusive site, people took their word for it.
 
A repeated frame exactly every 64 frames? How very odd. Could that be intentional? I mean, it's not some off number, but 64 being 0100 0000b (2^6) sounds like someone implemented some sort of counter. Which begs the question, why, and is it intentional or a bug? Also, what happens when the entire engine basically doesn't render anything during that last frame? Is the entire engine stalled, including game logic, or is just the graphics part in disarray? Is it some kind of overflow? Lag compensation? What is it?

Dammit, now I'm curious.

I read this entire post in Neil Tyson's voice and it was beautiful.
 

devonodev

Member
Hoping the fps drop can be fixed with a patch.
If it actually does have a noticeable jarring effect, would this stutter still be better than a solid 30fps?
 

ruie

Member
you left the most interesting part out, OP.

What makes this situation all the more strange is the fact that this problem only appears when CPU opponents are active. In time trials or split-screen matches, with AI-controlled drivers disabled, the frame-rate updates flawlessly while race introductions and victory animations all display correctly as well. The frequency and pattern of this problem suggests an internal timing issue, potentially related to Mario Kart TV, rather than one of performance. We can't be certain where the root cause lies but we certainly do hope Nintendo will take time to correct this problem in a patch.
 

lefantome

Member
These eagle eyed journalist can't see if a game is running at 720p or 1080p even with abundant aliasing? C'mon!
At least avoid writing so,ething you can't verify in your article
 
I mean seriously wtf is up with DF, there is nit picking then there is extreme nit picking

ridiculous and a little sad

also worth noting did a single review even notice this?

I suspect not

If they didn't mention it then eventually someone else would and they would be called out for missing it and labeled incompetent.
Pointing this stuff out is what these articles are for, it's not their fault if people make a bigger issue out of it than it really is.
 

Tommy DJ

Member
Good lord they go out of their way to make 1 frame drop sound like a huge deal.

59 FPS on a 60 hz display can introduce noticeable stutter. Its essentially the same sort of problem people have with unlocked frame rates..

The news here isn't the loss of one frame but that Mario Kart 8 doesn't maintain a frame rate that will exhibit zero stutter on a 60 hz display.
 

Raist

Banned
dark10x
60 fps 60 fps 60 fps 60 fps 59 fps 60 fps 60 fps 59 fps

Judging by the video it's more like

59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 60 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps 59 fps
 

dark10x

Digital Foundry pixel pusher
Was watching the FPS video. Dat red shell at 5:05. Sweating much, dark10? :p
Ha ha, I'm glad someone caught that. :p

In the two player split-screen video I actually recruited my wife who really doesn't play twitch games. It was her first time trying Mario Kart and she was struggling hard but in the end did OK. She insisted on using motion control, though.

The news here isn't the loss of one frame but that Mario Kart 8 doesn't maintain a frame rate that will exhibit zero stutter on a 60 hz display.
Exactly.
 
The article says that most people won't even notice it, I haven't seen any of the people that have played it already mention it, and apparently it only occurs with cpu players so the online should work fine.
 

Papercuts

fired zero bullets in the orphanage.
Ha ha, I'm glad someone caught that. :p

In the two player split-screen video I actually recruited my wife who really doesn't play twitch games. It was her first time trying Mario Kart and she was struggling hard but in the end did OK. She insisted on using motion control, though.


Exactly.

Hahah, was she the lakitu? It look like she gave up on the airport stage.
 

Durante

Member
I think this is a perfect instance where the inadequacy of frames per second as a measurement shows. What's actually going on is that you have 98.5 percent of your updates with a latency of 16ms and 1.5% with a latency of 33ms.
 
I think this is a perfect instance where the inadequacy of frames per second as a measurement shows. What's actually going on is that you have 98.5 percent of your updates with a latency of 16ms and 1.5% with a latency of 33ms.

happening every 64 frames. So it is a constant phenomenon, and arguably, really annoying froma visual perspective.

Unlike a game having that 1.5% of poor frames at the beginning of a sequence and fat lining.

IMO, I am suprised such a constant stutter got past QA

Pre-order cancelled, Nintendo promised 60 FPS.
I feel betrayed.

As I just stated, this is not the same as consant 59 FPS, (which would not be a problem), but rather a constant hitching like every 1.X seconds
 

Foshy

Member
Isn't 60 fps most of the time 59, XX ?

Well, if a game is locked at 30fps or 60fps, its "average framerate" is technically lower if it ever drops. Say, in a game which is 60fps nearly all the time with only a single framedrop in the entire game, per mathematical definition becomes the average becomes something like 59,999999.

In the case of Mario Kart, it actually seems to be running at 59 fps most of the time. Not that it matters much, obviously, but it's a different thing.
 

KageMaru

Member
The game seems to be a great achievement considering the hardware it's running on. Disappointing they couldn't implement some quality texture filtering or AA. You would think the GPU could handle one of these two at least.

Correct me if I'm wrong, but the point of DF highlighting a drop of just 1fps is not that you'd feel the frame rate difference itself, but the judder it may cause as a result of it breaking sync with your sets refresh rate?

Correct, hopefully they patch it.
 

dark10x

Digital Foundry pixel pusher
I think this is a perfect instance where the inadequacy of frames per second as a measurement shows. What's actually going on is that you have 98.5 percent of your updates with a latency of 16ms and 1.5% with a latency of 33ms.
Indeed. Which you can see clearly on the frame-time graph.
 

Marceles

Member
Great...now when I get the game I'm going to pretend I see a framerate drop like when Link hits an enemy with his sword in Wind Waker and all of the action freezes for a second to show that you've hit it.
 

Adaren

Member
You are welcome to not enter a DF thread in which they present the technical facts about a game if you can't handle seing those technical facts.

DF isn't giving the facts alone. The prose that they use to convey those facts has a tone that offers a subjective opinion.
 

kinggroin

Banned
The game seems to be a great achievement considering the hardware it's running on. Disappointing they couldn't implement some texture filtering or AA. You would think the GPU could handle one of these two at least.



Correct, hopefully they patch it.


There is texture filtering.



And as for the OP, this problem will drive me bananas. If the frame rate isn't locked due to a timing bug related to CPU ai sub routines, it may as well be 30fps with even more bells and whistles.

Pre-order canceled for now.
 
Top Bottom