Showing posts with label Viewer. Show all posts
Showing posts with label Viewer. Show all posts

Thursday, April 12, 2018

Singularity viewer DPI aware




The latest release of Singularity Viewer is now Windows DPI aware.


This means that instead of having to scale the fonts and user interface like you currently do on all viewers, Singularity automatically picks up your font scaling preferences from Windows.

Because I had my (settings) User Interface set to 1.050 (instead of default 1.0) and had  (Debug) FontScreenSize set to 106 (instead of the default 96), when I first ran the new version, I experienced a much bigger interface than I would usually expect.

However on reverting both of these settings to their default, I am pleasantly surprised to see that Singularity now matches my Windows settings (of 105%) exactly.

This further means that any changes I make in Windows will now automatically be carried forward to my viewer!

If for any reason you do not wish to avail yourself of this feature and wish to carry on using your manually tweaked UI and Font settings, you can do this by selecting Override high DPI scaling in the properties box that launches the viewer.

However, I recommend you try the new scaling first.  It's impressive.

Singularity viewer remains our favorite viewer for Laptops, thanks to its lighter than average footprint and quicker performance when compared to other viewers running on laptops.

For more information about Singularity viewer and the settings we use, see (half way down) the Resources page here

Thursday, March 22, 2018

Lost your Voice?



An interesting tip from the Firestorm people..

For those who find when they login, that voice will not work for them and subsequently have to relog multiple times:

Firestorm suggests disabling voice by going to settings <CTRL+P > <sound and media> <voice> and unticking Voice, as the last thing you do (when voice has been working) before you logout.

When you login, wait until you are rezzed, then do the same process again in reverse, this time enabling voice. Voice should then work.

So.. Does it work, because if so, in theory, it should work on all viewers?

Please comment below (anonymously if you wish) and tell us if this is a successful workaround (or not).

Wednesday, January 17, 2018

Lab releases native 64-bit viewer



Linden Lab has today released their first viewer to be built as a 64-bit application for Windows and Mac.

The use of 64-bit architecture gives much more memory available to application than ever before and offers a more stable experience with significantly fewer crashes.

The viewer will automatically patch its updates via an additional executable SL_Launcher.exe  ensuring you have the latest version, without the need for fresh installations.  It also downloads the specific best version for your operating system and graphics.  For example, if you are still running a 32-bit OS then the correct version of the viewer will automatically install for you.

To see the full story about this new viewer see the blog by Oz Linden

Sunday, September 04, 2016

Sudden Frame Rate Drops (KB3176938)




Updated 14th September (notes at bottom)

Finding your frame rate inexplicably goes from whatever is normal to about 2 frames a second?

Well you can relax to an extent, there is nothing wrong with your settings and you are not being griefed.

But you are a Windows 10 Anniversary user, and you have the KB3176938 update and it installed around 1st September. This is the cause of your problems.



This is not simply a Second Life related problem, this issue is common to all OpenGL rendered applications, including D&D Online, Runescape, and Xplane, with emerging reports from the Minecraft community.

The problem occurs when any other application steals focus from your viewer such as a web browser or going to your desktop or minimizing the SL viewer.  The SL viewer then fails to regain foreground priority until your relog.   Sometimes it can take an hour for this problem to show itself, sometimes just a few minutes.

Linden Lab are aware of the issue, and their developers are actively pursuing a resolution for the problem.  However, at the time of writing this, the only workaround they can suggest is to consider uninstalling the hotfix patch from Microsoft.

If you cannot wait for a resolution to this, which now seems likely to be a further fix from Microsoft, and you are feeling brave, here is a guide to removing updates:  http://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/

There is also a thread to follow on the Microsoft site, specific to this issue.  Although it says it affects Firestorm, the Lab confirms it is all viewers with this update:  severe performance issues on Firestorm viewer

You can also follow the issue on the Firestorm Jira: http://jira.phoenixviewer.com/browse/FIRE-20034

There is now a LL JIRA for this issue.  https://jira.secondlife.com/browse/BUG-37795



extra note:
Please be aware that whilst the workaround of uninstalling KB3176938 does solve the framerate issue, if like me, you have always had Cortana disabled, the removal will of KB3176938 will  trigger it to become activated.

One of the 'features' of the Anniversary update was to remove the "off" switch for Cortana and once activated, it cannot be turned off again without hacking the registry.


14th September

If you removed KB3176938 alas the frame rate problem returns on the update KB3176938 released last night.  The patch is cumulative, meaning that it gives you all the updates to date.  If you are therefore missing KB3176938 because you removed it, it will be included in the patch from last night.

You can follow this direct link to the MS trouble-shooter which allows you to Show or Hide updates from your PC:   http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab

You can run the troubleshooter and uninstall the patches as described here: http://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/

As previously explained, unrolling the updates will enable Cortana if you previously had it disabled, because a 'feature' of the Anniversary Update was to remove your ability to turn it off.

However by following this Registry Edit which I can confirm works as I have done it myself, will turn Cortana off in Windows 10 Anniversary.   Every caution should be taken when editing the registry.  Check and double check you have made any alterations correctly and back up your registry before meddling with it!  https://www.youtube.com/watch?v=iW1heCjMe3w