Hitomi Tiponi

Baloo Uriza wrote: They're claiming that innovation is dead when all that's changing is that they're actually expected to throw patches back upstream for compatibility. In other words, they're being held to the common courtesy most code forks already do. As far as I know all the TPVs have always been more than happy for LL to incorporate their changes, and have been willing to assist in the incorporation. If LL has a good reason for not implementing a feature (e.g. server load) I am sure that the TPV devs would leave it alone or amend it until LL were happy. The issue here is that if LL does not like that a feature for any reason at all ('not enough staff to implement', 'not our priority', 'we do not think it would be popular') it will not be possible to add it to any third party viewer.

https://wiki.secondlife.com/wiki/Linden_Lab_Official:Account_Security

I just don't think that making any change (unless it is an urgent security fix which this isn't) is wise unless people have had a chance to test it on the RC channels. Nothing 'should' happen, but there are all sorts of weird tie-ins in SL that can get messed up by the simplest changes.

At the TPV Developers Meeting it was stated that the required rollout to main grid and RC versions would take place this week - it actually appears to be the switching off of the texture files that announce what viewer a user is using.

I understand that this fix is planned to be rolled out to both the main grid and RCs this week. Could I please ask that it is just rolled out to the RC channels this week so that any other systems that may be affected can be tested for a week before it hits the main grid?

This depends on how tablets develop. It may be possible that a powerful Windows 8 based tablet could run SL, but rather slowly.

Cummere Mayo wrote: 2) What counts as the latest released Linden Lab viewer? Do the Snowstorm and Beta viewers count as released? The latest released viewer is defined by LL as the 'full release' viewer (at time of writing 3.2.8) - so Beta, Snowstorm and project viewers are not applicable. And I think you mean TPV unless we really have a viewer of Textured Vegetable Protein. :catwink:

If LL were starting now with Second Life they would undoubtedly make some changes to the basic game engine, but really it does pretty well for an engine that has to work with changing objects produced in non-optimal ways, largely by people who know little about optimisation. The idea of pre-downloading regions is something that others have raised before, also I think better caching would help - LL are looking at a few things now, so maybe these are among them. Second Life already uses the state-of-the-art Havok physics engine, used by many modern games, and will soon be using Havok AI for pathfinding as part of the implementation of NPCs and other goodies that are based around the ideas in Linden Realms. Second Life's graphics may not match the best MMOs but can still be tuned to be pretty impressive, and are way ahead of most other social and creative games and at least match those in games produced using Unity. Hopefully these changes will help towards improving quidditch and other games in Second Life.

Loki Eliot wrote: Well maybe that can be proven by turning Mesh Rendering off inDebug and see if that makes a difference. Which i just did and saw no difference, so i dont believe Mesh is the issue. They added in a new rendering pipeline with the arrival of mesh - switching off mesh rendering doesn't remove that pipeline, there is no way to remove it.

Since Mesh was integrated into the viewer my tests have also shown that fps rates have become slower. It does seem that the mesh rendering stream is somewhat slower.

I know there are already many people on here who already like the six colourful skin options provided by StarLight for the standard Viewer. Recently StarLight has added the option to easily customise the main colours you use in the UI using two new themes 'Custom Light' and 'Custom Dark'. See examples here, but it's up to your own taste what colours you choose. You just add the skins to the standard Second Life Viewer using either the standard download (for all OSs) or the Windows Easy Installer. Find the downloads and more details of the additional features StarLight provides here. StarLight is provided to make your SL experience more enjoyable and provides some of the features that residents have liked in third-party viewers (TPVs) without the need to switch viewers. Even after you install StarLight the standard skin remains available, and you can remove all traces of StarLight by re-installing the Viewer. A version of StarLight is provided for every official Viewer full and beta release. Enjoy! :smileyhappy:

Theresa Tennyson wrote: After testing on my viewer (and breaking it the same way) I found a JIRA that says that due to a glitch in how the menu is set up the point the button to "affect movement" responds to when clicked isn't actually on the button itself. Move your mouse around in the area until the button highlights and then you can click that point. I found it near the middle of the word "movement" in the button description but apparently it depends on screen size. Supposed to be fixed in 3.2.8. I've just checked the latest 3.2.8 dev version and it is still not fixed.

Have you got 'single click to walk' turned on? It is set to be normal behaviour in V3 viewers and can mean you walking off into the sunset.

As this appears to be a Firestorm issue it might be best to contact Phoenix and Firestorm support.

I suggest you try logging into your account on another machine - that will determine if it is account-related.

I have to disagree with you Nalates - GPU and CPU are important - in my experience GPU makes the biggest difference, running an Intel dual core with an aged Nvidia 8600GT is still a good mix, and an Nvidia Ion on any netbook certainly makes a vast difference. But you do have to tune the rest of your system to take advantage of it - I feel this is one reaon why Hamlet gets such lousy performance from his Alienware laptop.

There are a number of JIRAs associated with this - all just sat there doing nothing. This seems the most appropriate - https://jira.secondlife.com/browse/VWR-27642.

Blackie Lubitsch wrote: Thanks. It doesn't have to be the latest and greatest version. But a decently recent version preferably. The link you gave has no downloads yet, guess it's still building. I think I will try if not for nothing else but to check if it fixes this problem... It appears the auto-build has broken again. There is the previous working version (that has built) at http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/davep_shining-fixes/rev/245264/index.html.

I suggest you contact support and file a ticket under Linden Home category. If you tried raising a JIRA they would probably just tell you to do that anyway.

The latest shining-fixes branch of the official development viewer is addressing the openGL graphics driver issue. If you really want the latest viewer then I suggest you try it: http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/davep_shining-fixes/latest.html though remember that as it is still being worked on it is not an officially supported viewer.

I believe that prior to Server 1.40 the limit was 32 prims with each seated avatar counting as 1 towards that total. Since 1.40 the avatars no longer are counted. Unless there has been a more recent change?

The trick that Simerion describes only works if you are using the Firestorm Beta Viewer - don't know why, but that viewer seems to be affected in that way.

Or you could use the StarLight viewer skins for a smaller camera and lots more. See this comparison of the standard and StarLight camera controls:

On the top right of that page there is a section entitled 'People'. To 'vote' and 'watch' this issue click on those words on that section.

Unfortunately what Tristizia suggests is only available if you use the StarLight skin. If you are using the unmodified Viewer you will have to look at the Debug Settings which you can get to via the 'Advanced' menu. The settings that you have to set to false are ShowHoverTips, ShowAllHoverTip and ShowLandHoverTip. LL sadly do not like to make such useful settings obvious.