Jump to content

Sarah21 Baily

Resident
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm running the latest Firestorm, and I've narrowed the issue down to texture loading. Ever since the new "rendering subsystem" with the 6.6.2 codebase, If I cam around to areas where many people have unloaded textures, my framerate drops to a single frame every 3-5 seconds until the textures are loaded, making the viewer almost unusable to the point typing and moving are impossible. At times turning on transparency (CTRL-ALT-T) has actually caused such a long freeze-up (over 30 seconds) that my viewer crashed. This issue does not happen when I drop Avatar Complexity below 150,000... but over half the avatars are jellydolled. Vsync does not affect this whatsoever. This happens at all graphics levels, including the absolute lowest possible setting with all shading and atmospheric rendering off. Please note that I did not have this issue AT ALL with 6.5.6.66221 whatsoever. The latest versions of the viewer with the "improved" rendering engine are what cause this. I am running an HP EliteDesk 800 from 2014 with a MSI GTX1650LP graphics card. Needless to say, I'm quite upset 6.5.6.66221 was blocked. I suspect there is zero fix to this issue, which leaves my options as needlessly spending $1000s upgrading to a new system entirely, or simply no longer using SL. Is there a way to get LL to unblock just this one viewer? Or am I stuck with this problem until I upgrade my system?
  2. Anyone got a clue what's going on? I upgraded Firestorm from 6.5.6.66221 to the latest version recently and I've had nothing but problems with stuttering and freeze-ups. If avatars are loading, my FPS stutters. If I cam around, my FPS stutters. If I turn on/off transparency, the viewer completely freezes up for 8 entire seconds. 6.5 never did this. Does it have to do with the new rendering subsystem? And if so, how do I disable it in the new Firestorm? Should I revert back to 6.5?
  3. I run a large venue on a mostly residential private-owned sim. As of the past two or three weeks, LL has been restarting our sim at random times, one of which was during an event we were hosting. I was given an explanation that described how a simulator may be prone to crashing when it approaches stored memory capacity, and that LL employees may restart sims that near this limit to mitigate crashes. I was not given any explanation what this means, nor was I given any steps to take to eliminate this problem aside from "restart more frequently." I've not heard any other large venue owners complain about this problem, nor have I seen them require more than the single restart on Tuesdays to my knowledge. Does anyone have any idea what about my specific sim may be causing this? What can I do to reduce the sim's stored memory usage? Our sim uses just under 600MB of total memory from what I can see in the About Region tab.
  4. I believe I may have solved my own problem: It appears that Clearing Cache does NOT remove cached sounds, textures and images from C:\Documents and Settings\[username]\Local Settings\Application Data\SecondLife at all. I believe a corrupted file may have been to blame, probably in this folder. All seems to be in working order so far, after I deleted all instances of Phoenix Viewer out of the system registry and deleted all Second Life-related folders from Local Setings.
  5. Ever since the release of Phoenix 1.4, I've had issues with the default transparent texture not loading. The issue seems to be random and sometimes can be fixed by re-logging. However, such isn't always the case. And clearing cache does not necessarily fix the issue either. It is the only texture I have any issues loading. The problem can be rather annoying sometimes, as a good number of clothing items (such as shirts created on jacket layers) use the default transparent texture for the unused half of the layer. While humorous that I sometimes walk around with a gray butt, it's still slightly annoying to have to relog multiple times in a row until the texture finally loads. Disabling HTTP textures also does not help. It seems to be a very weird issue in the fact that this -one- texture is a problem. I have no issues loading any other textures whatsoever. Any ideas what may be causing the problem?
×
×
  • Create New...