Rolig Loon

Get a free one on Marketplace You really ought to be putting things in Direct Delivery now, though. :smileywink:

You have to tell your Mac to "authorize applications from anywhere" in the security settings in your Mac preferences. Take a look at Valerie's 2nd response in this thread>>> http://community.secondlife.com/t5/Technical/Cannot-log-into-SL-on-my-MAC-Book-Pro/qaq-p/1635127

Congratulations. :smileyhappy:

All you have to do is put the llParticleSystem function call in your money event. You should also start a timer and then put llParticleSystem([]) in your timer event so that the particle effect turns off again in a short time.

It might be fraud, of course, but it's more likely that the landowner couldn't keep up his payments for land fees (maybe he lost his RL job, landed in the hospital, died ..... ?), so Linden Lab removed the sim. Sims fold all the time as people discover that they can't cover the costs as well as they hoped. Unfortunately, it's a matter between you and the landowner. Linden Lab can't offer you any refund for a deal between the two of you. Fortunately, L$599 is only about $2 US, so you're not out a lot of cash. (That's really cheap rent.)

You can't have tried everything. The answer is in the previous posts this ancient thread. Update your graphics drivers. If you still have trouble, please do NOT add information to someone else's VERY old thread. Start a new question of your own, where people are likely to see it.

Primstar IS compatible with Blender 2.49, but the smart way to install it is to get JASS-2, which contains Primstar, Python, and Blender, all in the proper and compatible versions. Install JASS-2 and everything falls into place automatically. The free version of JASS-2 is sufficient for most SL sculpty purposes. See the Machinimatrix web site.

This thread continues and is answered at http://community.secondlife.com/t5/Avatar/Fix-for-repeated-quot-bake-fail-quot/qaq-p/1692739/comment-id/10196#M10196

This thread is a continuation of http://community.secondlife.com/t5/Avatar/Repeated-cases-of-quot-bake-fail-quot-AKA-the-cloud/qaq-p/1692715 See also http://community.secondlife.com/t5/Avatar/Where-would-I-post-a-solution-to-a-technical-issue/qaq-p/1692721

The best place to put it is as additional information in your own previous post here in Answers. That post already has a good title, so it will pop up when anyone searchs for "bake fail" or "cloud". To add information there, just click on the Options link in the upper right corner of your question and select EDIT. While you are there, be sure to click the box to indicate that your question has been answered. When you have done that, the thread will be archived among the successfully answered questions. Linden Lab mines that archive for tips that should be added to the Knowledge Base for general help.

It's not easy. SL's sun penetrates through all obstacles. One way that helps a lot, though, is to make the prim walls of your cave emitters of black light. You can do it two ways. 1. Select a prim with your Edit/Build tool and then go to its Features tab and put a check in the box marked Light to activate it. Set Intensity to 1.0, Radius to 20.0, and Falloff to 0.01. Click the color picker window and select black. 2. Put this script in a prim.... default{ state_entry() { llSetLinkPrimitiveParamsFast(LINK_THIS,[PRIM_POINT_LIGHT,TRUE, <0.0,0.0,0.0>,1.0,20.0,0.01]); llRemoveInventory(llGetScriptName()); }} That script should turn on the black emitter and then delete itself, so you don't have an extra script hanging around. ETA: Hmmmm.. That's odd. I haven't tried this trick for a while, and I can't get it to work today. That's disappointing.

I doubt that you will be able to get any of the viewers to work on a computer that small, but you might try a text-only viewer like Metaverse or Radegast.

It occurs to me to point out that if you use the first method that I just outlined, you can simplify the way you use SLPPF by using PRIM_LINK_TARGET, as in ... touch_start(integer total_number) { gON=!gON; //basic on/off switch integer i =1; list Params; list WhichWay; //Conditions which will change on touch if(gON) { WhichWay = [PRIM_COLOR,ALL_SIDES,<1.0,0.0,0.0>,1.0]; // Red door } else { WhichWay = [PRIM_COLOR,ALL_SIDES,<1.0,1.0,1.0>,1.0]; //White door } while(i<llGetNumberOfPrims()) { //build the parameters list, in the format PRIM_LINK_TARGET, link number, parameters Params+=[PRIM_LINK_TARGET]+[llList2Integer(gDoors,i)]+WhichWay; i++; } llSetLinkPrimitiveParamsFast(LINK_SET,Params); //apply the parameters to all 'Door" prims }

You can do it either of two ways. One way, as you say, is to put a routine into state_entry that polls all of the prims to put them into groups... integer i;while (i < llGetNumberOfPrims() ){ ++i; if (llGetLinkName(i) == "Door") { gDoors += [i]; } else if (llGetLinkName(i) == "Window") { gWindows += [i]; }} Then you can use SLPPF anywhere later in your script to address all of the doors by referring to their link numbers stored in gDoors, and all of the windows by their link numbers in gWindows. The other way is to poll the links as you need to. integer i;while( i < llGetNumberOfPrims() ){ ++i; if (llGetLinkName(i) == "Door") { llSetLinkColor (<1.0,0.0,0.0>, ALL_SIDES); }} The second way saves you having to use memory for global lists, but it means you're having to poll all the prims in your linkset every time you turn around. Of course, if you don't want to change all of the doors at once but merely identify a particular door, all you have to do is ask if (llGetLinkName(llDetectedLinkNumber(0)) == "Door") // Do something to this link which doesn't depend on either method.

Just so you know ..... You can't sell L$ back to Linden Lab, because you never bought them from them in the first place. Here are the important parts of the TOS (Section 5.2): "The Service includes a component called the 'LindeX exchange' or the 'LindeX,' which refers to an aspect of the Service through which Linden Lab permits transactions in which users may exchange their Linden dollars with one another. [ .... ] Regardless of terminology used, you acknowledge that as used in this Agreement and throughout the Service in the context of Linden dollar transfers: (a) the term 'Sell' means 'to transfer for consideration to another user their Linden dollars in accordance with the Terms of Service,' (b) the term 'Buy' or 'Purchase' means 'to receive for consideration from another user their Linden dollars in accordance with the Terms of Service,' " You are always buying or selling L$ with other SL residents, not with Linden Lab.

Check the manual for your laptops. They probably have a different mapping for the CTRL+Alt+F1 combination that overrides the standard mapping. If that's the case and if you are adventurous, you can remap key combinations yourself to activate a different combination. See https://wiki.secondlife.com/wiki/Keyboard_mapping for instructions. Please pay close attention to the instructions, particularly this one : IMPORTANT: Make a backup copy of keys.xml. so you can restore the original configuration if something goes wrong.

All you can do is ask whoever you bought it from. Some merchants will be understanding and kind-hearted. Don't count on it, but give it a try.

Ms. Aonifall seems to have given you a scripted gift that detects when you log in and sends that e-mail, or perhaps you have subscribed to some device in her shop. If you can't find the object to delete it, the best solution might be to add her name to your e-mail program's spam filter. EDIT: I misread this one. :smileyembarrassed: Still no solution after a long in-world conversation with the OP.

That's true. I was trying to be careful about language without making it sound too arcane. The point is that even if your Mono-compiled script doesn't actually use the 64K of memory allocated to it, that memory is reserved for its use from the total script memory potentially available in the sim. If you can squish several scripts into one, saving much of that reserved memory, you are a better steward of sim resources.

You have the syntax for the llSetPrimitiveParams function in your script already, although I would use llSetLinkPrimitiveParamsFast instead because it doesn't have a delay built into it. Color vectors in SL are normalized RGB vectors, so <255.0,255.0,255.0> (white) is <1.0,1.0,1.0> in SL. To translate "ordinary" RGB into something useful here, then, simply divide each value by 255.0. See https://wiki.secondlife.com/wiki/Category:LSL_Color and, even more useful, http://lslwiki.net/lslwiki/wakka.php?wakka=color . If you want to change colors interactively instead of digging into the script each time you want to change the value of your color vector, one way to do it would be to load a set of vectors into a list and then offer the options in a dialog

Reduce the number of scripts. Whether it's active or idle, a Mono-compiled script has been assigned 64K of memory, so your 50 scripts are being allocated 3.2M of server memory vs. the 64K that one script does. Each of those individual scripts are also using 0.001 to 0.003msec of script time while idle, so adding up to 0.15msec to the server load. All of that is aside from the added efficiency in the script itself when you can do away with a lot of duplicated code. Besides, using llDetectedTouch* functions and textured buttons is a whole lot less clunky-looking than a pile of prim buttons. :smileywink:

Thread continues with more information from the OP at http://community.secondlife.com/t5/Viewers/Firestorm-logging-in-problems/qaq-p/1691937#M5254 . To add information, click on the Options link in the upper right corner of your question and select EDIT. Please do NOT start a new thread.

Thread continued from http://community.secondlife.com/t5/Viewers/Firestorm-logging-in-problems/qaq-p/1691929 . To add information, click on the Options link in the upper right corner of your question and select EDIT. Please do NOT start a new thread. From http://wiki.phoenixviewer.com/mac_osx_10.8 : It is believed that Firestorm on Mac OS X 10.8 Mountain Lion on hardware which has ATI (AMD) graphics cards, will have issues. This is also true for the standard LL viewer; see VWR-28793. If you have an ATI graphics card in your Mac, it is recommended that you NOT upgrade to 10.8 until this is resolved.

Go to Preferences → Graphics; if you cannot see that tab full of options, press the Custom button. Then enable, in order: Basic Shaders Hardware Skinning If either of those remain greyed out, then increase the level of Quality and Performance until they become enabled and can be checked. In some cases, worn mesh attachments will not render properly still. Go to Advanced → Rendering and disable both of the Automatic Alpha Mask options (Press Ctrl-Alt-D if you cannot see the Advanced menu). If none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, find MeshMaxConcurrentRequests and gradually increase the value. It is recommended that you not go over 64; try to keep it less.

Many of the things that we normally suspect -- bad Internet connection, misbehaving router, firewall or anti-virus issues --- are not reasonable here, because you can log in with a different viewer. The problem is apparently in your Firestorm viewer. It is possible for a buildup of too many notifications to cause Firestorm to disconnect during or shortly after login. If you experience such disconnections repeatedly on Firestorm, then follow the instructions under “Firestorm Logs Out During Login” here. If that doesn't help, I suggest logging in with Phoenix and then posing your question live in the Phoenix/Firestorm help group in world.