A DBR shouldn't have destroyed the route. That means there's something else going on, or it was corrupted all along and that explains why it kept crashing when you worked on it. The program would reach that part in the code where the route is corrupted and would crash.
All is not lost, though.
Try reverting instead of opening. That will bring you back to the last successful save rather than loading the corrupted version. This may not work if you opened up and resaved the corrupted route.
If that doesn't work, we can restore the route and or session from the backups folder. It's a bit more complicated than it should be, but it's not difficult to do.
- Check your backups folder located where your data is installed.
- Click on the Launcher then Trainz settings, then on the Install tab. Take note of where your Trainz data is stored. By default, it's in C:/Users/ (your login name)/App Data/Local/N3V Games/TRS22/Build-something. The Build-something is that Build folder with the various letters and numbers in the name.
- Open that folder in Windows Explorer and then open the Backups folder. In that folder are various sub-folders with dates for their name.
- The current folder is named: 23-07-29. (You may want to go back prior to this date. It may mean you've lost your current work but at least the route and session will still be there.
- Open that folder and look for the .tzarc file with your route-name and KUID.
The largest files are your route while your session will be whatever name and KUID you have and that will be much smaller.
- Copy these files once you find them to your desktop or some other folder.
- Open up Content Manager.
- Drag the route .tzarc file into Content Manager.
- Check the progress bar carefully. It'll should show 0 errors and 1 warning. The one warning because you have a route with the same KUID installed.
- Open up the Open for Edit view in Content Manager and revert the route if it shows open for edit.
- You can remove the extra New Assets that are listed since they are temporary from your route that crashed.
- Close CM and try opening up the route again in TRS22+
If this works, repeat with the session and you should be all set.