Madelaine McMasters

I never used Pages much, but I like the context aware tools on the right. Flash is even more of a red headed stepchild under Mavericks. It's now sandboxed in Safari because it's just too dangerous to let run wild. It still won't work in SL and I doubt Adobe is going to fix that. I'm quite pleased with Mavericks overall. It's nice to plot a trip in Maps on my Mac, then send it to my phone. I also like being able to read my books on the Mac now. Activity Monitor has always been there, I don't recall seeing any changes to it in Mavericks. Battery life on my MacBook Air has increased significantly with Mavericks, that's very nice. And all my Macs feel faster.

Hi Vic, Rolig Loon was having trouble with llTargetOmega, which prompted me to code up a quick experiment. I sent you a copy of it, which produces the sort of rotation changes you desire. Why your code doesn't do what you want I can't say, but perhaps my demo will give you some insight. As I mentioned in my IM to you, be careful about high rotation rates. llTargetOmega is sampled by the scene's frame rate, and if that falls sufficiently, you will see erratic rotation. Imagine your anemometer has three cups and spins three times per second. If you happen to have a frame rate of 9fps, it will appear to stand still, as each cup will have moved to exactly the position of the previous one at each new frame.

KarenMichelle Lane wrote: WOW - Madelaine - you get the Compassion Award for helping that way. Applauds!!!! Do I still get the award if I admit that I was setting fire to pin filled Linden voodoo dolls while helping other people learn SL? Oh, and call me Maddy, I don't like being reminded that I don't know how to pronounce Madelaine.

Blue Voix wrote: Which is why almost every third party viewer has a in world support group..... Which is inefficient and does not address the issue of trying to help, or get help from, people using different viewers. In the past, when trying to teach people about SL, I often found it necessary to inquire which viewer they were using, then download and run the same myself. This was the only way I could avoid the confusion of that Tower of Babble.

The issue isn't that scenes look different, it's that the user inteface is different. So when you're trying to teach someone how to navigate the SLV UI, you can't say "Go to the "Me" menu" and expect the other party to understand, as they may have no such menu. They may also have a drop down right-click, where you have a pie, and with different options in each, or the same options, but with different names. Across the TPV's the UI is a Tower of Babble.

valerie Inshan wrote: Good morning Hippie. Hugs you. Cheer up, or I'll drag you outside to play... Hi, Kids!!!

Hiya Pussycat, I'm not having viewer problems beyond the norm. The latest Firestorm beta isn't terribly stable, but the release version runs without too much hassle. The LL viewer seems to work as well under Mavericks as Mountain Lion. I won't say that any viewer runs nicely under Mavericks, but in my 5.5 years here, no viewer has run well on any OS. Mavericks doesn't seem to have broken anything and, beyond SL, Mavericks is a pleasant experience. If you have Western Digital external drives running Smartware, be careful... http://www.zdnet.com/western-digital-warns-customers-os-x-mavericks-may-destroy-drive-data-7000022800/

The syntax is probably wrong (been a while since I've coded) but you should be able to work it out. You'll also have to supply the starting of the timer and other stuff... float alpha = 1;integer color = 0;integer prim; Set stuff up here... timer{ color=color++%5; // color cycles 0->4 for(prim=1; prim<=10; prim++){ llSetLinkPrimitiveParamsFast(prim,PRIM_COLOR(ALL_SIDES, llList2Vector(list,(color+prim-1)%5), alpha); }} The magic here is in the modulo operator. You don't actually need it in the first instance, as using it inside the llList2Vector call constrains it to the valid range of 0-4. Also, your example color names are not quite the way the computer would see them. The first item in a list has an index of zero. So your colors go from c0 to c4. Your prim numbers are correct however, as the root prim in a linkset is 1 and the children go up from there. The "-1" in llList2Vector may not be needed. it simply ensures that the script starts with the sequence you listed. If you don't care that the first iteration is p1=c2 (by your naming, c1 by the computer's), then remove it. Oh, and I've no idea if this will complie, much less work. Good luck, Life!

Hit Ctrl-Alt-T to highlight transparent textures (and again to return to normal). The prim will appear as a translucent red thing and you should be able to locate it. Then right click and delete/return it. If it's a very large prim, it may be encroaching from a neighboring sim. If so, you'll have to contact your sim neighbor and have them remove it, or AR it for "encroachment". Good luck, Grizzly!

Dresden Ceriano wrote: But seriously, have you ever even considered that I may have already been dressed as a Christmas tree? If you'd already been dressed like a Christmas tree, I'd not have decorated you, right? You were dressed as a garden variety Colorado Blue Spruce, and the only dates you'd have attracted in that outfit would be squirrels and cardinals. One of those would go for your nuts, the other for... well from what I've seen of the Catholic Church, you'd have done alright with a cardinal. So, I'll take a little credit for your meeting this gingerbread fella. Don't get crumbs on the sheets!

Hi Mosspelt, Failure to rez is often the result of a poor connection between your computer and the SL servers. Here are a couple links that address the issue... http://wiki.phoenixviewer.com/phoenix:bake_fail and... http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ Good luck! ETA: There's a lot of stuff to go through in those pages, Mosspelt. If you're on wi-fi, did you try a cable connection? Did you try using Google's DNS servers at 8.8.8.8 and 8.8.4.4? Hopefully someone else will be along shortly to shine some light on this. It is curious that everything BUT your avi appears to load correctly.

What doesn't kill you makes you stronger - Nietzsche

Good morning, you two!

valerie Inshan wrote: Good morning Hippie! Back at work today but I would have loved to stay in bed this morning... *sighs* Hugs you all guys! Back at work? That means you didn't drink the chicken juice. I'm heartbroken.

Tex Monday wrote: Maybe you should stay in and try to save everyone's soul... Or clean it. I can't do it all by myself.

Baby steps, Peter!

Hi Syle, At first blush, I'd say your problem is that your tests are actually assignments. = assigns == tests if(list_item = 0){} sets list_item to zero, rather than compariing it to zero. The test will always fail, as list_item will always be zero. you want if(list_item == 0), etc Good luck!

Good morning Kursatefe, You're lucky my typing fingers are warmed up... integer Opaque; // 0 = transparent, 1 = opaque default{ state_entry(){ llSetTimerEvent(1); Opaque = 0; } timer(){ if(Opaque){ Opaque=0; llSetAlpha(0,ALL_SIDES); // was opaque, make transparent for one second llSetTimerEvent(1); } else{ Opaque=1; llSetAlpha(1,ALL_SIDES); // was transparent, make opaque for five seconds llSetTimerEvent(5); } }} There's no warranty for that code, express or implied. Good luck!

valerie Inshan wrote: Nooooooooo!!!! Not chicken juice please!!!! LOL You're under the weather? Well, well, well, how convenient that I'm here. I'll fire up the old chicken juicer and have your mind off your sickness in no time!

Hi Cameron, If you are asking why Flash doesn't work, you might want to join the Adobe Flash forum here... http://forums.adobe.com/community/flash We residents didn't invent Flash, nor did Linden Lab. Adobe stopped developing Flash for mobile two years ago and seems to be paying little attention to it elsewhere. I imagine Flash's death will be slow, but it is dying.

RorickVolsung wrote: How did you guys figure out who you were meant to be in second life? Don't rush me. I've no idea who I was meant to be in real life. First things first.

Dresden Ceriano wrote: ...Dres *finally unsubscribes from this thread* ... runs in and decorates Dres like a Christmas tree, six weeks early. Cuz he'll never know. ;-)

Hi Harliew, You can find older releases of Firestorm here... http://wiki.phoenixviewer.com/fs_older_downloads If rolling back to a previous version doesn't fix your problem, come back and edit your question (via "Options" over there on the right) to give us additional information that might help us troubleshoot your problem. Good luck!

I saw that.

Hi LetMe, Your PC laptop may have a better graphics subsystem than the Mac's integrated Intel HD 4000 and so might produce faster framerates at any particular SL graphics quality setting. Beyond that, SL Viewers for Mac do not take advantage of the latest versions of OpenGL, and so usually do not perform as well as on Windows machines of similar capability. There may also be viewer settings differences between the two laptops. Make sure the Mac's draw distance isn't too high (I usually run at 128m) and that you've not enabled intensive things like "Advanced Lighthing" in Preferences->Graphics. SL wants a good network connection and it's possible the two laptops are configured differently. Because I find them to be faster and more reliable than my ISP's recommended DNS servers, I use Google's DNS at 8.8.8.8 and 8.8.4.4 Here are instructions for changing DNS if you use Airport routers... http://www.macinstruct.com/node/447 And here are instructions for changing DNS if your laptop connects directly to your cable modem... http://www.plus.net/support/software/dns/changing_dns_mac.shtml I don't recommend making such changes until you've checked viewer settings to make sure you aren't asking the Mac to do more than it's integrated graphics adapter can handle. If you want to give us more information about the two laptops, come back and edit your question via "Options" over there on the right. We might have better insight into your lag issues if we learn more about your computers and network connection. Good luck!