New art tutorials - Revision history

Fire-hound at 09:20, 2 May 2020

2020-05-02T09:20:41Z

Fire-hound at 17:56, 13 February 2018

2018-02-13T17:56:09Z

Fire-hound: better explained, modified the headings so content index is shown

2018-01-25T13:34:05Z

better explained, modified the headings so content index is shown

Fire-hound: /* Scripts */ linked the XML params

2018-01-25T13:26:58Z

‎Scripts: linked the XML params

Fire-hound: added the bottom links?

2017-12-09T09:57:11Z

added the bottom links?

Fire-hound: /* Physical nodes */ linked it in

2017-12-05T20:54:58Z

‎Physical nodes: linked it in

Fire-hound: added a section on bodies and helpers

2017-12-05T20:52:58Z

added a section on bodies and helpers

Fire-hound: /* Scripts */ defined how to rename

2017-12-05T09:24:30Z

‎Scripts: defined how to rename

Fire-hound: /* Libraries */ illustration of Class tags

2017-12-05T09:21:44Z

‎Libraries: illustration of Class tags

Fire-hound: /* Libraries */ explain why clone in editor

2017-12-05T00:12:39Z

‎Libraries: explain why clone in editor

@@ Line 1: / Line 1: @@
+{{ Stub }}
 == New art tutorials ==
 Here we will try to better explain how the various entities get glued together to work in the game.

← Older revision		Revision as of 17:56, 13 February 2018
Line 68:		Line 68:

	In case the helpers are absent, the turret gets joined about it's prats 3d origin points.		In case the helpers are absent, the turret gets joined about it's prats 3d origin points.
		+
		+	{{Navbox Mapping}}

	[[Category:Mapping]]		[[Category:Mapping]]

@@ Line 1: / Line 1: @@
 ==Libraries==
 {| cellspacing="5"
 |[[File:1._New_library.jpg|350px]] || The first thing to create is the library that will reference to the new assets, the '''Entity Archetype Library'''.
@@ Line 21: / Line 26: @@
   Note, the Entity archetypes library can be made map-local to the map folder, while the entities seem to be bound to the game folders?
-==Scripts==
+===Scripts===
 {| cellspacing="5"
 |[[File:6._Weapons_XMLs.jpg|350px]] || Now on we copy the XMLs defining the entities matching ours the closest.
 |}
 {| cellspacing="5"
-|[[File:8._Create_Entities.jpg|350px]] || We create them, by copying and renaming them in the new place. New names are predetermined by the '''Class''' tag in the library we edited before. Each typing mistake will render the object and yield an error in the Sandbox2 log.
+|[[File:8._Create_Entities.jpg|350px]] || We create them, by copying and renaming them in the new place. New names are predetermined by the '''Class''' tag in the library we edited before. Each typing mistake will render the object inactive and yield an error in the Sandbox2 log.
 |}
 {| cellspacing="5"
@@ Line 41: / Line 46: @@
 For more in depth explanation of the parameters, look up the [[XML parameters]].
-==Physical nodes==
+===Physical nodes===
 An physical node can be an 3d body, an empty "dummy" or both. They can be interactively linked in the point the dummy is placed, and rotated about one of it's axes (usually the X axis).
 It is customary that the Y axis points "down the barrel" if we speak bout turrets or weapons.

@@ Line 39: / Line 39: @@
 |}
 Fire up the editor and check how they work by first opening the new library, and importing some asset into the map. After saving and restart of the editor, enter the game mode and watch how it behaves. Adjust repeatedly until satisfied.
 ==Physical nodes==
 An physical node can be an 3d body, an empty "dummy" or both. They can be interactively linked in the point the dummy is placed, and rotated about one of it's axes (usually the X axis).

← Older revision		Revision as of 09:57, 9 December 2017
Line 61:		Line 61:

	In case the helpers are absent, the turret gets joined about it's prats 3d origin points.		In case the helpers are absent, the turret gets joined about it's prats 3d origin points.
		+
		+	[[Category:Mapping]]

@@ Line 43: / Line 43: @@
 It is customary that the Y axis points "down the barrel" if we speak bout turrets or weapons.
 To import an foreign body into an map, simply place the dummy box into it and change it's object to point to Your */*.cgf file.
-The material will either automatically be assigned from the equally named *.mtl file, or maunally asingend to it in the material editor.
+The material will either automatically be assigned from the equally named *.mtl file, or manually assigned to it in the material editor.
-To produce an cgf and mtl file  refer to New_art creation.
+To produce an cgf and mtl file  refer to [[Asset_creation]] creation page.
-Those physical nodes can be replaced on the turrets as slong as some few rules are obeyed in the process of theyr creation:
+Those physical nodes can be replaced on the turrets as long as some few rules are obeyed in the process of their creation:
 . Reset the bases' origin to it's center - it's what it will pivot (yaw) about

@@ Line 12: / Line 12: @@
 {| cellspacing="5"
 |[[File:4._Find_it.jpg|350px]] || Find the library in the filesystem and open it with an text editor (I used Geany) and change the entries accordingly to point to Your instead of existing entities.
 |}

@@ Line 5: / Line 5: @@
 The new library itself can only hold existing archetypes, so for the initial creation of the yet to be made archetypes, an existing one is to be selected from the in editor list.
 {| cellspacing="5"
-|[[File:2._As_many_as_needed.jpg|350px]] || Until all to be made entries are created just select along or clone each next one.
+|[[File:2._As_many_as_needed.jpg|350px]] || Until all to be made entries are created just select along or clone each next one. It is necessary to make this in the editor, so each gets it's unique ID, by which it's referenced internal now on.
 |}
 {| cellspacing="5"