Paladin Pinion

You are such a boon to us, Cerise. Is there a way to beg you for the preview hovertext in the forum lists? I miss that more than anything. The ability to hover over a link and see a snippet of the post is so handy, you don't have to open every single page to see if it is something you want to read. Possible? I was so dependent on that.

I'm not sure what I did, but when I logged in this morning I had a private message telling me my rank had gone up from "honored resident" to "member". I haven't a clue why. But gosh, I'm so proud.

Yoz Linden wrote: Curious Hazelnut wrote: 2) The editor built into viewer 2 still doesn't line up the cursor with the text you are editing properly on large files. This is very common for scripts and when writing instructions for new products. It is a huge problem when trying to edit what has already been written. This sounds like a nasty bug in our editor - do you know of a JIRA issue for it? I haven't looked, since I figured LL must know about it, it's so pervasive. It's been there ever since V2 was first released. The longer the script, the more incorrect the cursor offset becomes. I'm just guessing, but if the editor supports unicode, it looks to me like the byte count is wrong. Sometimes it is impossible to place the cursor where you want, it goes to another place in the line, usually offset by one or more characters to the right. An external editor isn't a great solution for me, since I do use the tooltips and popup definitions to remind me of syntax. When the cursor gets off, I look to see how many characters away it is and then use the arrow keys to move back to where it belongs. The cursor doesn't always display there, but when I type, the characters go into the right place. The effect sometimes happens when editing notecards too, but I edit scripts more often so that's where I notice it. I'm on a Mac, if that matters.

Innula Zenovka wrote: So it rather looks as if, one way or another, a version of Sione's Media Filter will very shortly be a feature of the official V2 viewer. Thank you for following this -- it's very good news. I appreciate the post.

I haven't received a single review since the new marketplace opened, though I do get compliments in IM. I see competing products with hundreds of reviews that were transferred from XStreet. Their reviews are largely static too now, but they always look better because they are displaying the old totals.

Darrius Gothly wrote: Porky Gorky wrote: Has search changed then Darius? Looks the same from where I am sitting....prefabs houses keywords etc. Massively changed, back on Feb 15th. So that's what happened. My sales suddenly went to zero about then. They are slowly picking up again but it was a very sudden drop. I'm glad someone is following this, I haven't time.

Steve Noland wrote: Copybotting is still a major issue in SL and still needs to be addressed. Perhaps this community (greenies) and others can work together and look for real solutions to this issue and find some of the same success we are finding in fighting for our privacy. I personally dont have any skills to lend to this (that I know of) but would still show all support I can (afford to with respects to time and funds) to any group opperating with full transparency that seeks a real solution to fighting this great evil. I agree 100% about the need for a solution and the seriousness of the crime. I had my main product stolen and resold. But from a programming perspective, it is difficult if not impossible to prevent copybotting. LL has already done the most obvious thing -- forbidding all known offending viewers. But I don't think there is much more that can be done. If your viewer claims to be the official LL viewer, and passes all the login checks, then it has to be admitted to the grid. There is no way to detect copybotting as it actually is happening either. Every viewer must download the data about all the objects around it. If that data gets saved to someone's hard drive, how is the server or LL to know? From a technical perspective I think it is impossible to detect or stop copybotting. The main recourse we have is to report every incident we know about. But even that won't stop offenders from coming back in a different alt and doing it all over again. Sorry to be so negative, but I can't see what more LL can do about something that is impossible to detect when it happens.

I'm mostly just delighted that Kelly posted at all. I have often wondered about this kind of construction: if(llGetStatus(STATUS_PHANTOM)) // If the object is un-solid llSetStatus(STATUS_PHANTOM, FALSE); // Set the object solid. Seems it would be just as efficient, or maybe more so, to just set phantom to false without bothering to check its current state at all. Is that true?

I imported your original settings and just changed the angle and downward acceleration. You will probably need to adjust it depending on what you want to do. In particular, the age of the particle determines how far it goes. Three seconds may be more than you want. //This script was created by Mote Particle Script Generator. integer onFlag; startParticles() { llParticleSystem([PSYS_PART_FLAGS, 0| PSYS_PART_EMISSIVE_MASK| PSYS_PART_INTERP_COLOR_MASK| PSYS_PART_INTERP_SCALE_MASK| PSYS_PART_FOLLOW_VELOCITY_MASK, PSYS_SRC_BURST_RATE, 4.0, PSYS_SRC_BURST_RADIUS, 1.0, PSYS_SRC_ANGLE_BEGIN, 1.5708, PSYS_SRC_ANGLE_END, 3.1416, PSYS_PART_MAX_AGE, 3.0, PSYS_SRC_BURST_SPEED_MIN, 0.05, PSYS_SRC_BURST_SPEED_MAX, 0.05, PSYS_SRC_TEXTURE, "Particle Texture - Butterfly", PSYS_PART_END_COLOR, <1.0,1.0,1.0>, PSYS_PART_START_SCALE, <0.07,0.07,0.07>, PSYS_PART_END_SCALE, <0.07,0.07,0.07>, PSYS_SRC_ACCEL, <0.0,0.0,-0.2>, PSYS_SRC_PATTERN, PSYS_SRC_PATTERN_ANGLE_CONE ]); } default { state_entry() { onFlag = FALSE; llParticleSystem([]); } on_rez(integer start_param) { llResetScript(); } touch_start(integer total_number) { onFlag = !onFlag; if (onFlag) { startParticles(); } else { llParticleSystem([]); } } } This script toggles particles on touch. If you want a different type of response, you'd need a different control structure. I'll be inworld shortly, if you want me to change this just ping me and I'll be happy to help. It literally takes just a couple of seconds, the whole thing is automated.

You have two or three copies of the particle system in there, plus a listen. I can click you up a script in 2 seconds with Mote if you can describe exactly what you're after. I'm pretty sure the posted stuff isn't really what you want. The Ama Omega script is bulky, and most of it isn't necessary. The "smokey feet" stuff is for one of the particle systems she produced, which you don't want for a wind chime. How far do you want your butterflies to go, in what direction(s), and how often and how fast?

What I am when I'm not me:

Interesting reply from Soft. I'm a little confused about where that leaves RZ now. If the requested changes are made, it sounds like RZ can continue to operate as long as it does not disclose alt info. If so, then it will still ban presumed alts, the only difference being that the user can't identify who those alts are. Since RZ mismatches people all the time, it sounds like it will continue to ban the wrong people as long as it does that silently. Do I have it right?

Lexie, this is so much better than the old forums. I've been exploring the options and prefs, I see now how I can recognize new posts. I have to learn a few more things, but in general this is a vast improvement.

I was able to edit the post I made in the Building forum. It was under the Options menu at the top right of the message. Also, the text here for me shows as black on white. EDITED: I was able to edit this one too.

On Firefox it's showing up as black on white, which for me is a vast improvement over the barely visible green text in the old blogs. I find this much more legible, I can even disable my Greasemonkey script now I think. Another big improvement is the reply editor. The cursor even stays where I put it. Anyone know if there's a way to see only new messages since you last visited?

Yoki Enoch wrote: Most people hate Viewer 2 still. I don't know if "most" is the correct term, but I like it. And I agree that many of those who dislike it haven't even tried the latest version. Once you learn where things have moved to, it grows on you. I have trouble with the ancient 1.x interface now. My main wish for V2 is implementation of standard menu items, the ones that exist on every OS. We need File and Edit menus at the very least. I'm not sure why these basic essentials were removed, but I think having those would make it easier for people to locate some of the interface items they believe are "missing" right now.

Old-timers may already know this, but anyone can get free temporary image uploads using the standard LL Viewer. It takes some extra steps over third-party viewers but it works. Log into Aditi, the beta grid. Uploads there are all free.Upload the images you want to test. Make a note somewhere of their UUIDs.Log out and re-log into the main grid, Agni.Use a script to assign the image by UUID to your build.This lets you view the image which is stored on the beta grid. No one else can see it, your object will look gray to others. But you will be able to see how it looks and decide if you want to upload it permanently to the main grid. Here is a script that you can use to assign the image to your object: default { state_entry() { llSetTexture("5748decc-f629-461c-9a36-a35a221fe21f",ALL_SIDES); } } Substitute the UUID of your test image for the one in the script. Hopefully we'll get temp images in the LL viewer some time, but for now this is a viable solution. It's particularly helpful if you have lots of images to test, because you can upload them all in bulk on the beta grid.

It could be done without too much trouble, but unpackers are very easy to bypass -- just right-click and choose Open. In fact, I don't much like unpacking scripts so I always bypass them and use the manual method instead. So your script idea could work but it wouldn't be completely reliable.

I have to agree. I don't want anything to do with Facebook or Twitter, and we need a way to prevent those connections in our profiles. LL: please allow us to turn this off.

Sorry, I was thinking of http-in, where the caveats on the wiki page say: The following applies when making a request to a script using HTTP-In: When appending a query string to a cap URL there MUST be a trailing slash between the cap guid and the query string token '?'. IE https://sim123.agni.lindenlab.com/cap/f23b4b94-012d-44f2-bd0c-16c328321221?arg=gra will return an HTTP 500, but https://sim123.agni.lindenlab.com/cap/f23b4b94-012d-44f2-bd0c-16c328321221/?arg=gra will succeed. But since you're sending out, I guess that wouldn't apply. The same page says you'll get a 499 error if there are any spaces or if the URL times out. It sounds like you already knew that, though. I'm not sure what else could cause it. The only thing I can think of is that your browser is managing the connection much faster than SL. Maybe SL is timing out due to other internal traffic or something similar.

There's some info here: <http://forums-archive.secondlife.com/54/15/248856/1.html> Make sure your URL is formatted correctly (see the wiki.) Escape it, and make sure there's a slash between the URL and any query parameters you're sending.

Thanks for looking Ella. I've actually had that hard hang myself a few times, but turning off etiher one of anti-aliasing or deferred rendering fixed it. They've done some work on that now but it isn't perfect yet (I think that's why I crashed last night, after looking at too many textures.) The hang I get with 2.4, which doesn't happen in 2.3, is that the initial launch window won't display, so I can't even get to the login screen. As soon as it tries to open, the viewer hangs and the cursor spins forever till I force quit. The Mac is okay after that, it doesn't crash the computer. I just can't launch the viewer. I'd forgotten 10.4.11 wasn't being updated any longer, so yes, you're right about needing to check for updates to QT. And Flash needs to be checked manually by everyone on any version of OS X, the system doesn't do that either. So thanks, I stand corrected. I guess I should JIRA the launch issue in 2.4.

Just a quick comment, most of those suggestions do not apply to Mac users, with the exception of possibly removing the user data files. Macs don't lose chat logs when updating, or have uninstallers (removing the user setting files has to be done manually,), or require QuickTime or Java updates (which are managed by Apple system updates.) Rebooting is almost never required unless the user can't access the internet (and if you know how the Network control panel works, you can often use that instead.) It isn't necessary to delete older versions of the viewer, just don't launch them. Mac apps are pretty much self-contained with no dependencies. I think the real reason the OP is having trouble is because beta 2.4 is not compatible with most recent iMacs. I cannot run 2.4 beta either, it hangs immediately on launch and requires a force-quit. The problem is 100% repeatable. I've heard this is due to incompatibilities with ATI graphics cards, and I hope LL fixes it because virtually all new iMacs have ATI cards. The problem is a combination of issues with Apple drivers and the viewer code. Like the OP, I can run 2.4 fine on my Macbook Pro, which has an nVidia card. I searched JIRA the other day to see if it's been reported but I couldn't find anything. I'm pretty sure the issue has to be in there somewhere, it affects a lot of people, so I was hesitant to enter a duplicate. Several Mac people said they were having trouble on the blog announcement page. Maybe you could find it?

Thanks for entering the bug report, Laurent. I hope Apple pays attention. I've launched 2.4 beta on my MBP and it runs, so the problem does seem to be the ATI cards. Shadows are disabled on my nVidia card too though. If Apple doesn't update its drivers, I wonder if we'll be able to use 2.4 ever, even the final release.

Unfortunately, Radar, it's the Macs with an ATI Radeon graphics card that have the problems, which means any iMac (as far as I know--could be wrong...) That would explain it. My iMac has an ATI card. I'll try it on my older MacBook Pro with the nVidia card. All the 2.x viewers have had a lot of trouble with ATI cards and I wish they'd fix that. All new Macs use ATI only.