but the cuts are still open, they're starting to bleed
First up, for everyone: please consider signing this if in the US. There's something truly baffling going on at the FCC currently: they are contemplating handing over the internet as a whole to companies that will demand pay-or-don't-play compliance. This is insane. The internet has arisen slowly from educational servers and military interconnections into what it is today, and sure, there's a lot of nonsense on the net, I'll be the first to admit. But to take it away totally and hand it entire to phone and cable companies? So they can start charging for access and banning anyone whose views they disagree with?
This is ridiculous. Please make your voice heard.
This comes from Lilipily Jewellery:
NOTE: The latest Second Life release has caused some interesting problems, due to a new limitation imposed in it by Linden Lab to force builds to be less prim or especially vertice intense and supposedly ease the problems of lag. This imposition has caused existing builds to not manifest properly, so that bits and pieces appear to be missing. This happens whether the build is of normal prims or sculpted. It happens because there are too many prims in the same area, with too many faces needing to be 'seen.' It is worse in any area where there are a lot of prims, or avs gather with a lot of attachments - so pieces of buildings don't rez, or bits of hair or jewellery or clothing can't be seen.
Until the growing outcry from content creators and their customers forces Linden Lab to return the higher rez ability that was seen in previous release versions, there is only one way that you can ensure that you will see your multi-prim jewellery, or other extensive builds, effectively. It won't help other people to see them better, if they haven't used this work-around, but it will help you know that the area you're visiting or the jewellery you're wearing, for instance, actually IS there, and can be enjoyed by you - and also anyone you tell this workaround to. Here it is:
At the top of your screen, next to the Help button, there is an Advanced button. If you can't see that button, Press ctrl - alt - shift - d. The Advanced button should appear.
Open the Advanced menu and scroll down to the option called "debug settings." This will open a box, where you can either type in, or use the drop down menu to select the setting, "RenderMaxNodeSize." Change the value (it will probably be 4096) to 8192, though you could go as high as 9001 so long as it doesn't cause you any other problems.
Hopefully, when the next release comes in a few months time, this problem will be fixed in the system. In the meantime, spread the word!
*
I discovered this problem when I brought out sculpted handmade necklace chains I made many months ago, thinking I would now attach some pendants to them. They just didn't rez properly, and had lots of pieces missing, though I could see them in edit - and though the bits that were invisible weren't transparent, they just didn't show on my screen. I can tell you that was extremely frustrating, because I'd spent so much time on these chains, and didn't use a machine/script generator to make them (quirk of mine, that I like to make my stuff by hand and eye, alone - especially since I did buy that generator, but have never yet used it!).
They were well over 200 pieces in each chain, and to find that they were suddenly unworkable was really disappointing. So, when I discovered that this is an SL problem, that has been in-built in the latest release, I breathed a sigh of relief that I didn't have to rework them - but, then, realising that sculpted prims have a multitude of vertices that ordinary prims don't, and that so many in one object would create problems for anyone who didn't use this workaround, or who didn't have the computer capacity to use this workaround, I felt that it would be unfair to use the beautiful chains I had created from the lovely sculpted links I'd bought - so, I started from scratch, anyway, to create new chains solely from cut and tortured prims. Now, they may still create some problems for you, if your computer setup is a slow one, because cut and tortured ordinary prims also have more faces than usual. But I did reset to the default levels of my RenderMaxNodeSize, and saw that they rendered well on my screen - so I believe you will only have any problems with these chains if you are in an area where lots of avs are wearing high prim levels, or the area you are in is prim intense. In that case, the above workaround may still work for you, so that you can see your beautiful jewellery on yourself, at least.
Note: the problem persists once you raise it to 8192. I know, mine's been there for a while now. But, it does lessen the problem, so it's good to do anyway.
[19:54] Hope Dreier: Most interesting I'm in VC and the most interesting sequence of prims occurred
[19:56] Hope Dreier: [19:44:21] Caledon Victoria City Freeze detector: 2010-04-06T02:44:23.447141Z: Prims delta: -1598
[19:44:27] Caledon Victoria City Freeze detector: 2010-04-06T02:44:28.745111Z: Prims delta: -58
[19:46:34] Caledon Victoria City Freeze detector: 2010-04-06T02:46:36.690308Z: Prims delta: 58.
[19:46:40] Caledon Victoria City Freeze detector: 2010-04-06T02:46:42.216085Z: Prims delta: 1624
[19:46:43] Caledon Victoria City Freeze detector: 2010-04-06T02:46:44.856602Z: Prims delta: 419
[19:46:47] Caledon Victoria City Freeze detector: 2010-04-06T02:46:49.317261Z: Prims delta: -2092
[19:46:49] Caledon Victoria City Freeze detector: 2010-04-06T02:46:50.948963Z: Prims delta: 2092
[19:46:54] Caledon Victoria City Freeze detector: 2010-04-06T02:46:56.275643Z: Prims delta: -2092
[19:46:54] Caledon Victoria City Freeze detector: 2010-04-06T02:46:56.658608Z: Prims delta: 37
[19:48:13] Caledon Victoria City Freeze detector: 2010-04-06T02:48:14.982112Z: Prims delta: 2055
[19:56] Emilly Orr blinks at the multi-line message.
[19:56] Emilly Orr: Err...what's a Freeze detector?
[19:56] SteelCobra Calamari: o.O
[19:56] Hope Dreier: prim count seems toe be fluctuating rather wildly
[19:57] Terry Lightfoot: yeah....
[19:57] Terry Lightfoot: what's that?
[19:57] Wrath Constantine: What IS that?
[19:57] Hope Dreier: It's a script that detects script [execution] drops
[20:01] Emilly Orr: So essentially, if I understand it, scripts are registering extremely high, then vanishing the next instant? What would cause that?
[20:01] Kamilah Hauptmann comes to have a look.
Still don't know what was causing it, but that was just wild. There then gone then there then gone again. I mention it only in light of the earlier notecard from Lilipily. Same issue?
This is not a spiral. Trippy.
From Miss Muse Carmona comes how to be a neko. I don't agree with everything (for one, I've never been a grunge kitten, with the backpack and the armbands and the scuffed boots. My interpretation has always been finely dressed, whiskered, and furred, thank you, not smooth-skin gutter kitten), but it does lead to fabulous resources on neko stores on the grid.
And where Linden Labs might be going, according to Miss Gwyneth Llewelyn. Me, personally, while there will be instability in the beginning, I'm hoping she's right--because if she is, the world changes a little, but remains.
The way I see things going? We lose the world.
This is ridiculous. Please make your voice heard.
This comes from Lilipily Jewellery:
NOTE: The latest Second Life release has caused some interesting problems, due to a new limitation imposed in it by Linden Lab to force builds to be less prim or especially vertice intense and supposedly ease the problems of lag. This imposition has caused existing builds to not manifest properly, so that bits and pieces appear to be missing. This happens whether the build is of normal prims or sculpted. It happens because there are too many prims in the same area, with too many faces needing to be 'seen.' It is worse in any area where there are a lot of prims, or avs gather with a lot of attachments - so pieces of buildings don't rez, or bits of hair or jewellery or clothing can't be seen.
Until the growing outcry from content creators and their customers forces Linden Lab to return the higher rez ability that was seen in previous release versions, there is only one way that you can ensure that you will see your multi-prim jewellery, or other extensive builds, effectively. It won't help other people to see them better, if they haven't used this work-around, but it will help you know that the area you're visiting or the jewellery you're wearing, for instance, actually IS there, and can be enjoyed by you - and also anyone you tell this workaround to. Here it is:
At the top of your screen, next to the Help button, there is an Advanced button. If you can't see that button, Press ctrl - alt - shift - d. The Advanced button should appear.
Open the Advanced menu and scroll down to the option called "debug settings." This will open a box, where you can either type in, or use the drop down menu to select the setting, "RenderMaxNodeSize." Change the value (it will probably be 4096) to 8192, though you could go as high as 9001 so long as it doesn't cause you any other problems.
Hopefully, when the next release comes in a few months time, this problem will be fixed in the system. In the meantime, spread the word!
*
I discovered this problem when I brought out sculpted handmade necklace chains I made many months ago, thinking I would now attach some pendants to them. They just didn't rez properly, and had lots of pieces missing, though I could see them in edit - and though the bits that were invisible weren't transparent, they just didn't show on my screen. I can tell you that was extremely frustrating, because I'd spent so much time on these chains, and didn't use a machine/script generator to make them (quirk of mine, that I like to make my stuff by hand and eye, alone - especially since I did buy that generator, but have never yet used it!).
They were well over 200 pieces in each chain, and to find that they were suddenly unworkable was really disappointing. So, when I discovered that this is an SL problem, that has been in-built in the latest release, I breathed a sigh of relief that I didn't have to rework them - but, then, realising that sculpted prims have a multitude of vertices that ordinary prims don't, and that so many in one object would create problems for anyone who didn't use this workaround, or who didn't have the computer capacity to use this workaround, I felt that it would be unfair to use the beautiful chains I had created from the lovely sculpted links I'd bought - so, I started from scratch, anyway, to create new chains solely from cut and tortured prims. Now, they may still create some problems for you, if your computer setup is a slow one, because cut and tortured ordinary prims also have more faces than usual. But I did reset to the default levels of my RenderMaxNodeSize, and saw that they rendered well on my screen - so I believe you will only have any problems with these chains if you are in an area where lots of avs are wearing high prim levels, or the area you are in is prim intense. In that case, the above workaround may still work for you, so that you can see your beautiful jewellery on yourself, at least.
Note: the problem persists once you raise it to 8192. I know, mine's been there for a while now. But, it does lessen the problem, so it's good to do anyway.
[19:54] Hope Dreier: Most interesting I'm in VC and the most interesting sequence of prims occurred
[19:56] Hope Dreier: [19:44:21] Caledon Victoria City Freeze detector: 2010-04-06T02:44:23.447141Z: Prims delta: -1598
[19:44:27] Caledon Victoria City Freeze detector: 2010-04-06T02:44:28.745111Z: Prims delta: -58
[19:46:34] Caledon Victoria City Freeze detector: 2010-04-06T02:46:36.690308Z: Prims delta: 58.
[19:46:40] Caledon Victoria City Freeze detector: 2010-04-06T02:46:42.216085Z: Prims delta: 1624
[19:46:43] Caledon Victoria City Freeze detector: 2010-04-06T02:46:44.856602Z: Prims delta: 419
[19:46:47] Caledon Victoria City Freeze detector: 2010-04-06T02:46:49.317261Z: Prims delta: -2092
[19:46:49] Caledon Victoria City Freeze detector: 2010-04-06T02:46:50.948963Z: Prims delta: 2092
[19:46:54] Caledon Victoria City Freeze detector: 2010-04-06T02:46:56.275643Z: Prims delta: -2092
[19:46:54] Caledon Victoria City Freeze detector: 2010-04-06T02:46:56.658608Z: Prims delta: 37
[19:48:13] Caledon Victoria City Freeze detector: 2010-04-06T02:48:14.982112Z: Prims delta: 2055
[19:56] Emilly Orr blinks at the multi-line message.
[19:56] Emilly Orr: Err...what's a Freeze detector?
[19:56] SteelCobra Calamari: o.O
[19:56] Hope Dreier: prim count seems toe be fluctuating rather wildly
[19:57] Terry Lightfoot: yeah....
[19:57] Terry Lightfoot: what's that?
[19:57] Wrath Constantine: What IS that?
[19:57] Hope Dreier: It's a script that detects script [execution] drops
[20:01] Emilly Orr: So essentially, if I understand it, scripts are registering extremely high, then vanishing the next instant? What would cause that?
[20:01] Kamilah Hauptmann comes to have a look.
Still don't know what was causing it, but that was just wild. There then gone then there then gone again. I mention it only in light of the earlier notecard from Lilipily. Same issue?
This is not a spiral. Trippy.
From Miss Muse Carmona comes how to be a neko. I don't agree with everything (for one, I've never been a grunge kitten, with the backpack and the armbands and the scuffed boots. My interpretation has always been finely dressed, whiskered, and furred, thank you, not smooth-skin gutter kitten), but it does lead to fabulous resources on neko stores on the grid.
And where Linden Labs might be going, according to Miss Gwyneth Llewelyn. Me, personally, while there will be instability in the beginning, I'm hoping she's right--because if she is, the world changes a little, but remains.
The way I see things going? We lose the world.
Comments
Actually, no. The FCC decided to step in and prevent ISPs from doing just that, and a court has ruled that the FCC in fact has no power to do so. I don't see what writing the FCC to complain will accomplish. (If you want to complain to somebody, make it Congress, and tell them to explicitly grant the FCC more powers.)
Though writing Congress is never a bad idea. Whether or not they do anything about it, letting them know we have issues with the current decisions is never wrong.
I agree with you, "grunge" is the last genre I prefer to dress in... (I'm usually found in anything from kimono to lovely fashion). But strangely, it seems to be what most of the kittehs on the grid seem to *think* constitutes Neko. And stores too...many of them literally call their "grunge" fashion outfits "Neko fashion."
So I decided to challenge the mindset and wrote a fun story about this in another post (I don't wanna link to it cuz that'd be spammy, lol) but you can find it if you look for the story with the PINK photo on the home page... hehe... titled "Kawaii Neko vs Grunge Neko." For reading in your *spare* time. Right. hehe.
Now as for that FCC ruling... THANKS for that link. I'm spreading it far and wide.
Warmly,
Stacia
Thanks for the Neko referral.
As for the FCC issue, Miss Poindexter is right - the FCC isn't trying to give control of the Internet to the incumbent telco/cable/ISP operators and corporations - Monday's decision in the appeals court denied the FCC the jurisdiction to 1) punish ComCast for alleged throttling of user traffic to prevent or slow down connections to BitTorrent and 2) exercise broad jurisdiction over broadband providers, which some fear may scuttle the National Broadband Plan as well as adoption of Net Neutrality principles.
However, the Free Press petition IS a good one, in my opinion, because the FCC technically has the power to reclassify broadband services in a way that gives it jurisdiction over such providers, without having to go back to Congress for more legislation (which would take forever, be fought over).
I could say more, but you really don't want 1.5 years of telecommunications law study splattered all over your nice clean blog, Miss Orr.
Comcast (xFinity be damned, they're still Comcast) has expressly been going after those who use BitTorrent for years now. And on the basis of other peoples' rights, they have filed--or said they've filed--DMCA takedowns on those who torrent down films, whether or not those films are in the public domain.
I know because two of my former roommates got such letters, from Comcast--one fellow for downloading EVERYTHING in the known universe, and the other for downloading a film from the 1930s that had, by accord and by her understanding, been in the public domain for at least ten years.
But both of them used BitTorrent to do it. And Comcast has no qualms about scaring people with just enough truth to get them to stop doing what's not always illegal, anyway.
I don't use BitTorrent, and weirdly, that's the only one they watch for--I have downloaded things that are not precisely legal to download, using another torrent program, and Comcast never said a word. So they're only throttling people they find using BitTorrent, specifically, as far as I know.
Does that make what I did legal? No, though I have the intention to buy the DVDs for what I did download, and have deleted those files from my system. That's about all I can do to remain, in my view, legally compliant, if still culpable. (It's a hard road to hoe, being a media fan and an avid television watcher, without cable.)
The point is, though, Comcast doesn't have legal standing to do what they're doing in the first place, but then, the FCC doesn't have much for legal standing, either.
Though to reflect back to Miss Poindexter's point, I think the FCC abuses the power they have; I don't think I want them to be gifted more powers to be media despots.