Template:CCG-top
From TrainzOnline
(Difference between revisions)
(genesis, finally) |
(+usage) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <div id="CCGnotice" style="background:#FFFFE0<!--#E3FFE3 | |
| − | + | -->; width:100%; align:right;"><!-- | |
{{CCG-top|cur=* The current equivalent of this format is [[KIND Track]].}} | {{CCG-top|cur=* The current equivalent of this format is [[KIND Track]].}} | ||
--><div style="width:100%"><!-- | --><div style="width:100%"><!-- | ||
| Line 11: | Line 11: | ||
<td class="mbox-text" style="{{{textstyle|}}};padding-right:6px;"> | <td class="mbox-text" style="{{{textstyle|}}};padding-right:6px;"> | ||
<font color=red>'''Note'''</font>: This page is not an official reference guide to ''currently supported'' Trainz content {{wp|data structure}} technologies and ''may describe some obsoleted asset formats''. This guide to historic older technology has been assembled by the Trainz user community from the excellent .pdf file manuals known as: '''Content Creator's Guides''' as updated thru the '''TRS2006 through Trainz Classics 3''' era's simulator releases and in general... this data model and technology was valid up to TRS2009-SP1. <hr/> | <font color=red>'''Note'''</font>: This page is not an official reference guide to ''currently supported'' Trainz content {{wp|data structure}} technologies and ''may describe some obsoleted asset formats''. This guide to historic older technology has been assembled by the Trainz user community from the excellent .pdf file manuals known as: '''Content Creator's Guides''' as updated thru the '''TRS2006 through Trainz Classics 3''' era's simulator releases and in general... this data model and technology was valid up to TRS2009-SP1. <hr/> | ||
| − | {{Bull}} The information here is valuable as a reference to both experienced content creators and especially to <font color="blue">''those learning to create new content or learning to fix errors in older content''</font>, and regardless, should be valid in assets ''[["Trainz-build" tag|Trainz-build tag]] levels'' prior to {{{ver|2.9-3.0}}}).<br/> <font color=red>This background information should not be taken</font> as'' 'how-to advice' ''for upgrading to newer asset standards, but only as information for upgrading older assets short of version {{{ver|2.9}}} or earlier. <hr/><font color="blue">{{Bull}} '''Please refer to the corresponding more modern Container and [[KIND]] [[:Category:Trainz reference pages|Trainz data specifications pages]]'''</font> in the [[TrainzBaseSpec]] hierarchy and the ''specific container needs'' when upgrading or creating assets.<hr/>{{bull}} As a guideline for fixing broken assets, these pages should prove invaluable to both older and newer Trainzers as to what may be the trouble with the newer data structures implemented in [[Trainz-build]]s (versions) above 3.0</td></tr></table><br/>{{{text}}} | + | {{Bull}} The information here is valuable as a reference to both experienced content creators and especially to <font color="blue">''those learning to create new content or learning to fix errors in older content''</font>, and regardless, should be valid in assets ''[["Trainz-build" tag|Trainz-build tag]] levels'' prior to {{{ver|2.9-3.0}}}).<br/> <font color=red>This background information should not be taken</font> as'' 'how-to advice' ''for upgrading to newer asset standards, but only as information for upgrading older assets short of version {{{ver|2.9}}} or earlier. <hr/><font color="blue">{{Bull}} '''Please refer to the corresponding more modern Container and [[KIND]] [[:Category:Trainz reference pages|Trainz data specifications pages]]'''</font> in the [[TrainzBaseSpec]] hierarchy and the ''specific container needs'' when upgrading or creating assets.<hr/>{{bull}} As a guideline for fixing broken assets, these pages should prove invaluable to both older and newer Trainzers as to what may be the trouble with the newer data structures implemented in [[Trainz-build]]s (versions) above 3.0</td></tr></table><includeonly>{{TOCright}} |
| − | {{{1}}}</div> | + | </includeonly><br/>{{{text|}}} |
| + | {{{1|}}}</div><noinclude> | ||
| + | ;This template is specifically written for auto-categorizing and warning unwary new Trainzers that the [[Content Creatior's Guide]] is dated material, however useful at times. | ||
| + | *The complimentary template {{Tl|CCG-bot}} should be placed on the page bottom. | ||
{{SelfTdoc}} | {{SelfTdoc}} | ||
</noinclude> | </noinclude> | ||
Latest revision as of 21:07, 1 July 2013
|
|
Note: This page is not an official reference guide to currently supported Trainz content data structure technologies and may describe some obsoleted asset formats. This guide to historic older technology has been assembled by the Trainz user community from the excellent .pdf file manuals known as: Content Creator's Guides as updated thru the TRS2006 through Trainz Classics 3 era's simulator releases and in general... this data model and technology was valid up to TRS2009-SP1. • The information here is valuable as a reference to both experienced content creators and especially to those learning to create new content or learning to fix errors in older content, and regardless, should be valid in assets Trainz-build tag levels prior to 2.9-3.0). This background information should not be taken as 'how-to advice' for upgrading to newer asset standards, but only as information for upgrading older assets short of version 2.9 or earlier. • Please refer to the corresponding more modern Container and KIND Trainz data specifications pages in the TrainzBaseSpec hierarchy and the specific container needs when upgrading or creating assets. • As a guideline for fixing broken assets, these pages should prove invaluable to both older and newer Trainzers as to what may be the trouble with the newer data structures implemented in Trainz-builds (versions) above 3.0 |
- This template is specifically written for auto-categorizing and warning unwary new Trainzers that the Content Creatior's Guide is dated material, however useful at times.
- The complimentary template {{CCG-bot}} should be placed on the page bottom.
