Hardware Design - Revision history

Khornel at 11:31, 8 March 2022

2022-03-08T11:31:37Z

Khornel: /* Tutorial */

2022-03-08T11:30:53Z

Tutorial

Khornel at 11:30, 8 March 2022

2022-03-08T11:30:48Z

Khornel at 15:09, 28 July 2021

2021-07-28T15:09:07Z

Khornel: /* Hardware design construction */

2021-07-23T17:00:57Z

Hardware design construction

Khornel at 17:00, 23 July 2021

2021-07-23T17:00:34Z

Khornel: /* Textures */

2021-07-23T15:17:43Z

Textures

Khornel: /* Textures */

2021-07-23T15:16:26Z

Textures

Khornel: /* Hardware design construction */

2021-07-23T15:15:34Z

Hardware design construction

Khornel: /* Hardware design construction */

2021-07-23T15:14:38Z

Hardware design construction

← Older revision		Revision as of 11:31, 8 March 2022
Line 69:		Line 69:

	2. This display will show how your atlasses are mapped on the main texture, each UV will have a different color, here seen in red and then green.		2. This display will show how your atlasses are mapped on the main texture, each UV will have a different color, here seen in red and then green.
−
−	~~== Example ==~~
−	~~Example TyD goes here~~

@@ Line 5: / Line 5: @@
 == Tutorial ==
 Check out a video tutorial on how to create hardware designs here:
 ‎<youtube>b68eGCr5KAg</youtube>

@@ Line 1: / Line 1: @@
-Introduction goes here.
+Hardware designs allows the player to create a visual version of their hardware products, to make them more tangible.
-== TyD file layout ==
+To edit hardware designs, open the Mods window from the main menu and click on "Hardware design editor" button.
-How to layout initial TyD file goes here.
 == Hardware design construction ==

@@ Line 7: / Line 7: @@
 === Overall structure ===
-A '''hardware design''' constists of a bunch of '''Mesh objects''', each of which has a mesh with optional morph targets. The '''hardware design''' has one '''Mesh object''' as its base model, with '''attachment points''' on its faces to attach other '''Mesh objects'''.
+A '''hardware design''' consists of a bunch of '''Mesh objects''', each of which has a mesh with optional morph targets. The '''hardware design''' has one '''Mesh object''' as its base model, with '''attachment points''' on its faces to attach other '''Mesh objects'''.
 The assembled hardware design should fit in a 2x2x2 cube centered around (0,0,0), i.e. stretching 1 unit out along each axis. To see if your object has the correct dimensions, check that it fits neatly on screen in the editor.

@@ Line 9: / Line 9: @@
 A '''hardware design''' constists of a bunch of '''Mesh objects''', each of which has a mesh with optional morph targets. The '''hardware design''' has one '''Mesh object''' as its base model, with '''attachment points''' on its faces to attach other '''Mesh objects'''.
-The assembled hardware design should fit in a 2x2x2 cube centered around (0,0,0). That is stretching 1 unit out along each vector. To see if your object has the correct dimensions, check that it fits neatly on screen in the editor.
+The assembled hardware design should fit in a 2x2x2 cube centered around (0,0,0), i.e. stretching 1 unit out along each axis. To see if your object has the correct dimensions, check that it fits neatly on screen in the editor.
 === Attachment points ===

@@ Line 23: / Line 23: @@
 You'll need 3 textures, of which the last 2 are optional.
-. texture maps each R, G and B channel to a color the player chooses.
+. texture maps each R, G and B channel to a primary, secondary and tertiary color the player chooses.
 . texture where the R, G and B channels map to Smoothness, Emission and Mask, where the mask controls whether the first texture maps to player colors or just render as-is.

@@ Line 17: / Line 17: @@
 === Textures ===
-All '''Mesh objects''' should map to 1 atlas texture. Each mesh can have sub atlasses within the main atlas texture, in a single line, e.g. a row or column of textures in your atlas that is used as an atlas for one of your mesh objects.
+All '''Mesh objects''' of a '''hardware design''' should map to 1 atlas texture. Each mesh can have sub atlasses within the main atlas texture, in a single line, e.g. a row or column of textures in your atlas that is used as an atlas for one of your mesh objects.
 Textures work exactly the same as the standard furniture textures, [[Furniture Modding#The standard furniture shader|which you can read about here]].

@@ Line 10: / Line 10: @@
 === Attachment points ===
-An attachment points sits in the middle of a triangle of the base model's mesh, facing outward, i.e. perpendicular to the triangle's plane. Attachment points naturally move as the base mesh is morphed.
+An '''attachment point''' sits in the middle of a triangle of the base model's mesh, facing outward, i.e. perpendicular to the triangle's plane. '''Attachment points''' naturally move as the base mesh is morphed.
-Mesh objects can be attached to an attachment point with some offset position and rotation.
+'''Mesh objects''' can be attached to an '''attachment point''' with some offset position and rotation.
-Mesh objects do not need to be attached to a triangle that matches where it will sit on the object, but it should be attached to an attachment point that moves in the same way you want the Mesh object to move when the base model is morphed. For instance, if you have a airplane wing and you attach a motor, the attachment point doesn't need to be where the motor is attached, but rather a place on the wing that moves in the same direction you want the motor to move, when the wing is curled or stretched.
+'''Mesh objects''' do not need to be attached to a triangle that matches where it will sit on the object, but it should be attached to an '''attachment point''' that moves in the same way you want the '''Mesh object''' to move when the base model is morphed. For instance, if you have a airplane wing and you attach a motor, the attachment point doesn't need to be where the motor is attached, but rather a place on the wing that moves in the same direction you want the motor to move, when the wing is curled or stretched.
 === Textures ===
-All mesh objects should map to 1 atlas texture. Each mesh can have sub atlasses within the main atlas texture, in a single line, e.g. a row or column of textures in your atlas that is used as an atlas for one of your mesh objects.
+All '''Mesh objects''' should map to 1 atlas texture. Each mesh can have sub atlasses within the main atlas texture, in a single line, e.g. a row or column of textures in your atlas that is used as an atlas for one of your mesh objects.
 Textures work exactly the same as the standard furniture textures, [[Furniture Modding#The standard furniture shader|which you can read about here]].