kiramanell

I had the same thing happening to me the other day (64-bit FS). After a bit of trial and error, I figured it out, though. First install FS. Then go to your Control Panel, and click the 'uninstall' button, You'll see 2 recently added Visual Studio 2013 redistribuable packages listed. Double-click on each of them, and choose 'Repair.' Then FS will start up again.

^^ Been out of it for while. Too bad, I had hoped LL had some concrete info by now. Guess not.

What a weird reactions, LOL. If it's not too much asking, I too would like to know what to expect of Sensar. Is that such a strange question?!

Sara, I stopped using the Linden viewer a while back already. I did use the Black Dragon viewer for a bit, but it kept texture-trashing after a while, after all. The Firestorm viewer, seems to have gotten it 100% right, though: no trashing, not even after having been online for several hours. One thing the Black Dragon viewer did superiorly, was a kind of specular reflection (I forgot the corresponding LL term; it shows real floor reflecions; FS makes the surface looks black when you enable that option).

Christhiana wrote: As far as I know LL has nothing to do with it. The credits go to the firestorm team. LL doesn't even have a 64bit viewer... Christhiana wrote: As far as I know LL has nothing to do with it. The credits go to the firestorm team. LL doesn't even have a 64bit viewer... When I asked them about it, in the firestorm suppport group (as to why they had changed their mind), they told me it was Linden who had instigated the change. Strange.

^^ Ít's currently implemented in the 64-bit Release version of Firestorm (LL viewer too?); and it's rock-stable! Yup, Linden did good!

I want to thank LL for upping the video memory limit to 1G. It's been an uphill battle (on my end, LOL). After sometimes very abusive responses, and sitting thru endless sessions of ppl angrily telling me it can't possibly be done, guess what, it's been done, after all. :P The brief 'I told you so!' moment despite, I primarily just want to thank LL for having done this. Let there be no misunderstanding, I was already half-way out the door, as many of my materials-enabled homes/scenes just kept texture-trashing, sucking all the fun out of SL. And now I can enjoy all those things again, in their full glory. This has definitely sparked my renewed interest in SL. So, thank you, LL, for having upped the video memory cap to 1G! Kira

Jennifer Boyle wrote: I'm not willing to take the time to read the bloated SL TOS again now, but a few years ago it was a TOS violation to collect IP addresses of residients. That was because the TOS prohibited the collection and use of personal information that had not been voluntarily released by the resident. IP banning obviously requires collection of IP addresses. Finally a decent answer offered to the OP. Yes, it's not so much the *banning* that is against the TOS, but collecting a person's real-life identifiable information (which might include their IP address). Yet, unless the collection itself involved criminal activity (hacking their computer, for instance), obtaining/using the IP address to ban someone is. *an sich*, not a criminal offense: it's against the TOS in SL, and possibly tortuous towards the one you're banning (like if you feel you were unlawfully excluded from a store or something, but very hard to make that stick); but not a criminal offense.

LlewLlwyd wrote: Reputedly the Black Dragon Viewer allows you to use more graphics memory than any other. [Personally, I use the Red Dragon Viewer, which allows me to view female avatars with their clothes removed.} Yes to using more video memory of Black Dragon viewer! As to your second comment, I'm trying to determine whether that's sad or funny. I'm leaning towards sad at the moment.

Nova Convair wrote: kiramanell wrote: Unity Canare wrote: I am asking if its possible that is all.. I have never heard of this without chat relays or such devices. A regular llSay() is limited to a 20m range. And any script can listen on channel 0 (it's public, after all).. I suck at math, LOL, but if you put down enough of these 'devices' (just a prim with listener script in it), so as to get full region coverage, then yes, theroretically you could listen in on everything, said everywhere (not counting height, as you'd need a sheer infinite number of devices to cover all up to 4,000m). No one in their sane mind would do this, though, as an endless amount of 'wildcard' listeners would produce an insane amount of lag. Tl;dr: there's no special admin privilege that allows them to listen in on everything, if that's what you meant. That is totally wrong, you need only a few. What makes you think a scripted device has to have a fixed position? It's an invisible micro prim that will go near avatars hide inside of other prims and change their names to something in the vicinity. The sim owner can NOT see the chat on the sim. He needs to use this spy devices. I'm not sure if that isn't against the TOS. I think it is but I'am too lazy to check that. Don't know if someone will care though since it is open chat. Not 'totally wrong' at all. Flying towards a group of avis means you'd have to detect them first (that's the easy part); and by the time you did, there's a good likelihood you will already have missed part of the conversation. So, for a true dragnet, the spy devices would already need to be present (stationary). Also, avis move. So, whereas your spy device can detect them (as an event on entry of the sim, for instance), you would need to continuously poll their current position to make sure you are still in range, lest you lose part of the convo again. The lag of which will kill you (unless, again, you're willing to allow holes in your dragnet). Anyway, all of this is largely academic, really, as the question was about what one would need to create a true dragnet, without *any* holes, I maintain that this cannot be done unless someone were to put an insane amount of such devices on the sim (btw, requiring a LI far in excess of the 15k prim count even).

Unity Canare wrote: I am asking if its possible that is all.. I have never heard of this without chat relays or such devices. A regular llSay() is limited to a 20m range. And any script can listen on channel 0 (it's public, after all).. I suck at math, LOL, but if you put down enough of these 'devices' (just a prim with listener script in it), so as to get full region coverage, then yes, theroretically you could listen in on everything, said everywhere (not counting height, as you'd need a sheer infinite number of devices to cover all up to 4,000m). No one in their sane mind would do this, though, as an endless amount of 'wildcard' listeners would produce an insane amount of lag. Tl;dr: there's no special admin privilege that allows them to listen in on everything, if that's what you meant.

And here's the old FS Jira I once filed about it: http://jira.phoenixviewer.com/browse/SUP-14023 Black Dragon viewers, or anyone else, of course, should feel free to drop in.

Vulpinus wrote: Nice screen shot; this is indeed how SL should look! The visual experience is one of the main draws to me in SL. I recently built myself a mansion which uses a lot of specular and normal maps, many of them home-made. I've eliminated 'superfluous' texture use anywhere I can and reduced the image size of a lot of bought-in textures. Even so, Firestorm and the official LL viewer still struggle after a short time there and the blurries hit. With Black Dragon, it just works, and looks better too. Now that Niran has shown using more GPU memory is not only possible, but makes such a difference (at least to some of us), perhaps LL and the Firestorm devs might take notice... we can hope. In the meantime, I'm getting used to using my Spacemouse to move around with again in Black Dragon. Yes, both LL and Firestorm viewer struggle with the blurring: they're simply using too little video memory. Niran (looks like the man made Black Dragon viewer all by his own self; pretty impressive) showed, irrefutably, that using more video memory than 512MB can be done. I shall endeavor to getting a Firestorm JIRA I once started about this re-opened, pointing to this thread, and ask them to either talk to Niran, to figure out how it's done, or to just flat-out hire the man! Like you, I'm glad I didn't compromize on my build and materials: it was worth the wait. I will try Texture Compression, though, which I saw in Black Dragon today, and which, iirc, is available in Firestorm too. The former says it only reduces the textures' colors (bit-depth reduction only?). Anyway, it might be worth the experiment. Black Dragon will not support per-parcel windlight settings, which is kinda sad; but Niran said LL is planning a complete overhaul of windlight settings (including per-parcel, I take it); so, when the time is there, he will just implement the latter.

Dillon Levenque wrote: I have no data on the issue of video memory limit, so this won't do a thing to help you find an answer. I just wanted to say that your OP and the rest of your comments were very refreshingly cohesive. You identified what appears, based on your discussion and the input of others, a very real and presumably fairly easily solvable issue, but you managed to do so without screaming in rage at the readers of the forum as if we were all employees of Linden Lab. Without screaming at all, actually. I don't believe I even heard you raise your voice. Not only that, but you actually used the phrase 'per se' appropriately, meaning you know what it means. You'd be absolutely astonished to know often it is used in entirely the wrong context (and not infrequently spelled wrong to boot). Point is, you make sense. I didn't miss how you put quotes around 'game', either. I don't recall seeing you before, but you do have 130 posts. Maybe you spend most of your time in other places than GD. I hope you stop by here more often. *blush* Why, thank you for all the kind words! Oh brave virtual world that has such people in it! Also, again a great big thanks to Vulpinus, for his golden tip regarding the Black Dragon viewer! In all honesty, I was not letting my hopes up too high (I figured, how good can it be, next to, say, Firestorm!?). Well, I can be short about it: Black Dragon viewer instantly solved ALL my blurring issues (after, indeed, allocating 2x chunks of 1G video memory to the viewer). So yeah, not to rub it again, but there's the proof: (naturally) using more than 512MB can be done! By the way, Black Dragon also comes with superior Screen Space Reflections to boot! Firestorm viewer has those too, but they totally blacken the mirror surfaces first (thus rendering the feature kinda useless). To wit, here's a snapshot from one of those heftily materials-enabled skyhomes I was talking about: https://www.dropbox.com/s/wjr52zzrwapzgeo/Skyhomes.jpg?dl=0 Just look at those fantastically rendered Screen Space Reflections! (the mirrory effect on the floor). THIS is how SL was meant to be experienced!

Vulpinus wrote: You're welcome. There have been a couple of updates since I last tried it, so I've just been running it again myself. Graphics rendering is spot-on. No thrashing textures, no dumping textures behind my back only to reload them again when I turn around, and, maybe it's me, but everything seems to look just a little better. I'm still struggling to get used to it; mostly I really miss the mouse-walk function that was added to Firestorm but there are other differences too. I guess I'm just used to doing things a certain way. I'll stick with it for a while though I think. Maybe I'll get used to not having the mouse-walk. Wish Niran would add it, but it seems that's not going to happen. I look greatly forward to using it! (Will be at my own computer again tomorrow) Already put in a request, on their forum, for per-parcel windlight settings (Firestorm style). Those I will likely miss the most.

Syo Emerald wrote: Are you using japanese signs as well for that name? If so, I wouldn't IM you, because I would assume you only speak Japanese, because all japanese residents I saw in SL seem to keep to themselves and rarely speak English. ^^ This. Names in Kanji are usually a good indication people are likely Japanese speaking (only), and I won't IM them (what HarrisonMcKenzie would call 'racist,' but which, in a non-tinfoiled world, is just called being respectful: they call that thang a language barrier for good reason). Store owners with Kanji names are different: I will IM them when I need to, and then just assume they probably know English because they're doing business in an English speaking world.

Coby Foden wrote: kiramanell wrote: “No more Linden Programming Language, so you can use existing experts.” Wait, wut?! No more LSL?! Oh yeah, that's gonna work great for backwards compatibility. The Next Generation Platform (as Linden Lab refers to it at the moment) will not be an upgrade of Second Life. It is totally brand new world. Just think that it has nothing at all to do with SL and then you're fine. I had always entertained the (perhaps idle) hope that there would be sort of if not backwards compatibility, then at least some importability. But, as another poster said, obsolescence has become the new business model.

16 wrote: he is MAC address banned. he just has to change it on his computer. he can google to find out how to do that And YOU should not 'aid and abet' him in circumventing his perma-ban, Even offering 'friendly' suggestions thereto is wholly unwise. Just sayin'. The OP, now allegedly matured, should follow suit as an adult, and use the appropriate appeals procedure. Posting on a forum, discussing personal moderation aganst you, I'm sure that's against the TOS too.

Vulpinus wrote: I agree, having been suffering from all this repetitive texture blurring for a while. With what I'm gradually learning about how LL operates though, I think the request is hopeless. I think enforced obsolescence is a standard business practice these days. Security holes in Windows? Buy the next version. SL(1) not working well enough for you? Don't worry, just move to SL2 and buy everything again! /soapbox Have you come across Niran's 'Black Dragon' viewer? It allows separate control of texture and scene memory, up to 1GB each. It worked for me. Once I ramped up the values, the texture thrashing stopped. Unfortunately I still much prefer Firestorm overall. So, more than 512MB certainly is possible. http://niranv-sl.blogspot.co.uk/ ^^ That's a great tip! Thx! Gonna try it out rightaway!

“No more Linden Programming Language, so you can use existing experts.” Wait, wut?! No more LSL?! Oh yeah, that's gonna work great for backwards compatibility.

LlewLlwyd wrote: kiramanell wrote: by the time SL2 gets to the point where there's as much available as in SL now, we'll be 5 years further ahead. Hold your horses! You're getting a bit optimistic there... Not sure if you're being sarcastic, but the 5 year estimate feels reasonable to me, I have many top-notch homes, and furniture, and what not. First SL2 has to be released; and then I project it will really take several years ere the same level of variety and quality, akin to SL, will be available. And that's assuming it will gain maximum traction from the get-go, that is.

Ren Toxx wrote: In many of the numerous discussions about this issue, I’ve seen commented that the 512 Mb. is “a soft limit”, something along the lines that the viewer doesn’t actually “stop cold” at 512 Mb., refusing to load anything else even if the graphics card has more available memory, but rather keeps going if actually necessary. I would say that this is likely true, as I’ve often opened the textures console and seen the numbers raising well past that, often without making the “bias” climb which, in turn, causes the blurring -or, worse, the dreaded “texture trashing” cycle. Nevertheless you do have a point, as both the single-instance blurring and the texture trashing are still existing bugs that affect many people, and none of the countless tentative fixes released so far has definitively eliminated the problem... I reckon because no one has apparently identified the ultimate cause yet, after just as many have been pointed out, from heavy HUDs to badly optimized/separated UI elements, to awfully overtextured products by creators, to outdated 3D rendering engine issues such as you suggest yourself... You can search for this issue at both the official viewer's and Firestorm's JIRA websites, where it has been discussed at great lenght many times. I doubt that you'll find a permanent solution, even for your particular case, but at least it's very probable you'll glean you'll glean a far deeper and technical description about it all than I could possibly provide. Yeah. I've been part of the discussion on Jira, btw. Thing of it is, though, while I've heard many alleged technical reasons for why it can't done, ('32-bit' is always a popular one), I don't wanna hear it. No, seriously, like I said, every other game in the last decade has been able to do so, no sweat; so I don't want to hear some mumbo-jumbo as to why it can't be done, cuz I know, for a fact, that it can. And if they didn't want ppl to run out of video memory (run out of their imposed limit, rather), then why introduce materials?! Realizing it may triple your texture memory needs is not exactly higher math, you know. And what will they do for SL2? Still brush ppl off with some story about 32-bit and alleged issues on AMD cards?! They'll become the laughing stock of the industry. P.S. Got to posting about this again when, the other day, I started up GTA V. You know how much video memory it wants?! Around 3G (if you don't want every shiny option disabled, that is). Not saying SL should be like GTA V per se, but LL just needs to get with the program: everyone else has moved forward a long time ago: so should LL.

NatalyaCrump wrote: Maybe ( maybe) things like this will be improved on when the thing we are all calling "SL2" (or perhaps it should be called SL Vista ! ) eventually is released. But a lot share your frustrations currently. SL2 won't do be me much good for my current homes. And by the time SL2 gets to the point where there's as much available as in SL now, we'll be 5 years further ahead. LL just really need to put some minimal effort into finally lifting the limit. Especially, like I said, since other 'game' makers have been able to do so successfully for over a decade now.

I like to request that LL raise the video memory limit. With the advent of 'materials', essentially the video memory requirements have tripled (max case). Yet the limit remains, stubbornly, set at 512MB, which is, no offense, ridiculously low. I have requested an increase before; as have others. The answer is invariably the same; something like "We've looked into it... 32-bit... some issues with AMD..., etc." Honestly, these answers are pretty lame. *Every* game out there, for the last ten years (and yes, SL is like a game in this context) has been able to use however much memory your card has available. Imagine, say, the makers of Crysis 3 fobbing you off with some story about 32-bit, and no, sorry, no can do! I'm quite serious here. I think LL needs to proudly march into the 21st century, and put some effort into doing what other game makers have accomplished a good decade before already: to use if not all, than at least almost all your available video card memory for SL. The detractors are often hilariously funny. Like I'm being told SL can't use your available video memory, because Windows won't release it again afterwards. (Sic!) Yeah; how many games have you recently played that said 'Sorry, you have to reboot now, as we used up all your memory.'!? Seriously, LL needs to stop making silly excuses. Especially since the request for a raise to the memory limit is not unreasonable at all. I have many materials-enabled scenes, most of which are (even when small-ish) only half-finished, as I'm beginning to run out of video memory on them (you can watch it on your graphics menu, and you know you're hosed when memory usage starts to tilt that 512MB limit, and things start to blur). Could I strip all those materials-enabled scenes, and replace and/or disable the materials altogether. Sure. I don't *want* to, though. Instead I want LL to follow suit on their memory-tripling introduction of materials, and actually start to use all my card's video memory (I have 4G). Or at least scale the memory limit in accordance with the tripling of the memory requirements for materials. It's beginning to affect my enjoyment of SL: if half my homes start blurring, then I'm half inclined to stop being in SL and spend money on it. Can't put it any simpler than that.

Gavin Hird wrote: Because people a) don't like the idea of throwing away their stuff – particulary when the stuff has been made significant personal effort into, like a sim or environment. b) they don't want to be left behind (on the old, when new and shiny is there) and c) they have been generally educated and expect also electronic items to persist over even a lifetime. Form a business standpoint it is almost a disaster as LL will wipe the slate clean, and they will compete with a million voices out there for your attention and money. There is no guarantee the customer base will move to the new, and they migh not even stay on the old. Is it bad that i agree with everything you said here?! Kudos for a point well made!