Thanks for uploading the model, it makes things clear. Taking for example the half-walls in your screenshots, with textures running vertically rather than horizontally, the problem is that you are trying to use both explicit Rhino texture mapping, and Real Scale, at the same time; in the rendering, you see the RS mapping, but in Rhino's viewport, you see Rhino's mapping, and naturally, they can't match (if they could, then we wouldn't need RS in the plugin, because that would mean Rhino itself was able to do RS). There are two ways to go:
- a) Delete the Rhino box mapping (and refresh the viewport to update the RS UVs).
- b) Set all the textures in the material to use Relative scale (you can hold CTRL+SHIFT while you change the value to have it set in all the material's textures).
When you use (a), the viewport will match the rendering because the plugin will be able to show you the RS UVs it is going to create. And when you use (b), the viewport will match, because the plugin will just render whatever you have set up in your Rhino box mapping. You just can't use both methods at the same time, for a given object.
As a side note, I gather you have some confusion about the meaning of the "Use Override" switch. How you can think of this is that there is a texture in the material that has no button in the interface; any texture in the material that has Use Override enabled uses the projection properties of this invisible global texture, rather than its own. You can see the effect of this by enabling Use Override, changing Repeat U to 2.22, selecting a different texture, enabling Use Override for that texture, and seeing that the Repeat U value shows the 2.22 you set in the first texture. Changing Repeat U to 3.33 and then switching back to the first texture, you'll see 3.33 for Repeat U there, too. So, any texture in the material with Use Override enabled shares projection property values with every other texture that has it enabled -- that is all that it does.
I hope this helps to clarify things for you.