Any route using assets from its own provider or that of the Kuju structure will currently work as required. This is because the route in question is being loaded from within its own provider set resulting in any assets also under that provider being loaded with it. The Kuju assets are loaded by default.
However, any route using assets from outside its own provider folder structure or that of Kuju/RailSimulator will fail to load because assets from outside these two locations are not being picked up by Rail Simulator as requirements to be loaded.
This is a known bug that is fixed in the up coming patch.
Example Situations:
- Provider A creates a route using default assets (located under Assets/Kuju)
- Route loads fine
- Provider B creates a route and some assets to go with it (located under Assets/Provider B)
- Route loads fine
- Provider C creates a route, but uses assets by Provider D (located under Assets/Provider D)
- Route fails to load