.
Results 1 to 9 of 9

Thread: Faulty C40-8s

  1. #1
    Join Date
    Apr 2019
    Location
    Cleveland Ohio United States
    Posts
    129
    Blog Entries
    1
     

    Default Faulty C40-8s

    I have 3 payware C40-8s and they are all faulty. The error is something about the build number? What does this mean and can it be fixed? I'd really love to use them lol.-MK
    Last edited by Mkultra04; October 15th, 2019 at 06:00 PM. Reason: Spelling
    How Tomorrow Moves

  2. #2
    Join Date
    Aug 2019
    Location
    United States of America, In Front Of My PC
    Posts
    232
     

    Default

    Do they run, even though displaying the faults ?

    You may have to boost up the config file trainz-build line numeral, to remove any faults.

    My understanding is that "faulty assets still run OK" ?

    To find your actual trainz-build numeral, build a small simple one track route, and examine the route config file in Notepad (the route trainz-build numeral will be displayed there).
    Last edited by MP242; October 15th, 2019 at 06:40 PM.
    I want all my performance sliders set to "Full"

  3. #3
    Join Date
    Apr 2019
    Location
    Cleveland Ohio United States
    Posts
    129
    Blog Entries
    1
     

    Default

    Quote Originally Posted by MP242 View Post
    Do they run, even though displaying the faults ?

    You may have to boost up the config file trainz-build line numeral, to remove any faults.

    My understanding is that "faulty assets still run OK" ?

    To find your actual trainz-build numeral, build a small simple one track route, and examine the route config file in Notepad (the route trainz-build numeral will be displayed there).
    They don't run unfortunately, and I should be more specific, the error say that "this asset uses an obsolete trainz building number" and that the C40-8 cab mech is faulty.
    How Tomorrow Moves

  4. #4
    Join Date
    May 2014
    Location
    United States of America
    Posts
    9
     

    Default

    Does the error have a yellow triangle in front of the message? If so, that shouldn't be the problem. The errors to look for are the ones that have the red circle with a white 'X' inside it. I have a couple of JR's C40-8s that I got through N3V back in 2010-2012 days. I have them working in both TANE and now, Trainz2019. I think I may have had to tweak the configs on them to get them to work (assuming it was allowed for these files). I don't remember specifically what I had to do.

    Anyhow, in content manager, right click on the compiled item (i.e., not 'Open for edit'), click on 'View Errors & Warnings', click on the first line of the resulting message, hold down the shift key, scroll to the bottom of the message and click again to highlight & select the whole message, then post the result here - that should give people here the info they would need to be able to help you out. Also right clicking on the compiled item should avail you to a listing of the dependencies to the item. If anything there comes up as faulty, right click on that item and select 'List asset versions'. A lot of times there will be newer versions of files available and downloading a newer version of a dependency will fix the problem. I apologize if I'm being presumptuous and you're already familiar with that whole process. One of the hazards of being an old IT guy who spent much of that time doing user support.

  5. #5
    Join Date
    Nov 2006
    Location
    United States of America, Massachusetts, Haverhill
    Posts
    25,721
     

    Default

    Quote Originally Posted by thenelm1 View Post
    Does the error have a yellow triangle in front of the message? If so, that shouldn't be the problem. The errors to look for are the ones that have the red circle with a white 'X' inside it. I have a couple of JR's C40-8s that I got through N3V back in 2010-2012 days. I have them working in both TANE and now, Trainz2019. I think I may have had to tweak the configs on them to get them to work (assuming it was allowed for these files). I don't remember specifically what I had to do.

    Anyhow, in content manager, right click on the compiled item (i.e., not 'Open for edit'), click on 'View Errors & Warnings', click on the first line of the resulting message, hold down the shift key, scroll to the bottom of the message and click again to highlight & select the whole message, then post the result here - that should give people here the info they would need to be able to help you out. Also right clicking on the compiled item should avail you to a listing of the dependencies to the item. If anything there comes up as faulty, right click on that item and select 'List asset versions'. A lot of times there will be newer versions of files available and downloading a newer version of a dependency will fix the problem. I apologize if I'm being presumptuous and you're already familiar with that whole process. One of the hazards of being an old IT guy who spent much of that time doing user support.
    Welcome to the old IT guys that spent much time doing user support club. There are a few of us here.
    John
    Trainz User Since: 12-2003
    Trainz User ID: 124863
    T:ANE Build: 94829
    TRS2019: 98592

  6. #6
    Join Date
    Nov 2006
    Location
    United States of America, Massachusetts, Haverhill
    Posts
    25,721
     

    Default

    JR has recently updated cab interiors I recommend checking for the one that works with those locomotives. They are available in the freeware section of the their website.
    John
    Trainz User Since: 12-2003
    Trainz User ID: 124863
    T:ANE Build: 94829
    TRS2019: 98592

  7. #7
    Join Date
    Apr 2019
    Location
    Cleveland Ohio United States
    Posts
    129
    Blog Entries
    1
     

    Default

    LOCO

    ; <kuid2:45324:100221:1> Validating <kuid2:45324:100221:1>! <kuid2:45324:100221:1> VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
    ! <kuid2:45324:100221:1> VE82: Individual mesh files are not supported for traincar assets. Upgrade 'mesh_body/radmod.im' to a .lm file.
    ! <kuid2:45324:100221:1> VE109: The low-detail meshes total more than 500 polygons. This may have a negative impact on performance: 0: 38866, 1: 25370, 2: 18828, 3: 9603, 4: 8996
    ! <kuid2:45324:100221:1> VE111: The meshes in LOD level 4 must total at least 20% fewer polygons than the next higher LOD: 0: 38866, 1: 25370, 2: 18828, 3: 9603, 4: 8996
    ; <NULL> Performing asset precache
    ; <kuid2:45324:100221:1> Loading asset <kuid2:45324:100221:1>
    ; <kuid2:45324:100221:1> Loading asset <kuid2:45324:90301:1>
    - <kuid2:45324:100221:1> TADGetSpecFromAsset> <kuid2:45324:90301:1> is faulty and will not be loaded
    - <kuid2:45324:100221:1> TADGetSpecFromAsset> no local file available for <kuid2:45324:90301:1> [<kuid2:45324:90301:1>]
    ! <kuid2:45324:100221:1> MapObjectSpec::LinkSpecs> Asset is missing required interior <kuid2:45324:90301:1>

    OK I think I did this right, but its the cab mech that's faulty so I'll post that too.

    CAB MECH

    ! <kuid2:45324:90301:1> 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-61||kuid2 45324 90301 1.tzarc|
    ; <NULL> Loading mesh wheelslip_light.im
    ; <kuid2:45324:90301:1> Mismatch: Payload mismatch on: matEmissive
    ; <kuid2:45324:90301:1> Mismatch: payloads: (0.223529,0.223529,0.223529,0.223529) != (0.134118,0.134118,0.134118,0.134118)
    ! <kuid2:45324:90301:1> VE186: Material 'arc:fld:$(local)/hash-61||kuid2 45324 90301 1.tzarc|**indicators_lit.m.onetex' is shared between multiple chunks in this asset but the material parameters conflict.
    ; <NULL> MeshResource::LoadResource> <NULL> | arc:fld:$(local)/hash-61||kuid2 45324 90301 1.tzarc|
    ; <NULL> Loading mesh sand_light.im
    ; <kuid2:45324:90301:1> Mismatch: Payload mismatch on: matEmissive
    ; <kuid2:45324:90301:1> Mismatch: payloads: (0.223529,0.223529,0.223529,0.223529) != (0.134118,0.134118,0.134118,0.134118)
    ! <kuid2:45324:90301:1> VE186: Material 'arc:fld:$(local)/hash-61||kuid2 45324 90301 1.tzarc|**indicators_lit.m.onetex' is shared between multiple chunks in this asset but the material parameters conflict.
    ! <kuid2:45324:90301:1> VE61: Required tag 'interior-controls-type' was missing and has been set to default.
    - <kuid2:45324:90301:1> VE30: The tag 'image' in '0' refers to a nonexistent file: 'art_icon.tga'.

    Thanks for they help guys it has been much appreciated!-MK
    Blue font to help separate my comments and the error stuff.
    How Tomorrow Moves

  8. #8
    Join Date
    May 2014
    Location
    United States of America
    Posts
    9
     

    Default

    The Cab Mech that is currently being used in my installation of the JR CNW C40-8 is basically the same as yours <kuid2:45324:90301:x>, but <kuid2:45324:90301:4> rather than :1. As suggested by JCitron, the newer version of cab should be found at the JR website under Dependencies. (This is in Trainz 2019 BTW.)
    Last edited by thenelm1; October 17th, 2019 at 12:05 PM.

  9. #9
    Join Date
    Apr 2019
    Location
    Cleveland Ohio United States
    Posts
    129
    Blog Entries
    1
     

    Default

    Quote Originally Posted by thenelm1 View Post
    The Cab Mech that is currently being used in my installation of the JR CNW C40-8 is basically the same as yours <kuid2:45324:90301:x>, but <kuid2:45324:90301:4> rather than :1. As suggested by JCitron, the newer version of cab should be found at the JR website under Dependencies. (This is in Trainz 2019 BTW.)
    Ok cool so could I just go in and replace the 1 with the 4?
    How Tomorrow Moves

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •