TrainzOnline - User contributions [en]

Mobile-area-driving-select route

2016-11-24T19:20:37Z

Idham.: Trainzvportal

{{Trainz_Logo}}

== Select Route ==

In Trainz, a "Route" is the name given to the "world" that you will be driving in. A Route can be big or small, real or fictional.

Tap on "Select Route" to load a list of Routes that are available.

[[file:main_menu-select_route.png|500px]]

==Select Route Menu==
[[file:section-select_route_large.png|500px]]

==Selecting a Route==
On the left-hand side you will find a list of routes. Tap on any route to display additional information including screenshots and route background.

Once you have chosen the route you want, tap the "View Sessions" button and you will be taken to another screen that lists all the sessions ( gameplay ) that is available for the chosen route.

==Editing a Route==
When a route is selected, you may get the option to "Edit Route". The edit route option means you can open the existing route and change it however you like. Payware routes cannot be edited.

==Creating a New Route==
To create a Route from scratch, tap the "Create Route" button. This will take you into Trainz world building tool called [[Help:Mobile_Surveyor|"Surveyor"]] and starts you off with an empty world to let your imagination run wild.

==Route Colour Codes==
Each route is colour coded:
* WHITE routes are routes that you own and you are free to edit them all you want.
* GREEN routes are routes that have additional sessions ( gameplay ) that you can purchase.

==View Sessions==
Click to view all the Sessions related to the selected Route. "Sessions" are the interactive elements of a Route and provide the actual driving/operation experience.

For more information on Sessions, click [[Mobile-area-driving-select_session|here.]]
{{Platform_Mobile_Select_Area}}

Trainz Online

2015-07-16T16:47:21Z

Idham.: Idham. moved page Trainz Online to User:Trainz Online: youu

Trainz Online - a window to the exciting world of Trainz.

Trainz Online is a union of technology and content that encourages Trainz users to become part of the online community. It enables content creators to showcase their content and provide additional information and real world background about their route, loco or even scenery objects. It enables users to locate and browse useful information without leaving the Trainz game environment. It also allows users to share their feedback with creators directly and to share information amongst themselves.

== Content ==

Trainz Online is a new community-driven website that will provide mechanisms for the online community to share information, content, and participate in discussions of Trainz-related topics. Whilst in development, Trainz Online is a subset of the TrainzDev site. As it is fleshed out more it will be tested online and then in-game prior to being fully launched in conjunction with the launch of TS2009.

Trainz Online will provide numerous community features including forums, per-user blogs, per-user image gallery, a wiki, and some community management features such as news and home pages.

Future extensions of the Trainz Online site may include the ability for users to embed DLS content, content galleries, user-driven community groups, etc.

== Technology ==

Within the Trainz game environment, Trainz Online is expressed through an [[embedded web browser]] window. This allows new users to get a taste for the Trainz Online site without having to go out of their way to locate, sign-up, and participate in our web community. It is expected that frequent users will use a regular web browser for most online activities, since a regular browser is optimised specifically for browsing and does not carry the overhead of the Trainz game for simple browsing tasks. The intent of the embedded browser is not to compete with a regular browser, but rather to make specific content available in a context where a regular browser would be inappropriate.

From the point of view of a content creator, this means that users can click on a link from a menu page and become immersed in whatever content can be delivered through a web page. The current limitation to this in-game is the lack of support for Flash or other plug-ins. Currently it is expected that webpages will be published through an Auran controlled website for security reasons. Webpages will be published using similar tools to the current TrainzDev site.

The following specific tasks are intended to be solved through the use of the embedded Trainz Online browser:

* Encourage new users to become involved in the Trainz online community by providing integrated access to selected areas of the [[Trainz Online]] site from within the game environment.
* Allow the browsing of tutorials and rapid lookup of [[Help: Main Page|online community-driven help]] and information without leaving the game environment.
* Promote third-party content creation by encouraging [http://www.trainzdev.com/index.php?option=com_comprofiler&Itemid=26 personal] and [[Content Creation Groups|group]] areas within Trainz Online and allow content to lead the user directly to these areas.
* Allow the use of standard HTML editing tools for the creation of in-game tutorials and informational pages.

==In-game==
Within the game environment, [[Trainz Online]] can be accessed from anywhere- Surveyor, Driver, even the main menu. The user may open the [[Trainz Online]] interface at any time, and content may provide links to [[Trainz Online]] help or information pages. [[Trainz Online]] users have access to the following components:

* [[iTrainz Chat]] allows communication between users whenever they are in-game, enabling community chat channels and private messaging.
* The [[embedded web browser]] allows users to surf the [[Trainz Online]] site.
* The [http://online.ts2009.com/mediaWiki/index.php5/Help:Main_Page online help system] provides contextual information on tools and content.
* [[Trainz Online]] pages may provide asset links, which the user may preview or install without leaving the game environment.

[[Category:Trainz Wiki]]

Trainz SP3

2015-05-20T10:11:56Z

Idham.: /* Language Elements */

The title "[[Trainz SP3]]" typically refers to Trainz version 1.3. Although this version was a free update for existing users, it is generally considered a major product release in its own right due to the significant functionality upgrades present as compared to the [[Trainz 1.0]] release.

'''Bold text'''== New Features since Trainz 1.0 ==
* Scripted Scenarios using [[TrainzScript]].
* TBD.

]]== Included Content ==
TBD.
----
Indonesia

Class MapObject

2015-05-20T10:05:46Z

Idham.:

''Indonesia'''*[[TrainzScript Language Reference|API Hierarchy]]
**[[Class GSObject|GSObject]]
***[[Class GameObject|GameObject]]
****[[Class PropertyObject|PropertyObject]]
****[[Class TrainzGameObject|TrainzGameObject]]
*****[[Class MeshObject|MeshObject]]
******MapObject
 

*This class extends MeshObject to include product queues.
*A MapObject can have a number of product queues as defined in the queues section of the config.txt file for the asset.
*The class also provides methods to control particle emissions.
 

==MapObject Messages==
 
{{TableHeader|width=50%|margin=15px}}
|-
|bgcolor="#EEEEEE"|'''Major'''||bgcolor="#EEEEEE"|'''Minor'''||bgcolor="#EEEEEE"|'''Source'''||bgcolor="#EEEEEE" |'''Destination'''
|-
|[[MapObject Messages|MapObject]]||View-Details||?||MapObject
|-
|[[MapObject Messages|MapObject]]||View-Schedule||?||MapObject
|}
 

==Methods==
 

===GetPFXEmitterLifetime===
{{MethodHeader|public native float GetPFXEmitterLifetime(int id, int phase)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
;Returned Value
*Value of the lifetime of the effect at the specified phase.
;Syntax
float lifetime GetPFXEmitterLifetime(0,0);
;Notes
 

===GetPFXEmitterMaxRate===
{{MethodHeader|public native float GetPFXEmitterMaxRate(int id)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
;Returned Value
*Maximum rate of emissions per second.
;Syntax
float maxRate = GetPFXEmitterMaxRate(0);
;Notes
 

===GetPFXEmitterMaxSize===
{{MethodHeader|public native float GetPFXEmitterMaxSize(int id, int phase)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
;Returned Value
*Maximum size of particle at the specified phase.
;Syntax
float maxsize = GetPFXEmitterMinSize();
;Notes
 

===GetPFXEmitterMinRate===
{{MethodHeader|public native float GetPFXEmitterMinRate(int id)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
;Returned Value
*Maximum rate of emissions per second.
;Syntax
float minRtae = GetPFXEmitterMinRate(0);
;Notes
 

===GetPFXEmitterMinSize===
{{MethodHeader|public native float GetPFXEmitterMinSize(int id, int phase)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
;Returned Value
*Minimum size of particle at the specified phase.
;Syntax
float minsize = GetPFXEmitterMinSize();
;Notes
 

===GetPFXEmitterPhysicsDelay===
{{MethodHeader|public native float GetPFXEmitterPhysicsDelay(int id, int phase)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
;Returned Value
*Value for the physics delay in emission.
;Syntax
GetPFXEmitterPhysicsDelay(0,0);
;Notes
 

===GetPFXEmitterRate===
{{MethodHeader|public native float GetPFXEmitterRate(int id, int phase)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
;Returned Value
*Rate of particle creation per second.
;Syntax
particlesPerSecond = GetPFXEmitterRate(0,0);
;Notes
 

===GetPFXEmitterVelocity===
{{MethodHeader|public native float GetPFXEmitterVelocity(int id, int phase)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
;Returned Value
*Velocity in metres per second along the direction vector of emitted particles at the specified phase.
;Syntax
float speed = GetPFXEmitterVelocity(0,0);
;Notes
 

===GetQueue===
{{MethodHeader|public native ProductQueue GetQueue(string queueName)}}
;Parameters
'''queueName''' = Name of the product queue to be returned.
;Returned Value
*A reference to the queue if possible, null otherwise.
;Syntax
ProductQueue queue = GetQueue("passengers");
 

===GetQueues===
{{MethodHeader|public native ProductQueue[ ] GetQueues(void)}}
;Parameters
*None
;Returned Value
*An array of product queues, if there are no queues the array will be empty.
;Syntax
ProductQueue[] queues = GetQueues();
 

===PlaySoundScriptEvent===
{{MethodHeader|public native void PlaySoundScriptEvent(string soundTrigger)}}
;Parameters
'''soundTrigger''' = Name of the sound event to start playing, this equates to the ''trigger'' tag of the sound script subcontainer in ''config.txt''.
;Returned Value
*None
;Syntax
PlaySoundScriptEvent("dayloop");
;Notes
*Plays the specified sound event from the asset's SoundScript.
*SoundScripts are defined as sub-containers in the soundscript container of the asset's configuration.
*For details on creating assets with SoundScripts, see [["Soundscript" container|here]].
*This method will start playing the sound.
*Depending on the SoundScript configuration, the sound will either be played just once or played continuously in a looping cycle such that [[#StopSoundScriptEvent|StopSoundScriptEvent()]] will need to be called to stop it.
 

===SetPFXEmitterConeSize===
{{MethodHeader|public native void SetPFXEmitterConeSize(int id, float x, float y, float z)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''x,y,z''' = New X,Y and Z components of the particle cone size.
;Returned Value
*None
;Syntax
SetPFXEmitterConeSize(0,2.0,3.0,2.0);
;Notes
 

===SetPFXEmitterEmitParticles===
{{MethodHeader|public native void SetPFXEmitterEmitParticles(int id, int number,float time)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''number''' = The number of particles to emit.
*'''time''' = The time in seconds over which the particles are to be created.
;Returned Value
*None
;Syntax
SetPFXEmitterEmitParticles(0,100,10.0);
;Notes
 

===SetPFXEmitterEndColor===
{{MethodHeader|public native void SetPFXEmitterEndColor(int id, int phase, float r, float g, float b, float a)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''r,g,b''' = Red, green and blue components of the required color.
*'''a''' = Alpha value of the color.
;Returned Value
*None
;Syntax
SetPFXEmitterStartColor(0,0,128,128,128,64);
SetPFXEmitterStartColor(0,0,0.5,0.5,0.5,0.25);
;Notes
*Red, green, blue and alpha may be entered as integer or float values in the ranges 0..255 and 0.0..1.0 respectively.
*Both of the examples above give the same result.
*Note that 1,1,1,1 will be interpreted as float input and will produce white, whereas 2,2,2,2 will be interpreted as integers and will give a result which is almost black.
 

===SetPFXEmitterLifetime===
{{MethodHeader|public native void SetPFXEmitterLifetime(int id, int phase, float life)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''life''' = The new lifetime of particles in seconds at the specified phase.
;Returned Value
*None
;Syntax
SetPFXEmitterLifetime(0,0,10);
;Notes
 

===SetPFXEmitterMaxRate===
{{MethodHeader|public native void SetPFXEmitterMaxRate(int id, float newsize)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''rate''' = The new maximum rate of emission per second.
;Returned Value
*None
;Syntax
SetPFXEmitterMaxRate(0,5.0);
;Notes
 

===SetPFXEmitterMaxSize===
{{MethodHeader|public native void SetPFXEmitterMaxSize(int id, int phase, float newsize)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''newsize''' = The new maximum size of particles at the specified phase.
;Returned Value
*None
;Syntax
SetPFXEmitterMaxSize(0,0,10);
;Notes
 

===SetPFXEmitterMinRate===
{{MethodHeader|public native void SetPFXEmitterMinRate(int id, float rate)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''rate''' = The new minimum rate of emission per second.
;Returned Value
*None
;Syntax
SetPFXEmitterMinRate(0,5.0);
;Notes
 

===SetPFXEmitterMinSize===
{{MethodHeader|public native void SetPFXEmitterMinSize(int id, int phase, float newsize)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''newsize''' = The new minimum size of particles at the specified phase.
;Returned Value
*None
;Syntax
SetPFXEmitterMinSize(0,0,10);
;Notes
 

===SetPFXEmitterPhysicsDelay===
{{MethodHeader|public native void SetPFXEmitterPhysicsDelay(int id, int phase, float value)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''value''' = The new physics delay value to set for the specified phase.
;Returned Value
*None
;Syntax
SetPFXEmitterPhysicsDelay(0,0,5.0);
;Notes
 

===SetPFXEmitterRate===
{{MethodHeader|public native void SetPFXEmitterRate(int id, int phase, float rate)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''rate''' = New rate of particle creation per second at the specified phase.
;Returned Value
*None
;Syntax
SetPFXEmitterRate(0,0,5.0);
;Notes
 

===SetPFXEmitterStartColor===
{{MethodHeader|public native void SetPFXEmitterStartColor(int id, int phase, float r, float g, float b, float a)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''r,g,b''' = Red, green and blue components of the required color.
*'''a''' = Alpha value of the color.
;Returned Value
*None
;Syntax
SetPFXEmitterStartColor(0,0,128,128,128,64);
SetPFXEmitterStartColor(0,0,0.5,0.5,0.5,0.25);
;Notes
*Red, green, blue and alpha may be entered as integer or float values in the ranges 0..255 and 0.0..1.0 respectively.
*Both of the examples above give the same result.
*Note that 1,1,1,1 will be interpreted as float input and will produce white, whereas 2,2,2,2 will be interpreted as integers and will give a result which is almost black.
 

===SetPFXEmitterTexture===
{{MethodHeader|public native void SetPFXEmitterTexture(int id, KUID textureKUID)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''textureKUID''' = The kuid of the new texture.
;Returned Value
*None
;Syntax
SetPFXEmitterTexture(0,<kuid:1234:5678>);
;Notes
 

===SetPFXEmitterVelocity===
{{MethodHeader|public native void SetPFXEmitterVelocity(int id, int phase, float velocity)}}
;Parameters
*'''id''' = The ID of the particle effect, starting at zero and in the order defined in ''config.txt''.
*'''phase''' = The phase of the effect, if there is only one phase use zero.
*'''velocity''' = New velocity in metres per second along the direction vector of emitted particles at the specified phase.
;Returned Value
*None
;Syntax
SetPFXEmitterVelocity(0,0,5.0);
;Notes
 

===StopSoundScriptEvent===
{{MethodHeader|public native void StopSoundScriptEvent(string soundTrigger)}}
;Parameters
'''soundTrigger''' = Name of the sound event to start playing, this equates to the ''trigger'' tag of the sound script subcontainer in ''config.txt''.
;Returned Value
*None
;Syntax
StopSoundScriptEvent("dayloop");
;Notes
*Terminates a looped sound script previously started with [[#PlaySoundScriptEvent|PlaySoundScriptEvent()]].
 

==Related Methods==

==Categories==
[[Category:Script Class]]

TrainzScript Language Reference

2015-05-20T10:03:33Z

Idham.: /* Language Topics */ indonesia

*[[Trainzscript Index]] 

Indonesia

[http://www.example.com
Indonesia

Trainz indonesia

=Categories=
[[Category:TrainzScript]]

TrainzScript Language Reference

2015-05-19T19:49:42Z

Idham.: /* Language Elements */

*[[Trainzscript Index]] 

Indonesia

[http://www.example.com
Indonesia

=Class API Reference=
The following classes form the core of the TrainzScript language, and are present in all runtime environments.

''Classes marked with an asterisk have no parent class.''

*[[class GSObject|GSObject]] *
**[[class Asset|Asset]]
**[[class GameObject|GameObject]]
***[[class TrainzGameObject|TrainzGameObject]]
***[[class PropertyObject|PropertyObject]] *
****[[class Library|Library]]
**[[class KUID|KUID]]
**[[class Soup|Soup]]
**[[class StringTable|StringTable]]
*[[class Constructors|Constructors]] *
*[[class Math|Math]] *
*[[class Router|Router]] *
*[[class Str|Str]] *

Other common classes used in the Trainz game runtime environment are documented under [[TrainzScript Library Reference]].

=Categories=
[[Category:TrainzScript]]

TrainzScript Language Reference

2015-05-19T19:48:18Z

Idham.: /* Language Elements */

*[[Trainzscript Index]] 

Indonesia

=Language Topics=
*[[Arrays]]

=Class API Reference=
The following classes form the core of the TrainzScript language, and are present in all runtime environments.

''Classes marked with an asterisk have no parent class.''

*[[class GSObject|GSObject]] *
**[[class Asset|Asset]]
**[[class GameObject|GameObject]]
***[[class TrainzGameObject|TrainzGameObject]]
***[[class PropertyObject|PropertyObject]] *
****[[class Library|Library]]
**[[class KUID|KUID]]
**[[class Soup|Soup]]
**[[class StringTable|StringTable]]
*[[class Constructors|Constructors]] *
*[[class Math|Math]] *
*[[class Router|Router]] *
*[[class Str|Str]] *

Other common classes used in the Trainz game runtime environment are documented under [[TrainzScript Library Reference]].

=Categories=
[[Category:TrainzScript]]

Trainz SP3

2015-05-19T19:46:53Z

Idham.: /* New Features since Trainz 1.0 */

TrainzOnline:Copyrights

2015-05-19T19:42:45Z

Idham.: jakarta

[[File]]This page really should exist. I'm entering this in the hopes that someone with authority will replace this with the relevant information.

Template:Platform Mobile Select Area

2015-05-19T19:41:09Z

Idham.: iyy

[http://www.example.com link'''<nowiki>Bold text</nowiki>ic
''' title]=Other Topics=
Select the area within Trainz Mobile you want to explore.

[[File:area-menus.png |link=Help:Mobile Main Menu]] [[File:area-driving.png |link=mobile-area-driving]] [[File:area-building.png |link=Help:Mobile_Surveyor]] [[File:area-dlc.png|link=Help:Mobile_Main_Menu:Get_New_Content]]

[[Select your Platform|View help for a different platform]]