CB&Q E5 Zephyr Engine and Consist

Heinrich505

Active member
Still being new to all this, I'm looking for CB&Q engines, but having trouble finding them as I am way behind the curve. More specifically I am looking for the E5 in CB&Q livery for the Zephyr Routes.

I saw an E5 and passenger consist for the CB&Q Zephyr on the Trainz Forge site, marked Exposition Flyer Pack 2 as payware. But, I'm not sure the site is still up, having seen a site marked Trainz-Forge which I think is their new site. The exposition pack is not on that site.

I've tried sending emails to the original site and new site but have gotten no replies. I'm not sure if either site is still up. The team members and contributors seem to be the same for both sites. I recognize some of them from seeing their posts on this forum.

That site appears to be the only one that ever had an E5 engine in CB&Q - at least the only one I've found so far. If anyone has a site to direct me to, I'd be grateful.

If anyone from Trainz-Forge can advise me if the Exposition Flyer Pack 2 is still available and will work in TANE SP2, that would be great as well.

Heinrich505
 
Richard57,
Thanks for the information. I tried to order the Exposition Pack 2 from the Trainz-Forge website but it didn't seem to work. :(

The Western Pacific site was really good. I downloaded the F7 you suggested. Worked just fine. Then tried some of the other downloads and they came up faulty. Ugh.

I was hoping some of the dependencies from the one that worked would correct my other F7 errors but no luck.

Heinrich505
 
Richard57,
Thanks for the information. I tried to order the Exposition Pack 2 from the Trainz-Forge website but it didn't seem to work. :(

The site works perfect, click on the item you want, put it in the basket, go to check out, pay, and wait a little for download link.

The Western Pacific site was really good. I downloaded the F7 you suggested. Worked just fine. Then tried some of the other downloads and they came up faulty. Ugh.

I was hoping some of the dependencies from the one that worked would correct my other F7 errors but no luck.

At the TOP of that page there are 3 (THREE) bottons for dependencies 1, dependencies 2, dependencies 3, get them ALL!

Heinrich505

..................................

:)

And it's not only Western Pacific.

There are two more

https://projectwestern.weebly.com/diesel-road-index.html
 
Last edited:
When I click on Dependencies 1 for the F7s, it sends me to the Jointed Rail new releases page. I've no idea what dependencies I should be looking for. Ugh.

The other dependencies load with warnings.

The Bloody Nose F7s show faulty in Trainz Content but when I open them up for dependencies, everything shows installed, built-in, or modified. But, there are errors listed in the warnings/errors section so the engines won't show in game.

The same goes for the Bloody Nose SD9s, unfortunately, as they are a particular favorite of mine. :(

But, I did get some of the Western Pacific F7s to load up just fine. Scratching my head in confusion.

Heinrich505
 
Post the errors and we can help you fix them. I fixed the engine ages ago, but I can't remember what the problems were.
 
JRegner1955,
Have done so several times - definition of insanity, right? Keep repeating the same action but expecting different results, heh heh. It downloads but with 15, 3, 11, and 8 warnings respectively. I'm not sure they are taking.

JCitron,
It seems they all show up in Content Manager as Open for Edit. I've clicked on Revert Unsubmitted Edits in the past. Doesn't seem to change anything but they close from the Edit screen. I think I've also clicked on Revert to Original before as well, but again, seemingly no change. Any suggestions would be much appreciated.

Specifically, for the SP-F7A "Bloody Nose," the below are not in red, and show Installed, Built in, or modified.

<kuid2:37581:1151:3> Nathan M5 #2 Installed from DLS
<kuid2:104722:53567:1> EMD 16-567C enginesounds Built-in
<kuid2:45324:10103:3> Green Corona Built-in
<kuid2:45324:10101:3> Red Corona Built-in
<kuid2:45324:10104:3> Lunar Corona Built-in
<kuid2:45324:54002:7> Locomotive sound effects library v1.1 Modified
<kuid2:45324:85307:4> EMD 10 Blade 36 Radiator Fan Installed from DLS
<kuid2:45324:85308:5> EMD 48in 10 Blade Fan Modified
<kuid2:104722:2501038:127> Arn library, v2.02 Built-in
<kuid:438995:100231> Blomberg B type bogey (SP Grey) Modified
<kuid:467590:100500> Incandescent Bulb Corona Dark Modified
<kuid:467590:100372> Incandescent Bulb Corona Modified
<kuid:-25:483> F7 Built-in
<kuid:-25:1005> F7 Interior MPH RHD Installed from DLS


If I click on errors/warnings, I then get 2 errors and 11 warnings. I highlighted the errors in red; the rest are warnings.

! <kuid:438995:1030> VE186: Material 'arc:fld:$(local)/hash-65||kuid 438995 1030.tzarc|mesh_body**map_c.m.reflect' is shared between multiple chunks in this asset but the material parameters conflict.
; <NULL> MeshResource::LoadResource> <NULL> | arc:fld:$(local)/hash-65||kuid 438995 1030.tzarc|
; <NULL> Loading mesh mesh_body/shadow.im
; <kuid:438995:1030> Mismatch: Diffuse color mismatch
! <kuid:438995:1030> VE186: Material 'arc:fld:$(local)/hash-65||kuid 438995 1030.tzarc|mesh_body**black_m.notex' is shared between multiple chunks in this asset but the material parameters conflict.
; <kuid:438995:1030> Mismatch: Diffuse color mismatch
! <kuid:438995:1030> VE186: Material 'arc:fld:$(local)/hash-65||kuid 438995 1030.tzarc|mesh_body**black_m.notex' is shared between multiple chunks in this asset but the material parameters conflict.
! <kuid:438995:1030> VE62: Required container 'thumbnails' is missing.
! <kuid:438995:1030> VE39: The texture 'mesh_shadow/black.tga' is a uniform color.
- <kuid:438995:1030> VE70: The KUID tag is not a valid KUID value: '_'.
! <kuid:438995:1030> VE146: An asset must be specified for tag 'texture-kuid'.
- <kuid:438995:1030> VE70: The KUID tag is not a valid KUID value: '_'.
! <kuid:438995:1030> VE146: An asset must be specified for tag 'texture-kuid'.
! <kuid:438995:1030> VE109: The low-detail meshes total more than 500 polygons. This may have a negative impact on performance: 0: 12762

I hope y'all can make more sense of all these than I. So much to learn and I'm so new to the game.

Particularly vexing is the same thing with the "Bloody Nose" SP SD9 #5449, one of my favorite engine versions and again a problem with SP. The 5 downloaded number versions are all faulty.

<kuid:438995:101123> flexicoil Modified
<kuid2:96914:55947:3> Undec high-hood interior SHF Modified
<kuid2:9000:51003:1> T3P SD9 TRS v1.1 Built-in
<kuid2:104722:53567:1> EMD 16-567C enginesounds Built-in
<kuid2:37581:1047:3> Nathan NCP5A Installed from DLS
<kuid2:104722:2502000:2> US Locomotive sound effects library v1.00 Built-in

None show red and appear to be downloaded correctly.

But, when I click on errors and warnings, I get 6 errors and 8 warnings. Clearly something is not working right for this.

! <kuid:438995:101122> VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
; <NULL> MeshResource::LoadResource> <NULL> | arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|
; <NULL> Loading mesh sd9_undec_body/lod3.im
- <kuid:438995:101122> VE170: Failed to open compiled texture 'sd9_undec_body/digit_1a.texture' for 'arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|'
- <kuid:438995:101122> VE165: Texture 'sd9_undec_body/digit_1a.texture' is missing or could not be loaded in mesh 'sd9_undec_body/lod3.im', material '*lod3*B64F0BB1*mtl #5*m.onetex'.
- <kuid:438995:101122> VE170: Failed to open compiled texture 'sd9_undec_body/digit_1b.texture' for 'arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|'
- <kuid:438995:101122> VE165: Texture 'sd9_undec_body/digit_1b.texture' is missing or could not be loaded in mesh 'sd9_undec_body/lod3.im', material '*lod3*6B0DFE96*mtl #11*m.onetex'.
- <kuid:438995:101122> VE170: Failed to open compiled texture 'sd9_undec_body/digit_2b.texture' for 'arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|'
- <kuid:438995:101122> VE165: Texture 'sd9_undec_body/digit_2b.texture' is missing or could not be loaded in mesh 'sd9_undec_body/lod3.im', material '*lod3*EC942D3D*mtl #10*m.onetex'.
! <kuid:438995:101122> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'sd9_undec_body/lowlight.im' to a .lm file.
! <kuid:438995:101122> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'sd9_undec_body/m5.im' to a .lm file.
! <kuid:438995:101122> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'sd9_undec_body/sd9markers.im' to a .lm file.
! <kuid:438995:101122> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'sd9_undec_body/engineer.im' to a .lm file.
! <kuid:438995:101122> VE62: Required container 'thumbnails' is missing.
! <kuid:438995:101122> VE39: The texture 'sd9_undec_shadow/shadow.bmp' is a uniform color.
! <kuid:438995:101122> VE109: The low-detail meshes total more than 500 polygons. This may have a negative impact on performance: 0: 16440, 1: 7906, 2: 4424


Any help on this would be greatly appreciated. These two engines were downloaded from the ProjectWestern.weebly site and really look nice, but they don't want to work with TANE SP2, for a number of reasons, as noted above. SP is one of my favorite lines too. :(

Heinrich505
 
Hi Heinrich, welcome to the wonderful world of trainz. The good thing is that you can find just about anything for trainz, the bad thing is that they may not work.

I am going to address the SP-F7A "Bloody Nose," first.

<kuid:438995:1030> SP F7A 'Bloody Nose from Project Western

The errors
- <kuid:438995:1030> VE70: The KUID tag is not a valid KUID value: '_'.
- <kuid:438995:1030> VE70: The KUID tag is not a valid KUID value: '_'.
indicate that the problem is probably in the config.txt file for the locomotive itself.

So to open the file for editing right click on the engine in the Content Manager and select "Open..." then "Show in Explorer"

Now double click on the config.txt in the folder, that should open the file in Notepad. Take a moment to just skim through the file since if you hang around in trainz for any length of time you'll be messing with these files a lot.

What we are looking for "_" and we find them in the mass-table section in the fclass0 and fclass1 subsections.

texture-kuid "_"

The first thing we can try is removing just the dash.

texture-kuid ""

First make a copy of the config.txt to your desktop or wherever.
Then delete the dashes in both locations.
Save the file and close Explorer.
Right click on the locomotive in the Content Manager and select "Submit Edits"
Hey, presto! Fixed!

Now you might be asking why did the creator, timothetoolman, stick a dash in there? The answer is that this is an older asset and, while improving game, N3V changed the format for this particular effect. (Don't ask it is a special, secrete Australian programming thing.)

:D
 
Last edited:
Now lets take a look at the B unit

<kuid:438995:1091> SP F7B 'Bloody Nose

The error messages are
- <kuid:438995:1091> VE65: The *.texture.txt file is missing for texture resource 'mesh_art/mesh_art_512.texture'.
- <kuid:438995:1091> VE65: The *.texture.txt file is missing for texture resource 'mesh_art/mesh_art_icon.texture'.

Now this error is, again, caused by changes in the format of how things work in game by N3V.

You could download some nifty tools that allow you to change the format of the texture resource to comply with the new formating but that can get complicated. It is necessary sometimes but there is a down and dirty fix in this case.

Again Open... the engine file in Explorer.
Move the mesh_art folder to your desktop
Close Explorer and Submit Edits
Hey, it's fixed!

Delete all that clutter you have on your desktop.

You can repeat the above steps to fix the weathered versions
<kuid:438995:100244> SP F7B 'Bloody Nose' Whethered
<kuid:438995:100237> SP F7A 'Bloody Nose' Weathered


:D

I was unable to find the SD9 so I can't help you there.

Edit; I did find a Bloody Nose SD9 on the DLS <kuid2:90657:12:3> SD9_SPacific by spectnaz that, while old, doesn't seem to have any problems.
 
Last edited:
OK, found the SD9s you are talking about.

The errors

- <kuid:438995:101122> VE170: Failed to open compiled texture 'sd9_undec_body/digit_1a.texture' for 'arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|'
- <kuid:438995:101122> VE165: Texture 'sd9_undec_body/digit_1a.texture' is missing or could not be loaded in mesh 'sd9_undec_body/lod3.im', material '*lod3*B64F0BB1*mtl #5*m.onetex'.
- <kuid:438995:101122> VE170: Failed to open compiled texture 'sd9_undec_body/digit_1b.texture' for 'arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|'
- <kuid:438995:101122> VE165: Texture 'sd9_undec_body/digit_1b.texture' is missing or could not be loaded in mesh 'sd9_undec_body/lod3.im', material '*lod3*6B0DFE96*mtl #11*m.onetex'.
- <kuid:438995:101122> VE170: Failed to open compiled texture 'sd9_undec_body/digit_2b.texture' for 'arc:fld:$(local)/hash-EF||kuid 438995 101122.tzarc|'
- <kuid:438995:101122> VE165: Texture 'sd9_undec_body/digit_2b.texture' is missing or could not be loaded in mesh 'sd9_undec_body/lod3.im', material '*lod3*EC942D3D*mtl #10*m.onetex'.

A quick check shows that the texture files are just not in the sd9_undec_body folder, sometimes this error means that there is something wrong with the texture file but not this time.

So where can we find these? A look at the dependencies hinted that these were a repaint of bdaneal's SD 9s so I went to his site http://steammachine.com/bdaneal/index.htm and under "Generic" I found his EMD SD7/9 stuff (all the way down).

I downloaded his undecorated EMD SD7/9 but the missing files were not in there either, I next downloaded his D&RGW SD7. Eureka!
The missing files
digit_1a.texture.txt
digit_1b.texture.txt
digit_2b.texture.txt
were in that locomotive's sd9_undec_body folder. A look at the txt files showed that they all referenced a single texture file, chain_a.bmp which was already present in the SP SD9's sd9_undec_body folder. So I copied the three files above into each of the SP SD9 folders and...

Fixed.
 
Last edited:
Normhart,
Thank-you for the welcome. I've been an HO train guy forever, and it amazes me that it took so long for me to get involved in this extension of that hobby. This simulation has me staring at the screen in jaw-dropping amazement at the layouts that have been created, and at other times with mind-numbing frustration as to why an engine didn't download properly. Quite the hobby.

At present, I have a stable of virtual locomotives that I would never be able to afford in HO scale, or even find, in some cases. Thanks to you, I've been able to add the "Bloody Nose" versions of the F7AB, washed and weathered versions, as well as the "Bloody Nose" SD9 engines.

Your walk-through was perfect. I've needed some specific guidance along these lines, and this was spot on. It is all freaking magic to me sometimes, and your performance here as a magician was amazing. Thank-you so much for the mini-tutorial. When I checked my installed content, I found that I did have bdaneal's undecorated SD7/9 engine, and also the D&RGW SD7. They both downloaded properly. I then copied the three files you found for me into the Bloody Nose versions and...voila...magic...they were fixed.

I don't want to go to the well too often :eek:, but if you have the time, I'm also struggling with a problem that seems to wreck about 50% of my downloads of F7A&B engines, that is unrelated to the fix you helped me with on the Bloody Nose F7A's. Let me know if you have some time to assist on that.

Thanks so much for all this help. It is very appreciated.

Heinrich505
 
Normhart,
I really appreciate this. It is close to detective work, digging around in the files. I can tell you that I've now fixed almost all the red-lined faulty SD9 engines, by cutting and pasting those three files into each of their undec_body folders. It was like freaking magic. I have SD9 engines in almost every livery - more than I will ever probably use, but they look so damn cool!!! :cool:


There are two sets of faulty F7As that are coming up. The first problem seems to center around a faulty kuid, namely kuid:-10:198. I've googled and searched the forum and that one seems to come up as unknown. The author shows as Auran. The warnings and errors for that kuid show as:

; <kuid:-10:189> Validating <kuid:-10:189>
! <kuid:-10:189> VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
! <kuid:-10:189> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'f7_body/f7_body.im' to a .lm file.
- <kuid:-10:189> VE44: Tag 'name-it' in the container 'traincar' is obsolete.
- <kuid:-10:189> VE44: Tag 'name-cz' in the container 'traincar' is obsolete.
- <kuid:-10:189> VE44: Tag 'name-pl' in the container 'traincar' is obsolete.
! <kuid:-10:189> VE39: The texture 'f7_shadow/black.tga' is a uniform color.
! <kuid:-10:189> VE109: The low-detail meshes total more than 500 polygons. This may have a negative impact on performance: 0: 7555
! <kuid:-10:189> VE73: Image file 'f7_art/f7_art_icon.tga' is incorrectly used as both a texture.txt source file and a raw image file.

Oddly, the dependencies all show downloaded.

<kuid:-25:137> default Built-in
<kuid:-25:175> QR2100 Modified
<kuid:-25:483> F7 Built-in
<kuid:-25:1005> F7 Interior MPH RHD Installed from DLS
<kuid:-25:485> f7_bogey Installed from DLS

This seems to be the main fault for most of my problem F7A downloads.

An example for this is the BN F7A (728).
<kuid:35848:728> BN F7A (728) Author sg1

<kuid:-25:137> default Built-in
<kuid:-10:175> gp38 bogey Modified
<kuid:-25:175> QR2100 Modified
<kuid:-25:483> F7 Built-in
<kuid:-10:189> f7 Installed from DLS, Faulty
<kuid:-25:1005> F7 Interior MPH RHD Installed from DLS, Faulty

I tried deleting -10:189 from the config files, but probably didn't do it right. The step I think I was missing was the submit edits step. That might do the trick but I'll wait to see what you think. So many of my F7A's come up with the f7 -10:189 as the only dependency that is faulty.


The second F7A problem is a little more confusing. An example of this is:

<kuid:467590:100460> KCS F7A #4054 (White) Author - ulmer94
The B unit downloaded just fine.

Dependencies show okay - nothing listed as red or faulty.

<kuid2:45324:10101:3> Red Corona Built-in
<kuid2:45324:10103:3> Green Corona Built-in
<kuid2:45324:10104:3> Lunar Corona Built-in
<kuid2:104722:2501038:127> Arn library, v2.02 Built-in
<kuid2:45324:50022:4> Blomberg B (black a) Installed, Payware
<kuid2:45324:54002:7> Locomotive sound effects library v1.1 Modified
<kuid2:126982:54002:1> Nathan P5 Modified
<kuid2:45324:85307:4> EMD 10 Blade 36 Radiator Fan Installed from DLS
<kuid2:45324:85308:5> EMD 48in 10 Blade Fan Modified
<kuid:467590:100511> Smoke Modified
<kuid:648132:100136> F Unit Spark Arrestor Modified
<kuid:-25:175> QR2100 Modified
<kuid:-25:483> F7 Built-in
<kuid:-25:1005> F7 Interior MPH RHD Installed from DLS

The errors and warnings show the following:

; <kuid:467590:100460> Validating <kuid:467590:100460>
! <kuid:467590:100460> VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
; <NULL> MeshResource::LoadResource> <NULL> | arc:fld:$(local)/hash-46||kuid 467590 100460.tzarc|
; <NULL> Loading mesh mesh_body/body.im
! <kuid:467590:100460> VE166: 22 combined chunks (of 22 source) in .im file:
! <kuid:467590:100460> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'mesh_body/body.im' to a .lm file.
! <kuid:467590:100460> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'mesh_body/drgw_parts.im' to a .lm file.
; <NULL> MeshResource::LoadResource> <NULL> | arc:fld:$(local)/hash-46||kuid 467590 100460.tzarc|
; <NULL> Loading mesh mesh_shadow/shadow.pm
- <kuid:467590:100460> VE168: File 'mesh_shadow/black.texture' is not a valid compiled texture file for 'arc:fld:$(local)/hash-46||kuid 467590 100460.tzarc|'
- <kuid:467590:100460> VE165: Texture 'mesh_shadow/black.texture' is missing or could not be loaded in mesh 'mesh_shadow/shadow.pm', material '*f7_sfred_shadow.pm*f794a7be*material #10*m.onetex'.
! <kuid:467590:100460> VE86: Legacy .pm files are no longer supported. Switch to using a .lm file.
! <kuid:467590:100460> VE39: The texture 'mesh_body/antenna.tga' is a uniform color.
! <kuid:467590:100460> VE39: The texture 'mesh_body/check.tga' is a uniform color.
! <kuid:467590:100460> VE39: The texture 'mesh_body/digit_3b.tga' is a uniform color.
! <kuid:467590:100460> VE39: The texture 'mesh_body/digit_4b.tga' is a uniform color.
! <kuid:467590:100460> VE39: The texture 'mesh_body/digit_5b.tga' is a uniform color.
! <kuid:467590:100460> VE39: The texture 'mesh_body/digit_6b.tga' is a uniform color.
! <kuid:467590:100460> VE39: The texture 'mesh_body/mu box.tga' is a uniform color.
- <kuid:467590:100460> VE65: The *.texture.txt file is missing for texture resource 'mesh_shadow/black.texture'.
- <kuid:467590:100460> VE70: The KUID tag is not a valid KUID value: '_'.
! <kuid:467590:100460> VE146: An asset must be specified for tag 'texture-kuid'.
- <kuid:467590:100460> VE70: The KUID tag is not a valid KUID value: '_'.
! <kuid:467590:100460> VE146: An asset must be specified for tag 'texture-kuid'.
! <kuid:467590:100460> VE109: The low-detail meshes total more than 500 polygons. This may have a negative impact on performance: 0: 13188

Looks like mesh problems for the errors for VE168, VE165, and VE 65. The VE70 errors seem to be the same ones you described earlier with the '_' situation where the _ was deleted and that fixed the Bloody Nose F7.

These two situations account for most of my remaining faulty downloaded F7A's. The f7 kuid was particularly vexing as it was a download from the Content Manager but once it was downloaded, it showed as faulty.

I've spent most of my time playing around in the config files today instead of running trains. And, it is sort of addicting too.:D

Any help on these problems will be greatly appreciated.

Heinrich505
 
Normhart,
Sorry, I forgot to include the warnings and errors for the BN F7A. They are as follows.

; <kuid:35848:728> Validating <kuid:35848:728>
! <kuid:35848:728> VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
; <kuid:-10:189> Loading asset <kuid:-10:189>
- <kuid:-10:189> TADGetSpecFromAsset> <kuid:-10:189> is faulty and will not be loaded
- <kuid:-10:189> TADGetSpecFromAsset> no local file available for <kuid:-10:189> [<kuid:-10:189>]
- <kuid:35848:728> VE33: Alias mesh 'bn f7a (728)_body/bn f7a (728)_body.pm' not found in dependency <kuid:-10:189>.
- <kuid:35848:728> VE33: Alias mesh 'bn f7a (728)_shadow/bn f7a (728)_shadow.pm' not found in dependency <kuid:-10:189>.
! <kuid:35848:728> VE62: Required container 'thumbnails' is missing.


As you can see, there is a major problem with the -10:189 kuid.

Thanks for your help on this.

Heinrich505
 
It is past my bedtime but I'll take a quick shot at the second problem now. I don't have that engine and it doesn't seem to be on the DLS so I'm guessing here.

1 yes delete the underscore '_' in both locations and submit the edits. The asset will still show as faulty but when you look at the error message the lines about the "_" should be gone.

2 open the asset in explorer and look in the folder named mesh_shadow you should see two files named black.texture.txt and black.tga or black.bmp or something like that. If you see black.texture then you have a problem. The best way to solve this is to get the tools to convert this file into the more modern format, however a quick fix is to check some of your other not faulty locomotives and see if you can find black.texture.txt and black.tga or black.bmp and copy them into the mesh_shadow folder in your faulty locomotive.

Good luck, I'll check in tomorrow and take a look at the other locomotive if someone doesn't beat me to it.

BTW the problem with -10:189 probably has something to do with what is called aliasing which is a real can of worms.
 
Normhart,
Sorry I missed your post last night. It was well past my bedtime too.

I tried some moving and replacing of files from a good F7A engine to the faulty KCS White F7A, per your suggestion. I played around in the mesh_shadow folders. No luck, but it was mostly guesswork on my part. I did see something marked black.texture, but this also shows in a good engine. I tried replacing the good engine black.texture file into the bad one, but probably didn't do it right. This doesn't look promising so I may just be stuck without these.

The -10:189 problem looms large too. I'm not really sure if there is a kuid that would replace that one in one fell swoop. Seems Auran would have an answer for that, since there are so many of those engines on DLC that require the -10:189, and since the faulty f7 file is still listed on the DLC for download. If you download it, you get the faulty error message, but if you don't, the kuid is listed in the dependencies as available for download from DLC. Odd that it would be on DLC but still faulty - pretty much a set-up for failure and frustration on the part of the customer.

Please let me know what you think on all this.

Thanks,

Heinrich505
 
OK I'm back :D

I checked <kuid:-10:189> on my system and it was fine. I was going to suggest that you try Revert to Original but when I did that it caused the asset to turn faulty on my system! The errors seems to be caused by overly enthusiastic error checking.

Auran is N3V so it belongs to the game maker and they will have to fix it. At some point they "fixed" it by upgrading it sort of. But now it seems that new error checking is creating more faulty assets. I checked in the new Beta version of the game and the same problem exists there.

In the meantime here is what you can do

- <kuid:-10:189> VE44: Tag 'name-it' in the container 'traincar' is obsolete.
- <kuid:-10:189> VE44: Tag 'name-cz' in the container 'traincar' is obsolete.
- <kuid:-10:189> VE44: Tag 'name-pl' in the container 'traincar' is obsolete.

Open... Show in Explorer
Double click on config.txt
Find;
name-it "f7"
name-cz "f7"
name-pl "f7"
and delete the entire line for each.
Be sure that you are deleting these exact lines as there are similar lines in there that you don't want to delete.
save the config.txt, close the Explorer window, and Submit Edits

That should do it. :D

Now right click on the asset and select List Dependants
This should give you a list of all the F7s that use this model and you can identify those that need more work. Let me know what you need more help with.

I'll take another look at the black texture problem later today.
 
Last edited:
OK on the KSC White Ghosts

I downloaded it and took a look and I'm seeing 2 B units that are fine and 4 A units that are faulty.

We already discussed the "_" problem and I am assuming that you have gone through and fixed this for each of the four engines.

Here is what is happening with the black problem. In the early days of trainz the paint colors were stored in a compacted file called black.texture, then N3V decided to uncompact the files producing two files black.texture.txt and black.tga. Then they decided to resurrect the compacted file using a different compaction method, this caused the old compacted file to become faulty. Or at least that is how I understand things.

Taking a look at the <kuid:467590:100460> locomotive by Open... Show in Explorer and opening the mesh_shadow folder. We see 2 files; black.texture and shadow.pm, shadow.pm is the mesh and black.texture is the compacted paint.
Open... Show in Explorer one of the B units (I used
<kuid:467590:100472>) and look in the mesh_shadow folder. We see 3 files; black.texture.txt, black.tga, and shadow.im.
Delete the black.texture from the A unit folder
Copy black.texture.txt and black.tga from the B unit into the A unit's mesh_shadow folder.
Submit Edits and it is fixed
Repeat for the other three A units.

:D Have fun!
 
Last edited:
Back
Top