Kris Spade

Thank you for your contributions! Hopefully this will pave the way for all viewers to have a Apple Silicon build in the future.

This offers absolutely no value for me whatsoever, so I'll stick to regular Premium. I think the 70 group cap is plenty, and any more than that would simply be too overwhelming with "dings" all the time. I think if LL needs additional revenue, one simple thing they can do that never made any sense to me as to why this rule is in place, is allow residents to purchase their own Homestead region directly from LL without the pre-requisite of having a full region. It costs them nothing to make this change and offers a lot to the residents. There's a certain sense of security that exists with having a region in your own name, and many simply can't afford a full one. In my near 19 years here, I can't tell you how many times I've been screwed over by a land baron.

Yeah, that's what I run into. It goes from Tilia to PayPal which takes time, and then from PayPal to my bank which again takes time. If I could buy them on PayPal with the ability to send them to my own wallet, I could live with that, it's just the 2 steps that have to happen that seem to take longer than they should. If it could go from Tilia to a Bitcoin wallet directly with the same regulatory things (how they generate the 10-99s) in place as if it were going to PayPal/Skrill, that would be fantastic.

PayPal has recently allowed it's users to buy cryptocurrency, which is a step in the right direction, but unfortunately you can only buy them, and sell them there. Can't send to another wallet or trade as far as I know. I wish there was a way to get my Tilia USD to Bitcoin without a series of steps (Tilia to PayPal, then PayPal to Bank) that take a long time, while Tilia still being in full compliance with the IRS. It would be even more awesome if the linden dollar just became it's own cryptocurrency that was available on several exchanges

I just updated BUG-227725 on the Jira with my findings on how I got this fixed for myself today, in case anybody else runs into this in the future. In my case, it was a piece of software called Nahimic, which is packaged with the Realtek HD Universal Audio driver. If you manually close the NAHIMIC processes from Task Manager and open the viewer on the second monitor, it opens up just fine. After discovering that terminating these processes solved the issue for me, I disabled the Nahimic service in Services and rebooted, and no longer have the issue. No software modification was required (I couldn't find an uninstaller for this specifically).

Do you have multiple monitors by any chance?

Nice! Is the viewer launching from either of the monitors just fine? I can launch it from my primary (which is the monitor on my right) but if if I drag it to the left monitor, and relaunch it, it will attempt to launch on the left monitor and freeze with a white screen (Not Responding).

The person who originally filed it was on a 1070 having the same issue, although I am on a 1080 Ti. I did try disabling the Intel onboard GPU from Device Manager, but no change in status (I read that Jira also). Did you happen to do it that way, or through the BIOS?

Hey all, I have 2 monitors, and an nVidia GTX 1080 Ti. Several days ago, any time a Second Life viewer (TPV or official) launches on the second monitor, it just shows up white, with (Not Responding) in the window title. Looking at the update history, it seems that the only Windows updates around that time were Windows Defender antivirus signature updates, and security updates. At the time this started to occur, I was running a fully updated Windows 10 1909. I tried everything I could think of to get it working, various clean installs, video driver rollback, etc. What is interesting is that I ran into a few other people who have only started having the issue around this time. I know in the past, nVidia cards had this issue for "some" people, but it seems recently it hit a whole lot of people who were never experiencing this in the past. I never had an issue with this since I've owned this computer for over a year now. Considering I couldn't seem to fix the issue, I dared to take the plunge and update to Windows 10 2004, hoping maybe this would fix it since one of the things they worked on was enhanced multi-display support. Unfortunately this did not correct the issue, and thankfully, did not cause any additional issue. Both monitors are using display ports, so I decided to try and have the secondary monitor use HDMI instead; this did not fix the issue so I reverted it back to the display port. I tried to switch from the nVidia Game Ready Driver, to the nVidia Studio Driver, but this did not fix the issue either. I am hoping anybody out here might have some insight, has run into this, and was able to find a fix. I am also wondering if there is anybody out there on a Windows 10 desktop machine (with latest updates) with more than one monitor, and an nVidia card that, that is having no trouble launching a Second Life viewer from the secondary or tertiary display? I have no problems with the viewer if I launch it from the primary display, and drag it over to the secondary display, but if I close the viewer on the secondary display, it will want to pop up there again next time, and freeze. I have made some comments on the JIRA, but not everybody looks there, so I was hoping maybe somebody had some exposure to this who is reading the forums. For anybody interested, the JIRA on this issue is here: https://jira.secondlife.com/browse/BUG-227725 Any insight or guidance on this issue is highly appreciated. Thank you!

Started here in 2003, and have some very very old ones, but I'm just going to go with the Decade Challenge and post one from 10 years ago, and one from now.

I see there are some references of Experience Tools in the latest server release notes: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/15#15.01.23.298475 Could this be related?

Just curious, have any of these been issued yet? I had sent a request at the e-mail address as instructed. Thank you!

We're having a strange non-reproducable error on Electrobit City (well I can't reproduce it anyway) where a small number of people who join the experience, auto attaches and teleports are not working for them. This happened to one of my testing alts today which is why I am posting now. The "quick fix" I found was to launch the project viewer and leave the experience, and then get our request to join it again, and then everything worked fine. The huge majority of our visitors don't use the Project Viewer and can't perform this function themselves. I see no way to eject anybody from the experience if they are having this problem, so they end up trapped at the start area not being able to get anywhere. Anybody experience anything like this?

Every MMO out there always suggests, "We reserve the right to purge your data if you don't login/subscribe for more than so many months" however in practice, this never happens. It would be a shame, if a wonderful MMO were to be created in SL, a player gets to a very high level obtaining rare artifacts/gear/weapons, isn't able to login to SL for 6 months (or insert any number there) and all that work/questing was gone. A reasonable limit, per avatar, would be great if doable, with the ability to upgrade that limit per avatar for a price. I haven't logged into Everquest since 2001 but all my stuff is still on my characters

We are only just starting to take a look at the database functions, however I think a global size limit is a bit, limiting. Could we possibly consider space per avatar? Say you have an experience that has been running for years, and 2 years ago, some new person to SL tries the experience ... this person has now been gone for over a year, never to return again, yet this data is still in your database and you are paying for it. New avatars have unlimited inventory associated with their account, and often go away, never to return again; LL is able to deal with that same how, could we apply this sort of idea with a set amount of storage per avatar in the experience (which if isn't enough, could be updgraded globally. Even if that number is super small, like 256 KB, at least that's a limit we can adapt to if needed.