4 ms·

> It's completely normal in AAA games to have a few imperfect and in-optimal things. No, mate, stop. The state of C:S2 is well beyond anything we should accept

• Retric 3y ago
  Their point is that specific mesh could be left alone and the game still be playable as long as other issues were fixed. Chances are a nearly complete version of C:S2 was playable and they “broke it” at the last minute by not finishing the optimization process.
  • mvdtnz 3y ago
    That's speculation based on nothing but vibes.
    • Retric 3y ago
      It’s speculation based on these mesh sizes being so arbitrary in the game development process and what’s broken being unnecessarily window dressing for gameplay. It’s the kind of thing that could be delayed to the last minute with some simple placeholder. “Now you might say that these are just cherry-picked examples, and that modern hardware handles models like these just fine. And you would be broadly correct in that, but the problem is that all of these relatively small costs start to add up, especially in a city builder where one unoptimized model might get rendered a few hundred times in a single frame. Rasterizing tens of thousands of polygons per instance per frame and literally not affecting a single pixel is just wasteful, whether or not the hardware can handle it. The issues are luckily quite easy to fix, both by creating more LOD variants and by improving the culling system. It will take some time though, and it remains to be seen if CO and Paradox want to invest that time, especially if it involves going through most of the game’s assets and fixing them one by one.” IE: The the game would have looked nearly complete even if none of these meshes where in use. Meanwhile the buildings themselves are optimized.
      • ethbr1 3y ago
        Agreed. This really smacks of late asset delivery, which probably happened because delivery dates to the rest of the dev team kept being bumped. Then, by the time the assets were finally delivered, it was recognized they weren't optimized (as expected), but there wasn't any time to fix that. Or the same thing with an internal asset team. Although honestly, you'd think after seeing the performance numbers they would have implemented an "above X zoom level, people / anything smaller than this are invisible" sledgehammer fix, until LOD could be properly addressed. Better to deal with pop-in than have everything be unexpectedly slow.
• taneq 3y ago
  What trade off would you choose between fixing a performance issue which is somewhat avoidable and fixing a game breaking crash bug? Because the latter gets priority and there’s never enough time to fix all of those before launch, let alone work your way up to closing out every last frame rate drop.
  • Aeolun 3y ago
    I think if you get 100k poly models in your (city builder) game in the first place (for any but the most amazing wonders) your process has failed spectacularly at some point.
• Guthur 3y ago
  They pay for it they accept it, it's that simple. All this crying when they could have simply returned the product or not buy it at all. Colossal Order themselves warned about the performance before it was even released. There were plenty of reviews that said the same thing. So to get up in arms about the performance means they are just being exceptionally stupid and entitled, and they should just grow up and stop crying over their toys. Colossal Order can release whatever garbage they want to. And you can choose to buy it or not, or even buy it and return it (fight for better return policies if you want something positive).
• dingnuts 3y ago
  Good grief, I have a mid tier AMD card and I'm having a blast with almost 40 hours in the game already. Can we quit with the "defective" propaganda? The game runs fine and it's really fun. This "controversy" really drives home for me how detached from reality online discourse often is
  • hwillis 3y ago
    The most common GPU on steam stats is a 3060. The AMD 7800/7700 do 90% and 70% better on benchmarks. So if you have either of those, you're getting nearly twice the FPS that the most common steam user would see.
    • squeaky-clean 3y ago
      I'm running on a laptop 2070 and doing just fine. Calling it defective is just blatantly lying. It should be better optimized, but calling it "defective" does nothing but make people dismiss your comment.
    • beowulfey 3y ago
      I have a 1660Ti. I get 40+ fps on 1080p. It's functional. Now, whether it is really any better than the previous generation is the more relevant question in my opinion. There are a few things improved, and a whole lot missing. The performance issues are only a small fragment of the game's issues.
      • red-iron-pine 3y ago
        yeah this here is the real point. runs alright for me, too. just alright, but for what it is that's fine. however it's not really much better than the predecessor, and needs to give me a reason to give up on the HUGE mod community and well documented approaches from CS1.
  • unaindz 3y ago
    It works on my machine
  • 3y ago
• johnnyanmac 3y ago
  you're missing the forest for the badly rendered tree in some E3 showcase that everyone nitpicked to death. Can we not treat this discussion like a Reddit rant, please? Gamedev has many shortcuts, and some things simply fall through the cracks. Some are caught and fixed, some are caught and not fixed, some just aren't caught at all. I imagine it's the 2nd case here; There's a unfortunate large amount of bgs these days caught by QA but not given time to fix before publisher mandates.