Various performance issues have been reported with 4.157. Ssnake's post here (https://www.steelbeasts.com/topic/12982-benchmarking-framerates-between-40-and-41/page/2/?tab=comments#comment-193592) and the rest of the thread after that contains a good discussion. Ssnake mentions later in the discussion that a patch is on the way to reduce both RAM usage and VRAM usage with the default settings.
Was it not stated that it had been beta tested?Yes, the last page of the release notes says so. I am disappointed with the number of problems that have surfaced so far, though I am happy that a patch is on the way to fix them.
They can't keep their story straight. On the one hand, Ssnake is saying that he thinks that the legacy TER and HGT files will be included with the next patch (https://www.steelbeasts.com/topic/13011-4157-legacy-map-conversion/page/5/?tab=comments#comment-194209). On the other hand, Volcano is saying that the legacy map files will be coming either with the next full installer or when they can make a legacy map installer (https://www.steelbeasts.com/topic/13011-4157-legacy-map-conversion/page/5/?tab=comments#comment-194210). Note that they are talking about official legacy maps, user-made legacy maps are not uninstalled when you uninstall 4.023.
OK, knowing that a clean install doesn't create the terrain and height folders clears most of it up for me. I think some people don't know what "clean" means. That means uninstalling and removing all personal game files. If you do a real "clean" install, you'll have to create the terrain and height folders for the legacy maps. That might need to be more explicitly called out for people doing a real "clean" install.
Yes, i can used 4.023 version. But what do you see the problem in using 4.1 version? I am really impressed with the effects of the new version. I can organize pre-testing the old scenario.My problem was worry about the legacy maps. Since I am the only person who has been worried about 4.1, and since you can organize a pre-testing of an old scenario, I think we can switch to 4.1.
We have about 2,000 discovered and not yet fixed bug reports. Who knows how many are undetected (it's by definition unknown). Since 2005 a total of almost 7800 bug reports were added to our database, the last 2100 of them since we released version 4.023. Those are the basic statistics. I think we can conclude from this that
a. we have become much better at reporting bugs (now that we have several full-time beta testers)
b. the majority of reported bugs actually gets fixed
c. in each Release Notes document since version 3.0 we have listed bugs "without a bugzilla entry" that were fixed;So, the number of bugs reported per year is about 1,000; for every two reported bugs there's about one without a report number, and, assuming an exponential distribution, for every six bugs that get noticed there may be one bug that goes unnoticed. So, with currently about 2,200 bugs reported we may assume about 550 old bugs still waiting for their discovery (while we're adding new ones in the process of feature development, sigh).
Version
2.654
3.027
4.000
4.023
4.156max BZ
2187
3911
4739
5696
7687non-BZ
83
150
44
83BZ
175
158
85
829ratio
47%
95%
52%
10%Growth
1724
828
957
1991
..which is why I'm not afraid making them public. :)
It's probably even better, actually, since about 800 of especially the older "bug" reports in the database are actually feature requests, not actual bugs. Which might reduce the best estimation of the number of undiscovered bugs by 200, to about 350.
This happens every time SB Pro gets an update. There are quite a few issues. Some even game breaking. This happened to us in the past more than once where we had to all revert to an older version. After such a long delay you would have thought that the beta testing would have been a little more thorough.Yeah, they really need to finish rewriting the code for maintainability. And Volcano's attitude of "Well, I do confess I didn't read any replies (kind of like scenario briefings). LOL" (https://www.steelbeasts.com/topic/12953-free-for-all/?tab=comments#comment-194624) doesn't help.
No software or update is ever released 100% bug free.
4.158, yes. There were a number of issues reported, why wait fixing them. ;)
Other issues will take longer, so there'll be an update some time in September/October, but we want to address the most annoying/easy to fix bugs and oversights as soon as possible.
Hrmpf. Bug fixes without pretty tracers, or pretty tracers without bug fixes?
Or bug fixes and pretty tracers, but only in three weeks.
Decisions, decisions.
All this is clearly still work in progress. I apologize for the inconvenience but we had to stop the endless tinkering at some point and release what we had.
We will now resume the tinkering, thanks.