The Xbox One version doesn't show any sign of tearing, if that's what you mention as "go in the Xbox's favour", perhaps the lock would make it better. Maybe... Skyrim ran okay back in the day, and I spent a lot of hours playing it on the X360, at 30 fps.If it's as simple as that, then run every game with an unlocked framerate. That won't go in the Xbox's favour either you realise? The PlayStation version has a refresh rate lock (at least for some of it), hence why it's either 30 or (very rarely) 20.
But DF also says that Far Cry 4 runs at 30 fps and I can't stand playing it, I can see transitions and "jumps" between frames. Maybe I got used to 60 fps games.
The Witcher 3 is fine. I see those typical framerate transitions in 30 fps games, but it doesn't upset the brain.
This game makes me reaffirm what I have always thought that X1 being a slightly less powerful hardware than the PS4 or PC, is able to run games in a very balanced and solvent way, even if it requires some time, desire and extra talent by programmers. I think DX12 will follow that way, by facilitating the use of hardware for better results with less effort.
Well, I get the basics if that's any consolation. If vsync'ed and *properly* capped the game tries to keep the framerate at 30 all the time, if a frame can't be properly synced to avoid tearing then framerate drops occur, and because the framerate is locked and runs based on multiples, those are more prominent. Basically that's how I understand it. Is that right?I am sorry that you don't understand completely the concepts of frame-time fluctuations or dynamic 20fps cap in cutscenes (you don't spend enough time in this forum! that must be it!). And I really look forward to having the same discussion next year when you'll start studying computer science.
But I'am not sure they'll teach you those concepts in their program...;-)