Look, ma! I can do it without wheels!
Above is another example of this disturbing graphics issue.
Thanks for the suggestions, but I fear that these cannot be the cause, as I'll explain.
Alpha textures issues.
It could certainly be alpha texture issues, but if so, these cannot be due to problems with shape or texture files. I have been using these trains, on this route, for at least ten years. No changes have been made to any shape or texture files for these trains for at least seven years. These files do not, overnight, on their own, develop alpha layer issues. If these now occur, that must be due to a change in the program.
Memory issues.
The previous version did not have any memory issues. No changes were made to route, trains, or environment, so if there are now any memory issues, that must be due to changes in the program.
Below are the debug HUD details for the two versions (top, new version; bottom, version based on unstable in February). These screenshots were taken at the same play time, same train, same location.
There are two significant differences.
First is the Kb/frame allocation, which, in the old version, is a factor 100 (!) higher as in the new version. I am not a graphics expert, so I do not know what this means, but it is strange and does point to the fact that, apparantly, changes were made to the graphics process.
The other difference is that in the new version, used memory is about 30% more (!) than in the old version. It would be very interesting to know what is causing this significant increase in memory usage.
In all, it is clear to me that the problem must somehow be caused by changes to the program, between February and now. All other elements are the same - same route, same timetable, same trains, same computer etc.
Somehow it is not surprising that I would be the first user to encounter any such problems if these are due to performance issues introduced by program changes. The route is a very large route, allthough it has little scenery. The timetable is very large indeed, with, for most part of the day, over 250 active AI trains at any one time.
But for me, this new version is no longer useable. What this means for the timetable update which I was about to commit, and for any future updates, is not yet clear.
I am very disappointed in the lack of interest of those developers who have been working on graphics changes between February and now, and also of the lack of interest by the OR management team. It seems the problem is considered to be a personal issue, due to my use or environment. It is not, the issue is clearly due to program changes. I just happen to be the first to run into these problems. If nothing is done, I am sure I will not be the last.
Regards,
Rob Roeterdink