This is one for the books.
I've been testing routes and sessions in the new Plus beta and I've been setting up an extensive number of consists throughout my large route. This is to test performance and force the program to work in a worst case scenario with performance or other issues relating to a huge number of consists. The route has lots of large freight yards, sidings, a few big passenger terminals, and coach yards.
I put in a Missouri Pacific 50ft boxcar I had repaired ages ago. I do not know the origins of "my boxcar" but whatever fix I did back in the day fixed a problem then and the boxcar went into Trainz content and as is the case with many of us, this said boxcar then sat there in amongst all the other boxcars and other freight cars that are neglected as I chose something else. In my zeal to create lots of consists, I chose this particular one.
Much later I saved my session and exited and noticed an error in Trainz - a red "!" on the session. The error occurred after placing lots and lots of consists, meaning lots of long trains and small single freight cars throughout the route, I initially thought the error was due to too many freight cars and I had reached an unknown limit to the number of consists we can add.
Since the error occurred during the beta, I was going to send in a bug report/ and while I was gathering all my ducks to put them in a row, I noticed something. The error was related to text strings being unknown, and the text was the names of freight cars and passenger cars that I had added as if the config.txt file somehow ended up scrambled.
I opened the config.txt file and found train-car usernames outside of the string-table again and cleaned that up and submitted the session in Content Manager only to have the error occur again when I was editing! I could run the session okay, but there was still this error. When I opened the config.txt file, the text strings were outside of the string-table.
I dug deeper and after cleaning up the session again for the umteenth time, I noticed that the error occurred at a particular boxcar initially making me think the text was truncated. I opened the config.txt again and fixed the error.
I checked Content Manager and sure enough, the culprit was MOPAC boxcar. 50ft Hi-Cube Boxcar MP (Clean) {JR}.
The username has curly brackets - these things { } in the name causing in the error as shown above in bold.
These little suckers completely scrambled the string-table causing text strings to be placed outside of the string-table either at the top or below due to Content Manager seeing the { } as delimiters and getting confused when it compiled the config.txt file.
Once I tracked it down, I fixed the asset username and replaced the asset on my route.
What's interesting is Content Manager never caught this error and it was Trainz Plus that did.
I've been testing routes and sessions in the new Plus beta and I've been setting up an extensive number of consists throughout my large route. This is to test performance and force the program to work in a worst case scenario with performance or other issues relating to a huge number of consists. The route has lots of large freight yards, sidings, a few big passenger terminals, and coach yards.
I put in a Missouri Pacific 50ft boxcar I had repaired ages ago. I do not know the origins of "my boxcar" but whatever fix I did back in the day fixed a problem then and the boxcar went into Trainz content and as is the case with many of us, this said boxcar then sat there in amongst all the other boxcars and other freight cars that are neglected as I chose something else. In my zeal to create lots of consists, I chose this particular one.
Much later I saved my session and exited and noticed an error in Trainz - a red "!" on the session. The error occurred after placing lots and lots of consists, meaning lots of long trains and small single freight cars throughout the route, I initially thought the error was due to too many freight cars and I had reached an unknown limit to the number of consists we can add.
Since the error occurred during the beta, I was going to send in a bug report/ and while I was gathering all my ducks to put them in a row, I noticed something. The error was related to text strings being unknown, and the text was the names of freight cars and passenger cars that I had added as if the config.txt file somehow ended up scrambled.
I opened the config.txt file and found train-car usernames outside of the string-table again and cleaned that up and submitted the session in Content Manager only to have the error occur again when I was editing! I could run the session okay, but there was still this error. When I opened the config.txt file, the text strings were outside of the string-table.
I dug deeper and after cleaning up the session again for the umteenth time, I noticed that the error occurred at a particular boxcar initially making me think the text was truncated. I opened the config.txt again and fixed the error.
I checked Content Manager and sure enough, the culprit was MOPAC boxcar. 50ft Hi-Cube Boxcar MP (Clean) {JR}.
The username has curly brackets - these things { } in the name causing in the error as shown above in bold.
These little suckers completely scrambled the string-table causing text strings to be placed outside of the string-table either at the top or below due to Content Manager seeing the { } as delimiters and getting confused when it compiled the config.txt file.
Once I tracked it down, I fixed the asset username and replaced the asset on my route.
What's interesting is Content Manager never caught this error and it was Trainz Plus that did.