KIND Texture-group: Difference between revisions

From TrainzOnline
Jump to navigationJump to search
No edit summary
Pencil42 (talk | contribs)
Updated to reference .texture files instead of image files directly
 
(3 intermediate revisions by 3 users not shown)
Line 16: Line 16:


  kuid <kuid:171456:100034>
  kuid <kuid:171456:100034>
  trainz-build 2.5
  trainz-build 3.5
  category-class "JO"
  category-class "JO"
  category-region "AU"
  category-region "AU"
Line 25: Line 25:
  textures
  textures
  {
  {
   0 "1.bmp"
   0 "1.texture"
   1 "2.bmp"
   1 "2.texture"
   2 "3.bmp"
   2 "3.texture"
  }
  }
  thumbnails
  thumbnails
Line 38: Line 38:
   }
   }
  }
  }
An example for the use of "texture-group" is a destination  board system. See [[HowTo/Implement_a_Destination_Sign_System|How to Implement a Destination Sign System]].
Note that as of TANE, all textures must be referenced as .texture files, not the image file (.bmp, .tga, etc) itself.


==Categories==
==Categories==
[[Category:Asset KIND]]
[[Category:Asset KIND|T]]
[[Category:TBD]]

Latest revision as of 15:19, 22 June 2015

KIND Texture-group defines a group of textures as an asset that can be referenced from another asset or via scripting.

KIND Hierarchy

Parent Classes

Child Classes

  • none.

Supported Tags

TBD

Example Config.txt

kuid <kuid:171456:100034>
trainz-build 3.5
category-class "JO"
category-region "AU"
category-era "1810s"
username "testTextureGroup"
kind "texture-group"
description "Test texture group."
textures
{
  0 "1.texture"
  1 "2.texture"
  2 "3.texture"
}
thumbnails
{
  0
  {
    image "thumb.jpg"
    width 240
    height 180
  }
}

An example for the use of "texture-group" is a destination board system. See How to Implement a Destination Sign System.

Note that as of TANE, all textures must be referenced as .texture files, not the image file (.bmp, .tga, etc) itself.

Categories