This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
fuss:metaverse_viewer [2014/07/16 18:02] – [Decreasing Viewer Loading Times] office | fuss:metaverse_viewer [2023/05/27 07:37] (current) – [Snowglobe] office | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Copying Vectors ====== | ||
+ | {{ fuss_metaverse_viewer_copying_vectors.png? | ||
+ | |||
+ | Copying vectors can be done by right-clicking an object, selecting the '' | ||
+ | |||
+ | ====== Printing Texture Information (Including Face Number) ====== | ||
+ | |||
+ | The shortcut to print a texture info is: | ||
+ | < | ||
+ | |||
+ | This can be accessed from the menu as well, in Viewer 2+, Develop-> | ||
+ | |||
+ | ====== Decreasing Viewer Loading Times ====== | ||
+ | |||
+ | After some testing, we consider this light-speed rezzing... It really blasts all other methods away. | ||
+ | |||
+ | Some *nix flavors, as well as Windows, have options for creating (mounting) a drive that represents a slice of your RAM. Consider, if you have memory to spare, offshoring the entire cache to RAM. There may be solutions around that would offer safely mounting and unmounting the drive by writing the cache files to harddrive after shutting down the viewer. This would have the effect that all your transactions are made directly from RAM, which would offer an incredible speed compared to hard storage. | ||
+ | |||
+ | If you are on Mac, Snow Leopard onwards, try the following in a Terminal: | ||
+ | |||
+ | <code bash> | ||
+ | imp:~noob$ diskutil erasevolume HFS+ " | ||
+ | </ | ||
+ | which will create a new ram-disk of 1GB size. | ||
+ | |||
+ | You can check by issuing the command in a terminal ''' | ||
+ | <code bash> | ||
+ | imp:~noob$ df -h | ||
+ | Filesystem | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | Next, configure your cache to write to that folder: | ||
+ | |||
+ | {{ fuss_metaverse_viewer_cache_settings.png? | ||
+ | |||
+ | * Based on the former, how about running the entire viewer in RAM. The viewer itself is only a couple 100MB in file-size. The cache, Imprudence' | ||
+ | |||
+ | Keep in mind that by using a RAM-disk, whenever you restart your machine, the cache will be purged. If you want to take this to the next level, consider a commercial/ | ||
+ | |||
+ | ====== Hide the User Interface ====== | ||
+ | |||
+ | < | ||
+ | |||
+ | ====== Using the Viewer AO ====== | ||
+ | |||
+ | Third party viewers, in particular, those that have forked off Snowglobe have a built-in AO that can be enabled via the options and allow an avatar to substitute in-world AOs for viewer-based AOs. | ||
+ | |||
+ | The main difference between the two is that in-world AOs rely on scripts that run server-side on the region that the avatar is currently occupying such that they are less prone to lag that would affect the viewer whilst viewer-based AOs run on the game client (the viewer) such that lag affecting the viewer will make the avatar animations lag. | ||
+ | |||
+ | On the other hand, viewer-based AOs reduce the overall lag to the server since the animations are triggered by the viewer directly without having any active scripts running. | ||
+ | |||
+ | Perhaps the easiest way to activate the viewer-based AO is to go to the debug settings by following the menu items '' | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | and enabling them by toggling the '' | ||
+ | |||
+ | The toolbar should now have a button named '' | ||
+ | |||
+ | Once the notecard is configured, it can be dropped on the interface and then by pressing the '' | ||
+ | |||
+ | ====== Solving the Local Typing Issue with Viewer AOs ====== | ||
+ | |||
+ | One of the problems with the built-in viewer AO is that the typing animation will override the "Play typing animation when chatting" | ||
+ | |||
+ | Unfortunately, | ||
+ | |||
+ | A workaround is to load the debug settings by following the menu items '' | ||
+ | |||
+ | * '' | ||
+ | |||
+ | and then click on the '' | ||
+ | |||
+ | {{fuss: | ||
+ | |||
+ | If everything was done correctly, then the UI to configure the viewer AO should reflect the change and the '' | ||
+ | |||
+ | ====== Aspect Ratios for All Profile-Related Images ====== | ||
+ | |||
+ | Textures uploaded in SecondLife for the purpose of becoming part of the avatar' | ||
+ | |||
+ | ===== Snowglobe ===== | ||
+ | |||
+ | * Search > All for " | ||
+ | * Search > Places and Classified tabs – $\approx7: | ||
+ | * Search > Land tab – $\approx7: | ||
+ | * Profile > 2nd Life tab – $\approx4: | ||
+ | * Profile > Picks tab – $16:9$ ('' | ||
+ | * Profile > 1st Life tab – $1:1$ ('' | ||
+ | * Profile > Classifieds tab – $\approx3: | ||
+ | * Profile > Web tab – $1:1$ ('' | ||
+ | * About Land > Options tab – $\approx3: | ||
+ | * Group Information > General tab’s "Group Insignia" | ||
+ | * A scrollbar uses 15 pixels on the right-hand side. | ||
+ | |||
+ | ===== Snowstorm ===== | ||
+ | |||
+ | * Search > Classifieds thumbnail – $\approx3: | ||
+ | * Search > Classifieds expanded – $\approx4: | ||
+ | * Search > Classifieds expanded > More Info – native aspect ratio | ||
+ | * Search > Destination Guide thumbnail – $\approx3: | ||
+ | * Search > Destination Guide expanded – $\approx4: | ||
+ | * Search > People – $1:1$ ('' | ||
+ | * Search > Places expanded $\approx4: | ||
+ | * Place Profile – $\approx3: | ||
+ | * About Land > Options tab – $\approx4: | ||
+ | * Profile > Picture – native aspect ratio; thumbnail cropped to '' | ||
+ | * Profile > Real world picture – native aspect ratio; thumbnail cropped to '' | ||
+ | * Profile > Picks thumbnail – $4:3$ ('' | ||
+ | * Profile > Pick expanded – $4:3$ ('' |