RoboCop Rogue City logo

Teyon is looking into fixing the shader compilation stutters in RoboCop: Rogue City

A couple of days ago, NACON released the PC demo for RoboCop: Rogue City. Developed by Teyon, the team behind Terminator: Resistance, this new RoboCop game has a lot of potential. However, the demo suffered from major shader compilation stutters. And, thankfully, the developers are looking into resolving them.

As NACON and Teyon stated:

“We want to address the performance issues you’ve been having in the last hours on the RoboCop: Rogue City Demo. While this was unforeseen, please rest assured the teams over at TEYON are working on fixes as we write these lines, and we’ll hopefully be able to stabilize the situation in the upcoming days. It would seem the source of the problem comes from shader compilation.”

In RoboCop: Rogue City, you’ll become the iconic hero who is part man, part machine, all cop. As such, players will attempt to bring justice to the dangerous, crime-ridden streets of Old Detroit.

The game promises to also feature iconic locations from the first movie. For instance, you’ll be visiting the Police Station. Nacon and Teyon also claim that players will be able to solve cases (by not showing their enemies).

NACON plans to release RoboCop: Rogue City on November 2nd.

Stay tuned for more!

4 thoughts on “Teyon is looking into fixing the shader compilation stutters in RoboCop: Rogue City”

  1. i love it when a developer listens and acknowledges that there is a performance or stutter problem. But even better that they COMMUNICATE that they are on it and going to fix it even before the game comes out.
    Thats the passion a lot developers miss, and only care about money and deadlines.

    Great job from the Robocop developers!

    1. Eh, maybe not. You see shader compilation stutter only happens the first time you encounter a certain shader, so if they tested the demo on the same machines they are developing the game on there would be no stutter – the driver has already compiled and stored those shaders. And it’s completely normal for game engine editors to stutter randomly for all sorts of reasons, so when the devs encountered the original stutter they wouldn’t think twice about it. So to amend what you said:
      Literally just play it once on a machine with empty shadercache.

Leave a Reply

Your email address will not be published. Required fields are marked *