Ran into an unusual problem over the past couple days. I decided that my install of Viewer 2, main viewer branch, likely needed updating, so off I went to download and install 184.108.40.206758. It unpacked neatly, installed, I clicked the icon to log in...and crashed.
Huh, I thought. How odd. I verified my settings, realizing that I had automatically chosen the Nostalgia Blue default setting for the StarDust skin, so switched to Original Orange. (Not my favorite, but hey, I can cope; I'm still hating everything about viewer 2 in the first place, so the colors generally don't get under my skin as much as the coding itself.)
And I crashed on login again.
So I switched to the nauseating baby blue, followed by the equally nauseating baby pink, variants of StarDust--colors that I would have serious trouble using. And crashed both times.
At that point I walked away from viewer 2 for a while, because technological glitches when I'm already in full hate mode don't do me any good, and only reinforce the hatred. I came back, hours later, and tried it again, going through both Original Teal and Nostalgia Blue of the Starlight skins. And crashed both times again.
That would be bad enough. But then I started having problems with Singularity, after I had downloaded and installed 220.127.116.11758.
(Well. To be fair, this has been ongoing for about two weeks now. I log in on Singularity and can barely move. I realize I'm carrying a heavy inventory load, but two weeks back, it worked fine; now, it doesn't.)
So, late last night, I tracked down the latest download of Imprudence, because even if I wanted to use Firestorm, I can't, because I crash every single damned time using that, and always have--and installed it. And crashed dead at the start when I loaded it up.
While I'm now uninstalling every version of every viewer I have on my engine, I'm idly searching JIRA filings for similar problems. And not finding much that's actually relevant.
Oh, there are mentions. This, for instance, filed near the end of July, which is now in JIRA limbo because a) the original poster gave almost zero info, and b) when asked for more, has never returned to the JIRA afterwards.
There's also this one from May, but a) it's complaining about a Mac feature for Snowstorm, not the main branch, and b) it's saying that there's a failure to start with install of a new graphics card, which frankly (at least for me) comes down to a driver issue, not a viewer issue.
There's another complaint specifically pointed at the 2.6.3 release, which again does me no good, because it's specifically pointed at Macs, too--and is about a viewer several generations beyond the one I'm trying to use.
And this comment from the SL Community forums just makes my teeth ache. Is your viewer experience less than optimal? Don't worry, you can fix it, because it's ALL YOUR FAULT. Yeah, thanks for that. Only that one doesn't matter for those of us who run Disk Cleanup every few days (though I will grant I don't defrag as often as I likely should). But still, the coding on the main SL viewer shouldn't be so sensitive that emptying the trash will give better performance!
Also, it's really starting to bug me that nearly the default stock answer on the Community forums is use Firestorm. Screw you people, that crashes too. Give me a viewer that goddamn WORKS, and I will swallow my innate mistrust of the Emerald-influenced conniving bastardy behind Phoenix--but since Phoenix can't do that for me, I'm not even considering their product as a viewer!
And Rainbow's out, because Rainbow has major code glitches in the Estate Management system. And now Imprudence is out, because every time I download it, it says the files are corrupted, and to download a new copy!
Friend Alex suggests CoolViewer, which just makes me depressed, but after I track down the latest version of SnowStorm to try that, I'm also going to install CoolViewer and see if I can stand it.
[Note from the Editrix: Near as I can tell, the actual CoolViewer hasn't been updated with any coding past 1.22. I'm trying to go forward, not to backslide into code made obsolete by 1.23! So no on CoolViewer.]
Look, Lindens, I realize I'm not the biggest viewer 2 booster on the grid--it's not hidden in any way that I despise every action of every section of the code. I do not like it really isn't virulent enough, unless I'm also etching that in hydrochloric acid on someone's skin.
BUT. Viewer 2.7 worked, as annoyed as I was by it, and I was hammering it into some form of shape I could live with (which admittedly, basically consisted of me beating at the code and asking it to tell me there were five lights while it begged me to stop hitting it all the time).
Now? Viewer 2.8 fails to work at all. This is, to borrow the parlance of the JIRA, a major showstopper, because if I can't get in, I can't participate on the grid. I can't buy things. I can't go to social events (though seriously, who am I kidding? I no longer go to social events). I can't support charitable efforts. I can't do the job I'm being paid to do. If I can't get onto the grid, why am I bothering to play Second Life?
And it's not just me. Friend Hank has a more highly evolved computer system than I do, and is running at least a dual-core processor, if not a quad-core. His system is fast, lean, and eats code with style and grace.
And he crashes with 18.104.22.168758.
To be absolutely, shockingly blunt about this--Lindens, you fucked up somewhere, and you fucked up badly. Your product no longer works. FIX. IT. Or you will lose people. Because "Fast, Easy, Fun" no longer works as a motto. This is no longer fast, it's far from easy, and in all seriousness, I'd rather be gang-raped by angry dentists than fight viewer 2.x this hard. I am really, honestly, openly, starting to despise everything connected with SL.
Now, if you'll pardon me, I have to install SnowStorm 22.214.171.124830, in the hopes that that will work, and start fixing everything I had fixed in the main branch of the viewer all over again.