selecting things still screwed up with trees around

Try selecting things around a few pine trees. It's impossible. You end up selecting the invisible parts of the tree textures.

About the only thing you can do there is to turn on 'highlight transparent', so you can see where the invisible edges of the tree's prims are, so you can avoid them.

I made a cherry tree recently, and forgot to make it phantom. People kept getting 'stuck in it's branches'. Had to go back and reset all the one's I had 'planted' around my home.

The partially invisible planes of foliage also make it a pain to navigate a camera in and around the branches of a tree. A couple of friends of mine made their home in a large tree, that one of them built. The foliage is on several flat prims that come up from the three main branches, and it's really strange trying to navigate a camera near their 'love nest'.

Sure would be nice if a 100% alpha part of a texture on a phantom prim wasn't clickable or an obstruction to camera movement!

This issue is still not on the know issues list. Ceera, would you please mind bug reporting it as well?

I bug-reported this a couple weeks ago, when it started happening to some people (right after the 1.9 release, it seemed).

One interesting point (I noted in the report) is that this only seems to affect people on PCs with Radeon video cards.

To work around it, you can go to the Debug menu and turn off trees.

I believe you'll find it affects all users the same way. I am in a Mac, and it happens to me.

Any time you have a prim that has a texture on it that is part alpha and part not, the whole prim's surface area is clickable. It's been that way since before I joined SL, not that this was all that long ago...

If you look at most trees with highlight transparent turned on, you can see the full extent of the partially visible planes that they use to make them. A pine tree has a pointy top, but is almost certainly mapped onto a set of three rectangular planes, so the upper part of each plane is a mostly transparent, yet still clickable, area.

backing up your statement. went thru this the other night trying to help a friend pick property...

This is really irritating, yes. I've had to dump a whole load of trees simply because I could not build with them anywhere near me.

Happens to me too. PC with Nvidia GeForce 256mb 6800 (maybe 6600 - I'm not at home where I can look at it.)

Would using the new planar texturing on a box with 0.0 x topsize and a x shear be a possible workaround, at least in so far as making (some, mainly triangular) trees slightly more managable..?

Ever since I came to SL, I've been able to select through transparent parts of masked textures so it doesn't affect all users the same way, Ceera. You say you're on (not IN) a Mac but what video card do you have? I've had only GeForce video cards and have never had masked-texture clicking work any differently (except in Active Worlds). Of course, just clicking a masked-textured prim will still work on the entire prim, as it should.

I'm using a Mac Mini, with the built-in video card in it (an ATI Radeon 9200 with 32MB DDR video memory), running Mac OS 10.3.9 and SL's current client SW. So I am on a Mac, but yes, with a Radeon card in it.

(Although you could say that "Ceera" is "in" my computer, since she's just my on-line Avatar, that was a typo earlier... )

I can drag-select, with 'select only my items' selected, and select items that trees are in the way of. Assuming they aren't my own trees. I do that a lot when I build now. But if I try to click on an item to select it, and there is any sort of alpha plane in the way, it usually means I just selected the tree, or wing, or whatever, and not what I was trying to click on.

I can't clearly recall it being any other way. Perhaps it didn't always do that. I'll admit I have only been in SL since September of last year, so my experience in that regard is limited.

Linden Trees aren't quite the same as ordinary alpha textures, and since 1.9 this has been happening even for trees that are close enough to be displaying in full detail... the enclosing "tree prim" and the virtual "texture prim" enclosing the leaves both seem to produce the same effect.

I'm getting it on a Mac mini with a Radeon 9200, and a PC with an nVidia GeForce card.

Trees are one thing but this is another (and incorrect):



Terrain trees aren't made out of prims. Hence, this statement is incorrect, which is what I am referring to (obviously, I thought)...

Actually it gets worse, last week I was clearing a few trees to make room for a pathway and I was finding it almost impossible to select the right tree! Which resulted in the deletion of a lot of trees I wanted to keep. Clicking on a tree and deleting was often resulting in a tree some 10-20 degrees to one side vanishing.

Indeed the entire process of object selection has become somewhat difficult of late. A couple of days ago I was attempting a simple build - abandoned when I ran into spontaneous permission change problems, linked objects moving when the object was taken and re-rezed, and failure of drag/select/link - which did however use some 23 prims, most of which were in the 0.5 x 0.3m range, all of which were quite close.
Actually selecting items was problematic, especially multi-selecting with the hugly fuzzy yellow lines making it near impossible to tell what was and wasn't selected.

I also noticed that when selecting a small object, then attempting to shift select another small object close by it is now very difficult to actually select, generally the first object becomes de-selected and the one you were attempting to shift select is ignored.

It looks very much to me as if basic bilding tools are now broken...

Oh, and.. Nvidia 6800GS, so it's NOT and ATI issue for once.

I'm on a Geforce 6200 and a desktop pc. I wish they'd get this sorted out.

I get this too and it is quite frustrating. I will submit a report next time I am in-world.

MM

This is what I love. A lot of Residents come together, send their bug reports in, and pool all their info in a thread like this. IT REALLY HELPS.

Thanks to all these details, while it hasn't shown up on Known Issues yet, I managed to repro it for myself over a week ago.

I labelled this as: Pending further verification and resolution from our Linden experts.

I will be pointing out this thread too, although I must emphasize it sometimes helps to keep info focused in a single thread so it isn't spread out--one thread with many replies is better than several with few (I could merge if it really came to that, but--just saying).

Earlier thread was this one:
Anyone having trouble selecting objects in 1.9?

Hey Torley thanks for your help. Just FYI, it's not just other people's trees, it's also my own. I have a ton of pine trees in De Haro.

Thanks Ingrid!

Hi. This should be fixed now:

/3/b8/98429/1.html

" * Trees should not steal focus from selection tool when selecting objects nearby"