bizarre texture behavior

Help. Please?

This is driving me absolutely insane.

Sometimes when I click on a prim, the texture repeats per face values I had previously set (and had been working and looking fine) go totally haywire and set themselves to 100.000.

This seems to happen with both single and multiple prim objects (where sometimes only one prim is affected), linked and non-linked

Other times, I log off with everything as its supposed to be and the next time I log in, the same thing can happen.

And there's more. Occasionally, I'll key in some repeat-per-face values and they instantly snap back to 1.000. And the object isn't locked.

Can any of you helpful people shed some light on this? Mucho thanks!

Reed - This has happened to me the last two days as well, but never before. One thing I did to minimize the problem was to stop the script running before I changed the texture. But... that did not always work either.

me thinks this is a new bug.... If I encounter it tonight, I will report it as such.

Ok this theory has not been tested but I am going to make a fairly educated guess as it has happened to me a couple times in the past couple days as well, I am almost 100% positive it has something to do with the stretch textures toggle. I *think* if a texture has been edited while that box is on, and then the object is selected again (either the object itself or just that face.. ?) the texture repeat sets itself to 100.0 x100.0 yes... this is REALLY annoying.

Check your texture rotation value. Anything other than zero can cause this. Whilte it's possible to get textures right in most cases (though not the sides of cubes with reduced topsize) many of the automatic value adjust ments are, and always have been, completely hosed.

They've said that the next big version will have major graphics updates. Damn, I sure hope so! It'd be about time.

Yes, this exact thing used to happen to me all the time, even before the release of 1.5.

You select an object or a prim in that object, you don’t even need to be on the texture tab you could just be changing the name, then on release or on selecting another part of it, every (and I mean every) texture on the linked section snaps to a repeat of 100x100. Hours of work you did to get those textures painstakingly aliened, poof. The lagyer the environment the worse it got. There were no scripts involved in the builds, just basic prims and textures.

I had bug reported it and posted it to the tech issues forum and I haven’t had the issue for a month or so now, knock on plywood, so I had assumed it had been addressed. But by your account it seems it is back.

All I can suggest is take pictures and bug report it. It helped me to build in the quiet times in the Sim when the lag was at it’s lowest or to build it in a low lag area and then move it in place.

I hope they find the cause.
I feel your pain
KX

I appreciate you all taking the time to respond. One more question. Is anyone else running Mac OS X? Could it be platform specific? If so, it could be the reason we haven't been hearing so much about it since most users are on Windows.

Just wanted to pipe in and mention this is a very old bug. When I first joined (May 2004) this texture behavior was almost the norm. It happened constantly. I am non to happy to see that it has returned.

I run OS/X and have similar texture hiccups all the time: repeats per meter and various other parameters snapping to unexpected values, etc. (Mostly repeats per meter.) Considering previous posts, it doesn't seem to be platform-specific. It seems to me there must be some kind of logic or other coding problem whereby the texture engine (or whatever) has a hard time deciding which parameter takes precedence and how to override previous settings when the values are changing in too many fields at once. I imagine part of the problem has to do with having multiple ways to adjust the same information on the texture tab (i.e., Repeats per Meter and Repeats per Face, which both in the end set the size of the basic pattern unit) and no explicit way to turn each of those on or off.

But this is all just guesswork.

<*hiccup*>