Search the Community
Showing results for tags 'default viewer'.
-
Due to Firestorm being extremely buggy and laggy on macOS as of late (I'm guessing it's due to all the latest server-side changes, or something like that, and Firestorm is not on par with Linden Lab's latest performance improvements - But I'm eagerly awaiting an update, as I love Firestorm's features), I've been using the Default Viewer a lot lately - It has epic performance in comparison to TPV's (Nearly double the FPS, and zero lock-ups or crashes. on Firestorm, by comparison, I have to completely disable ALM for barely tolerable performance.) but unfortunately, despite the great over-all performance of the default viewer, it falls short when it comes to texture rendering (probably due to its hard-coded 512mb texture memory limit). I'm attempting to take pictures for various projects including snapshots for my new Second Life related Blog but It's a real struggle on the default viewer with textures going blurry at random. I would be focussed in on the perfect shot and then suddenly, one of the objects in the scene would go blurry right as I'm about to take a snapshot. On rare occasions, I manage to catch everything in full resolution for a second. It's mostly a waiting game, sitting around for 10-15 minutes for every snapshot, waiting and hoping for all objects in the scene to render at full resolution at the same time, and hopefully hitting the screenshot button at the right moment, before something goes blurry again. Sometimes it happens, other times it feels like it's never going to happen. Is this a macOS-only issue? Or is this a general Default Second Life Viewer issue? Or is this a me/my system issue? I've tried to increase the texture memory of the viewer through the debug settings to the same value that I use when running Firestorm (1024), and I do not experience this problem on Firestorm, but due to FS's recent performance issues, I'm sticking to the Default Viewer until there's (hopefully) a Firestorm update that fixes the performance and stability issues. Regardless of what value I enter in the default viewer's texture memory debug setting, it always defaults back to a maximum of 512. Now I'm wondering, is there a way to force it to a higher value? Or is there another debug setting that I'm unaware of, that I could change, to stop textures from constantly going in-and-out of focus? There must be a way around this. Please help! Here are my system (potato?) specs for reference: (iMac 4K, Late-2017 - I'm still saving up for a new M1X MacBook Pro)
-
Just got the newest update on the default viewer, for whatever reason my arrow keys, wasd, the numpad and even my mouse don't actually make me walk or move at all. Interestingly, I can still control the camera just fine with my mouse/arrow keys and with my xbox one controller. The keys that would otherwise move me to the side by default, just make me rotate in place. It's not a connection issue, and I've cleared my cache. Not entirely sure what's going on, but I know it's not me. Even the onscreen movement prompts don't really function aside from the left and right buttons which spin me right round, baby right round, and still do bugger all besides that.