Viktoria Dovgal

Haven't done anything with the marketplace in years, hope this came out right, Freebie intan hud replacement that works in no scripts spots. it's supposed to be mod/copy/no transfer and it's supposed to work, holler if not. https://marketplace.secondlife.com/p/alternate-hud-for-intan/5710438

SodaGnome wrote: Thanks Viktoria! There was a copy in the received items section!!!!!!!!!!! I noticed if you take off the item it dispeaars from main inventory - but the copies remain in the received folder. Never thought to look there. Originally LL was going to make it so that rezzing and wearing would not work from Received Items, so that this kind of problem wouldn't come up. I wonder why they changed their minds. Anyway, yeah, links will show up in the current outfit folder, and in saved outfits too, but the originals stay hidden from find until you move them out of received.

If you got them thru marketplace, peek down in the received items section. Maybe you'll luck out and the SL10B stuff is still in there. Standard inventory find ignores that part, so it's good to get in the habit of dragging things out into a regular folder.

Phil Deakins wrote: It's excellent news that those vehicles are gone. They were a real pain for road users. LL did something right for a change. @Dillon. For some reason, I couldn't see anything in AnnMarie's profile with the LL viewer but I could read it all with the Singularity viewer. The old non-web style profiles ignore the privacy settings we can set theough the web version.

Huh, those cars must have been more reliant on that autoreturn exploit than it appeared.

Don't expect to see any newer drivers for the 4000 cards, this is what happens to older hardware generations. Nvidia does about the same thing; newer installers will run for their old cards, but old drivers are installed for them. Now this is unusual for Microsoft, but with the Windows 8.1 update it looks like they are installing the latest available drivers for AMD cards. I found out this one the hard way: I wanted to temporarily downgrade the driver to run an older viewer that hadn't been patched for the Catalyst crash, so uninstalled Catalyst, and Windows replaced it with an identical driver version. I also could not install an older Catalyst without crashing, so there is no looking back for the current cards on 8.1. If you decide to experiment with other drivers for that 4850, save the state with System Restore first. AMD's installers don't do that automatically, and you'll want a nice fresh restore point if an installer dies half the way through.

AbbyFraser wrote: oh i see. Well yes i was talking about those "lookat hints"... Sometimes they stay gray in front of the avatar, sometimes they become blue for a few seconds or sometimes they stay pink. I was just wondering if bots can do that too. Someone told me if an avatar has that then its NOT a bot Abby Yeah, when bot software and custom viewers were still in their infancy, that was a difference you could mostly rely on. So whoever told you that was just working off old information. Good rule of thumb: if there is something bots seemingly can't do, then someone is working on making a bot that can do that, or already has.

The oldest bots didn't try to sent camera hints at all, but some newer bots and text clients do add some so the avatar looks a little more "alive". Nearly all bots that generate LookAt targets implement them a little differently from how a normal LL-derived client would, with both timing differences and a different choice of what hints to use when. LookAt hints are totally under the client's control. The location and color of the crosshairs you see don't necessarily have anything to do with what the avatar is really up to. There used to be a viewer gag in circulation that would randomly land crosshairs all around the region, just to mess with people who took them seriously.

Real phones do feed back a little bit of the speaker's voice to make conversations feel more natural. Artificial background noise is also commonly added, to compensate for the eerie silences compression and cancellation leave behind. Speakerphones had to leave these cues out, a big part of why talking on them can feel awkward.

Alicia Sautereau wrote: Wouldn`t know, rezzing in 40-50 people still takes 20 minutes lol Ha, yeah. Big crowds of people are usually in the same spaces as big piles of vendor textures, and massive floods of object updates from all those avatars. There is no winning this game.

Reposting here because there were several threads on this. There is a new test viewer you can try. It is working for me with Catalyst 13.9, I hope this fix will do the job for others too. http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/simon-ll-viewer-cat/rev/282303/arch/CYGWIN/installer/Second_Life_3-6-8-282303_Test_Setup.exe The red menu bar is normal, it's a reminder that you're on an experimental viewer.

Vinnie Myoo wrote: Is there no fix? I hate having to use Firestorm, i think the SL viewer looks way better. This is really bumming me out. There is a new test viewer you can try. It is working for me with Catalyst 13.9, I hope this fix will do the job for others too. http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/simon-ll-viewer-cat/rev/282303/arch/CYGWIN/installer/Second_Life_3-6-8-282303_Test_Setup.exe Oh yeah: the red menu bar is normal, it's a reminder that you're on an experimental viewer.

If you updated to Catalyst 13.9 on that machine, that would be the problem. 13.4 works.

OpenGL Version: 4.2.12441 Compatibility Profile Context 13.200.11.0 It's this, the graphics driver is too new. Second Life is not compatible with AMD Catalyst versions newer than 13.4 Help>About in the viewer will show "OpenGL Version: 4.2.12217 Compatibility Profile Context 12.104.0.0" for the last version that worked.

Not just you, SL is not compatible with the current Catalyst, on Windows or Linux.