leliel Mirihi

HotRodJohnny Gears wrote: How old scripts will handle the Display Name/username changes is unknown. I just gave up, closed the club and abandoned my mainland after not finding a buyer, and dropped my Premium membership. I really hope you're joking because LL posted the answer to that question all over the place. The only way you could have had trouble finding it is if you never bothered to look. But just in case the answer is there was no change, old scripts would continue to work the same as they always have. No need to worry about it.

SOCIAL-855 and/or VWR-25395

I think this parcel should be designated as an historical landmark to remind us of what mainland used to look like.

You can change RenderMaxNodeSize in the debug settings, altho I believe it gets reset to the default if you move the quality slider (untested). Be careful of just how high you set it tho. Objects that use more than 8MB of vram* for geometry data are already what I'd consider resource hogs. * It uses vram when VBO is enabled, system memory otherwise.

Tia Biscuit wrote: ......But what did seem to work was redirecting the DNS requests straight to the ISP. Is SL quiet heavy on the DNS requests then? Sort of, yes. the viewer doesn't handle slow or unresponsive domain name servers very gracefully. The viewer has a bad habit of trying something once and if it times out never trying again.

No King, you're still mistaken. Preventing your friends from seeing whether you're online is not the same as preventing your friends from seeing you on their friends list. The option to prevent your friends from seeing if you're online still exists in v2 and Peewee has already told you how to find it.

If you set the torus vertical it will sort of work, as long as all the avatars are on the bottom. I think a better approach would be to have people sit on a scripted pose ball that moves them around the torus correctly.

Elexis Reinard wrote: This camera debug values certainly is promising. It's however centered on the middle of the body. Increasing the height of the camera also makes it rotate downards, like to keep the body's center of mass in the middle of the screen. Is it possible to force the camera to "look" at a certain body part? Yes, there are corresponding debug settings to control where the camera is pointing at. FocusOffset[Front/Rear/Group]View

RenderMaNodeSize specifies the maximum amount of memory a single object can use for geometry data. The default is 4MB for low and mid settings, and 8MB for high and ultra I believe. When an object hits the limit the viewer just stops rendering the rest of it, that's how you end up with jewelry missing half the sculpties.

It's the development version of what will probably become viewer 2.7. The link to the latest version is in my first post. I don't know about the shutting down thing, but that does kind of sound like the winmm.dll problem. There are some other threads here talking about it.

I think it will probably work in the basic mode, you just won't be able to wear or edit your own physics shapes. The physics code has been updated to include breast sway (left/right), and the sliders have been simplified some what. Unfortunately it also resets your physics shapes back to the defaults, but they don't call it beta software for nothing.

You're mistaken, the only way to prevent some one from seeing you on their friends list is to defriend them.

Both the Intel HD graphics found on the Core i3/5/7-xxx and HD 2000/3000 found on the Core i3/5/7-2xxx chips will work with SL. They won't perform all that well, especially the HD graphics, but they're good enough.

Go to Preferences -> Advanced and check "Show develop menu". Then in Develop -> Rendering check the following; Framebuffer Objects, Lighting & Shadows, (optionally) Shadow Maps, SSAO. The last two will cause a big performance hit, but your card should be fast enough to have shadow maps enabled on a good portion of the grid.

The 200M is a mobile version of the x300 that uses shared memory. The x300 itself was just a minor update to the 9550. Anyway Cherriedoll, your best option is to just buy a new laptop. $500 will get you something that will run sl fairly well.

it could be by chance your misteress accidentally de-rendered you and this added you to their asset blacklist all your misteress need do is find the asset blacklist from the phoenix menu and remove anything in it then change group tag

This is the new Basic mode. You can get out of it by selecting Advanced mode at the login screen.

It's a bug, see WEB-3795.

Further testing has shown that it happens with deferred rendering disabled as well.

After some quick testing at Ahern I can now see the high speed animation bug, But neither the max # of imposters slider or RenderUnloadedAvatar effect it in anyway. And I still can't see the distant avatars disappearing bug. Do you have a link to the jira issue?

I wasn't really referring to you in particular. I just seemed like no one noticed my thread even accounting for how slow it is here.

The max number of avatars slider controls how many full avatars can be in viewer when imposters are enabled, no need to play with it when imposters are disabled. RenderUnloadedAvatars just controls whether you see clouds or gray ruths. I wouldn't call either one the full and correct behavior. And they really have nothing to do with avatar imposters. And the OP was asking about rendering glitches with imposters disabled, which I don't see on my machine. Sounds like a bug to me, you should create an issue in jira for it.

Torley Linden makes video tutorials on a wide range of subjects which you can find on youtube here.

I posted that here yesterday. I guess most people have me muted.

Looking at the picture I'd say Ishtara is right and you're seeing what the avatar really looks like. Unfortunately there's not much you can do about it. The only thing I can think of would be to turn on deferred rendering which would clean up the lighting, that way the jagged avatar mesh wouldn't be quiet as noticeable.