Jump to content

Cerise Sorbet

Advisor
  • Posts

    2,437
  • Joined

  • Last visited

Everything posted by Cerise Sorbet

  1. For your own stuff, you can use Build->Pathfinding->Linksets...
  2. The installer is blocking systems where the software doesn't really work right. It tends to crash a lot on those older systems even if it does launch and almost sort of kind of work. Note that only the installer does this blocking. The installer is really a compressed file, and the contents can still be extracted with 7-ZIp or your archiver of choice, and the viewer will run that way. About SSE2: the installer actually wasn't checking for that. Until this change, the viewer would install, and then simply wouldn't work right. The updated installer is to stop crap experiences like that, and tell the user it won't work right beforehand. Firestorm has been using updated installer checks for months now, and the world didn't end.
  3. Can't get there with clothing layers. If you want it on one arm you'll have to go with an attachment of some kind.
  4. Yeah, filters like Adblock are pretty simplstic and get lots of false positives. Not every combination of words like that will trigger the filters, but they're updated periodically. So, it's best to stick with neutral filenames even if they aren't blocked right now.
  5. Ebbe said at the education shindig this weekend that he has been working with LL lolyers on that ToS wording, Since this came from Ebbe, I'm inclined to believe it's actually being worked on.
  6. The listing looks OK, but your images will appear blank if you are runing an ad blocker. Rename your product images so they don't have words like "ad" in them, and your blocker won't try to hide them.
  7. nikita Jefferson wrote: I know the sl website is safe, but i don't know if it was always ok or they updated it .and i should change my password Typical linden labs, they give no info and it would seem they are oblivious to the heartbleed bug, although i would think they know full well about it, but have done nothing to put anyones mind at ease. You would think they would post an official notice on the website. Lat time a changed my password here turned into a knightmare so i don't want to do it unless necessary They did give all the info in the blog. They didn't have the heartbeat feature enabled on those servers, so our passwords were not vulnerable. Soft Linden went into more detail here; LL took the conservative approach and stayed on older OpenSSL releases, so they weren't using the broken versions anyway. As Soft mentions in that post, if you used the same password on SL and other sites, you could have something to worry about. If someone knows that an account on another site and your SL account belong to the same person, it would give them some good guesses to try here. That's the usual caution: don't use the same password on any sites that are valuable to you; especially big, don't use your email password on anything else, because email is so often the door to password recovery.
  8. Yes, exactly that, they've just bones that approximate what the avatar morphs do, they are actually independent. A good example of this is a bug in the current fitted mesh viewers. A typo or two made it in for the male chest and belly, so the body morphs are moving too much while the mesh attachments aren't. (A fix has been made for that one, but not in relased viewers yet.)
  9. Oh, yeah, the collision volumes aren't really a weighting story, they're just bones and the avatar body doesn't use them directly. Their legacy use is for detecting mouse touches. avatar_skeleton.xml for the definition and avatar_lad.xml for how the shape params affect it.
  10. Yeah, the weights are in the llm files. The weight changes being tried in STORM-1800 are being made by hand
  11. I remember this came up years ago, and the problem has been the LL are in the same boat, they are reverse engineering too. VWR-6199 has the story.
  12. 2. is closest. See FITMESH-5, first comment. Also, highlighted comment from Jeremiah Linden in FITMESH-2. And wikified that since this is becoming a FAQ.
  13. There is no physics driver on the handle volumes.
  14. SL used to pay contributors. There was money involved and this is SL, so naturally it was abused to death. The end.
  15. Wandering Soulstar wrote: Cerise .. Thanks for the suggestion, tried it but no joy :smileysad: Bummer. What viewer are you using? Does it happen if you try using a different viewer? I ask because this resembles a bug with alpha faces on meshes that is peculiar to Singularity.
  16. Those are called midnight madness, midnight mania, or just MM. Like the lucky chairs, there are lots of clones, all with slightly different names on that same "midnight" theme.
  17. Scat is also used as another name for coprophilia, so that would be the first word I would check. If that doesn't get you off the naughty list, cut out parts of the text until it passes at a lower rating, then add in the rest little by little until you find what's tripping the filters.
  18. The old script is probably checking the sender's key in the listen event, and only listening for llGetOwner(), So, even objects belonging to the same owner would be ignored. If you can't mod a script written that way, then the only ways to talk to it will be through chat, gestures, llDialog or llTextBox.
  19. The problem is not really with your script, but a bug in object updates. I know that LL is aware that this problem is still out there, but fixing it hasn't percolated to the top of their list yet. There is a workarund. After you change the alphas, use a call like this: llSetLinkPrimitiveParamsFast(LINK_SET, [PRIM_TEXT," ",<0.,0.,0.>, 0.0]); This won't add any visible text, but it will force the updates you need to make the mass alpha swaps work consistently. Each time you call that, use a different value for the text or color to make sure it updates, toggling between "" and " " works pretty well.
  20. You're not trying to move the root prim, are you? >_> If yes, make that one a child prim, and use something that doesn't need to move around as the root, or it gets messy.
  21. If you are using an ad blocker, temporarily turn it off and see if the image appears after a page refresh. If that works, take a look at the filename for your uploaded image. If it has words like "ad" or similar in it, ad blockers like to eat those. Pick a name that doesn't have any "suspicious" words in it.
  22. LaskyaClaren wrote: I'm not an expert, but surely PNG will serve the same function as TGA so far as SL is concerned? This is about alpha layers, isn't it? It's not a total replacement because Adobe's PNG exporter likes to wipe out the color channels on pixels with 0 alpha, without an option to preserve them. On the other hand, for the cases where that matters, PSE really isn't the right tool for the job anyway.
  23. At least some of these blank image problems are a bad interaction with Adblock Plus and similar, which people have been using more recently to counter LL's banner ads. Avoid image filenames that have words like ad, advert etc. in them. Even if you don't normally use an ad blocker, it's probably a good idea to test your listings with one on, to make sure your customers don't run afoul of the filters.
  24. Yeah, that's an LSL error message, nothing on your viewer's end. It's a transient bug, been happening since somewhere around last fall. It appears to follow the avatar rather than any particular region or scripted items. Sometimes a relog will clear it, sometimes it just stops on its own. I haven't figured out how to reproduce it at will, but it's real.
  25. the show look at page also explains why the pink crosshair is not a reliable indication of where a person is actually looking.
×
×
  • Create New...