This is driving me round the bend

This is a data corruption issue. I found an earlier backup made before this issue occurred and restored it. The problem doesn't exist in this area, or causes the rest of the route to suffer from the problem.

Since I have backups of everything, I'm going to perform some surgery and extract the working part and insert it into the broken route and see what happens after removing the faulty section of course. I'd hate to go back to the older route because I've made some route changes that took me a very long time to implement.
Probably not a good way to fix it, however have you tried to merge your route to a new created route. What I suggest is try to make a new route and merge your current route to that and see if anything happens. A person I helped some time ago had a problem where all his tracks were not showing, switches and everything, also a corruption problem, and this helped in the end.
 
Probably not a good way to fix it, however have you tried to merge your route to a new created route. What I suggest is try to make a new route and merge your current route to that and see if anything happens. A person I helped some time ago had a problem where all his tracks were not showing, switches and everything, also a corruption problem, and this helped in the end.
merging routes is not an option in TRS22+ Versions you have to use Iportals to send trains back and forth to thee other route.... Merging actually eats more memory up than what it used to do before 19 and 22 came to be.. the Devs Broke being able to Merge route at least for me it still doesn't work like that..
 
Probably not a good way to fix it, however have you tried to merge your route to a new created route. What I suggest is try to make a new route and merge your current route to that and see if anything happens. A person I helped some time ago had a problem where all his tracks were not showing, switches and everything, also a corruption problem, and this helped in the end.
That is something I was going to try today before I did anything else. I've had that fix weird issues before, besides I hate the alternative brute-force method.
 
That is something I was going to try today before I did anything else. I've had that fix weird issues before, besides I hate the alternative brute-force method.
I have been fixing issues around the community for the last couple of years. You are the veteran tho. I am very active on discord as there you can also voice chat and send message replies and images easier than here. If you end up doing the brute force, maybe we can look together before, maybe we can find an alternative.
Maybe look in task manager and see if before the drop the memory usage is increasing or the gpu usage.
 
merging routes is not an option in TRS22+ Versions you have to use Iportals to send trains back and forth to thee other route.... Merging actually eats more memory up than what it used to do before 19 and 22 came to be.. the Devs Broke being able to Merge route at least for me it still doesn't work like that..
We were talking about route merging to a an empty one to fix the issue, not send trains.. Maybe you refer to something else
 
I have been fixing issues around the community for the last couple of years. You are the veteran tho. I am very active on discord as there you can also voice chat and send message replies and images easier than here. If you end up doing the brute force, maybe we can look together before, maybe we can find an alternative.
Maybe look in task manager and see if before the drop the memory usage is increasing or the gpu usage.
I didn't have a chance to test this yet because I had to go out to a cookout. It's that time of year and a rare comfortable day too.

Before I left, I removed some road bridge splines and my tracks remained in place afterwards. Just for kicks I went into Driver and got 5.6 FPS instead of 20 to 26 FPS I was getting before. The buildings flash on and off which makes me think the old dmdrake buildings are really bad models, as good as they were in their day, and it's time to find a replacement for them.

All and all, I think it's a combination of assets in this area that are bringing the route down now. This started as stutters back in early July and progressed to where it is now. At the time, I did find some broken assets but I don't think all of the data is bad.

Thank you for the offer to help. I'll keep this in mind once I reach my virtual brick wall with this route.
 
Back
Top