New Linux enhanced viewer: The Cool SL Viewer

The Windlight experimental version 1.19.0.79627 of the Cool SL Viewer is available now for Linux at http://sldev.free.fr/

Enjoy !

I just can't get voice to work at all.

With nothing in the Openalrc, none of the lines uncommented in the script, voice will not connect

With
(define devices '(alsa native esd null))
(define alsa-out-device "hw:1,0"
(define alsa-in-device "plughw:1,0"

In the openalrc file, voice connects on my end and thats it, no green waves and what not when I talk. I get default and null device

Running Ubuntu 7.10 on a Creative Labs Audigy SE. Sound works in SL though with no problems though

Just wanted to tell you that your cool viewer is awesome! It is running much more stable on Ubuntu Gutsy than just the LL viewer does. I'm a big fan!

ditto!
well i seem to have just about no running issues with both official and unofficial viewers on slackware.

all that i wait for now so anxiously, is a linux client that has managed to mature beyond alpha. would anyone from Linden Lags care to comment?

Just FYI: You have a bug in your RestrainedLife code. The normal RestrainedLife viewer works correctly, but the Cool SL Viewer only honors RestrainedLife API commands from newly-attached items; items that were attached at login ignore all RestrainedLife permissions.

To verify this: put on any RestrainedLife-compatible locked item, log out, then log back in. You can remove it, and perform any actions that it would normally forbid. Now remove the item and re-attach it: it will now perform as per the RestrainedLife API.

Update: Nevermind; this is fixed as of your 1.19.0 build.

Before reporting bugs, please check the latest version....

Plus, this was not a bug in the viewer. This could be a bug in the attached item (which should refresh the RestrainedLife permissions on rezzing, i.e. when attached and when logging in).

But it's most probably the well known and infamous "lost changes on attachement after crash (or spurious log off)" bug... When you modify an attachment in any way (and this includes modifications to the state of its scripts) and a crash occurs (or, if not RestrainedLife-locked, when you drag and drop a new outfit on your avatar, or when you "Wear" a new attachment in the place of the old one), then all the changes are lost and the attachment returns to its old state (the state it was in when you attached it or last logged in).

This is because SL does not store the changes in the asset servers till the attachment is detached explicitly (and not "kicked off" by another either), or till you log off cleanly.

So, should you lock a RestrainedLife item and then crash or get logged off (which occurs pretty often after failed teleports lately), the asset server will not get the data from the sim (in which the attachment is actually rezzed) neither from the viewer (the 'detach' event), and next time you log on, the item will not be locked any more.

You can easily reproduce this weird behaviour without crashing:
- wear a copy-ok and mod-ok attachment.
- modify it in any way you like (shape, texture, color, scripts, etc...).
- right click on the attached item in your inventory and "Copy" it.
- Paste it and attach the new copy.
Surprise ! Your copy is in the state your attachment was before you modified it.

Conclusion: the asset server was not informed of the change till you detached the item... QED.

Henri.

Linux and Windows versions updated to 1.19.0.79890:
sldev.free.fr
my.opera.com/boylane

any chance of some mac (ppc) binaries?
for the cripple that i'm forced to use for some part of the day i need every single performance boost that i can get.

btw, running SL on a mac mini is an even more effective way to be unable to move than the restrainedlife viewer :/

Mo Noel just got a WindLight ready on the Mac (universal). Stay tuned.

link????

noooooooo!!!!!!!!


just installed the newest coolrelease, 80079, and "save screenshots in _sensible_ formats" (png or jpeg) is gone!!!!



noooooooo!!!!!


why?????

I am not sure if either of these are Cool Release issues or issues with SL and/or my incompetence in general, but here goes...

First question: I am using Second Life 1.19.0 (79627) (Cool SL Viewer - Windlight) and I cannot get my start location to show on the log-in screen, despite having set it so to do in Edit-Preferences. Any ideas?

Second question: I am trying to get SLURLs to work with Firefox 2.0.0.12. I've set
network.protocol-handler.external.secondlife and network.protocol-handler.app.secondlife in about:config, along with the path to /home/Innula/CRWindlight1.19/secondlife, and when I click on a slurl, SL starts to launch. Unfortunately, it crashes to the desktop seconds later, before completing the log-in. Any advice?

Do you have the Restrained Life stuff activated? Forcing login to the last locations is one of the features of Restrained Life.

It's because you have RestrainedLife enabled. To prevent avatars escaping a RestrainedLife cage or leash, the viewer prevents changing the login location and always logs you in at your last location, even when the prefs say otherwise. This is documented in RestrainedLifeReadme.txt...



Not sure how well a normal Linux viewer works with SLURLs... But it should log you in at your last location (because of RestrainedLife) and not crash. I'll have a look at this issue.

Because the Windlight code for the snapshot floater changed a lot, and there were many rejects that I could not fix fast enough.

The patch is back in the release 2 of the Windlight Cool SL Viewer v1.19.0.80079.

Thanks, Johnnie. I had some time ago turned Restrained Life on to see how it worked, but thought I'd switched it off. Clearly not. Anyway, that's fixed that.

I had hoped that it would also fix my problem with SLURLs, but it hasn't. I can now, though, see what's happening but I don't have the faintest idea how to fix it, and very odd it is, too.

If I click a SLURL in Firefox it opens up the viewer and tries to take me to the appropriate location. And, after I enabled Autologin in the debug settings menu, it actually gets me there. But then it crashes again. Before I'd enbled Autologin, it had been crashing during the login process.

It's not the SLURL .. if I copy that and paste it into the region name field and take out the secondlife:// bit, I can then get there. It's not a big deal, but it is puzzling. It looks as if the viewer doesn't like being opened by Firefox as opposed to being opened from my desktop shortcut.

I checked and the way I'm launching SL from Firefox is different: I am using the mozex plugin, and a script. IIRC I had the same troubles (crashes) when using the protocol handlers of Firefox with Secondlife, and it was a long time ago, long before the Cool SL Viewer existed, so it is not specific to my build of the viewer.

Here is how to configure mozex (got mozex v1.9.5): in the preferences menu of mozex, click on the "Universal" tab and put "slurl,secondlife" in the protocols scheme list, then "\usr\local\bin\slurl" in the command entry.

Then create an executable "slurl" file in \usr\local\bin, with something like this in it (adapt the path to your SL installation):

#!\bin\bash

\usr\local\SecondLife\secondlife -multiple -url $1

Henri.

PS: I replaced all the slashes with backslashes ("\" in the above text, because else I get an error from the message board when trying to post the message ("Not Found - The requested URL /newreply.php was not found on this server."... Weird !

Thanks, Henri..

Unfortunately I'm still having problems, probably because I know so little about Linux other than that my PC runs so much faster with it than with Windows XP,. Please bear with me.

First, what do I do about the settings I've already got in about:config -- disable them or leave as is?

Second, if I disable them, nothing happens when I try to launch SL from a slurl. If I don't, the viewer starts to launch and then shuts down.

Here, however, is what happens when I run the slurl file as a terminal command:

----------------------

linux-vlj0:/usr/local/bin # ./slurl
2008-02-18T08:45:42Z WARNING: LLHost::getHostName() : Invalid IP address
2008-02-18T08:45:42Z INFO: handleViewerCrash: Creating crash marker file /root/. secondlife/logs/SecondLife.error_marker
2008-02-18T08:45:42Z INFO: handleViewerCrash: Created crash marker file /root/.s econdlife/logs/SecondLife.error_marker
2008-02-18T08:45:42Z INFO: closeDebug: Opening debug file /root/.secondlife/logs /debug_info.log
2008-02-18T08:45:42Z INFO: removeMarkerFile()
2008-02-18T08:45:42Z INFO: do_elfio_glibc_backtrace: Opening stack trace file /r oot/.secondlife/logs/stack_trace.log
2008-02-18T08:45:44Z INFO: do_elfio_glibc_backtrace: Finished generating stack t race.
2008-02-18T08:45:44Z INFO: fork: Forked child process 7828
2008-02-18T08:45:44Z INFO: LLApp:etupErrorHandling - Starting error thread
*** Unclean shutdown. ***

*********************************************************
This is an ALPHA release of the Second Life linux client.
Thank you for testing!
Please see README-linux.txt before reporting problems.

linux-vlj0:/usr/local/bin #
-------------------------------------------


In my PC, CR Windlight actually lives in /home/innula/Windlight1.19 and runs fine when launched by a desktop shortcut pointing to that location.

Disable them.



Like I explained in my last message, you need the mozex extension ( http://mozex.mozdev.org/development.html ).



Err... You need to pass the slurl address as a parameter to the slurl script...

I downloaded it, as you told me to, and set slurl.secondlife under schemes and /usr/local/bin/slurl under command in the Universal Handler section. But it's not a big deal. Thanks for your help and patience.

coolrelease for mac? where/when?

Ok, got a bug here that I do not believe is an SL issue but rather specific to cool release for Windlight. I've seen it both under the Windows and Linux version of Cool Release, most recent Windlight Cool Release. The Lock button on the push to talk button doesn't work. You can't use it to lock your mic open. The only way around this is to go into the prefs and switch PTT over into toggle mode. I did not see this behavior in Windlight on either platform before I installed Cool release. A comment has been made over at the Windows Cool Release Blog at Boy Lane's site.

I do not use voice, never used it and will never use it...

So, I'm not sure whether what you describe is a bug or not: what was the behaviour of this button in Windlight v1.18.6 ?... It should be exactly the same as in the newest Windlight Cool SL Viewer, as in fact, I reverted all the UI changes for the volume controls to the pre-v1.19 UI. If it's the same behaviour, then it is not a bug, but instead a new feature of v1.19 that was not backported to the Cool SL Viewer (and will most probably not get backported till v1.19 becomes the stable viewer and replaces 1.1.

Please, also bear in mind that the 1.19 (Windlight and RC) versions of the Cool SL Viewer are _experimental_ versions and that for serious, everyday use, you should stick to v1.18.5.3 (just like for the official viewers...).

Henri.

I'm having terrible crashing problems today. Whenever I log in with 1.18.5.3 or Nicholaz BE-v in Windows XP I crash within 30 seconds. This is even after a clean reinstall.

Strangely enough though, the Cool SL Viewer is working beautifully on my Linux box with no problems whatsoever.

Thanks Henri !

The previous behavior was that the small lock button on the talk button locked the talk button down so that your mic stays live. In the current Windlight, without your viewer installed, it still does this. With Cool Release installed, the lock button fails to do this, and to work around it, one must go into preferences and switch PTT (Push To Talk) into toggle mode. This is a bug.

BTW, sorry I took so long to answer. I don't come to the forums every day.