Jump to content

Problem with crash in populated areas


You are about to reply to a thread that has been inactive for 1349 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Hello I been having this problem for few months since i got my new laptop. The problem is that every time am in a populated place like a club, event.. etc with more then 15-20 avatars my viewer crash. I try different viewers and settings but the same happen. If any  know any way to fix this pls

this is my computer info in firestorm

Firestorm 5.0.1 (52150) Dec 10 2016 12:21:33 (Firestorm-Release) with Havok support
Release Notes

You are at 215.5, 234.8, 3,001.1 in Atlantis City located at sim10499.agni.lindenlab.com (216.82.51.205:13001)
SLURL: http://maps.secondlife.com/secondlife/Atlantis City/215/235/3001
(global coordinates 155,351.0, 316,651.0, 3,001.1)
Second Life RC Magnum 17.03.10.324484
Release Notes

CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2591.99 MHz)
Memory: 16292 MB
OS Version: Microsoft Windows 10 64-bit (Build 14393)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 960M/PCIe/SSE2

Windows Graphics Driver Version: Unknown
OpenGL Version: 4.5.0 NVIDIA 378.92

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.47.0 OpenSSL/1.0.1h zlib/1.2.8
J2C Decoder Version: KDU v7.8
Audio Driver Version: FMOD Ex 4.44.61
LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32)
LibVLC Version: 2.2.4
Voice Server Version: Vivox 4.6.0017.22050

Settings mode: Firestorm
Viewer Skin: Firestorm (Grey)
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1.25
Draw distance: 32 m
Bandwidth: 1500 kbit/s
LOD factor: 1.5
Render quality: Low (1/7)
Advanced Lighting Model: No
Texture memory: 512 MB (1)
VFS (cache) creation time (UTC): 2017-3-2T17:8:5 
Built with MSVC version 1800
Packets Lost: 125/27,875 (0.4%)
March 20 2017 19:10:44 SLT

 

 

Link to comment
Share on other sites

Well you have a system very similar to mine and I have no issues on the same viewer. You have your draw distance turned down VERY low -- so low that if you move much the viewer "may" be having issues (I am not sure about this but others have talked about the need to "redraw" so just mentioning). You also have LOD set at 1.25 which is very low (mine is 2).

I can run several avatars at once and have no issue in crowded places.  Note that I have my Complexity Setting at 77 and I can lower as needed in crowded areas). 

My only suggestion would be to tune your Complexity "jelly doll" setting (the thing that renders folks in solid color rather than all (ALL) there gear).  The whole point of that recently introduced feature was to keep folks from crashing in crowded places.

It is difficult to say but you may very well be going to places where folks pay no attention to their render values. You don't really need to see EVERYONE in the club (well you might want to but then there is the crashing thing).

 

Not sure what your bandwidth is; mine is 20mbps which is 17.5 actual. 

 

 

 

Link to comment
Share on other sites

A 16 gb system running on LOW graphics, hmmm whats your setting for avatar imposters? turn that down, use aggressive jellydoll, turn advanced lighting back on, raise your draw distance a little, you shouldn't be having problems with that rig,  Oh, lower your bandwidth setting to 750-1000 maybe.
 

Link to comment
Share on other sites

My laptop has the same graphics card & processor as yours but I only have 8gb RAM & I don't suffer from this problem, unless I'm using a 32bit viewer.

I suspect your crashes are out of memory crashes if it only happens on busy regions.

Is there some reason you are using the 32bit version of Firestorm? All 32bit viewers are very prone to out of memory crashes - a 32bit viewer running on a 64bit system can only use a max of 4 gb memory before it will crash. In practice an out of memory crash will happen when the viewer is using ~ 3-3.5 gb memory as some of that memory is reserved for textures.

On a busy region with lots of blinged out avatars wearing high poly mesh, it's horribly easy to reach this kind of memory use.

Try switching to the 64bit version of Firestorm and see if this fixes the problem - choose the "For SL & Opensim 64bit" version here: http://www.firestormviewer.org/windows/

Link to comment
Share on other sites

  • 2 weeks later...

ty so much for the help now i dont crash with the 64bit version of firestorm and i change some of the settings... 

here is my settings now

Firestorm 5.0.1 (52150) Dec 10 2016 14:44:37 (Firestorm-Releasex64) with OpenSimulator support
Release Notes

You are at 227.9, 53.1, 2,501.3 in Tears Isle located at sim10258.agni.lindenlab.com (216.82.49.180:13016)
SLURL: http://maps.secondlife.com/secondlife/Tears Isle/228/53/2501
(global coordinates 224,484.0, 247,861.0, 2,501.3)
Second Life Server 17.03.10.324484
Release Notes

CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (2592 MHz)
Memory: 16292 MB
OS Version: Microsoft Windows 10 64-bit (Build 14393)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 960M/PCIe/SSE2

Windows Graphics Driver Version: 20.19.0015.4454
OpenGL Version: 4.5.0 NVIDIA 378.92

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.47.0 OpenSSL/1.0.1i zlib/1.2.8
J2C Decoder Version: KDU v7.8
Audio Driver Version: FMOD Ex 4.44.61
LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32)
LibVLC Version: 2.2.4
Voice Server Version: Vivox 4.6.0017.22050

Settings mode: Firestorm
Viewer Skin: Firestorm (Dark)
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1.25
Draw distance: 128 m
Bandwidth: 1500 kbit/s
LOD factor: 4
Render quality: Medium (3/7)
Advanced Lighting Model: Yes
Texture memory: 1024 MB (1)
VFS (cache) creation time (UTC): 2017-3-21T15:56:2 
Built with MSVC version 1800
Packets Lost: 28/375,933 (0.0%)
April 02 2017 19:37:06 SLT

 

ty again :D

  • Like 1
Link to comment
Share on other sites

  • 3 years later...
You are about to reply to a thread that has been inactive for 1349 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...