Rendering Thread Exception Batman Arkham — City

And he knew, deep in his code, that the Joker would never throw that error again.

Batman walked through the frozen polygons of Arkham City. He walked past the Riddler’s frozen green question marks. He walked up to the Joker’s frozen, half-deleted face. He placed a hand on the corrupted mesh.

Batman stared at the code. It wasn't the error that bothered him. It was where the error had happened.

Batman tried to grapple to a higher ledge. The grapple line fired, but the physics engine stuttered. He landed mid-air, floating. "You're a memory leak." rendering thread exception batman arkham city

admin forceauthor true

"You're not a feature," Bruce whispered. "You're a variable. And variables can be re-assigned."

He had two options.

"Bats?" he said, his voice normal again. "I feel… peculiar."

The Joker blinked. His mesh re-compiled. He looked down at his hands—solid, rendered, sane.

He raised his arm. Not to fire a batclaw, but to open the developer console. He typed a single command. And he knew, deep in his code, that

The world froze.

Option one: Force quit. Pull the plug. Let the Joker’s corrupted process die. But with it would go eight years of predictive data. Every pattern. Every contingency plan. The war on crime would reset to zero.

Bruce felt the warning. flashed again, but this time, it was recursive. The error was calling itself. The stack was overflowing. If the simulation crashed while his consciousness was still linked, the neuro-feedback would fry his prefrontal cortex. He walked up to the Joker’s frozen, half-deleted face

The rendering thread resumed.