Eldorado.Railroad, on 02 August 2023 - 02:29 PM, said:
1. Have you rebooted your O/S (cold)? Win10, forced update break things?
2. Failing hardware, RAM, GPU/RAM?
3. To narrow down what caused this you might have to do a bit of a binary search through the various testing releases, to see where it fails.
4. I, have looked at your log file, there is a lot of stuff being loaded at start up. Any bug(s) in the timetable data?
5. I keep my viewing distance way down, ViewingDistance, to about 2500 meters, this might help.
6. Things should not be broken like this, without an explanation. Sometimes we have to dig deeper to find what developer pulled what source and mangled things. That kind of inquisition could/may get sticky. Be prepared for some friction.
7. Maybe the answer is simple. Too many render primitives, etc? Some OR registry setting got flipped?
8. It is too bad that "upgrades" break things, and keep on breaking things. I do not like that. Often I just stick with some version and do my testing/experiments from there. But you have been with this project for many years, so I think you would know that.
Steve
Re. points 1, 2, 4 and 5 : these can be discarded as both versions, old and new, are running now, in the same environment, using the same settings and data etc. So if any of these issues were the cause, both versions should be affected in the same manner.
Re. point 3 : see below
Re. points 6 and 8 : yes, I know - been there before.
Re. point 7 : it looks like that, but what has been changed to cause this?
cjakeman, on 02 August 2023 - 11:32 PM, said:
Good advice, Steve, but we don't keep all the Testing Versions (although this is changing). However we do keep
all the Unstable Versions, so the first step would be to find the last Unstable Version which doesn't have the problem and the first one that does.
If you can do that, Rob, then we can work through the PRs to see which one made the difference.
Sadly, that's not possible. I have worked on the new update for months, it comprises over 2000 lines of code changes. Also, the full timetable has been adapted to the new version, adding new commands to a very large number of trains, which took me weeks to complete.
To insert all those patches in previous unstable versions would be an immense task. Given the time required to set up the test for a specific unstable version, start the timetable and run to the required time which properly shows the problem, it would take at least a day for each unstable version to test.
To revert the timetable changes so it could work with the unaltered code would also take quite some time.
Due to the problems I had with GIT (as I explained elsewhere), I have allready spend months on this update, not making any progress, but simply to get things sorted out so the changes could be committed and made available to others. I am not going to spend some more months on this to sort out problems which are not of my making.
I can commit the changes to the latest version and leave it at that. I have a proper working version with which I am happy. We can then forget about this whole issue and pretent it does not exist.
Sorry if this sounds a bit harsh, but it's not the first time I am making efforts to share my progress by committing my latest changes, only to run into all kinds of issues which I have nothing to do with, but which take up a lot of my time to sort out. I do find this all rather frustrating.
Regards,
Rob Roeterdink