Oh, you mean that kind of shower tile cubby.
I suspected it was some sort of storage arrangement, but it was impossible to discuss anything in concrete terms without some common point of reference.
Frankly, I’m still not sure what you’re having trouble with, or even what you’re trying to do. If your request is to make a model that looks like a photograph and to tell you how I did it, that I can do, but I’m not sure that’s what you’re asking. I originally suspected this had to do with the artful application of marble texturing to a shower setting; now I’m not so sure.
Please, ask a direct question.
As far as the Czuba model–what is dynamic about it? What is dynamic tile? It is not a Dynamic Component and contains no texture. What is it for?
Finally, SU model files have the extension .skp; .skb files are almost the same, except they are what is called “incremental backups.” Every time you save a model file, SU saves whatever is currently in memory under the name of the model with a .skp extension: e.g., modelname.skp. When it does that, it renames the previous version, if there is one, to modelname.skb. It is a backup of the previous version of the file. There are always a modelname.skp and modelname.skb representing the two most recent versions.
There’s no problem sending a .skb except it may not contain what you want to show us (since it’s the previous version).
Edit: By the way, modeling something like wall tiles is really not a good idea: all that geometry adds unnecessary size and degrades the performance of a model. Using an image of the tile, and letting the software repeat it all over a face, results in a far more realistic appearance and a leaner, more nimble model.
It makes sense to model a tile only if you are designing the tile itself and are therefore concerned with its geometry, not if you are covering a surface with copies of the tile. -G