Goku, on 30 May 2017 - 01:49 PM, said:
In old msts editor it can happen if you edit track vectors with interactives on them, but TSRE should allow this ..
Hi Goku,
Yes, TSRE seems to have no problems, it's the terrible condition of the PRR database files that's the problem. Like I said, ~1,789 tdb errors, >700 rdb errors and tons of mis-matched Dynamic Track sections. I'd like to delete all DT and all interactives.
The TSRE5 Editor seems able to handle the +50MB PRR tdb file, executing a save in about 3 seconds vs. anout a minute in MSTS!
But I don't expect TSRE5 to work well with databases in such bad condition and am actually surprised how well it edits the route. But I gotta get rid of the interactives and dynamic track.
Then I think I'll have a stable database to edit.
The about 1 mile section south from the North Philadelphia station to Zoo came out really nice but OR now craps out with an exception complaining about signals.
THATS why I want to remove them all and replacing them will keep me out of the pubs.
Call it a vacation from the LIRR. http://www.elvastower.com/forums/public/style_emoticons/default/pleasantry.gif
Question for Carlo:
Should I post the OR exception log on the off chance there could be a simple answer in the data?
regards.
vince
an example of the prr database problems is how database errors have skewed these sound regions on the main line at N Philadelphia.
prr skewed sound regions.jpg (192.59K)
Number of downloads: 2
The yellow lines normally run straight across the track. Here references in the tdb are 'off?'and the lines get skewed. It shows up in several I've found for siding, mileposts and in on case here, a signal head located almost 1/2 mile from the track signal marker.
Cheers, v