Jaylinbridges

I'm going to agree more with @Flea Yatsenko after taking a second look at the OP pics. It does looks like her laptop was not rezzing much of the scenery at all, and the white webs were in the early glow stage of rezzing. This can happen when your computer is overloaded, but in her case it persisted instead of clearing up. I went back and took a close up pic of the first shop on the left, with a decent EEP, not the Shared Environment of the region. Compare that and the surroundings with her washed out pic with about 50% of the objects missing and texture colors not even starting to rez. (And I was in the correct region, but the shared environment was blacking out the inside of the shops since I was outside of their local parcel EEP. )

I agree something was set wrong in phototools. You should not get effects like that just because your GPU is maxed out. I visited the same region (Dahlia) and using the region shared environment EEP, and your settings, get the same view as Scylla. Changing my graphics settings did not make any noticeable difference. I wonder if the glare was from unrezzed spider webs?

Your laptop should be playable for normal activity. You should expect around 60 fps in an empty skybox and 20 -30 fps in the usual club with 20 avatars. Do not listen to those that have no experience with that level of machine - because they are gamers and assume everyone needs AAA game experience, or they just listen to what others here say and repeat. SL is not a game and for the most part not much is going on. If you can reach 30 fps you won't be missing anything in SL. IF you can afford to buy/build a real gaming system, then of course go at least mid range CPU and separate GPU with at least 8 GB VRAM, and at least 16GB RAM. However, every day my partner gets along quite nicely in SL with this AMD Ryzen 5 4500U with Radeon Graphics and 8GB RAM laptop. She bought it new in 2021 and it is a 2020 released product. It has less CPU and memory than yours, yet she works in clubs, hosts, and is not limited by the lag. She crashes only because her local rural cable internet supplier goes down regularly. If her wireless cable stays up, she stays logged, sometime for 3 days at a time It is called a "gaming laptop" by HP, which is rather optimistic, but more accurate than saying it can't run SL at all, which I can see every day is not true. Here's a review about one: https://www.techspot.com/review/2045-amd-ryzen-4500u/ Here are her system specs from FS Help/About menu: Firestorm 7.1.9 (74745) Jun 20 2024 10:49:53 (64bit / SSE2) (Firestorm-Releasex64) with Havok support Release Notes CPU: AMD Ryzen 5 4500U with Radeon Graphics (2370.55 MHz) Memory: 7542 MB (Used: 1309 MB) Concurrency: 6 OS Version: Microsoft Windows 11 64-bit (Build 22621.3737) Graphics Card Vendor: ATI Technologies Inc. Graphics Card: AMD Radeon(TM) Graphics Graphics Card Memory: 512 MB Graphics Card Memory (Detected): 512 MB Graphics Card Memory (Budget): UnlimitedWindows Graphics Driver Version: 30.0.14046.0 OpenGL Version: 4.6.14802 Core Profile Context 21.40.46 30.0.14046.0 Settings mode: Firestorm Viewer Skin: Vintage (Classic) Window size: 1920x991 px Font Used: Deja Vu (96 dpi) Font Size Adjustment: 0 pt UI Scaling: 1 Draw distance: 64 m Bandwidth: 1500 kbit/s LOD factor: 3 Render quality: High (5/7) Disk cache: Max size 9984.0 MB (1.2% used) Built with MSVC version 1940 Packets Lost: 20/808,089 (0.0%) July 09 2024 22:54:20 SLT I am pushing her to upgrade the RAM to 32 GB, but that's about all that should be done if she used a PBR viewer. Of course a good bottom cooling fan system and regular cleaning of the air passages is also necessary. She survives by simply setting the Performance Slider to between Mid and High, but turning on Transparent Water. In Hardware Settings, leave at default with Vsync Off. And in Rendering restrict texture rendering resolution to 512 pixels, and Limit Frame rate to 35 fps. Oh and since she is using the non-PBR, turn ALM ON, because her fps is still fine with ALM ON, and she can see the BP materials. We have not found enough PBR builds to turn on any PBR shiny features so far. Her laptop can handle the FS PBR viewers with graphics features turned down as above, with no loss in FPS. But with only 8GB RAM and integrated graphics chip, PBR will cause texture rezzing issues with 8GB RAM. If she has to stay on pre-PBR she will not miss anything important to her. That is what the folks promoting PBR hate to hear - not everyone is in SL to be a graphics critic.

Alt + Shift + R to refresh attachments. It is an increasing problem. My partner TPed to the same club she's been at daily, and lost her hair for everyone but her. That was a problem about 3 years ago. She was still on non-PBR FS viewer (which seems to make no difference.) So SL is slowly moving backwards with all this new shiny stuff.

A white screen just means the program is still loading and is not a a "white screen of death". The first time you start a new update, depending on the state of your CPU cache and the FS cache, it can take up to 1 min to get to the login page. And sometimes with a new version, you actually log in and little rezzes while it should rezz in about 30 secs or less. You just close the program and relog. It works the second time around, and on successive logins. Even if you clear the FS cache, it still loads very quickly as in seconds if you have a reliable and fast internet connection. It's not important what Windoz and FS are thinking about when first introduced. It would help to know what OS you are using (version numbers too) and what FS Version you were using. Also what is your net connection, wired, wireless, packet loss etc. All of this in Help/About Firestorm/Info window/. And if you upgraded from an older FS version, did you do a clean install? Ask in the FS Support group. Nothing is wrong with the latest FS Release itself. Most have no issues at all with the new Release.

When you install a new NVIDIA driver, do your NVIDIA Windows Control Panel settings also change? Could just be the new driver installs defaults that increase performance. Meaning the old driver with the correct defaults also will increase performance, and it's not some new driver magic at all.

because every link in this July feedback is now Server Error 500, just a reminder: In-world population stats haven't updated for four days. tracked animats Resident Viewers and in-world population meters are stuck at 39,122 users. The API for this info, https://api.secondlife.com/datafeeds/homepage.txt is returning inworld_updated_slt 2024-07-27 20:00:00 inworld 39122 Note the date. July 31, 2024 Activity Feed Sort by Newest first Tjay Wicken Any update for this one? Considering that this is a metric provided through an official API, I would expect something more than a tracked status, or at the very least some kind of estimate on when resolution can take place. · August 6, 2024 · Reply Maestro Linden Merged in a post: Avatars inworld count not updated properly Bavid Dailey I have an old avatar inworld counter that has been saying that there are 39122 avatars inworld for ages now. The script is mod, so I took a look and it scrapes a page at https://api.secondlife.com/datafeeds/homepage.txt and sure enough the last line always 39122. July 31, 2024 August 1, 2024 SL Feedback Thank you for bringing this to our attention. This issue has been previously reported and is being tracked. We have no estimate when it may be resolved, but please stay tuned for future updates. Your input is valuable, and we appreciate your patience. · July 31, 2024 · Reply SL Feedback Tracked: Issue tracked. We have no estimate when it may be implemented. Please see future updates here. · July 31, 2024 · Reply SL Feedback marked this post as tracked · July 31, 2024 · Reply

FWIW, I see no difference whether I set RenderGLMultiThreadedTextures to TRUE or FALSE in Win 10. Probably a hardware thing, that it helps some on WIndows with TRUE. It is an essential setting for most Macs though.

Just noticed you are running same driver I am for my GTX 1660 Super. It seems to be optimized for the older gen NVIDIA cards.

Well that's too bad, because I was going to set TextureMemory to 100GB. Other things I did to clear up the initial slow rezzing and grey textures was: Reboot Win10. Clear all FS caches. Restart 7.1.10, and all textures loaded quickly with no grey after about 20 secs of walking around to cam all the objects. I also whitelisted my cache files again, even though I had whitelisted them after I installed 7.1.10. My cache folders are separate from the AppData locations, and a new FS already knows where they are when I first startup - since I add the cache location in the Target in a shortcut, like so: "C:\Program Files\Firestorm-Releasex64\Firestorm-Releasex64.exe" --set InstallLanguage en --set CacheLocation I:\Win10PBRCache --set NewCacheLocation I:\Win10PBRCache Normally with all my beta testing, I've never had the slow texture rezz issue. So I blame it on WIn10 MS updates, or something...

Unless you delete the settings file, as in a clean install, some debug settings can carry over. The debug defaults for a new version do not override your old settings either. And if you used some older FS versions, the defaults are different than in 7.1.10. Because everyone seems to have a different version history, with different debug settings, you get these different reports from users. For instance - I had a FS version that set my max VRAM to 2048 MB. That set debug texturememory value to 2048. When I installed the latest 7.1.10 release, I had a lot of grey textures, rezzing very slowly. I checked debug and it still had 2048MB as the amount of memory to use for textures. My NVIDIA card has 6 GB of VRAM. The correct setting should be 0 = autodetect. Once I set that to where it should be, and relogged FS, textures all snapped right in. This was one of the performance improvements for this update. Some of these problems are cache related. Always set the caches to 19968 MB in preferences. And always clear your caches before installing a new version. Do not listen to anyone that says clearing your caches is a terrible idea. You might have to wait another 30 secs or so after clearing your cache, and start over with clean cache. We are not using dialup modems anymore, and the CDN fills up your cache in seconds, not minutes. It is also a good idea to move your cache file to another partition or drive. Caches can get very defragmented, slowing access time. At least use the Windows defragmenter to trim your SSD's.

https://api.secondlife.com/datafeeds/homepage.txt is hosted on AWS servers. So a server failure (cleaning lady unplugged the Linux desktop from 1992) can't be the cause. Entering just the IP# only sends (redirects) you to the SL Wiki page about their API.com services, the default for api.secondlife.com. Adding a folder to the url gives Server Error (500) as reported. Some employee at LL knows why this happens. But we don't have a need to know, so we can have fun with conspiracy theories until the numbers look better. The Wiki page on datafeeds: https://wiki.secondlife.com/wiki/Linden_Lab_Official:Live_Data_Feeds

This was obviously written by an AI program. A linden would not know about the Firestorm splash screen, but an AI bot would. Part of the AI's training is to read post's like Rowan's and conclude the stats failure is of no importance to anyone. Another inconsistency is the AI thinks reporting this issue will improve Second Life. The AI bot is very confused. The downtrend just before the failure is only a statistical fluke. Yep, that's the ticket.

How dare you be helpful on an SL forum! Smart ass remarks get more likes. Firestorm has a new Release out today, Firestorm Release 7.1.10 (75913). All PBR users on FS should upgrade. The old beta (75910) is no longer supported.

I am not testing performance with the PBR features, and basically run my PBR viewer to see BP textures. So with the shiny features all turned off, and only shadows on - I don't see much difference in the latest FS beta, and the previous FS alpha. The last alpha : Firestorm 7.1.9 (75794) Aug 18 2024 16:44:33 (64bit / SSE2) (Firestorm-Alphax64) with Havok support The new beta: Firestorm 7.1.10 (75843) Sep 1 2024 13:54:07 (64bit / SSE2) (Firestorm-Betax64) with Havok support No stuttering after all textures are loaded. No stuttering when swinging my cam 360 degrees, although fps drops during rapid cam rotation, but recovers fps in a few seconds. No long texture loading times but that depends on the region build. Some clubs are really terrible. The full region is owned by the club owner and they fill it up with script and texture heavy landscape and toys. On the latest Beta I have RenderGLMultiThreadedTextures set to the default of FALSE. When I set it to TRUE textures would load slightly faster on a new region, but I noticed some stuttering on cam rotation. This setting works more for Mac users. I have a 10 yr old CPU and motherboard, with a more modern GPU, all on a supercooled tower system. I throttle fps to 40, but if I turn off limiting, I run around 80 fps at my heavily landscaped and texture heavy home. Best feature for the new beta was default of turning off mirrors, since every time I would load up the older FS PBR, I had to wait about 30 seconds for mirrors to turn off after using my graphic presets, and the viewer would freeze while it turns off mirrors the first time. As long as the newer versions keep things the same or moving forward, I don't see any reason to keep testing performance. I am happy with what I am getting now. I usually run two instances of FS also, as my alt is busy doing business things. Those that want to run everything on Ultra settings and get 200 fps everywhere with PBR full on, can spend 10K on a system that might do that. I am not impressed with shiny objects myself. CPU: AMD Phenom(tm) II X4 965 Processor (3400.06 MHz) Memory: 16384 MB (Used: 2089 MB) Concurrency: 4 OS Version: Microsoft Windows 10 64-bit (Build 19045.4780) Graphics Card Vendor: NVIDIA Corporation Graphics Card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 Graphics Card Memory: 5980 MB Graphics Card Memory (Detected): 5980 MB Graphics Card Memory (Budget): UnlimitedWindows Graphics Driver Version: 31.0.15.3623 OpenGL Version: 4.6.0 NVIDIA 536.23 Settings mode: Phoenix Viewer Skin: StarLight (Original Teal) Window size: 1920x1017 px Font Used: Ubuntu Font Family (96 dpi) Font Size Adjustment: 0 pt UI Scaling: 1.15 Draw distance: 128 m Bandwidth: 2000 kbit/s LOD factor: 3.5 Render quality: High-Ultra (6/7) Disk cache: Max size 19968.0 MB (36.2% used) Built with MSVC version 1941 Packets Lost: 198/1,154,082 (0.0%) September 10 2024 05:25:23 SLT ---------------------------------------------------------------------------------- To stay on topic - I also have tried the latest SL viewer beta: Second Life Release 7.1.10.10708851543 (64bit) with supposed better performance than FS. I noticed a slight increase in fps, about 5 fps increase, from 75 to 80 fps. Also 5% more GPU utilization, and about 10% less CPU utilization, with less CPU spiking to 100% . As far as it feeling any different, nothing at all. I also have some sculptie rocks on my home build, a stream bed border, that FS refuses to rezz until I click where they are. On the SL Viewer the rocks always rezz right in like everything else. So there's that.