Jump to content

Allen Kerensky

Resident
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Allen Kerensky

  • Rank
    Member
  1. Mircea, I've spent a good 3 hours today hacking through a raft of LL shader compile issues I've encountered on Fedora 18 and 19 with Catalyst 13.4, 13.6-beta, and the radeon kernel driver. I wrote up the following notes to remind myself what I might have to do each viewer upgrade, which may help you out too: http://allenkerensky.com/shader_hacking Error 1: Uninitialized i in LIGHT_LOOP(i) function. Error 2: ukiOpen* function errors cause viewer to drop into "Indirect rendering" (and be basically unusable as it crashes Error 3: EXTENSION directive/keyword undefined Error 4: uniform float delta errors Error 5: __ only for reserved macros
  2. Excellent idea and pretty decent sounding implementation.
  3. Have you read through: "How to Improve Viewer Performance"? http://community.secondlife.com/t5/English-Knowledge-Base/How-to-improve-Viewer-performance/ta-p/1316923 Other things to try: 1. If you are on wifi - try switching temporarily to a wired connection. 2. Check your wireless access point/switch/router to see if you are logging lots of dropped traffic. Network errors means that the SL server, or the viewer, have to wait until an expected message times out, and is resent, which feels like "lag". 3. Make sure your DNS settings are correctly set to your ISP. DNS is an internet service to look up a website or computer's network address based on its name. If it can't lookup the name from where it expects, it can timeout, or spend time retrying elsewhere, causing delays for whatever request its trying to make. 4. Use a multi-traceroute tool to investigate the entire network path from your machine to Linden Lab and the SecondLife servers. Any Internet server or router between you and the SL server that has problems will cause lag-feeling network issues. You want to see round trip times <100ms... the lower the roundtrip times, the better. 5. Look for stuff to shut down: msconfig can show you everything started when you login. Is all of that necessary, or just stealing CPU, RAM, disk, and network I/O time from what you want to do. Be careful not to shutdown necessary security software, but also look for unnecessaryware that tends to come bundled in windows, especially laptops and netbooks. What is each item in your startup? Who created it? What job is it doing? 6. Clean up your system using tools like CCleaner and MyDefrag. 7. Review and tweak your system from the hardware up: http://www.tweakguides.com/NVFORCE_2.html 8. Read the SecondLife debug log (it used to be CTRL-SHIFT-4 on v1 viewers) for viewer reporting errors and investigate and resolve as many of those as you can.
  4. Melody, There's more to it than that. RANT: ON When I signed up to SL it was perfectly clear: 18+ only, always, end of story. LL really confused things by allowing people in child avatars in the first place - which is the literal definition of "ageplayer" if there ever was one. LL further confused things by allowing the child avatars unfettered access to "Mature" or "Adult-Only" rated areas. When LL inflicted Zindra on us, they had the chance to fix that problem, and Jack Linden blew it under pressure from certain unnamed child-avatar activists who demanded to be kids on a continent plainly labeled ADULT ONLY. Ultimately, kid avs who butted their way into Mature and Adult-Only areas through their "political activism" only muddied the waters for themselves and everyone else and now we all pay for it. Rationally *applying* and *enforcing* LL's own rating system would have stopped, prevented, and clarified much of the "ageplay" nonsense right out of the gate. But no - common sense policy has always taken a back-seat to hysterically-inflicted policy as a result of some RL legal case against LL. Before the child players and their "parents" get in an uproar over tipping at their sacred cow - I stand behind it - kid avs should be restricted by LL Community Standards to G-rated areas, along with the people who want to play as parents of kids avs. Want to be a kid or act line one, then why on earth does LL *or* your so-called parents take you to mature or adultonly areas... or worse... live in one, dragging their so-called kids with them. Since LL can't or won't enforce their own maturity standards, it's fallen to the rest of us abuse report the kid for truancy or tresspass, and their so-called parents for negligence If you see a child avatar in mature or adult. But who does that? And let's call it what it is: anyone in a kid av is NOT roleplaying WELL if they demand to be a kid in a mature or adult-only area and then get upset with being kicked out. Drag a kid to a topless bar or adult store in RL and tell me how it goes? If you want to go to the nudie bar or topless dance club - become an adult first. DONE. Since its all roleplaying, we should do what would you do in RL if you saw a young child wandering into a sex shop. Holding the kids to actually acting like kids (rather than grown-ups in creepy avs) will end a lot of the nonsense right there by pushing the kid community to police themselves better. Dragging their roleplaying parents into kids-court too will only provide more encouragement to RP correctly. RANT: OFF Many others have pointed out many "look-based" criteria, but every one of those has a fatal flaw: if you set a specific quantified value - someone will find a way to "game the system" in a way that causes problems when specific policies are literally applied. Now, here's the super-tricky part - what about adult avies who want to be child-like? For example - the Lolita fashion wiki link posted earlier showed adults dressing child-like for whatever reason. Legally - they are still adults even in childlike clothes. How many Halloween costumes in RL would qualify as "ageplay" in SL terms? Or New Years costumes for that matter. Someone else mentioned diapers - which should not even be part of the ageplay discussion without suddenly lumping everyone who is incontinent into an "ageplayer" category, which most would find insulting, as well as some in the BDSM community which has been known to use them for certain scenes having nothing at all to do with under-18 behavior. So, here are some thoughts to make it unambiguous: As far as criteria go, the *first* criteria for any "ageplay" investigation should be: sim rating. Basing the "subjective" child-or-adult rating should include the location where the avatar is. G-rated? bias to assuming, subjectively, that a child-looking av IS a child, since that's the only rating where children avs should be playing anyway. Yes, this also means expecting kid avs and their families to keep their activities on G-rated sims. End. of. story. The *second* criteria should be "are you roleplaying as someone under 18?", as an explicit setting right next to the "maturity rating" a user/Resident chooses to see. LL could also add third unambiguous criteria of "age-rating" to shapes and clothing as a settable attribute. You know how items say: ages 18+ or ages 3-6 - let designers set that explicitly on things they design. For shapes you could add the age rating to the shape settings like gender. You create a shape, and you set the avatar gender AND apparently age, while wearing that shape. Otherwise, the apparent age defaults to "NONE" which has various effects depending on sim rating as described above. Then, LL would have data to make much more consistent determinations of age violations than the "ad-hoc, at-whim, subjective" rating "system" they haphazardly apply now. The real message should be that no one should have to guess. Allow for specific settings and you have specific information to act on. Plus, you could have some additional benefits/features such as auto-muting any under-18 avatar.
  5. Jinx FJ - I mentioned drive-by malware first *laugh* Time to insert another PSA on the dangers of Windows and Internet Exploder and how it is a favorite attack vector. Then, a PSA for http://browserspy.dk which shows just how much information your browser reveals about you. Follow that with an ad for Firefox 4 with NoScript and the extensive list of web-based attack types NoScript protects against. Next an ad for Shields Up at GRC https://www.grc.com/x/ne.dll?bh0bkyd2 shows how open your computer is to direct attack from the Internet if you are not using a firewall, NAT filter, or similar connection tool. Then, let's have a late-night infomercial for the benefits of running Privoxy and Tor for the tin-foil hat crowd. This concludes our Internet security programming day. Cue the Star Spangled Banner music now over a waving flag infographic.
  6. One "numerous method" is to simply harvest the email addresses and other personal right out of your own computer as a result of a breach by a trojan or other drive-by infectious malware.
×
×
  • Create New...