It's not the communication about specific plans or news - it's the fairly complete silence that I suspect bothers many people.
I agree they need to talk soon and looking on the time frame it should be sth like that they announce update 2 with some prelim patch notes. They really need to turn around their communication which somewhat started okayish, but went a bit awkward with the silent DLC and more...sorry, but i expect more
What you are seeing on SteamDB is internal updates for the developers. An actual update will come with patch notes released by Frontier and will also be listed on SteamDB as a Hotfix/Patch etc. When you see an "Changelist" with a bunch of numbers, they are not public updates.I've been looking at the SteamDB updates. But my question is, how do we know if they've fixed the thing that caused my crashes. (Snap kit interactions) I have been avoiding using them because thet could cause a consistent crash.
The advantage of patch notes is that I know what they were working on so I can test it again.
I am happy with the game, I have had a few crashes, but I would simply ask for a list of places they were working on so I can that's the versions fully.
If you are right, then either their PR Team is still on holidays, they are drastically understaffed or they are doing a bad job.Im going to speculate and predict the update coming this Thursday the 16th. Each update has come on a Thursday so far and Frontier said they were looking at an update in early January. I would concider Thursday Januray 23rd or later to be mid/late January. I could be and am possibly very wrong tho!
You are welcome. SteamDB has no affiliations to Steam or Valve in any way. And is simply tracking changes made on Steam. This could be anything from internal updates for development, all the way to a change in review scores etc.Thanks for the clarification. First time diving into this kind of stuff on Steam DB
I dont understand why they feel the need to wait and release a big patch rather than pumping out small but often bug fixes. Seeing a patch every week or so, even small ones, would be enough for Frontier to be as silent as they wish. Once you squash a bug, ship a patch.If you are right, then either their PR Team is still on holidays, they are drastically understaffed or they are doing a bad job.
The Game got a bit of 'reviewbombed' in the last 30 days, mostly because of the DLC, since then it has been radio silent from Frontier. I understand the holidays and everything, but this would be drastically not trying to mitigate the bad reviews, by sending out: "yeah we are cooking on the following: ....", especially, if they are so close to patchrelease. Silentdropping isn't a thing anymore: Most games hype up their patches by communicating and tieing the knot with their community.
Those moves make them actual look a bit amateurish like a small indie developer and not AA-Game Company.
You are welcome. SteamDB has no affiliations to Steam or Valve in any way. And is simply tracking changes made on Steam. This could be anything from internal updates for development, all the way to a change in review scores etc.
I dont understand why they feel the need to wait and release a big patch rather than pumping out small but often bug fixes. Seeing a patch every week or so, even small ones, would be enough for Frontier to be as silent as they wish. Once you squash a bug, ship a patch.
Testing is what they should have done before releasing the game. Then they wouldn't be needed to fix as much afterwards (incl. bad reviews)...Testing. You want to make sure everything runs fine. Fix a bug, create another. This is sometimes the dev daily business. So after you did this and you did your part.-
...
When it comes to game breaking bugs that stop people playing the game, it is better to ship regular updates even if they introduce new bugs. You then fix those new bugs and keep going till the game is almost bug free. There is no reason to take so long to patch bugs that are causing people to not be able to play at all.Testing. You want to make sure everything runs fine. Fix a bug, create another. This is sometimes the dev daily business. So after you did this and you did your part.-
"Nvidia drops a new driver and it f's up your engine, then you need recode this and that.
Oh we are experience crashes on intel GPUs? Let's fix that. Damn, we are now not using the full power of AMD CPUs and the game slows down on them. Now we can release this single fix, oh wait the Xbox series S slowls down again, we need to adjust that."
I know most users just see the change in value, but every single change can create a load of issues somewhere else in your code. They are doing 3 Forks and especially PC can be hellish since hardware isn't standard in PCs. All the Steamdb updates for today could just be updates for the MSI RTX 2060 Super, cause they may encountered an issue with exact this card (and only this card)
The first and foremost target of every dev is a stable release and they aren't so easy to achieve as many of you think.