Thank you DR and Graham for your help on this.
I haven't altered any settings during route building and the viewing distance has no discernible impact on the colour being displayed. Its mostly the selected brown colour but can turn grey whenever the mood takes it.
Have read through the entire original thread on this topic. It seems to have taxed quite a few people and it's not entirely clear that the problem has yet been resolved. As you have identified, the 7 August 2017 post #50 from p-dehnert (see below) suggests a way forward:-
"The problem is <kuid:101839:60004> LRW Track Mesh Library. The mesh files for the brown ballast (starting with ballast-b- ) and for the grey ballast (starting with ballast-g- ) use the same material name ballast.m.tbumptex. Changing the material name, using a hex editor, of the grey ballast files to ballasg.m.tbumptex fixed the problem.
Trainz doesn't like 2 meshes in the same folder using the same material name, but having different textures for the materials.
Peter"
A later post, #72, 18 July 2019,from GP30Fan indicates this fix resolved the problem, at least for him.
As such, went into (TRS 2019 Build 105096) CM and opened the config txt files for 60004, also 21010 (brown) and 21024 (grey) and started looking for the mesh asset files as described by Peter, hoping to be able to do the same 3 minute fix.
However, my screen displayed the following:-
Brown Ballast
Lod O "Ballast - B - O. im"
Lod 1 "Ballast - B - 1. im"
Lod 2 "Ballast - B - 2. im"
Lod 3 "Ballast - B - 3. im"
Grey Ballast
Data and layout identical to Brown Ballast as above, EXCEPT for letter "B", substitute letter "G". Not exactly the data format that Peter described.
First question - am I looking in the right place/the right data and second, if I am, have the config. txt/mesh asset files been altered/upgraded since August 2017.
Third question - which way from here?
John