![how to use sl cache viewer how to use sl cache viewer](http://slcacheviewer.com/img/image_dialog.png)
- #HOW TO USE SL CACHE VIEWER MAC OS X#
- #HOW TO USE SL CACHE VIEWER INSTALL#
- #HOW TO USE SL CACHE VIEWER SKIN#
- #HOW TO USE SL CACHE VIEWER UPGRADE#
- #HOW TO USE SL CACHE VIEWER CODE#
Then Launched Firestorm (FS) and took a couple. I launched Black Dragon (BD) and took a couple of pictures, see below. The video did get me looking and comparing Black Dragon and Firestorm. I don’t even try to make video tutorials when I am sick. Luca The Guide, the author, was ill the day she made the video. The video (4 min) I found has horrible audio. The thing they were doing is getting hair shadows to render well on the avatar face. I recently saw a video about getting Firestorm Viewer’s shadows to look as good as Black Dragon’s shadows. This makes it so easy to fix you could add it to your first steps of troubleshooting. Poof the problem bridge is turned into free electrons to evaporate into the valley of lost bits. Click Avatar->Avatar Health->Recreate LSL Bridge. Now there is a BUTTON! Yay! Well… more a menu command than button, but you get the idea. Then it can be a pain to fix the bridge… and often a headache figuring out just what the problem is. The viewer is smart enough to resolve most problems on its own when something goes wrong with the bridge. Also, the general flakiness of a connection to a virtual world can cause problems with the bridge. The techy details are here: Firestorm Bridge.Īs one bounces between viewers, like I do, one can run into problems. Basically, it gives the Firestorm viewer more capabilities. It provides an interface between in-world scripts and the viewer. The bridge is an attachment the viewer puts on your avatar. Posted in Firestorm, Second Life, Viewers. My four cores are all carrying about the same load but the overall use is about 50%, which is similar to past versions. There are 20 to 30+ Firestorm threads running at anyone time. So, detecting a slowing or a speed-up due to the new multiple threads is tricky. That is what I experience… sometimes… There are some oddities happening when one teleports. I guessed that I might even see FPS dip while textures were decompressed as more CPU cycles would be getting used by the texture processes. I wouldn’t expect a higher FPS (Frames per Second) rate.
#HOW TO USE SL CACHE VIEWER UPGRADE#
Beta testers for Firestorm will have had the upgrade for some time.įrom the changes the FS Team has made, I would expect this viewer to be faster at rendering a scene. I think this is the first release of Firestorm that has this upgrade. I think this should only affect your first-time post-install-visits to places you frequent.Ī while ago the Firestorm Viewer was upgraded to use the simplified cache developed by the Lab.
#HOW TO USE SL CACHE VIEWER INSTALL#
One thing that can affect our perception is this install clears our viewer’s cache of downloaded content. Neither is precise and measurements are highly influenced by our location in the region, which way we are looking, our cache – when did we last visit, the region’s construction, and avatar occupancy. A few of us may now and then even time it.
![how to use sl cache viewer how to use sl cache viewer](https://blog.inf.ed.ac.uk/atate/files/2016/10/SL-Setup-to-Hide-Ground.jpg)
I suspect most of us hit a region and consider how long it takes for the place to render. But actually, measuring it well is quite complicated. The major effect of texture decompression is in scene render time. But since it has had little effect on Frames per Second numbers it doesn’t seem to have been a high priority to change. Decompressing is a task that has bottle-necked performance forever. The big thing is Firestorm’s viewer now uses multiple threads for decompressing textures. My experience is: this version is better. I just want to consider what people are experiencing based on what I can see and measure. I’m not going to repeat what she has already written. This version is covered in detail over on Inara’s blog here: Firestorm 6.4.21. So, I went and ran my tests, which I rate at one half-a-posterior. Which made me curious because that is NOT my impression. The thread Newest Firestorm version – lag monster popped up 8/4.
#HOW TO USE SL CACHE VIEWER CODE#
AcknowledgementsĬache parsing code based on PySLCacheDebugger.The Firestorm Viewer version 6.4.21 had been out for a bit now.
#HOW TO USE SL CACHE VIEWER MAC OS X#
RadTextureViewer uses WPF, which only works on Windows, but RadTextureViewer.Core is a DotNet Standard library using ReactiveUI so theoretically Linux and Mac OS X frontends could be created as well. The contents of your texture cache should load.ĭouble-clicking on a texture will open a save dialog for saving that texure to disk. If you click the button in the top right corner, a file dialog will open, and in the left sidebar of the dialog there will be a "Local" shortcut, which is helpful because AppData is a hidden directory. This will normall be C:\Users\you\AppData\Local\your_viewer\texturecache\texture.entries. Select the location of your texture.cache file. Do not use Rad Texture Viewer to steal content.
#HOW TO USE SL CACHE VIEWER SKIN#
Rad Texture Viewer can be used for making edits to skin or clothing textures you have purchased, but it can also be used to steal content. This is a cache browser for modern Second Life viewers.