Is there a new problem with floating text?

The money tree on my public island always used to show a bunch of floating text indicating who donated Lindens, how much paid out, etc. But over the last 2 or 3 days I have noticed that it's not displaying any floating text at all. There are no documented configuration options to disable the text. I have verified that it's not just my avatar- my alt can't see the text either. It's not just my tree either- the money tree at Bravo Bravo (the distributor) doesn't currently show the text (at least on my computers/accounts). I HAVE seen other money trees whose text is still working though... so whatever's happening, it's an inconsistent problem. Other floating text appears to be working... my custom titler and text over boxes at malls, for example, seems to work (but I don't know if it's ALL working). Oh- and the tree's definitely operational. Lots of people have shaken it today, and it's still reporting to the Bravo Bravo index.

I have left a notecard with the creator of the Money tree but she is out of town for a while. This appears to be a recent development. (Client update?) Anyone else noticing inconsistencies with llSetText floating text in general, or with the text on money trees specifically?

Here's what a money tree is supposed to look like:


Here's what my tree (and the one at Bravo Bravo) looks like:

ur using the new and improved .3 client right?

I am indeed.

Me, too. And I noticed the floating text of one of my items (at home) had disappeared. I had to remake it. (It wouldn't take just a replacement or fixing of the embedded text script.)

I checked an item or two at my shop, but I guess I should check them all, including my money tree.

coco

problem solved

more serious note, this build is a nightmare, most of the new bugs ppl post here, tech and current version forum is mainly cause of the .3 ........ (don`t even dare call it a downgrade anymore so bad)

i`d recommend to uninstall and go back to either .1 or .2 wich ever was more stable for u

I've found "unlinking" brought the float texts back for me in 6 cases so I left them unlinked.

Yep, others are seeing it, and not just with money trees. It's new with client 1.17.0.2:
https://jira.secondlife.com/browse/VWR-1448

floating text is lame anyway, too much leaking, ruins stores with other peoples prices floating over your items on the other side of the wall. also the 'do not enter' leak is pathetic...

Floating text is one of my pet hates in SL, like others hate ad farms. People put objects with floating text next to my house and the words appear inside the house. For 10L$ it's possible to upload a texture with writing on made in Paint! or whatever that can be applied to a sign board or a sale box, so there's little need for floating text.

The problem is, that it isn't possible to change that text dynamically (well not easily without upload a lot of textures and using a lot of prims). *If* LL actually implemented the long promised render html to prim, *then* much of the need for floating text would vanish.

Matthew

to prim? I'd be happy with "<b>render html to forums.</b>" (yes, quake before the might of my bolded text that is not bold!)

Back on topic, I've had no problem with floating text, but the text in scripts (but not notecards) appears funny to me. I can see the colors, but the letters appear flattened. It's kinda cool, like a "Lindenese" alphabet, but frustrating as it gets when I need to change a script.

Oh well, I still have a copy of the 1.17.1.0 (or whatever it was) viewer around here somewhere....

Except those signs might not rez!

Of course, if you haven't moved past, realize it's a sign, hold your mouse pointer over it and wait for it to rez, it might have fonts and colors that are unreadable anyway!

At least floating text is instantly readable, and objects can be moved away from walls to not bleed through easily enough...

Vendor with 1 thing in it your looking for and 50 things your not...I would much rather read the floating text of whats showing now then to have to wait all day to load each texture till I find the one I'm looking for. Also, animation vendors...floating text is a must have..or each anim would have to have it's own vendor. Thats why I'm here..I can't see the text over the vendors.

Yeah this still hasn't been fixed, it seems.

It's not new, it's been like that for at least five months. Some times you can see the text on the trees, some times not. Different avas around - one sees it, the other doesn't. The same ava sees it one day and not the next. Was getting better a while back, but turned worse I think two weeks ago.

Animations are one of the very few things for which I'll actually brave the grid to shop, so I've experienced most every anim-selling prim on the grid. It's not actually necessary to use hovertext for this application; the script can just IM the person who's operating the vending prim. Given the odd behavior of hovertext recently, the IMs seem much more reliably associated with the current state--that is, if I buy, I'm more likely to get what was described by IM than what was displayed by hovertext. (Of course, specifically in the case of animations, download delay is such that there's usually plenty of time for the description to get sync'd before the anim plays anyway.)

It's an ongoing problem now. Doesn't matter if you are in Aditi, MG or which client you use. I have set text for my HUD buttons & 90% of the time it doesn't show now. resetting the script doesn't fix it. Have to actually unattach and then reattach it.

Yup. Float text generally borked here as well.
As usual it only happens sometimes. Just to save a Linden saying it: If anyone can come up with a repeatable way of making float text not appear when it should, please please please log it on the JIRA and let this thread know! I'll happily vote for it to be fixed!
Post note:
Related JIRA entries you might want to vote for -
https://jira.secondlife.com/browse/VWR-1533
https://jira.secondlife.com/browse/VWR-1536
https://jira.secondlife.com/browse/VWR-1448 - Apparently fixed internally! Woo!
So it looks like a fix for this has been around internally for at least a month, and it should be in the next RC release. In theory. Honest. No really. Stop looking at me like that!