Help:VE171 - Revision history

Tonyhilliam at 02:33, 20 February 2018

2018-02-20T02:33:14Z

← Older revision		Revision as of 02:33, 20 February 2018
Line 1:		Line 1:
	''Expected texture file type but found 'image filename' for 'resource reference'''		VE171: ''Expected texture file type but found 'image filename' for 'resource reference'''

	For example:		For example:

Windwalkr at 12:36, 12 November 2016

2016-11-12T12:36:42Z

← Older revision		Revision as of 12:36, 12 November 2016
Line 1:		Line 1:
	Expected texture file type but found ''image filename'' for ''resource reference''		''Expected texture file type but found 'image filename' for 'resource reference'''

	The procedure which parses the mesh file expected to find a reference to a texture, but found a reference to an image file instead. This is a result of the content creator using an image in the mesh, instead of using a texture.

	For example:		For example:
Line 7:		Line 5:
	- VE171: Expected texture file type but found 'bok.tga' for 'arc:fld:$(local)/hash-35\|\|kuid2 110019 1118 1.tzarc\|'		- VE171: Expected texture file type but found 'bok.tga' for 'arc:fld:$(local)/hash-35\|\|kuid2 110019 1118 1.tzarc\|'

	~~This~~ error ~~requires re-configuration~~ of the ~~original source mesh~~. If ~~no other options are available it~~ is ~~possible to edit~~ the .im file ~~to refer to a~~ texture ~~file~~ (~~''image~~.texture'') ~~instead of an image~~ file~~, and~~ create a ~~texture and matching image~~ file in ~~the asset~~. ~~Note that~~ editing the ~~.I'm file in this fashion creates~~ a ~~risk of corrupting it beyond repair~~.
			Trainz found a reference to a source image file (eg. "bok.tga") where a texture resource (eg. "bok.texture") was expected. Images and textures are not interchangeable. Also note that texture resource references end in ".texture", whereas source texture files on disk will end in ".texture.txt".

			The error must be corrected at the site of the reference. If the reference is in the [[config.txt file]] then this is as simple as replacing the image reference (eg. "bok.tga") with the appropriate texture resource reference ("bok.texture"), although if the texture.txt file does not already exist then you may need to create it first. If the reference is from a mesh file (such as "bok.im" or "bok.trainzmesh") then you will need to correct the source mesh in your modelling software (eg. Max or Blender) and then re-export it. N3V does not provide any tools for editing mesh files directly. If you do not have access to the source mesh, then the problem mesh should be treated as corrupted and replaced with a new mesh which does not have the same problem.

	[[Category:Validation Errors]]		[[Category:Validation Errors]]

Builderbob: Created from error message

2016-07-19T03:02:04Z

Created from error message

New page

Expected texture file type but found ''image filename'' for ''resource reference''

The procedure which parses the mesh file expected to find a reference to a texture, but found a reference to an image file instead. This is a result of the content creator using an image in the mesh, instead of using a texture.

For example:

- VE171: Expected texture file type but found 'bok.tga' for 'arc:fld:$(local)/hash-35||kuid2 110019 1118 1.tzarc|'

This error requires re-configuration of the original source mesh. If no other options are available it is possible to edit the .im file to refer to a texture file (''image.texture'') instead of an image file, and create a texture and matching image file in the asset. Note that editing the .I'm file in this fashion creates a risk of corrupting it beyond repair.

[[Category:Validation Errors]]