Recently, as a result of a conversation in an MSTS thread, I've been testing a long activity (057 Down Manchester Pullman) in the Thames - Mersey route. About an hour and a half into the act, various missing sms messages were displayed and some scenery and track textures were not being displayed.
It appears that OR has the same problem in that after about the same length of time, AI trains and some station buildings have just a grey texture! At the same time, the Key display (throttle, brake, F6, etc) weren't shown on the screen, although they did still work; also, the screen capture didn't work. The run was able to continue for about another 20 minutes until a "Stopped Working" message was displayed.
This has been reported to OpenRails (bug 1206693) and I have received a reply that it's very similar to a bug already reported (1191966), also involving a resource heavy route. Apparently, it is because of the 2GB limit applicable to 32 bit programs - OR uses 32 bit elements within it's construction. Unfortunately, saves being currently taken (at least on my setup) are reported as invalid and unable to be used; they MAY have solved this problem.
I ran the Large Address Aware (laa) program to set the flag in OpenRails.exe in the hope that it may help .... it didn't
It would seem that we are stuck with this problem, unless OR can be made completely 64 bit! In the shorter term, solving the 'save' problem may give a way out of it.
This is not a plea for help, but a report on my experiences. However, I would be interested to hear of others having similar problems.
An afterthought - I wonder if applying the LAA to RunActivity.exe instead of OpenRails.exe would help ?
Cheers,
Ged
