I have been reading all the messages regarding issues and problems with build 114800. I am running Trainz TR2019 plus. I guess I am fortunate in that all the routes I run work without a hitch. I was a beta tester so several issues along the way, so I submitted a bug report and they got fixed.
However I probably use only 30% of the functionality of Trainz so some of the issues identified would not even cross my radar when testing. It may be the same for other beta testers. As an example there were several apparent problems with in-cab controls. I have never used them so I didn't think about testing these.
There apparently were problems with reversed engines, but that apparently only affected people not using Trainz plus.
I don't know how many people are involved in beta testing. I do know that several weeks before build 114800 went public there were no major issues discovered and reported (show stoppers), hence the decision to go public. So one conclusion is that build 114800 is performing well for the beta testers.
Another conclusion may be that the beta testing process needs to be broadened to get a more meaningful sample of users who have different versions of Trainz (Plus, Platinum, Basic). Also there may be a need to include people who are really pushing the game to the limits and would be the most likely to find errors in scripting etc. One of the big issues identified and fixed was the portal issue which exist in build 111951. Along with this issue was a problem with the Central Portal Control, which was identified and fixed.
Trainz is a very complex simulation program and N3V has done a great job in moving it along. I doubt whether the programmers spend a lot of time building and running routes. They need more help in identifying these issues so that they can be fixed. The question really is how does that happen?
However I probably use only 30% of the functionality of Trainz so some of the issues identified would not even cross my radar when testing. It may be the same for other beta testers. As an example there were several apparent problems with in-cab controls. I have never used them so I didn't think about testing these.
There apparently were problems with reversed engines, but that apparently only affected people not using Trainz plus.
I don't know how many people are involved in beta testing. I do know that several weeks before build 114800 went public there were no major issues discovered and reported (show stoppers), hence the decision to go public. So one conclusion is that build 114800 is performing well for the beta testers.
Another conclusion may be that the beta testing process needs to be broadened to get a more meaningful sample of users who have different versions of Trainz (Plus, Platinum, Basic). Also there may be a need to include people who are really pushing the game to the limits and would be the most likely to find errors in scripting etc. One of the big issues identified and fixed was the portal issue which exist in build 111951. Along with this issue was a problem with the Central Portal Control, which was identified and fixed.
Trainz is a very complex simulation program and N3V has done a great job in moving it along. I doubt whether the programmers spend a lot of time building and running routes. They need more help in identifying these issues so that they can be fixed. The question really is how does that happen?