Textures not showing

Hi guys!

Another problem: The textures won't show up! The texture console from the debug menu let me think that everything is downloaded (there are no new keys coming up in the list), but the landscape remains brown and I can't see objects in my house. I can see hover text from objects or avatars, but not a single object itself.

When I'm in build mode, I can press CTRL+ALT and the objects show up in transparent red. I can see the door, the desk and stuff. Anyone has the same problem?

I have very slow FULL loads of textures, though my initial load is lots faster than windows. Setting my graphic memory to 128 (settings.ini) helped; but some things just don't load - like a transparent sphere I have, with a "star" pattern on it.

My workaround is, right click on the object , wait a few seconds, and then the load is forced. But the texture console displays a very different picture than in windows: look at the first few lines. Graphic memory is not well recognised/handled in the linux client yet

Also try the patch that forces SL linux to request a visual with alpha channel. As supplied, the client is quite happy to use the default visual, which doesn't have an alpha channel.

Even with all of that, "shiny" is not shiny in linux, though I have it enabled in the settings.ini, and it shows (greyed out) as being checked in the preferences. Trees and terrain do not rez to high detail for me, rather to low... Again, even though selected with the sliders. And unlike objects (right click) and avs (howver mouse), these textures refuse to be forced.

I think that alll the options in "preferences" that are greyed out can perhaps be forced, but are not fully implemented. To be expected with an alpha, I guess.

My "Wish Number One" is that the "request an alpha visual" patch get integrated into the client ASAP

Number Two, that the Graphics Memory be used properly, as well as system memory (reports 1 MB in "help, about Second Life", so that we can see what is the cleint, and what is "sensible" cache handling, when no memory is available.

And having said all that, I went back to windows yesterday for a while, and I quickly saw the difference speed and responsiveness between the linux and windows clients. It took only 10 minutes of saying "argh" and I was back in linux. Even though Windows does on its own fully load most textures, eventually.

Ok, it's hard to guess which values are important in the texture console, but here is a screenshot of mine:



There is the negative value for RAM too. I hope some one could explain the values. Lindens, anywhere? %-)

As I understand it, the "bound" value is for textures loaded into your card's memory (and actually in use). This never exceeds 16 in Linux for me, suggesting that the settings.ini hack didn't really work.

Have you tried changing to a low texture outfit? It might help a bit.

This post is what I found with the texture window:

/263/b3/87885/1.html#post893320

Bound seems the same with windows and linux. The GL Tot is not, and nor is the discard bias.

Eh, maybe I wasn't clear enough: ALL textures are missing. I can only figure out where the sky starts. Only if I press CTRL+ALT in build mode I can see objects, because they are marked red. But that's only the outline, still no textures.