Must be found in mesh?

The config.txt file for that asset references an attachment point in the mesh file that doesn't exist. This happens alot with passenger cars that have long list of attachment points for the passengers to sit. What kuid asset is this problem in?

Bob
 
The config.txt file for that asset references an attachment point in the mesh file that doesn't exist. This happens alot with passenger cars that have long list of attachment points for the passengers to sit. What kuid asset is this problem in?

Bob


Well its the Brisbane tramcar 400 that I downloaded for example that was been saying that. I dunno about the Kuid however.
 
I downloaded Brisbane Four Motor Tramcar 400,<kuid2:108959:400:2>
into TRS2006 and it commited without errors. The mesh file has all of the attachment points. What version of Trainz are you using?

Bob
 
I downloaded Brisbane Four Motor Tramcar 400,<kuid2:108959:400:2>
into TRS2006 and it commited without errors. The mesh file has all of the attachment points. What version of Trainz are you using?

Bob

Trainz Classics. That was the route (City of Morgan) was for? So thus I downloaded some of the Brisbane Trams but not all of them. I think it 2.7 built. (TC)
 
I am so so so so sorry for reviving this thread if it was dead.

The attachment point error is with the mesh. There was an error with TC which essentially stopped variable detail (LOD) meshes from working.

This is an error in the actual scripting of TC1+2. If you are running TC3, I do not have a clue as to what is happening. I will not have TC3 until well after christmas as I am saving up for more RAM. 1Gb to be precise. It means better layouts for all of you.

To fix it (please do not get up me Motorman) you have to change the mesh reference in the config file to the high detail mesh. This one does work.

CoM V3 is still on the cards if my computer can stay on for long enough for me to write a new boot sector and get Trainz working.
 
Last edited:
Here is an extract from the config for this item. This is the original default mesh table.

Code:
mesh-table {
 default {
[COLOR=red]mesh     "400 body/400 body.im"[/COLOR]
  auto-create    1
  effects {
   destsign {
    kind   "texture-replacement"
    texture   "texture dest.texture"
   }
  }
 }

You need to change only the red line to as follows:

Code:
mesh-table {
 default {
[COLOR=red]mesh     "400 body/400 body high.im"[/COLOR]
  auto-create    1
  effects {
   destsign {
    kind   "texture-replacement"
    texture   "texture dest.texture"
   }
  }
 }

NOTE: The line in the config is not red. Do not spell it wrong as it will bring up error flag after error flag. Also, the .im has to be in lower case otherwise CMP and Trainz will not recognise the mesh and bring up a "mesh not found" flag.
 
Last edited:
Hello Trainz community. I have one question? What does "attachment must be found in mesh" means? o.o

When I had this problem with a passenger car, I looked at the model in FileViewer and saw the attachments were there. I then searched the CCG (I forget what I used) and discovered the entry in the config for attachment-points in the queues section could be replaced by something called animated-mesh. I manually changed the entry and the problem went away.
Look up the two items in blue text in the CCG and you will see how they are used. Try replacing the first for the second.
 
Here is an extract from the config for this item. This is the original default mesh table.

Code:
mesh-table {
 default {
[COLOR=red]mesh     "400 body/400 body.im"[/COLOR]
  auto-create    1
  effects {
   destsign {
    kind   "texture-replacement"
    texture   "texture dest.texture"
   }
  }
 }
You need to change only the red line to as follows:

Code:
mesh-table {
 default {
[COLOR=red]mesh     "400 body/400 body high.im"[/COLOR]
  auto-create    1
  effects {
   destsign {
    kind   "texture-replacement"
    texture   "texture dest.texture"
   }
  }
 }
NOTE: The line in the config is not red. Do not spell it wrong as it will bring up error flag after error flag. Also, the .im has to be in lower case otherwise CMP and Trainz will not recognise the mesh and bring up a "mesh not found" flag.

Thanks. :)
 
Back
Top