Atomic Systems

markpullinger wrote:The assets supplied with the route caused the issue though rather than the route itself

OK, so open the route supplied .bin file for a particular signal arm and compare it to the same signal from the original pack. If that shows no differences look in the .GeoPcDx files, particularly at the <SourceLToPTransform> sections. For ostensibly the same signal to behave differently from one pack to the other there has to have been a change somewhere along the way.

Apart from the working signals having a different earlier date, the texture file for the posts is a different size (smaller in the route) and some of the lua file are way different - about half the size of the working ones. These are the BRS_TU_Posts.

markpullinger wrote:These are the BRS_TU_Posts.

No, look at one of the stand alone signal arms, not the posts.

Non of the arms are supplied with the route so they are exonerated. I checked the posts which were supplied with the route and there were the differences I posted. I am assuming that the position the post calls for the arm to be in is different between the two. Swapping the renamed folder back in or overwriting the posts etc from the original pack sorts it though, so the problem is with the altered files.

Are the signals you're looking at full assets?---complete with arm and post as one.

No. they are an offset post with platform and a separate arm on the railtrack bit at Kidderminster and when you go into the editor and try to click on the arm, the info in the pop out box is for the post and not the arm.