Jump to content

Madelaine McMasters

Resident
  • Posts

    22,941
  • Joined

  • Days Won

    19

Everything posted by Madelaine McMasters

  1. Lia! Welcome back! As Belinda explained, you might have been given a RLV scripted attachment, perhaps even another collar disguised as something else. Look in the Worn/Wearing tab of either inventory or the outfits tool to see what attachments you're wearing. If you see something you don't recognize, remove it, relog with RLV enabled, and see if you can now TP. Restrictions are the sum total of all restrictions created by all RLV scripted things you wear. Someone could give you a rose which contains a RLV script that completely locks you down. Removing every other RLV thing you're wearing won't undo those restrictions. You'd have to detach the rose, which would likely require disabling RLV. It's also possible for nefarious actors to access your collar via the built in relay. For your own safety, make the the relay is off or set to "Ask". I think you can also type "@list" in chat and get a listing of all active RLV attachments and the restrictions they set. That should reveal your culprit. Good luck!
  2. When you right click and "Block", the viewer blocks the user by username. If you entered his display name into your ban list, that will fail. Enter his username.
  3. I don't think there is a future for AMD/NVIDIA on macOS. Apple Silicon does not support external GPUs.
  4. https://www.amazon.com/Eve-Female-Drove-Million-Evolution-ebook/dp/B0BR51FB12
  5. I just compared a texture I uploaded in 2012 to the same texture uploaded moments ago, from the same original. I saved both textures back to my Mac. Using "difference" in my image editor, I get a histogram with only <0,0,0>. Nothing has changed for me.
  6. I hear ya, Lindal. I just "graduated" from cardiac rehab. In February I learned, unexpectedly, that I have significant coronary artery disease and it's not easily addressed. That's reset my expectations for longevity. As compelling as SL is, having RL threaten to kill you if you don't pay more attention to it gets your... attention. I won't be sad to see you go, as it's the best path for you. Instead, I'll be thankful for the time you were with us and wish you the best.
  7. Elevators are perfect. Start this video at 11:00. https://archive.org/details/saturday-night-live-s-10-e-06-ed-asner-the-kinks
  8. https://www.thisamericanlife.org/801/must-be-rats-on-the-brain
  9. The appearance of cleavage depends on the skin as much as the shape sliders. Some skins come with cleavage/no-cleavage options. If there's a sharp cleavage line in the skin, no amount of slider jamming will get rid of it. Here's an example... ... there's nothing the sliders can do about that third boob.
  10. I was raised in a gender ambivalent family, so there's a lot of cultural norm BS I can't relate to. Like you, there's no difference in my feeling or behavior in male or female avatars. I am, however, quite aware of society's nonsensical beliefs, and see them applied to me every day. Those beliefs are more amusement to me than anything else, but I can see how baseless cultural norms can truly limit people from achieving their full potential and so I do push back on them. You don't have to know a thing, Krystina. Just don a male avatar and let everyone else project on it.
  11. Bleuhazenfurfle, in the JIRA comments, points out the FATAL flaw in any desire to invoke SIMD instructions in LSL. LSL does not support arrays. The overhead of unpacking one SIMD register's worth of data from a list, then repacking the result, will dwarf any advantage of the SIMD instruction. The true value of SIMD instructions comes from their use in loops that walk through arrays of data already in SIMD format. This request is DOA.
  12. Move the "string sound;" statement from the sound script to the top of the particle script. Take the one line inside state_entry() in your sound script and move it inside state_entry() in your particle script. Take the llStopSound() call from the sound script and place it right after the empty llParticleSystem([]) call in your particle script. Take the llLoopSound() call from the sound script and place it right after the startParticle() call in your particle script. By using only one toggle (isOn), you eliminate the possibility of sound and particles decoupling.
  13. Any nostalgia I feel for the "good old days" is really just my endless desire to be a newbie. It's up to me to make that happen.
  14. There were two prohibitions listed. My code addressed them, and only them. Your code prohibits ANY behavior. That's a pretty egregious error, don't you think?
  15. My code was correct. Your code will reject values of BehaviorInQuestion that are not prohibited. You once expressed relief that you never had to write code for medical instrumentation. I share that relief.
  16. I guess "both" is ok! default { state_entry() { integer Okay = 0; integer SexuallyExplicit = 1; integer IntenselyViolent = 2; integer BehaviorInQuestion = SexuallyExplicit + IntenselyViolent; if( ( (BehaviorInQuestion & SexuallyExplicit) | (BehaviorInQuestion & IntenselyViolent) ) != Okay){ llOwnerSay("Love doesn't understand basic logic."); } } }
×
×
  • Create New...