That's exactly what I've done in every posting I've made publicly, both here, on Google , on SLUniverse, and on the LL forums. One thing I don't understand is the fetish some of our haters have for accusing us of lying. There have been a few comments recently from folks claiming to fork - or even "take over" - the development of the Phoenix viewer. As team lead Tonya Souther blogs:Įver since we announced the end of Phoenix support, people have been bitching and moaning about it. What's somewhat confusing is that many Phoenix users are enraged by this rejection, and angry at the Phoenix team for walking away - even though they're still working on third party viewers (the mesh-enabled Firestorm), they're a group of volunteers working on an open source project, and, you know, they gave Phoenix away for free. The in-world support group is: Phoenix Viewer Support.Oh Internet: The developers of Phoenix, once a very popular third party Second Life viewer, are no longer supporting the client, because it's not compatible with recent updates to the official SL viewer codebase (including mesh). If I give it a couple of minutes, it sometimes recovers… sometime not. See: Phoenix Viewer Beta DownloadsĬhanging the window size by dragging still drives my Phoenix viewer into Not Responding. Visit the main download page and get your new copy of Phoenix. Also, there is a fix file for those that are crashing on viewer launch. The viewer no longer pegs my CPU at 100%. This one is optimized for SSE CPU’s (newer CPU’s). Update: I downloaded a new copy of the viewer today. Changing the llkdu.dll made the most improvement. Whatever, I mostly can’t get past “Your clothing is still downloading…” I tried several work-arounds. Others using other viewers have reported similar problems and issues with being able to login. I tried again after swapping llkdu.dll files, which seems to have helped a little. I repeated the process a couple of times. Unfortunately the viewer went right into Not Responding. Lots of disk and network activity at logon, which is to be expected. My resource meter shows 20 threads running and 98% of my CPU devoted to Phoenix. Even before I logon the viewer is sluggish, taking seconds to respond to clicks or typing ID/password and holding the CPU at 100%. My CPU immediately pegs at 100% when I start the viewer. Not surprising in a quick change and release. I’ve seen some small interface mistakes here and there. So, the team has done some work on this viewer. On opening Preferences you’ll see a user interface with a different appearance. CORRECTION: Beezle points out in comments that this llkdu.dll is from Snowglobe. That has to raise some questions in the wake of Emeraldgate. So, I have no idea where this KDU version comes from, but it is way larger than most of the KDU files out there. The SLV2.1.1 version of the llkdu.dll is 712,704 bytes, yesterdays Snowstorm viewer has an llkdu.dll that is 999,424 bytes, and the Display Name Project Viewer’s llkdu.dll is 712,704. The file llkdu.dll (1,175,522 bytes) is used but there is no emkdu.dll. I wish these viewers would just use their own cache. I suggest Ĭ:\Users\\AppData\Local\Phoenix It defaults to the Second Life cache, I recommend you change the cache location before logging in. The viewer installs in a Phoenix folder and creates its own icons. We may yet get a good interface for SLV2 improvements. Their plan is to move quickly to the Snowstorm code base, which is the SLV2 code base and the future of SL viewers. This viewer is based on the Emerald Viewer code and that on Snowgobe 1.5. One can get a copy of the Phoenix Viewer (1.5.0.1) there now. They have a web site up, incomplete… very incomplete. The new team currently consists of Dakun Flux, Dimentox Travanti, Jessica Lyon, Kitty Barnett, LordGregGreg Back, Techwolf Lupindo, Tonya Souther, Vortex Saito, Wickman Gibbs. See the announcement here: From the ashes…. The name… Phoenix Viewer… ok… it is not that novel but it certainly is appropriate. Jessica Lyon is heading up a team to build a TPV (Third Party Viewer). I think many of us were expecting something like this.
0 Comments
Leave a Reply. |