Jadebullet's GP30 help

[constar261]

I have this error - VE70: The KUID tag is not a valid KUID value: '_'.

This is the config file text and I do not see any thing wrong can some show me how to correct this.



username "ATSF GP30"
trainz-build 2.9
category-class "AL"
category-region "US"
category-era "1960s;1970s;1980s;1990s"
kind "traincar"
engine 1
enginespec <kuid:-1:42004231>
enginesound <kuid:334896:1059>
hornsound <kuid:219472:100085>
mass 108000
script "JR_loco"
class "JRLoco"
fonts 2
interior <kuid:-1:101475>
fonts-path "mesh"


script-include-table
{
loco_fx_library <kuid2:45324:555200:1>
}


extensions
{
number_low "1200"
number_high "1285"
class_lights "1"
}


mesh-table
{
default
{
mesh "mesh_body/numbers.im"
auto-create 1
}

locomotive
{
mesh "mesh_body/gp30.lm"
auto-create 1

effects
{
fan1
{
kind "attachment"
att "a.fan1"
default-mesh <kuid2:45324:85308:3>
}

fan2
{
kind "attachment"
att "a.fan2"
default-mesh <kuid2:45324:85307:3>
}

fan3
{
kind "attachment"
att "a.fan3"
default-mesh <kuid2:45324:85308:3>
}

dfan1
{
kind "attachment"
att "a.dfan1"
default-mesh <kuid2:45324:85308:3>
}

fclass0
{
kind "corona"
att "a.fclass0"
texture-kuid "_"
object-size 0.09
directional 1
}

fclass1
{
kind "corona"
att "a.fclass1"
texture-kuid "_"
object-size 0.09
directional 1
}

rclass0
{
kind "corona"
att "a.rclass0"
texture-kuid "_"
object-size 0.09
directional 1
}

rclass1
{
kind "corona"
att "a.rclass1"
texture-kuid "_"
object-size 0.09
directional 1
}
}
}

shadow
{
mesh "mesh_shadow/shadow.im"
}
}


queues
{
conductor
{
size 1
initial-count 0

attachment-points
{
0 "a.fireman"
}

allowed-products
{
0 <kuid:156765:1781>
}
}

engineer
{
size 1
initial-count 0

attachment-points
{
0 "a.engineer"
}

allowed-products
{
0 <kuid:156765:1783>
}
}
}


bogeys
{
0
{
bogey <kuid:156765:100275>
reversed 0
}
}
kuid <kuid:276364:100048>


kuid-table
{
arn_lib <kuid2:104722:2501038:2>
sfx_lib <kuid2:45324:54002:2>
white <kuid2:45324:10104:1>
red <kuid2:45324:10101:1>
green <kuid2:45324:10103:1>
0 <kuid:-1:42004231>
1 <kuid:334896:1059>
2 <kuid:156765:100275>
3 <kuid2:45324:555200:1>
4 <kuid2:45324:85308:3>
5 <kuid2:45324:85307:3>
6 <kuid:156765:1781>
7 <kuid:156765:1783>
8 <kuid:219472:100085>
9 <kuid:-1:101475>
}

 

[n8phu]

Remove the " texture-kuid "_" "fclass0, fclass1, rclass0, rclass1.

That should fix you right up.

 

[ktain.ny]

Isn't it illegal to post a config file of a pAyware asset? I'm just asking not trying to be snarky.

 

[trainman7616]

Why would it matter?

 

[SailorDan]

Remove the " texture-kuid "_" "fclass0, fclass1, rclass0, rclass1.

If a script requires that tag then removing it will just create a different error, or the texture replacement will silently fail.

A better fix is to insert the kuid of any suitable texture asset.

 

[Vinnie264]

Isn't it illegal to post a config file of a pAyware asset? I'm just asking not trying to be snarky.

This isn't payware. Its old USLW freeware.

 

[n8phu]

Isn't it illegal to post a config file of a pAyware asset? I'm just asking not trying to be snarky.

They aren't payware items, these are older content that used to be available from USLW.

A handy reference for you to use to check what is and isn't payware from the gang at JR is to go to their site, Click on Payware, and look ahead of time.

If a script requires that tag then removing it will just create a different error, or the texture replacement will silently fail.

A better fix is to insert the kuid of any suitable texture asset.

This is a config file, not a script file.

This is how I fixed all of the USLW GP30s and many other units with this warning / error (IE JR F7, RRMODS SD35s, Etc) in TS12 SP1 HF4

Inserting a kuid of a texture would also require you to list it in the kuid table at the bottom of the Config file also. Since the original author did not specify one in either area, you would not know what one to use.

For more fixes that work, check out the series here on the board and On The Erecting Hall called "Fixing with Hack"

OP, Please post when you try this fix so we can all know how you made out

 

[lenlawrence]

Hi folks

if I'm reading this right?
"_" error
sometimes a config.txt file has an 'underscore' character in its first few lines. If so remove, save and commit

regards

Len

 

[SailorDan]

This is a config file, not a script file.

A script might depend on items in the config file in order to work correctly.

This is how I fixed all of the USLW GP30s and many other units with this warning / error (IE JR F7, RRMODS SD35s, Etc) in TS12 SP1 HF4

Then perhaps those assets didn't rely on having that tag available. Some do, some don't, and some just skip the replacement if it's not there. The best fix allows for both possibilities.

Inserting a kuid of a texture would also require you to list it in the kuid table at the bottom of the Config file also. Since the original author did not specify one in either area, you would not know what one to use.

Use any texture at all. IF the script requires that tag then it will replace the texture with the texture selected by the script. The texture nominated in the config is never used. That's why the original creator left it blank. It is only being inserted now in order to get around the stricter validation process. Removing the tag means that the script will not do the texture replacement.

 

[SailorDan]

if I'm reading this right?
"_" error
sometimes a config.txt file has an 'underscore' character in its first few lines. If so remove, save and commit

With caution. If the odd characters at the beginning of the file are the Byte Order Mark then removing them will destroy any foreign characters in the file. This has happened to a lot of assets in the past, resulting in descriptions that are just strings of question marks.

These characters should only be removed if they are reported as an error by the commit procedure.

 

[n8phu]

A script might depend on items in the config file in order to work correctly.


Then perhaps those assets didn't rely on having that tag available. Some do, some don't, and some just skip the replacement if it's not there. The best fix allows for both possibilities.


Use any texture at all. IF the script requires that tag then it will replace the texture with the texture selected by the script. The texture nominated in the config is never used. That's why the original creator left it blank. It is only being inserted now in order to get around the stricter validation process. Removing the tag means that the script will not do the texture replacement.

In practice this fix has worked thru TS12 SP1 HF4.

All of the USLW GP30s and a few JR F7s with this fix applied.

 

[luigiluigi109876]

I have this error - VE70: The KUID tag is not a valid KUID value: '_'.

This is the config file text and I do not see any thing wrong can some show me how to correct this.



username "ATSF GP30"
trainz-build 2.9
category-class "AL"
category-region "US"
category-era "1960s;1970s;1980s;1990s"
kind "traincar"
engine 1
enginespec <kuid:-1:42004231>
enginesound <kuid:334896:1059>
hornsound <kuid:219472:100085>
mass 108000
script "JR_loco"
class "JRLoco"
fonts 2
interior <kuid:-1:101475>
fonts-path "mesh"


script-include-table
{
loco_fx_library <kuid2:45324:555200:1>
}


extensions
{
number_low "1200"
number_high "1285"
class_lights "1"
}


mesh-table
{
default
{
mesh "mesh_body/numbers.im"
auto-create 1
}

locomotive
{
mesh "mesh_body/gp30.lm"
auto-create 1

effects
{
fan1
{
kind "attachment"
att "a.fan1"
default-mesh <kuid2:45324:85308:3>
}

fan2
{
kind "attachment"
att "a.fan2"
default-mesh <kuid2:45324:85307:3>
}

fan3
{
kind "attachment"
att "a.fan3"
default-mesh <kuid2:45324:85308:3>
}

dfan1
{
kind "attachment"
att "a.dfan1"
default-mesh <kuid2:45324:85308:3>
}

fclass0
{
kind "corona"
att "a.fclass0"
texture-kuid "_"
object-size 0.09
directional 1
}

fclass1
{
kind "corona"
att "a.fclass1"
texture-kuid "_"
object-size 0.09
directional 1
}

rclass0
{
kind "corona"
att "a.rclass0"
texture-kuid "_"
object-size 0.09
directional 1
}

rclass1
{
kind "corona"
att "a.rclass1"
texture-kuid "_"
object-size 0.09
directional 1
}
}
}

shadow
{
mesh "mesh_shadow/shadow.im"
}
}


queues
{
conductor
{
size 1
initial-count 0

attachment-points
{
0 "a.fireman"
}

allowed-products
{
0 <kuid:156765:1781>
}
}

engineer
{
size 1
initial-count 0

attachment-points
{
0 "a.engineer"
}

allowed-products
{
0 <kuid:156765:1783>
}
}
}


bogeys
{
0
{
bogey <kuid:156765:100275>
reversed 0
}
}
kuid <kuid:276364:100048>


kuid-table
{
arn_lib <kuid2:104722:2501038:2>
sfx_lib <kuid2:45324:54002:2>
white <kuid2:45324:10104:1>
red <kuid2:45324:10101:1>
green <kuid2:45324:10103:1>
0 <kuid:-1:42004231>
1 <kuid:334896:1059>
2 <kuid:156765:100275>
3 <kuid2:45324:555200:1>
4 <kuid2:45324:85308:3>
5 <kuid2:45324:85307:3>
6 <kuid:156765:1781>
7 <kuid:156765:1783>
8 <kuid:219472:100085>
9 <kuid:-1:101475>
}

Replace the underscores with <NULL>

 

[blueodessey]

Replace the underscores with <NULL>

It looks to me like your missing the Kuid # for Corona, it doesn't know which Kuid Asset you want for the Locomotive.....Here is an example of the way it should look just for Corona Part....

Don't pay attention to max-distance, max-size-mul, that's for Fuel distance metering, which means it is made to allow so much fuel capacity in your Locomotive, and if you don't watch your fuel, you run out and get stuck on the Track. Need to send a Rescue Locomotive to pull your Dead Loco back to a Fuel Depot somewhere......

texture-kuid <kuid2:45324:10100:1>



dl_corona
{
kind "corona"
att "a.corona"
texture-kuid <kuid2:45324:10100:1>
max-distance 2000
max-size-mul 8
}


I don't know what Coronas go for each light.......

But can you list the dependent Assets for your Locomotive, it could have some Corona's in the list, and you would just need to add the Kuid number for each Corona.

 

[JAGG]

The brackets mess only, check all are in pair and check their proper positions in the config.

 

[Forester1]

I think it is complaining about these. Since there are no KUIDs for these tags, I think they can be deleted. OR you could try as BlueOdessey and LuigiLuigi have mentioned above.
From this:

fclass0
{
kind "corona"
att "a.fclass0"
texture-kuid "_"
object-size 0.09
directional 1
}

fclass1
{
kind "corona"
att "a.fclass1"
texture-kuid "_"
object-size 0.09
directional 1
}

rclass0
{
kind "corona"
att "a.rclass0"
texture-kuid "_"
object-size 0.09
directional 1
}

rclass1
{
kind "corona"
att "a.rclass1"
texture-kuid "_"
object-size 0.09
directional 1
}
}
}



To this:

fclass0
{
kind "corona"
att "a.fclass0"
object-size 0.09
directional 1
}

fclass1
{
kind "corona"
att "a.fclass1"
object-size 0.09
directional 1
}

rclass0
{
kind "corona"
att "a.rclass0"
object-size 0.09
directional 1
}

rclass1
{
kind "corona"
att "a.rclass1"
object-size 0.09
directional 1
}
}
}

 

[JCitron]

I think it is complaining about these. Since there are no KUIDs for these tags, I think they can be deleted. ...

This is what I've done in the past with no ill effects. The locomotives didn't look any different which means the tag didn't work in the first place and was ignored rather than flagged as an error. Today, the error may be annoying, but this is the right thing to do, and the error is easily repaired.