PC Gamer

Microsoft talks Crackdown 3 PC's unlocked framerate, ultrawide support and modding potential

Wes Fenlon
 

I've played Crackdown 3, and wrote that its campaign feels straight out of 2007 in mostly fun ways. I didn't write too much about the PC version, but from what I saw it's almost all good news. The PC version ran well, with no slowdown or other issues in my experience, and out of the box had sensible key bindings—something recent games like Anthem and Fallout 76 have gotten wrong. After my demo, I chatted some with Xbox Studios' head engineer Brian Stone and Crackdown 3 head of production Jorg Neumann, who gave me a few details about the features the PC version supports.

Even given the power of the Xbox One X, the PC version is going above and beyond. "We used Gears 4 as the model of a really well-done PC version," Neumann said. "Brian was actually instrumental in deciding on the features, ultrawide and all that stuff, and we hired a specific developer for the PC version to help us. Double-11 has done an awesome job focused on the PC version, and I think it shows.

We're all really proud of it, frankly. "Stone told me that Microsoft put "dedicated design and engineering against mouse and keyboard controls" to get them right and made sure that it supports various ultrawide resoultions, including the extremely wide 34:9. And it supports unlocked framerates, including in multiplayer, which is especially a challenge because the mode supports crossplay with consoles. "That takes a lot of careful diligence on our side to make sure that it doesn't break the multiplayer experience when we're playing with devices with different capabilities," he said.

If you've ever wondered why certain games support unlocked framerates and others don't—or why that feature couldn't simply be patched in—Stone gave me a nice high-level explanation. "It goes to the decisions that you make very early on in development. If you start with your engine design so that the simulation is unlocked from the presentation layer, then you're pretty well set-up to be able to unlock framerate later on. If you don't have that as part of the sort of starting point of your engine architecture, then it becomes almost impossible to do that later.

Now in our case we're using UE4, which does have that as a core tenet of the architecture, and so all we really had to do was make sure that as we built on top of that, we weren't making any decisions to break that. … So it's important to hold onto that throughout the development lifecycle, that effectively 'present' and 'sim' are separate ticks, and can execute separately. "Any game that tied animations to framerate didn't follow that advice.

Read full article