Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
@JCitron -They no longer work due to stricter error checking required for scripts. The scripts did things that caused poor performance or crashes and N3V developers have been enforcing the error-checking. Prior, these were only warnings and warnings mean that at some point in the development cycle of Trainz, warnings can become errors and they did with SP5 for TRS19 and for the current service packs for TRS22 and Plus.
The history of this dates back to TRS2006. Prior to TRS2006, there was minimal if any error checking done on assets loaded into the program. Instead of flagging typographical errors and missing textures on assets or stopping outright faulty or poorly written scripts from loading, the early versions including TRS2004 just loaded the assets. Loading these assets and scripts allowed them to appear to work, but they didn't always work reliably if at all. The program performance was poor, crashed randomly to the desktop, or did other unreliable things worse than we have today.
Starting with TRS2006, stricter error-checking was introduced to flag faulty assets for repair and prevent them from loading. This early iteration stopped many things, mostly typographical errors in config.txt files and many other quick fixes but not like it is today. As each subsequent Trainz version was released, the error checking has been stepped up and with TS12 it got stronger due to the outcry from the community regarding poor performance. T: ANE introduced timeouts for scripts to ensure fewer stutters and stops along with a stricter enforcement on LODs and asset polygon numbers among other things.
Today, we have even more strict error checking than before and now these scripts among others have gone from warnings to errors. With the content being user-created, it's up to the content creator to update his or her scripts. If the assets aren't updated by the content-creator then the task is moved to the few volunteers belonging to the Content Repair Group to take on the task.
That is the reason, Rico. The issue I have is N3V didn't say anything about the enforcement occurring and just pushed the buttons, leaving many people stuck including the CRG who is trying to come up with a solution for this now.
TRC works, so why wouldn't the BUE signals work?
I "liked" the post by Matthias. I agree with him. These should be made available on the DLS for easy access rather than having to scout around the world for the signals, besides, should their FTP server go belly up again, the content will be safe.@karl1dlp , @JCitron and anyone else wanting a (possible) set of FORM signals, please pop over to this this thread and respond to post no. 23 by @MatthiasGose.
LINK >>> Update zu Signalen
He is offering a possible set for use, if interest is high enough.
Rico