Build Scale Boundaries

[canny]

Test Plan

• Verify the Horizontal scale and Vertical scale of textures is limited to -10000 to 10000.
• Test for Textures, PBR and Media.

---

I have been working with sculpts made for the leaves of trees. I was trying to copy the model so I could reproduce what the creator had intended so I could use my own textures. In the SL viewer, I cannot recreate the exact same texture. Scale must be set to H=2 V=256 Repeats per meter = 9, Offset is 0.500 for both H and V rotation is 90, Stitching type is a plane When I am in firestorm and use these options, It comes out perfectly. When I am in second life viewer, it does not work. I have tried everything. I cannot recreate the tree canopy with the sl viewer. I teach a class. I ALWAYS teach for the sl viewer. This is the first time I can't recreate something in the SL viewer. Do you have any recommendations? Why is it I can't recreate this simple sculpt texture in the SL viewer, but I have no problem at all in Firestorm?

https://secondlife.canny.io/admin/board/bug-reports/p/texturing-sculpt-issues

[canny]

This issue has been linked to a Canny post: Texturing sculpt issues. 🎉

[AtlasLinden]

Much higher horizontal and vertical scale values can be set via script but the Build Tools UI only allows [-100,100]
FS boundaries are set to [-10000,10000].
Let's do the same as this to avoid the confusion experienced by the reporter.

[akleshchev]

Repeats per meter allows values from -100 to 100, but setting scale to 100 sets repeats to 200, we probably want to fix that as well. Should I expand repeats per meters to match scale?

Also H=2 V=256 Repeats per meter = 9 would set either repeats to 4 or H to 4.5. How is this part supposed to work?

[AtlasLinden]

I thought I was able to achieve this earlier but I'm now having the same issue you're hitting while using FS.
I've reached out to the reporter for clarification.

[AtlasLinden]

User responded saying that repeats per meter resets itself (which will be determined by the size of the face which is info we don't have for this instance). Testing for these exact settings isn't necessary for this issue.
The main issue is that values outside of [-100, 100] cannot be used for scale.

Should I expand repeats per meters to match scale?

I can't see why this would cause any issues having access to these values in the UI if they can be set via script anyway