• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

CD Projekt RED Hacked, Attacker Claims to Have "Cyberpunk 2077" and "The Witcher 3" Source Code

If a problem occurs for one in a thousand players, you're still going to have thousands of loudmouth YouTube kids screaming about it like someone took their lollipop. This is low-brow, primitive attention economy at it's worst.
I honestly don't care what a bunch of adolescents scream about on YouTube.
I'm talking about the nature of some of the bugs. Those of us who have worked with graphics programming for many years got a good sense of understanding a bug just by observing it, and be able to tell if something is e.g. a shading bug, culling bug (there were some of those too), a synchronization issue or a flawed physics in the game simulation, without being familiar with the code base. Quite often, small graphical glitches are more an annoyance, while flawed game simulation often can be "game breaking".
Sometimes you can observe how well the game simulation is made by running it on a CPU that's barely fast enough. If you start to see objects flying around as a result of stutter (CPU limited, not GPU limited), it probably means the engine is using time deltas for calculating acceleration. Or if stutter causes objects to go through each other, fall through the ground etc., that probably means the simulation has "skipped" a few iterations. Both such examples are evidence of poor engine design.
 
Back
Top