How to Deal with Missing Assets: Difference between revisions
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
<td width=46> </td> | <td width=46> </td> | ||
<td width=75> </td> | <td width=75> </td> | ||
<td width=75>[[file:NextDown.png|link=# | <td width=75>[[file:NextDown.png|link=#stepCauses|alt=Next Down|Next Down]]</td> | ||
<td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | <td width=75>[[file:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | ||
</tr> | </tr> | ||
| Line 44: | Line 44: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[image:BlueDot10x10.png|link=]]</td> | <td>[[image:BlueDot10x10.png|link=]]</td> | ||
<td>Some '''Missing Dependencies''' can be deleted without affecting the operation of a route or a session</td> | <td>Some '''Missing Dependencies''' can be deleted or replaced without affecting the operation of a route or a session</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 51: | Line 51: | ||
</table> | </table> | ||
<br> | <br> | ||
=''' | <table width=1000> <!-- BEGIN Nav Buttons Table SECTION w SKIPS --> | ||
<tr valign="top"> | |||
<td width=629><span id="stepCauses"></span> | |||
='''What Causes Missing Dependencies?'''= | |||
</td> | |||
<td width=50> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | |||
<td width=75> </td> | |||
<td width=75>[[image:NextDown.png|link=#stepLocating|alt=Next Down|Next Down]]</td> | |||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | |||
</tr> | |||
</table> <!-- END Nav Buttons Table --> | |||
<table width=1000> | <table width=1000> | ||
| Line 112: | Line 124: | ||
<table bgcolor=#ffffff cellpadding=2> | <table bgcolor=#ffffff cellpadding=2> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td><span style="font-weight: 700; font-size: 15px;">Steps: To Identify and Restore any Disabled | <td><span style="font-weight: 700; font-size: 15px;">Steps: To Identify and Restore any Disabled Assets in Content Manager:-</span></td> | ||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
| Line 203: | Line 215: | ||
<tr valign="top"> | <tr valign="top"> | ||
<td>[[image:DotPoint3.JPG|link=]]</td> | <td>[[image:DotPoint3.JPG|link=]]</td> | ||
<td><span style="font-weight: 700; font-size: 15px; background-color: lightcyan;"> Left Click </span> on the <span style="font-weight: 700; font-size: 15px;">Status</span> column heading to sort the rows into category order (i.e. all the '''Available for Download''' assets together).</td> | <td><span style="font-weight: 700; font-size: 15px; background-color: lightcyan;"> Left Click </span> on the <span style="font-weight: 700; font-size: 15px;">Status</span> column heading to sort the rows into category order (i.e. all the '''Available for Download''' assets together).<br> | ||
<table bgcolor=#ffffb0 cellpadding=2> | |||
<tr valign="top"> | |||
<td width=25>[[image:NotePad.PNG|link=]]</td> | |||
<td>If the <span style="font-weight: 700; font-size: 15px;">Status</span> column is not present in '''Content Manager''' then refer to the '''Tips''' in the '''Steps''' above</td> | |||
</tr> | |||
</table></td> | |||
</tr> | </tr> | ||
<tr valign="top"> | <tr valign="top"> | ||
| Line 259: | Line 277: | ||
<table width=996 bgcolor=#ffffff cellpadding=2> | <table width=996 bgcolor=#ffffff cellpadding=2> | ||
<tr valign="top"> | <tr valign="top"> | ||
<td> | <td colspan=2> | ||
<table> | |||
<tr valign="middle"> | |||
<td width=35>[[image:Information.png|35px|link=]]</td> | |||
<td><span style="font-weight: 700; font-size: 15px;">If all attempts to locate and install the missing dependencies have failed then there are further options:-</span></td> | |||
</tr> | |||
</table> | |||
</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td width=10>[[image:BlueDot10x10.png|link=]]</td> | |||
<td>'''Delete the Asset Containing the Missing Dependency:''' If the missing dependency is crucial to the asset, e.g. bogies on a locomotive, interactive industries in a route or there are simply too many missing dependencies, then deleting the asset (e.g. the locomotive or the route) may be the best and only practical option.</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>[[image:BlueDot10x10.png|link=]]</td> | |||
<td>'''Delete and Ignore the Missing Dependency:''' If the missing dependency is part of a route but is not crucial to the route, e.g. one type of tree in a forest, then it could be deleted from the route and ignored. The option below is also a possibility.</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td>[[image:BlueDot10x10.png|link=]]</td> | |||
<td>'''Delete and Replace the Missing Dependency:''' If the missing dependency is part of a route or session and has a role in that route or session, e.g. a track object or a rolling stock asset, then it might be possible to delete it and replace it with a similar asset.</td> | |||
</tr> | |||
<tr valign="top"> | |||
<td colspan=2>Where the missing dependency is part of a route or a session, then it is important to discover where that dependency is located and how it is used before making a decision on which of these three options to use.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 266: | Line 306: | ||
</table> | </table> | ||
<br> | <br> | ||
<table width=1000> <!-- BEGIN Nav Buttons Table SECTION w SKIPS --> | |||
<tr valign="top"> | |||
<td width=629><span id="stepLocating"></span> | |||
='''Locating Missing Dependencies in a Layout'''= | ='''Locating Missing Dependencies in a Layout'''= | ||
</td> | |||
<td width=50> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | |||
<td width=75>[[image:NextUp.png|link=#stepCauses|alt=Next Up|Next Up]]</td> | |||
<td width=75>[[image:NextDown.png|link=#stepDeleting|alt=Next Down|Next Down]]</td> | |||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | |||
</tr> | |||
</table> <!-- END Nav Buttons Table --> | |||
<table width=1000 bgcolor="lightcyan" cellpadding=2> | <table width=1000 bgcolor="lightcyan" cellpadding=2> | ||
| Line 484: | Line 536: | ||
</table> | </table> | ||
<br> | <br> | ||
<table width=1000> <!-- BEGIN Nav Buttons Table SECTION w SKIPS --> | |||
<tr valign="top"> | |||
<td width=629><span id="stepDeleting"></span> | |||
='''Deleting Missing Dependencies'''= | ='''Deleting Missing Dependencies'''= | ||
</td> | |||
<td width=50> </td> | |||
<td width=50> </td> | |||
<td width=46>[[image:BackToTop.png|link=#top|alt=Top|Top]]</td> | |||
<td width=75>[[image:NextUp.png|link=#stepLocating|alt=Next Up|Next Up]]</td> | |||
<td width=75> </td> | |||
<td width=75>[[image:BackToBottom.png|link=#bottom|alt=Bottom|Bottom]]</td> | |||
</tr> | |||
</table> <!-- END Nav Buttons Table --> | |||
<span style="font-weight: 700; font-size: 17px;">Currently Under Construction</span><br> | <span style="font-weight: 700; font-size: 17px;">Currently Under Construction</span><br> | ||
Revision as of 23:49, 17 October 2026
|
|
|||||||||
What Causes Missing Dependencies? |
| Missing Dependencies can occur when an asset:- |
| has been installed from a .cdp file (e.g. from a 3rd party web site) or from a content folder (e.g. on your HD) without also installing other assets it requires. If an asset with Missing Dependencies has been installed using the Import Content Files... or Import Content Folder... options in the File menu of Content Manager, then the missing assets may be on the DLS. When these two import methods are used Content Manager does not check the DLS for any missing dependencies. |
||||||||||
|
||||||||||
| has been Disabled or Deleted in Content Manager. | ||||||||||||||||||||||||
| If an asset has been Disabled then it is still installed but it is blocked from being used. Removing the block will make it available for use. | ||||||||||||||||||||||||
|
||||||||||||||||||||||||
| If an asset has been Deleted then it is no longer installed. It can be reinstalled if it is on the DLS. | ||||||||||||||||||||||||
|
||||||||||||||||||||||||
| has been downloaded from the DLS but contains dependency assets that are not on the DLS or built-in. Downloaded assets can sometimes contain dependencies that are not on the DLS or Built-in (ones that came installed with Trainz). This can lead to frustrations especially if the creator of the downloaded asset has not provided any information on where these missing assets can be found. Even when the location, such as a 3rd party web site, has been identified that site may no longer exist. |
|||||||
| If the missing assets are not on the DLS then fixing this may not be easy. Possible solutions are:- | |||||||
|
|||||||
|
||||||||||||
Locating Missing Dependencies in a Layout |
| Missing splines and tracks in a layout will be shown as white dotted lines | |
| Missing textures will be, conditionally, shown as a bright blue colour | |
| Missing scenery objects, including rolling stock track objects (e.g. signals, switches) will NOT be visible at all |
Missing Splines (including Track)
| In the following examples... | |
![]() |
The missing spline asset is most likely a road. If deleted it will leave a "space" in the route but it will not affect the operation of sessions that use this route, just their appearence. |
![]() |
The missing spline asset is rail track - the presence of the track objects is a major clue. If deleted it WILL affect the operation of sessions that use this route. |
![]() |
The missing spline asset is a tunnel with track. If deleted it will leave a gap in the route and it WILL affect the operation of sessions that use this route. |
Missing Textures
![]() |
The false blue colour indicates that the missing asset is a ground texture. If deleted it will not affect the operation of the route, just its appearence.
|
Missing Scenery Objects (incl Rolling Stock and Track Objects)
|
| Locating these objects in a layout can give you useful clues as to what the missing assets are (e.g. trees/bushes, cars, buildings, signals, wagons, etc). |
|
| With the Show missing assets check box set on, each scenery object that is missing from the route or session will be shown as an Orange Wire Frame Box in Surveyor. They will still be invisible in Driver. |
| In the following examples... | |
![]() |
From its size and shape, the missing asset is most probably a building. If deleted it will leave a "space" in the route but it will not affect the operation of sessions that use this route, just their appearence. |
![]() |
The missing asset is almost certainly an Industry Active Platform, possibly an invisible platform. The presence of a visible station building indicates that the missing asset is just the platform. If deleted it WILL affect the operation of sessions that use this route. |
![]() |
From its size, shape and location, the missing asset (or assets - there may be several different missing assets) is most likely a tree. If deleted it will leave gaps in the forest but it will not affect the operation of sessions that use this route, just their appearence. |
![]() |
The missing asset is clearly rolling stock. If deleted it WILL affect the operation of the session. |
![]() |
Because of its position on the track the missing asset is clearly a track object and almost certainly a track switch. If deleted it COULD affect the operation of the session depending on the type of track object (switch track objects WILL have an effect while caution and whistle signs will probably not). |
Deleting Missing Dependencies |
Currently Under Construction
Trainz Wiki
|
|
This page was created by Trainz user pware in October 2026 and was last updated as shown below.













