[Genma Saotome]

Reviewing this again... while the original purpose of this thread was about untextured polys there is another condition than never-been-textured and that's unable to find the correct testure file. I think it would be beneficial for the "completeness method" to check for that and include the name of a missing texture (if that's possible). Substituting a grey texture and moving right along is great but it doesn't help resolve the actual problem.

And yes, I know Shapeviewer can be used to figure out whats missing but one needs to know to look and right now there's nothing coming out of OR to tell you that something is missing. IIRC there was at one time something that let you know to investigate but not now.

[James Ross]

Genma Saotome, on 24 January 2015 - 12:21 AM, said:

Reviewing this again... while the original purpose of this thread was about untextured polys there is another condition than never-been-textured and that's unable to find the correct testure file. I think it would be beneficial for the "completeness method" to check for that and include the name of a missing texture (if that's possible). Substituting a grey texture and moving right along is great but it doesn't help resolve the actual problem.

I thought that Open Rails would print a warning if it was told to load a texture that doesn't exist, but maybe not? If this is not the case, file a bug and we can get that added. It doesn't belong in the shape verification code though, as that's meant to be self-container to the S file.

[Genma Saotome]

James Ross, on 26 January 2015 - 01:08 PM, said:

I thought that Open Rails would print a warning if it was told to load a texture that doesn't exist, but maybe not? If this is not the case, file a bug and we can get that added. It doesn't belong in the shape verification code though, as that's meant to be self-container to the S file.

IIRC a long time ago it did... but whether that is correct or not it most certainly does not now. I'll create the bug report.