Route Problems

[Rafter]

I started to lay track on the sava-aurora DEM map. but whenever I try to save, CM says the layout has faulty dependencies. Then when I view the dependencies, nothing is wrong. the only thing it says is "Error: The Tag 'thumbnail' is not permitted within a container of type 'map'." Anyone know what to do?? It sucks because il spend half an hour, save, and then its not there. I just want to know how to make the layout not faulty.

 

[Fabartus]

"Error: The Tag 'thumbnail' is not permitted within a container of type 'map'." .... I just want to know how to make the layout not faulty.

Replace the thumbnail line with a thumbnails container. Just make up a jpg in Windows Paint with the Map title or something like that. // Frank

 

[bentrain14]

Open the map in content creator plus and go to thumbnail in the menu. Itll say something like add thumbnail. Now before you can add one, go and open the map in explorer and find a picture from your computer and copy and paste it on the open explorer file for your map. Then you can designate that photo as the thumbnail from content creator plus. Save and commit. PM me if I didnt do a good job explaining.

 

[GP30Fan]

The following lines must appear in the route config...

Note the image size must be 240x180. Not just any photo or pic will work.
Use your image editor to create an image of that size and use text to describe the route.
Save the image as a 'preview.jpg' and use that as the file name in the config tag.



thumbnails
{
0
{
image "filename.jpg"
width 240
height 180
}
}

-AL

 

[Rafter]

Open the map in content creator plus and go to thumbnail in the menu. Itll say something like add thumbnail. Now before you can add one, go and open the map in explorer and find a picture from your computer and copy and paste it on the open explorer file for your map. Then you can designate that photo as the thumbnail from content creator plus. Save and commit. PM me if I didnt do a good job explaining.

Thanks a ton! It worked! Hopefully it works from now on!

 

[Fabartus]

Thanks a ton! It worked! Hopefully it works from now on!

Interesting split in advised technique to get to the same thing. Who opens CCP without cringing? He needed a thumbnail, not a trainz-build adjustment forced down his throat! Yikes! Start here, (memorize, or almost) and make sure you know about and follow this. Remember the single character like thumbnail vs thumbnails in computer code OFTEN MATTER, so cultivate the habit of painstaking care when editing such. Further, Error messages from computers are usually VERY LITERAL, as was this one. If you'd have had a pre-V2.9 trainz-build and an username_art subfolder with a username_512.tga file, then the thumbnail line would have been satisfied. More than one way to skin a cat in Trainz, but using CCP to edit older assets is definitely a way to waste time. // Frank

 

[Rafter]

Interesting split in advised technique to get to the same thing. Who opens CCP without cringing? He needed a thumbnail, not a trainz-build adjustment forced down his throat! Yikes! Start here, (memorize, or almost) and make sure you know about and follow this. Remember the single character like thumbnail vs thumbnails in computer code OFTEN MATTER, so cultivate the habit of painstaking care when editing such. Further, Error messages from computers are usually VERY LITERAL, as was this one. If you'd have had a pre-V2.9 trainz-build and an username_art subfolder with a username_512.tga file, then the thumbnail line would have been satisfied. More than one way to skin a cat in Trainz, but using CCP to edit older assets is definitely a way to waste time. // Frank

well using CCP worked, so if the problem ever comes up again, il just use CCP

 

[JCitron]

This probably worked with CCP because the route version was current. If you had tried this with an older piece of content, it can cause all kinds of problems as many of us have found out the hard way, and is probably why we're a bit gun shy of the application.

John

 

[Fabartus]

This probably worked with CCP because the route version was current. If you had tried this with an older piece of content, it can cause all kinds of problems as many of us have found out the hard way, and is probably why we're a bit gun shy of the application.

John

That's because we're likely focused on just fixing enough to get it to work, not update to the current tech level. It actually makes some sense if you've got an asset built v2-5 and up. Assuming they weren't ignoring most of the warnings, but satisfied them. // Frank