I play a lot of city builders and so long as the UI is still smooth I really don't notice any gameplay difference between 30fps and 60fps.
I put 8 hours into Frostpunk before realizing I was limited to 30FPS.
But it's the fact that these figures are being seen with the most powerful consumer graphics card (on a brand new unpopulated game map) that's the problem.
Again, this is a simulation game. If I ask the game to spit out more detail and graphics than can be physically supported by today's technology, I guess I don't necessarily see this as a design fault.
Why enable those heavy, performance crippling post processing filters by default?
From what I can find in this comment section, and I guess this has to be taken with a grain of salt, performance doesn't scale. It seems we max out at 50fps on a beefy 13th gen Intel with the fastest GPU available, but then there's a couple comments with mid-range hardware where performance is nearly identical.
To be clear: I had to turn the quality down to much worse than I recall Cities Skylines 1 looking in order to get worse performance than Cities Skylines 1.
The major complaint here is not "I cannot max the settings on my mediocre hardware", but rather "I cannot mediocre the settings on my max hardware"; the performance is bad at any level, but my hardware, while not top-of-the-line, should be able to run a game like this at 4K playable, or at 1080p while looking awesome and running great. Instead, I get 1080p with a mix of medium/low settings in order to get it looking pretty okay in most aspects.
This assumes Cities Skylines 2 is using some next gen graphics technology when in practice it is a Unity game without any cutting edge graphics. Another comment mentioned they are doing 10k+ draw calls per frame - it's just poorly optimized.
As a city builder it has not just dynamic geometry (which makes graphics optimization more challenging) and lots going on on screen like DSP, but also a complex agent based simulation of a city, its transportation, its economy, and individual agent AIs. It is far more complex than most games despite not being graphically intensive. And do note that as far as cities builders go, it's also one of the most ambitious graphically. My personal opinion is they deserve some slack as long as the game continues to improve.
Yes, scalability towards the future is good -- but not at the detriment of player performance now.
If the player base doesn't stick around during our current dark-times medieval technology stack, there won't be a player base when we have whatever future tech makes it playable -- see the problem?
You're forgetting the increasing popularity of the Steam Deck where even 60 FPS is a luxury.
The Steam hardware survey suggests otherwise to my eyes; it's often easy to forget working in tech that a lot of Steam customers have relatively shit hardware:
https://store.steampowered.com/hwsurvey/Steam-Hardware-Softw...
While they don't track monitor peak supported refresh, just looking at the rest of the results suggests to me high-refresh gaming (over 60FPS) is going to be relatively niche at best. Lots of PC gaming specs I take for-granted on my own builds or consider "average" are actually not that common.
I absolutely agree 60fps should be considered the floor for most modern PC games running on "reasonable" hardware though, 30fps belongs to the past.
I wouldn't read too much into these stats.
This is probably one of the best public sources of data we have on the topic of what hardware actual PC gamers are using.
Woahhh
A bit unfair since most people aren't gaming at 4K (Steam hardware survey puts it at 3.29%), but still
Well-compensated people (like engineers) are more likely to own a 4K monitor and high-end GPU, so I meant to convey that there's probably a large overlap with the type of people who play city builders (like engineers), so they really should have accounted for that.
It was only after I bought my 4K 120Hz OLED that I found out how popular they are for sims, including pinball. It's been awesome.
30fps is fine for lots of games. Especially for stuff that doesn’t require super twitchy gameplay.
If somebody really cares about 60fps or 120fps, fine. But the developers have some effects they want to implement, and if some of them don’t fit into 8.3ms, let those of us who don’t mind 30fps enjoy them, right?
I remember easily getting frame rates far in excess of my monitor's top refresh rate back in 1999.
Undervolting also reportedly works really well in laptop nvidia chipsets, FYI.
But if that's with an empty map, it's an ominous sign for people who plan to build a city in this city building game, as rendering usually slows as polygon count increases.
And if it's with an $1800 GPU, its an ominous sign for the 99.3% of gamers who don't have an $1800 GPU.
And if that's at 1440p - well, I'd wager a lot of the folks with a $1800 GPU also have a 4k screen.
> I put 8 hours into Frostpunk before realizing I was limited to 30FPS.
Yes, and I have beaten games that rendered improperly at sub-30FPS as a kid, because the requirement was 16MB of VRAM, while my card only had 8. But that's just as irrelevant to the point being made.
The problem is that we're talking about the absolute highest end consumer card sold by nVidia rendering a blank map, without such a framerate lock in place. If it's not locked, then that framerate is the product of a performance bottleneck somewhere. With a modern gaming PC, "performance bottleneck" also means you're sitting next to a moderately powerful space heater.
Games get mocked for locking to 60hz, 30hz would get them laughed at outright.
In my experience 30 FPS is perfectly fine for a game like this, I'm not sure what do you mean about "scrolling" ?
It's the much more fast paced, mostly first person games that really need those 60+ FPS...
A top down city sim 'scrolls' up/down/left/right around a map, which is a movement that is strongly associated to screen tearing -- which i'm not really sure is a relevant thing to bring up given the variety of v-sync options available.
Even a game locked at 30fps that 'scrolls' often shouldn't experience significant tearing with the options out there.
Considering something like Simcity 2000/3000. Visual update is probably in single digits FPS most of the time, but the input cursor is very smooth.
Blur Busters explains:
Regardless, the problem is blown out of proportion. I think we can give it some weeks and 4090 performance issues will be in the past.
LOL. You just proved my point.
But also, yes, even in a city builder low for is very annoying when you're used to the smoothness of 100+.
The only workaround I can think of that wouldn't also defeat the point of having VRR would be to add some in-engine low framerate compensation artifically boost the reported framerate to a multiple of the real framerate, but I have yet to see any games that actually do this.
4K 16:9 3840 x 2160 = 8.29 million pixels (1.00x)
1440p 21:9 3440 x 1440 = 4.95 million pixels (0.60x)
1440p 16:9 2560 x 1440 = 3.69 million pixels (0.44x)Whats more, such simple filters should not tank FPS so dramatically, even with a severe CPU bottleneck.
Well thats very subjective, as I usually can't stand TAA and like SMAA.
60 hz has always been the bare minimum any display supports, so if any game is picking something below that then something has gone horribly wrong. But really, games should be using the current desktop refresh rate as the default, because you know it's supported and makes things like alt+tabbing considerably faster even in exclusive fullscreen.
Reading Reddit and going down to 1080p mediumish with depth of field turned off and it's fine, 30fps. It's a very fun game!
I have absolutely no idea why they didn't turn the defaults down. It would have been a 5 min config change surely and the impressions of the game would have been vastly vastly better.
It does look terrible for me though, despite being fun. The shadows are terrible and there are loads of rendering glitches.
I'm also a bit concerned now my city is getting bigger at how poor the traffic wayfinding is. Seems to be as dumb as CS1 (with no mods) which is really bad, with the added nuisance that the traffic cycle seems to be basically 0 cars until rush hour then a massive flood of traffic.
It's actually quite ironic that all I really wanted from CS was faster performance in bigger cities (huge fail from CS2 here), better traffic simulation (jury is out but isn't looking great) and better road tools (this is what cs2 is great at).
They should never be so intense.
Some shaders unintentionally scale nonlinearly with resolution, and I'm thinking that may be the case here.
I don't really like DoF anyway :P
Isn't that just LOD, and is done regardless of whether dof is enabled or not?
What?!? No it doesn’t. It uses the depth buffer to progressively box blur or gaussian blur the frame post-render.
https://lettier.github.io/3d-game-shaders-for-beginners/dept...
Nowhere are they replacing models, replacing textures, or anything of the sort. I suspect the issue here is that box blur with a sampling of 3x3 is exponential performance hit at 4k vs 1080p. By a factor of 8x due to the extra sampling lookups.
It's usually a pretty obnoxious effect even in action games, the first thing to turn off if the option exists...
Fast action doesn't turn into a shaky smeary mess, and there's no '24fps camera panning' judder as you look around
At 24fps motion blur in games or 3d movies is bad. But at 120fps or more motion will never look well without it.
Even in the 90s, the developers of 3D arcade racing games were well aware of this, ensuring that the original arcade versions of games like Ridge Racer, Daytona, and Sega Rally ran at 60fps, rather than sacrificing that smoothness to add more detail. And those games looked spectacularly good for their time.
"My Ryzen 7 3700X and RTX 3080 were able to handle it okay on just shy of max settings"
It _seems_ okay around 1080, but then you realize there's almost nothing going on and it's only doing ~60FPS. It'll choke on anything remotely complex.
The project manager said "Not high priority for launch", then closed the ticket.
The site none of us can read probably has more info about this being a RTX 4090 quirk. And it's not exactly surprising the dev team wasn't optimizing for RTX 4090, and the quirky reaction here would be justified if they were.
NVidia absolutely changes the assembly language rather dramatically between iterations. That's why the code is in NVidia PTX (or HLSL / Microsoft's DXIL, DirectX Intermediate Language), and then recompiled to actual GPU assembly each time you install a game or run the code on a different system.
Perhaps back in the very early accelerator days when everyone was making GPU-specific hacks of Quake 1 but even that was smoothed over by the transition to DirectX/OpenGL/GLiDE at the time
Two years later: "WE NEED TO RELEASE THIS TOMORROW. JUST MAKE IT BUILD AND SHIP IT!"
Quill18 had a live stream the day of release (Oct 19) and it seemed fine (2h10m in, after some Galactic Civilizations 4: Supernova) from what I saw:
* https://www.twitch.tv/videos/1954873419
Various other live stream days, as well as a separate Youtube series:
The big ones are paid cash, and before they stream they've already had a team working with them, covering what exactly they do or don't want shown and talked about - and if there are any technical problems, they've been worked out, which may even include special builds of the game.
The smaller ones are "partners" who get access to the game earlier than purchasers, zero-cost items for giveaways, and some access to game publisher staff - but only if they play by the (NDA'd) rules of the publisher, and those rules usually explicitly say "do not say anything negative about the game."
Before it was released, they told everyone that the game was not optimized graphically, and the minimum specs were already high. It was quite clear that there is still more work to be done to get it in a better state. So, not sure why you have this "cynical" take. This isn't something they are trying to deceive people with. I'm not even in the market to buy the game, and I know this.
This is made up drama.
It will just be lots of these things that need to be found and corrected.
lots of ways. It is very easy to do things which affect performance negatively.
Once you're sure about what you're doing and the data that you're drawing to the screen, then you can start optimizing things so that performance goes up.
Colossal chose to release when they did because they promised to release on that day. The game isn't done, and they've said this.
I had to set my resolution to 1080p in order to get anything remotely resembling performance (this change alone took main menu FPS from 5 to ~55), plus disabling motion blur, depth of field, and volumetrics, and turning model fidelity down. I've also heard that disabling vsync can make a huge difference, but it didn't affect things for me.
I don't want the UI to look horrible on my 27" 1440p monitor.
So if I have a budget PC, I should be content with running this game at Nintendo 64 resolution? Or I guess it's on me to fork over $1,000 for a high-end GPU if I want to run it at 2/3 the resolution of a midrange mobile phone, as you suggest.
A lot of games run poorly during most of the development process, performance and bugs get fixed in the last stages. But when the publisher forces a premature release this means the fixes have to be done in the months afterwards. See Cyberpunk 2077, Mass Effect Andromeda, Battlefield 2042 and countless others. And this will continue to happen as long as gamers keep preordering.
Vsync locking frame rate to half of 100Hz?
> I have a 13900k, 64GB of RAM, and a RTX 4090, playing on a 1440p ultrawide monitor. I got 35fps at the main menu and in game on a brand new map w/o building a single thing. Turning off motion blur and depth field increased this from 35 to 50fps. Not a single other graphics setting changed the performance at all. I turned off every single setting I could or set it to the lowest possible, and still only got 50fps.
How can a game even get to this point? Everyone in the development process must have noticed that it was running poorly. Even if all the developers had the most expensive consumer GPU available, they still would have seen poor performance.