UPDATE 14/8/14 6:28pm: Yesterday, Blizzard contacted Eurogamer to say that the dual frame-rate issue we uncovered in Diablo 3 was a bug it was looking into patching as soon as possible, and offered to talk us through it one-on-one at Gamescom. Thomas Morgan met up with production director John Hight in Cologne earlier today for a quick chat.
"First off, I want to thank you for going through it, digging through it. As it turns out we do have an interesting bug in the game," Hight explains. "Essentially what's going on is we're updating at 60 frames per second, except on the consoles it's 59.94. Effectively it's like a round-off here - we're updating 59 frames on the first second, and 61 frames on the next [meaning] we're literally double-writing a frame."
So it appears as though elements of the renderer operate at a pure 60fps, while the HDMI standard actually incorporates the legacy NTSC drop-frame standard, running at 59.94fps. The discrepancy is apparent on both versions, but according to Hight differences in the way they handle the rendering account for the more pronounced hit to PS4 performance.
Read more…
More...
"First off, I want to thank you for going through it, digging through it. As it turns out we do have an interesting bug in the game," Hight explains. "Essentially what's going on is we're updating at 60 frames per second, except on the consoles it's 59.94. Effectively it's like a round-off here - we're updating 59 frames on the first second, and 61 frames on the next [meaning] we're literally double-writing a frame."
So it appears as though elements of the renderer operate at a pure 60fps, while the HDMI standard actually incorporates the legacy NTSC drop-frame standard, running at 59.94fps. The discrepancy is apparent on both versions, but according to Hight differences in the way they handle the rendering account for the more pronounced hit to PS4 performance.
Read more…
More...