Prequel Blender to Trainz - Revision history

Ek.skirl: /* Parts of this prequel tutorial */

2023-08-19T09:27:35Z

Parts of this prequel tutorial

← Older revision		Revision as of 09:27, 19 August 2023
Line 58:		Line 58:
	https://online.ts2009.com/mediaWiki/index.php/Getting_Started_in_TrainzScript'''''		https://online.ts2009.com/mediaWiki/index.php/Getting_Started_in_TrainzScript'''''
	----		----
	(State: August 10, 2023, 19:10)		(State: August 19, 2023, 11:30)
	----		----

Ek.skirl: /* Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz */

2023-08-19T09:25:52Z

Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz

← Older revision		Revision as of 09:25, 19 August 2023
Line 2:		Line 2:

	'''''TBD: Some issue I didn't found the reason for: '''''		'''''TBD: Some issue I didn't found the reason for: '''''

	[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)		[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)
	SetFXAnimationState("doors", false); does not work as expected and closes the doors not immediately.		SetFXAnimationState("doors", false); does not work as expected and closes the doors not immediately.
Line 7:		Line 8:
	[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..		[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..
	[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.		[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.
	[*] P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door.		[+] P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door.
	The animations where deactivated and activated antipodal.		The animations where deactivated and activated antipodal.
	'''P.S. August 19, 2023: This tutorial site, the ZIP-file as well as the config and the script pages where updated.'''		[+] '''P.S. August 19, 2023: This tutorial site, the ZIP-file as well as the config and the script pages where updated.'''

			[*] A small not critical bug: The fascia name won't be shown immediatly right after the first propertie change.
			This may be caused by the not existing soup-value. Didn't found yet the location to fix it.
			Workaround is to save the asset properties, reopen it and do a small change to the text.

	=== Intro ===		=== Intro ===

Ek.skirl: /* Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz */

2023-08-19T09:15:12Z

Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz

← Older revision		Revision as of 09:15, 19 August 2023
Line 3:		Line 3:
	'''''TBD: Some issue I didn't found the reason for: '''''		'''''TBD: Some issue I didn't found the reason for: '''''
	[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)		[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)
	SetFXAnimationState("doors", false); does not work as expected and closes the doors not immediately. They will be closed not before the next open call with SetFXAnimationState("doors", true);.		SetFXAnimationState("doors", false); does not work as expected and closes the doors not immediately.
			They will be closed not before the next open call with SetFXAnimationState("doors", true);.
	[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..		[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..
	[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.		[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.
	[*] ~~'''~~P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door. The animations where deactivated and activated antipodal.		[*] P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door.
	P.S. August 19, 2023: ~~The~~ ZIP-file as well as the config and script pages where updated.'''		The animations where deactivated and activated antipodal.
			'''P.S. August 19, 2023: This tutorial site, the ZIP-file as well as the config and the script pages where updated.'''

	=== Intro ===		=== Intro ===

Ek.skirl: /* Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz */

2023-08-19T09:11:15Z

Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz

← Older revision		Revision as of 09:11, 19 August 2023
Line 3:		Line 3:
	'''''TBD: Some issue I didn't found the reason for: '''''		'''''TBD: Some issue I didn't found the reason for: '''''
	[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)		[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)
	SetFXAnimationState("doors", false); does not ~~works fine~~ and closes the doors not immediately. They will be closed not before the next open call.		SetFXAnimationState("doors", false); does not work as expected and closes the doors not immediately. They will be closed not before the next open call with SetFXAnimationState("doors", true);.
	[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..		[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..
	[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.		[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.
	[*] '''P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door. The animations where deactivated and activated antipodal.		[*] '''P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door. The animations where deactivated and activated antipodal.
	The ZIP-file ~~(without updated tutorial pictures yet)~~ as well as the config and script pages where updated.'''		P.S. August 19, 2023: The ZIP-file as well as the config and script pages where updated.'''

	=== Intro ===		=== Intro ===

Ek.skirl: /* Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz */

2023-08-19T08:53:39Z

Prequel to Andi Smith's wiki tutorial shed house Blender to Trainz

← Older revision		Revision as of 08:53, 19 August 2023
Line 4:		Line 4:
	[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)		[*] SetFXAnimationState("doors", true); works fine and opens the doors immediately. (script lines 175ff.)
	SetFXAnimationState("doors", false); does not works fine and closes the doors not immediately. They will be closed not before the next open call.		SetFXAnimationState("doors", false); does not works fine and closes the doors not immediately. They will be closed not before the next open call.
	A Trainz Support ticket [UIT-837-15571] was generated.		[+] A Trainz Support ticket [UIT-837-15571] was generated and is now closed..
			[+] A Trainz Bug Report was generated at 17.08.2023, 20:07.
	[*] '''P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door. The animations where deactivated and activated antipodal.		[*] '''P.S. August 17, 2023: Workaround (Solution?) is to use a second animation closing the door. The animations where deactivated and activated antipodal.
	The ZIP-file (without updated tutorial pictures yet) as well as the config and script pages where updated.'''		The ZIP-file (without updated tutorial pictures yet) as well as the config and script pages where updated.'''

Ek.skirl: /* Creating the two animation files opendoors.kin and closedoors.kin */

2023-08-19T08:22:33Z

Creating the two animation files opendoors.kin and closedoors.kin

← Older revision		Revision as of 08:22, 19 August 2023
Line 492:		Line 492:
	Using copied Blender file G2 the only change we do is to reverse the animation of the two door empties (not the doors itself). Than save the Blender file G2 and export with again marked doors and three animation empties. Remember that the third animation emptie is the b.r.main named empty, that has the two door empties as children and that the doors are children of their animation empties. The exported fbx file is closedoors.fbx.		Using copied Blender file G2 the only change we do is to reverse the animation of the two door empties (not the doors itself). Than save the Blender file G2 and export with again marked doors and three animation empties. Remember that the third animation emptie is the b.r.main named empty, that has the two door empties as children and that the doors are children of their animation empties. The exported fbx file is closedoors.fbx.

	==== Creating the ~~two~~ animation ~~files opendoors.kin and~~ closedoors.kin ====		==== Creating the second animation file closedoors.kin ====
	With the files (excluded the two .kin files) we now may start the first Trainz import run.		With the files (excluded the two .kin files) we now may start the first Trainz import run.
	Did you thought about the kuids? Ok. Import the ExportToTrainz folder to Trainz, possibly submit the edits and open the asset again in explorer. One will find two .kin files. We copy the „closedoors_scene.kin“ file ~~onto~~ the EportToTrainz folder as ouer second .kin file.		Did you thought about the kuids? Ok. Import the ExportToTrainz folder to Trainz, possibly submit the edits and open the asset again in explorer. One will find two .kin files. We copy the „closedoors_scene.kin“ file into the EportToTrainz folder as ouer second .kin file.
	The closedoors.fbx file in the BlenderToTrainz folder may be deleted or saved other where as well as the closedoors.trainzmesh file and the closedoors.fbx in the submitted asset folder.		The closedoors.fbx file in the BlenderToTrainz folder may be deleted or saved other where as well as the closedoors.trainzmesh file and the closedoors.fbx in the submitted asset folder.
	The second Trainz import run with the eleven files will bring the shedhouse asset to Trainz.		The second Trainz import run with the eleven files will bring the shedhouse asset to Trainz.

Ek.skirl: /* FBX export from Blender and import to Trainz */

2023-08-19T08:15:12Z

FBX export from Blender and import to Trainz

← Older revision		Revision as of 08:15, 19 August 2023
Line 442:		Line 442:

	=== FBX export from Blender and import to Trainz ===		=== FBX export from Blender and import to Trainz ===
	Starting from the Blender file ”shed house F animation.blend” we arrange some preparation for the FBX export. First we need Trainz fitting material adjustments and second we have to prepare some settings of the export dialog. Because one will use these export settings more than one time, one shell will use the possibility of Blender to create a template for these Trainz settings.		Starting from the Blender file ”shed house F1 animation opendoors.blend” we arrange some preparation for the FBX export. First we need Trainz fitting material adjustments and second we have to prepare some settings of the export dialog. Because one will use these export settings more than one time, one shell will use the possibility of Blender to create a template for these Trainz settings.
	As explained in part 3 finally we use a Trainz material named with the ending .m.onetex which tells that there will be only one albedo (diffuse) texture image. And we have finally only one material to export within the fbx-file.		As explained in part 3 finally we use a Trainz material named with the ending .m.onetex which tells that there will be only one albedo (diffuse) texture image. And we have finally only one material to export within the fbx-file.
	An fbx-file contains the meshes, the name of the material, the uv-mapping to it, the names and transformation data of the empties, the animation keyframes and the name of the source texture image files used creating the export material.		An fbx-file contains the meshes, the name of the material, the uv-mapping to it, the names and transformation data of the empties, the animation keyframes and the name of the source texture image files used creating the export material.
	Since we baked the texture from the whole model and with the premise that the mapping and model mesh were unchanged from that, the textures fit to parts of the model too.		Since we baked the texture from the whole model and with the premise that the mapping and model mesh were unchanged from that on, the textures fit to parts of the model too.
	The roof alone and the ~~other parts together~~ she'll be exported apart but we will use the same ~~material~~.		The roof alone, the walls (with the attachment empties) and the doors (with the animation empties) she'll be exported apart but we will ever use the same texture image for the materials.
	We use the “engineshed_textureimage.png” while exporting.		We use the “engineshed_textureimage.png” while exporting. If your file has another name so you have to exchange it with that here used “engineshed_textureimage” name in the fitting “engineshed_textureimage.texture.txt” file name.
	It is recommended to use a copy of the starting Blender file ”shed house F animation.blend”.		It is recommended to use a copy of the starting Blender file ”shed house F1 animation opendoors.blend”.

	==== Export settings of the FBX export dialog ====		==== Export settings of the FBX export dialog ====
	There are some settings to deal with and it is strongly advised you to use a copy of the Blender file “shed house F animation.blend” because we have to change models material shader.		There are some settings to deal with and it is strongly advised you to use a copy of the Blender file “shed house F1 animation opendoors.blend” because we have to change models material shader.
	And ~~that is~~ why the model in this phase does not ever look as real, especially for PBR materials.. The Trainz import needs some special material conventions to make the things possible. This is some kind of workaround for some problems. In our onetex case this doesn't happen.		And that’s why the model in this phase does not ever look as real, especially for PBR materials. The Trainz import needs some special material conventions to make the things possible. This is some kind of workaround for some problems.
	~~Here we copied~~ the ~~Blender file F~~ to “shed house G fbx export.blend”.		In our onetex case this doesn't happen. We use here the to “shed house G1 fbx export opendoors.blend” copied Blender file F1.
	If we start the export dialog we will get a properties window. The right panel there is to set the export properties. It offers on top the possibility to save Operator Presets as templates. There one may save a Trainz export settings preset. Use menu File,entry Export, option FBX to reach this window.		If we start the fbx export dialog, we will get a properties window. The right panel there is to set the export properties. It offers on top the possibility to save Operator Presets as templates. There one may save a Trainz export settings preset. Use menu File, entry Export, option FBX to reach this window.
	The following settings are useful property values.		The following settings are useful property values.

Line 460:		Line 460:

	==== FBX export of roof-part object (roof.fbx) ====		==== FBX export of roof-part object (roof.fbx) ====
	Enter the Shading workspace in Blender and mark the roof. Then in the Shader area unlink the material (x) and create a new one with the name “roof_mat.m.onetex”. Add a new Texture Image node to the left of the BSDF principled node and connect the Color output with the Base Color input.		Enter the Shading workspace in Blender and mark the roof. Then in the Shader area unlink the material (x) and create a new one with the name “roof_mat.m.onetex”. Add a new Texture Image node to the left of the BSDF principled shader node and connect the Color output with the Base Color input.
	Inside the Image Texture node we use the right sided folder symbol to connect our baked and saved texture image “engineshed_textureimage.png” to it. The roof in the 3D View should now again look fine. With the marked roof call the fbx export dialog (menu ~~file~~, entry ~~export~~ with option FBX).		Inside the Image Texture node we use the right sided folder symbol to connect our baked and saved texture image “engineshed_textureimage.png” to it. The roof in the 3D View should now again look fine.
			With the marked roof call the fbx export dialog (menu File, entry Export with option FBX).
	Now set the export settings in the right panel (see chapter Export settings of the FBX export dialog).		Now set the export settings in the right panel (see chapter Export settings of the FBX export dialog).
	Choose the ExportToTrainz folder, the filename as ~~roof~~.~~fbx~~ and start exporting.		Choose the ExportToTrainz folder, the filename as „roof.fbx“ and start exporting.
	That’s it for the roof.		That’s it for the roof. To save a little bit time one may copy the texture image node to insert it to the other materials.

	[[File:shed house G2 fbx export preparations for roof.png\|x300px\|Picture G2]]		[[File:shed house G2 fbx export preparations for roof.png\|x300px\|Picture G2]]

	==== FBX export of ~~remaining objects,~~ walls~~, doors,~~ empties (shed.fbx) ====		==== FBX export of walls and attachment empties (shed.fbx) ====
	In the 3D View mark ~~all parts without~~ the ~~roof~~. This may be done hiding the roof and with the cursor in the 3D View ~~press~~ A.		Enter the Shading workspace in Blender and mark the walls. Then in the Shader area unlink the material (x) and create a new one with the name “walls_mat.m.onetex”. Add a new Texture Image node to the left of the BSDF principled shader node and connect the Color output with the Base Color input.
	Then call the fbx export dialog (menu ~~file~~, entry ~~export~~ with option fbx), proof the export settings in the right panel (see chapter Export settings of the FBX export dialog), choose the ExportToTrainz folder, the filename as ~~shed~~.~~fbx~~ and start exporting.		Inside the Image Texture node we use the right sided folder symbol to connect our baked and saved texture image “engineshed_textureimage.png” to it.
	That’s it for the shed walls~~, empties, animation~~ and the ~~doors~~.		Or shorter insert the copied texture image node.
			The roof in the 3D View should now again look fine.
			In the outliner right top area mark the walls and the five attachment empties. This may be done also by hiding the roof, the doors as well as the three animation empties and with the cursor in the 3D View pressing A.
			Then with only marked walls and the five attachment empties call the fbx export dialog (menu File, entry Export with option fbx), proof the export settings in the right panel (see chapter Export settings of the FBX export dialog), choose the ExportToTrainz folder, the filename as “shed.fbx“ and start exporting.
			That’s it for the shed walls and the five attachment empties.

	[[File:shed house G3 fbx export preparations for shed.png\|x300px\|Picture G3]]		[[File:shed house G3 fbx export preparations for shed.png\|x300px\|Picture G3]]

			==== FBX export of doors and animation empties for opendoors (doors.fbx) ====
			And now the same for the two doors and the three animation empties and the output file name „doors.fbx“. This will include the animation keyframes for opening the doors.
			The material adding process is a little bit different and consists of two parts.
			First mark one door and add the new material “doors_mat.m.onetex“ as described. Second mark the other door and now one may append the same material again by choosing it from the list of the exiating materials. One will find it behind the small beachball icon.

			[[File:shed house G4 fbx export preparations for open doors.png\|x300px\|Picture G4]]

			Save the used Blender file G1 and then again as a copy “shed house G2 fbx export closedoors.blend”

			==== FBX export of doors and animation empties (closedoors.fbx) ====
			Using copied Blender file G2 the only change we do is to reverse the animation of the two door empties (not the doors itself). Than save the Blender file G2 and export with again marked doors and three animation empties. Remember that the third animation emptie is the b.r.main named empty, that has the two door empties as children and that the doors are children of their animation empties. The exported fbx file is closedoors.fbx.

			==== Creating the two animation files opendoors.kin and closedoors.kin ====
			With the files (excluded the two .kin files) we now may start the first Trainz import run.
			Did you thought about the kuids? Ok. Import the ExportToTrainz folder to Trainz, possibly submit the edits and open the asset again in explorer. One will find two .kin files. We copy the „closedoors_scene.kin“ file onto the EportToTrainz folder as ouer second .kin file.
			The closedoors.fbx file in the BlenderToTrainz folder may be deleted or saved other where as well as the closedoors.trainzmesh file and the closedoors.fbx in the submitted asset folder.
			The second Trainz import run with the eleven files will bring the shedhouse asset to Trainz.

	=== Suggestion for a session test layout ===		=== Suggestion for a session test layout ===

Ek.skirl: /* Adding three more empties as animation points and animate it */

2023-08-18T10:00:06Z

Adding three more empties as animation points and animate it

← Older revision		Revision as of 10:00, 18 August 2023
Line 384:		Line 384:

	While writing this tutorial I found that it is more effectiv to do this later down and not here. But one may use it as a small exercise.		While writing this tutorial I found that it is more effectiv to do this later down and not here. But one may use it as a small exercise.
	This file is never more used. The background of the second file is to get the second animation (.kin) file for closing the doors.		This file is never more used. The only background of the second file is to get the second animation (.kin) file for closing the doors.

Ek.skirl: /* Adding three more empties as animation points and animate it */

2023-08-18T09:59:14Z

Adding three more empties as animation points and animate it

← Older revision		Revision as of 09:59, 18 August 2023
Line 382:		Line 382:

	Now we setup a second file from this Blender file “shed house F2 animation closedoors.blend” with the only change to reverse the animation.		Now we setup a second file from this Blender file “shed house F2 animation closedoors.blend” with the only change to reverse the animation.

			While writing this tutorial I found that it is more effectiv to do this later down and not here. But one may use it as a small exercise.
			This file is never more used. The background of the second file is to get the second animation (.kin) file for closing the doors.


	[[File:shed house F6 animation result overview closedoors.png\|x300px\|Picture F6]]		[[File:shed house F6 animation result overview closedoors.png\|x300px\|Picture F6]]

	~~The background of the second file is to get the second animation (.kin) file for closing the doors.~~

	----		----

Ek.skirl: /* Texture text file engineshed_textureimage.texture.txt */

2023-08-18T09:30:24Z

Texture text file engineshed_textureimage.texture.txt

← Older revision		Revision as of 09:30, 18 August 2023
Line 412:		Line 412:
	The sound file will play repeatedly while doors are open. We use the file of the original tutorial. It's a short bell-sound.		The sound file will play repeatedly while doors are open. We use the file of the original tutorial. It's a short bell-sound.

	==== Texture text file engineshed_textureimage.texture.txt ====		==== Texture text file engineshed_textureimage.texture.txt and the texture image file engineshed_brick_metal_sheet.png ====
	All used textures need some text files as a bridge between texture file names and names used in the config.txt. These files tell Trainz some additional information about use cases of the image files.		All used textures need some text files as a bridge between texture file names and names used in the config.txt. These files tell Trainz some additional information about use cases of the image files.
	We here only use the .m.onetex materials type that only needs an albedo/diffuse texture file. We use the same for all three materials. While fbx-export from blender we use the in Part 2 D exported texture image “engineshed_textureimage.png” with the help of a Texture Image node. The name of the used texture image file without the ending “.png” we have to use for the first part of the .texture.txt file.		We here only use the .m.onetex materials type that only needs an albedo/diffuse texture file. We use the same for all three materials. While fbx-export from blender we use the in Part 2 D exported texture image “engineshed_textureimage.png” with the help of a Texture Image node. The name of the used texture image file without the ending “.png” we have to use for the first part of the .texture.txt file.