Beta Testing 1.26.0

A preliminary version of server 1.26.0 has been installed on the "Second Life Beta Server" regions of aditi.

To see which regions are where, see the Wiki page on aditi : https://wiki.secondlife.com/wiki/Preview_Grid

Release notes for 1.26 can be found here : https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.26

oo woo

Great release notes on this one

Nice that SVC-2596 and SVC-2925 are finally getting a fix. With the instant message but though I'm going to chance jinxing it by saying that I really hope the fix doesn't cause even more problems... just a weird feeling caused by hundreds of issues before this dealing with the communications systems where the fix has been worse then the original bug.

Can we get some elaboration on this:

r108151 qa/maint-server/maint-server-5-r108113

* Look into throttling AV (attachment) scripts more to keep sim frame rates high

As a maker of scripted attachments, Id like to know where this went. After looking into it, was it decided to do so, and just how much throttling are we talking?

Re: the throttling, initially there's no additional throttling beyond what there's now. There is code going in that will let us help measure and figure out what we can do to help sim performance.

I'll ask the devs involved for more information about it.

Re: the release notes, we'll work on making them more readable. Right now, they're copied from our internal release notes, which has titles of internal JIRA issues. I realize that they're not the most friendly in the world, but I wanted to get *something* out there with the 1.26 deploy.

I like the release notes on this one, it looks very informative and full of goodness

Okay, thanks, I look forward to hearing more.

I would love more details on the fix to https://jira.secondlife.com/browse/SVC-1042 given that case #1 of SVC-1042 is not a bug, and is required behavior.

In fact I'd appreciate seeing Linden comments on SVC-1042 explaining the fix.

God crash: Admin > God Tools > Request > Request: scripts <count>,<opt causes crash

Why?

I'd be very curious to know what changed regarding SVC-1042, as I agree with Kelly Linden's previous statements on some of the sub tasks and wouldn't want to see any functionality being broken. There's no information on the JIRA or the changelong, that I can see, as to what has been changed merely that something related to that JIRA entry has been addressed (Unfortunarely that JIRA entry is just an index to another group of JIRAs). Some of those sub-tasks I could understand being addressed, others would break functionality.

Could you please extrapolate on what changed?

Just a note -- if you see something you're curious about, you're welcome to log into aditi, go to one of the "Second Life Beta Server" regions, and try out the functionality that may be changed or that you're curious if it has changed.

I will do that, it would help if there were some neighboring regions and parcels with "No Object Entry" turned on and using the 1.26 server code so we could test what's changed in regards to SVC-1042, until the changelog says what's changed.

I'll set some up like that today or tomorrow, and will post here when I've done that.

Thanks.

Thats nice, but we really cannot test admin options there.

/me is looking forward to seeing this go live!!

I've heard this is one of the big causes of the sim fps drop when new folks (especially high-prim ones) TP into a region..

Is the super-long rolling restart stuff mentioned on the status blog for the 17th through 20th for 1.26, or some of the back-end changes we've been hearing about? Just wondering because the blog doesn't actually mention a sim upgrade this time around...

I need to ask a fairly dim question

As I see it, these BETA versions we are trying are really just tweaking and fiddling with things, the odd bug fixes, clean up's and tweaks.

To be honest, I've been running the BEAT for the last 3 or 4 revisions of it, and to be 100% honest, I'd not even know I was running the Bets as it seems to perforrm, look and function (for me) exactly the same as the official current release.

Perhaps I'm lucky, but I've not seen any of the bad graphical glitches posted about on these forums.

So, do I therefore take it, that when this Beta version is "ready" so to speak, this is going to be the new Release version?

Meaning, we're not actually going to get anything "New" in way of features at all?

Or, are the "New Features" part of SL programming done by a different team/dept than the Beta bug/fix people and we will actually see new things appear?

I know many just want bugs fixed and nothing else, but there are so many things screaming out to be tweaked/enhanced. I guess I'm hoping each version will bring obvious improvements to some things, rather than just bug fix's (which are of course great) but nothing to actually see that's new.

Piggie: this thread is about the new server (Beta Server 1.26), not the new client (Release Candidate 1.22.

Yeah, I know..... I cocked up !!!!

Was having my tea break at work and rushing to post.....

Doh !!!

Well this is all very nice, but why are you STILL doing rolling restarts?

Oh right, your 10 year old grid technology requires it to support those 10 year old graphics.

Man, I really wish you'd listened to some of us at the beginning instead of doing the same ego-freak game you're STILL doing.

Customer communication is 1% of your problem, lindens. Your crapulent software and incompetent management is the other 99%.

Nice to see you're trying to fix the easiest thing first though. Very much in character. Bravisse, bravissima.

Your post accomplished what now???

http://jira.secondlife.com/browse/SVC-3867

This is the showstopper bug I am watching that has the most concern. Is it possible for it to be fixed for 1.26?