Same here just to confirm.
EDIT: I've noticed its pushed me onto the normal branch and out of insider build. So I guess this may affect everyone.
Moderators: Balthagor, Legend, Moderators
Same here just to confirm.
That's the piece of information we were missing. Confirmed, thanks.
Too bad that there were no bug fixes but thank you!
I have to disagree on this one. Semantics or not ,and I don't know about the others, but after waiting so long for the update and seeing only some map fixes and content changes I feel rather dissappointed. Especially since we are all avare that this is probably the last update for SRU ever. And I'm not talking about new features and/or engine limitations but things that never worked the way they shoul'd and in every new game I encounter same old problems. Don't want to start another new game to see all that again Don't want to be rude, I'm just dissappointed with this update.
since i can forget about having real basic math in treasury calculation in this game , how about the bug that rails, roads and trenches have an in-game recon value although the equipment file has no spotting entries. is that also a design decision ?
I hear that some of it causes frustration, but I can tell you that we're already working on another update and this one will not take nearly as long. I know that because we're in studio every day now. For the last few years all of us had distractions as we tried to earn a living/get an education. The content of the update is a reflection of the resources we've had available the last while. For a game that is now four years old, additional features are more and more difficult to justify, but even some of those are on our road map.
I didn't say zero bugs, I said few bugs. And this example is never going to be high enough priority to get fixed IMO, I don't even remember what you're referencing. The roads/rails/trenches have no spotting type assigned, so any in-game recon value is a reporting error with no real impact on gameplay.
still wonder why there is even an reporting error - can your tooltip/blueprint reports not read the games unit files ? - sure that it has no impact on gameplayBalthagor wrote: ↑May 30 2018I didn't say zero bugs, I said few bugs. And this example is never going to be high enough priority to get fixed IMO, I don't even remember what you're referencing. The roads/rails/trenches have no spotting type assigned, so any in-game recon value is a reporting error with no real impact on gameplay.
And yes, fuzzy math around large monetary values to achieve better game speeds was a design decision.