Need your help again

[privite]

Hi,

i have a nother thread like this about a loco, but so far knowones been able to help me. my problem is that i've created some track for my new route, and it comes up in my game but its invisable. i have got auto create 1 in the config and points show up it i make one. any help will be appreciated and thanks in advance

by the way, im using gmax and the units setting is metric millimeters.

pic of my track

 

[4ndylloyd]

Good on you for trying content creation ! I have never been brave enough myself. Your screenie shows that an error has been reported byt the game, this could be whats causing the problem with the track. Click on the red dot in the lower right hand side of the screen and it will show you details of the problem. This could help you.

The last time that I was at the WSR they had run the tamper over the track at Bishop's and it is so oily there that the tamper had just left huge pot holes in the ballast

Andy

 

[privite]

Ah, thanks. im just trying it now...

by the way, you should try content creation with Gmax, thats free. once you get the hang of it its easy, but as you can see, im still in the learning stages:hehe:. this is quite a good site for learning: http://trainz.christrup.net/

 

[privite]

i did it and it said this:

Train : Thread Exception: ER_NullReference, line 1366, file train.gs (3)
UpdatesMenu : Thread Exception: ER_Timeout, line 100, file updatesmenu.gs (1)

what does this mean??

 

[4ndylloyd]

Thanks for the tip about Gmax, I have it installed and have taken a look but not got started! I dont know what your script error means I'm sorry, but someone else may be able to help. I am guessing that your track is error free in Content Manager? Is it any good for you to create your track but copy the script files out of some Auran track ? I have seen some threads regarding problems with splines in 2009/10, does it help if you change the build number on the config file to an earlier version?

Andy

 

[privite]

Thanks for that, i will have a look at the other thread. hopefully i will get it sorted, along with my failed attempt at a loco:hehe:
Thanks for all your help and good luck with Gmax.

 

[ray_whiley]

privite - could you post your config file for others to look at?

Ray

 

[martinvk]

This is stitched track, right? Have you got the LOD sizes and distances correct for your mesh? Millimeters you say, try changing that to meters, the track just might be 1000 times too small since the end splines show in the image.

 

[rweber95]

i have got auto create 1 in the config and points

I'm no Gmax creator but if that is a literal quote, the problem may be that the tag should be:
auto-create 1

Bob Weber

 

[Euphod]

I'm agreeing with Martin. I don't create models, but was recently reminded that GMax has a one to one scale, so if you use meters, you'll get meters, and if you use metric millimeters, you'll get far too small to see!

 

[privite]

Thankyou all for your replies, they are appreciated.

here's what you wanted:

1)auto-create is 1
2)the measurements in Gmax are: W:2.201m H:0.181m L:4.653m
3)here's the config:

 

[masontaylor]

I've not done any track yet, but I have made some splines which work in the same basic way. The one thing that strikes me immediately is that there's no mesh-length line in the table: looks as if you've copied the config. from elsewhere but edited too much out when you removed the LOD lines. Open up the config. for one of Auran's own tracks and you'll see that the mesh-length is specified.

Splines can be a nightmare - one wrong or missed entry in the table can create havoc. Have you seen these two Wiki entries? They'll explain a bit more ....

http://online.ts2009.com/mediaWiki/index.php5/Stitched_track

http://online.ts2009.com/mediaWiki/index.php5/"track-lod-tree"_container

 

[privite]

If your talking about the istrack and visable-on-minimap, they were there already when i opened it in CCP. thanks for the links though, i will have a look at them

 

[ray_whiley]

Here is the complete config for a track I made for TRS2004 which may help - it shows the length tag etc.

kuid <kuid2:275817:37995:0>
trainz-build 2.4
type "track"
region "Dukes Denver Designs"
category-class "TR"
category-region "FR"
category-era "1900s;1910s;1920s;1930s;1940s;1950s;1960s;1970s;1980s;1990s;2000s;2010s"
grounded 0
length 3
istrack 1
isroad 0
carrate 0
bendy 1
width 1
repeats 1
uncached_alphas 0
invisible 0
rgb 255,0,0
obsolete-table {
}
asset-filename "Metro single track"
kuid-table {
}
description "Single track with conductor rail for Metro systems. Might be useful too for light rail transit systems with outside third electrification. See read me file."
username "Metro single track"
author "Ray Whiley"
organisation "Dukes Denver Designs"
contact-email "via website"
contact-website "http://myweb.tiscali.co.uk/raywhiley"
license "This item may be used, modified and distributed freely provided that no payment is sought or accepted."
kind "track"

Notes:

1 It is best not to use '0' (zero) as the KUID version number - I didn't know this at the time but it hasn't seemed to be a problem.
2 This is for build 2.4 which could be changed to 2.8 - I'm not sure whether build 2.9 would work with this; someone may be able to advise. But as it works like this in TS2010 I haven't bothered to change anything.
3 Length - always in metres. If you have made your track in feet, convert the segment length to metres by dividing by 3.27 (there are 3.27 feet in a metre).
4 Width - also in metres but it doesn't seem to matter what you put!
5 Region - my own, as I wanted to keep all my creations in one place on the Surveyor tabs.

Hope this helps.

Ray

 

[martinvk]

We haven't talked about textures yet but they are also important. What is the exact size in pixels. Was it saved as a 24bit, uncompressed file? Very important or Trainz will not show the object even it is visible in GMax.

 

[clam1952]

For 2010 you should be using stitched mesh format. Better to start with the current method or like me you will find yourself having to update a lot of splines............

Simple track config for 2010 upwards with no Lod shown below:

username                                "Track "
trainz-build                            3.1
category-class                          "TR"
category-region                         "UK"
category-era                            "2010s"
kind                                    "track"
istrack                                 1
visible-on-minimap                      1
author                                  "clam1952"
contact-email                           "wherever@whatever.com"
description                             "Sample Track config - No lod"
license                                 "Freeware"

mesh-table
{
  default
  {
    mesh                                "default.im"
  }
}

track
{
  mesh-length                           2.500
  adjust-cross-section-to-ground        0
  
  track-lod-tree
  {
    mesh                                "default"
  }
}
kuid                                    <kuid:425700:xxxxxx>

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

kuid-table
{
}

 

[privite]

thankyou all for your replies, i will try the config again. i dont think its the textures that are the problem as i have dong ground textures and buildings before and they are fine, i will have a look though .

 

[privite]

IT WORKS!!!!

Clam1952's config did it. think its something to do with the mesh file in the track folder, not sure. but thanks for all your replies, i appreciate it.

 

[martinvk]

Before moving on, it would be best to understand exactly what happened so that the same problem doesn't occur again.

Clam1952's config example is just the barebones of a complete stitched mesh track config file. For it to truly work as it was designed to, more will have to be added.

Study config files from other stitched mesh tracks, noting the differences and similarities between the files. Read the wiki sections concerning these files. They (the wiki texts) are not the easiest to follow but are all we have at the moment. The main idea to understand is that as the viewer's distance from the track increases, different lower poly meshes are substituted. This should happen seamlessly. If the transition is obvious, then the track needs more work. The reason for using progressively lower poly meshes is that if you can't see the difference, don't waste the computer's time calculating all of the polys if only a few pixels are all that will be displayed in the distance.