![]() ![]() about 6000 hrs in total over the past three years on the update. If anyone has any suggestions I'm all ears. VE77: Unable to load indexed mesh 'waterfall-5c.im' VE195: Unable to parse chunk 2 in mesh file: waterfall-5c.im VE77: Unable to load indexed mesh 'waterfall-2a.im' VE195: Unable to parse chunk 3 in mesh file: waterfall-2a.im Bad index data in geometry chunk:3 at #71 VE77: Unable to load indexed mesh 'waterfall-5f.im' VE195: Unable to parse chunk 2 in mesh file: waterfall-5f.im MeshResource::LoadResource> | arc:fld:$(local)/hash-BF||kuid 47439 25645.tzarc| VE77: Unable to load indexed mesh 'waterfall-5d.im' VE195: Unable to parse chunk 2 in mesh file: waterfall-5d.im VE77: Unable to load indexed mesh 'waterfall-4e.im' VE195: Unable to parse chunk 5 in mesh file: waterfall-4e.im Bad index data in geometry chunk:5 at #12 ! VE62: Required container 'thumbnails' is missing. VE77: Unable to load indexed mesh 'waterfall-5a.im' VE195: Unable to parse chunk 2 in mesh file: waterfall-5a.im Bad index data in geometry chunk:2 at #5 MeshResource::LoadResource> | arc:fld:$(local)/hash-BA||kuid 47439 25640.tzarc| Trainz-build numbers below 3.5 are no longer supported. ! VE48: This asset uses an obsolete trainz-build number. I have just about cleaned up all the missing and faulty content after having moved Murchison 2 from TS2009 to TRS19, the 6 remaining faulty items are The good news is he is working on the route, although, as you can tell it's a very, very long process to ensure that everything is up to the current standards that he and the rest of us expect to see in TRS2019. He did a fabulous job with the assets of the times and sadly the route looks like it is from the TRS2009 days. It's not that Mike didn't do a wonderful job with the route. Once imported there are tons, upon tons of cosmetic things that need repairs. This track now creates its own ball of wax because there will be some, not a whole lot, of faulty junctions which require fiddling due to uneven terrain, or too tight a radius for the rails I didn't spend too much time trying to find out with those. If you do use this method, you need to export in batches, otherwise, you'll end up missing something or worse end up absolutely confused due to the shear number of assets.įixed junction assets need replacing because the track, by default, uses the built-in procedural track, and these fixed-junction assets are not quite up to par anymore, let alone that they may not work properly anymore. The errors are relatively easy, but there are hundreds of them. Once imported into TRS19, however, you will need to do many, many repairs on all content. If you have the TRS2009 version, however, you can with a really, really lot of work, export the routes and content. Exporting the content won't work either due to the copy-protection for these assets. The content is highly compressed and will not import directly and will have all kinds of errors. The Murchison 2 in TS12 61838 (SP1 HF4) is done in packages not unlike the DLC content we use today. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |