ZecMurphy
Community Assistant
Good Evening Domsarto
You are most certainly confusing two different things here.
The only assets that were included in the DLS clean up were those assets that showed as faulty in Trainz (most of which showed as faulty within TRS2006 as well...). Unfortunately, some of the people who 'fixed' these assets did not test them afterward. We are looking into ways to fix this, however we don't have an ETA on when this will occur.
It should be noted that any error that appears within Content Manager in current versions, is still an error in previous versions, the error checking simply didn't know about it at the time. This particularly applies with TRS2004, which had essentially no error checking. Many of these errors actually caused performance issues, or caused Trainz to crash in quite a number of situations... TRS2004 was extremely unstable due to this...
We have not, so far, made assets faulty in Trainz that are simply old. Sure, some of them have warnings, which should be expected to become 'faulty' in future versions, but this won't always be the case. In some cases, we may simply make this apply to only the newer build numbers as well, particularly where pre TS2009 content is concerned (not, plans do change, but at this stage TRS2004 content that isn't faulty, should remain so).
In particular...
We don't mark assets with .pm files as faulty. They do have a warning, which is essentially there to inform the creator that their content is obsolete, and warn route builders that the content uses an obsolete system. However, .pm files have been essentially obsolete since TRS2004 was released. When TS2009 was released, they were essentially handled as a standard .im file (disabling all 'LOD' type functionality within them). However, in neither case were they made inoperable.
That said, a .pm file cannot be used in new content. Nor is there any reason to do so, as it offers no improvement to performance (and may actually degrade performance).
Regards
You are most certainly confusing two different things here.
The only assets that were included in the DLS clean up were those assets that showed as faulty in Trainz (most of which showed as faulty within TRS2006 as well...). Unfortunately, some of the people who 'fixed' these assets did not test them afterward. We are looking into ways to fix this, however we don't have an ETA on when this will occur.
It should be noted that any error that appears within Content Manager in current versions, is still an error in previous versions, the error checking simply didn't know about it at the time. This particularly applies with TRS2004, which had essentially no error checking. Many of these errors actually caused performance issues, or caused Trainz to crash in quite a number of situations... TRS2004 was extremely unstable due to this...
We have not, so far, made assets faulty in Trainz that are simply old. Sure, some of them have warnings, which should be expected to become 'faulty' in future versions, but this won't always be the case. In some cases, we may simply make this apply to only the newer build numbers as well, particularly where pre TS2009 content is concerned (not, plans do change, but at this stage TRS2004 content that isn't faulty, should remain so).
In particular...
We don't mark assets with .pm files as faulty. They do have a warning, which is essentially there to inform the creator that their content is obsolete, and warn route builders that the content uses an obsolete system. However, .pm files have been essentially obsolete since TRS2004 was released. When TS2009 was released, they were essentially handled as a standard .im file (disabling all 'LOD' type functionality within them). However, in neither case were they made inoperable.
That said, a .pm file cannot be used in new content. Nor is there any reason to do so, as it offers no improvement to performance (and may actually degrade performance).
Regards