I don't think that it needs a "remaster", but more places like the island on the other side of the bridge, more streets, a harbour, an airport... Some stuff like this but not a total remake
FidelityFX and DLSS are different approaches to the same solution. DLSS uses real hardware cores to run a deep learning AI algorithm, producing a very good upscaling result. This improves FPS greatly by allowing the user to render at a lower resolution with little to no loss in quality. However, because it requires specific hardware, it's not compatible with anything but new cards with that hardware. It's also harder to implement the software (iirc), limiting its immediate potential. FidelityFX also upscales the image, allowing better FPS for the same reason, however it uses more traditional upscaling methods, albeit improved upon what exists already. This means more cards are able to be supported due to it not requiring specific hardware, but the quality isn't as "good" as DLSS. It's also much easier to implement, as it's already built in to beta branches of Unity and Unreal engine, two very popular game engines. All this to say neither is necessarily better, but have different use cases/ users in mind, to come to the same solution. It's possible .drive could implement FFX, which would mean a possible FPS boost for those with newish (last couple years) cards.
i think one bit of WCUSA that might get more attention is that industrial area near the race track. there's an intersection that just leads straight into a fence, which makes me think there might be a new bridge or something. im sure you guys have seen it.
Obviously not every post by a dev is development, but still... First testing of a scratches system, and dynamic / localized windshield damage? (also wiper damage?)
gabester makes music not just for the game, you know. Judging by the file names, it's from soundcloud.
I once again forgot to update my spreadsheet so here it is late after the party. It's been 2 updates that the devs managed to release a big update in less than the usual 120-130 days. Maybe they reorganized internally to work faster or maybe a ton of other reason but I think we can expect to see updates faster than we're used to (that's why the estimated date isn't an accurate date because the average time span is higher than what we can expect, so I reduced the estimation date).
I personally added 100 days from the 30 June to the next update (because the last two update were released 104 and 93 days after the previous one) and we get 8th October... So yeah, I'd say that 0.24 is coming on the first half of October, except if it's a specifically huge or small update