![]() In the download notes it does say Dell notebooks are not supported. I have to use the drivers provided by Dell, as the ones from NVidia (selected for this specific chipset) say that they can not find supported hardware, and fail to install. It is a Dell Latitude D620 with the NVidia NVS 110M chipset. It should NOT have overheating issues as it was taken apart for cleaning recently and also has a good fan system under it. This happens with both stock SL and Catznip, and started around the time Server Side Appearance was deployed (I did get some crashed before but much more rarely).Ĭrashes seem to be hardware related, as another laptop with the same software runs fine. These are very rare special cases, something that needs to be so extremely specific, something probably not coming from the Viewer itself directly unless it is an infinite while/for loop that is skipped/broken out of when the Viewer detects that it has been disconnected, another thing i could think of would be your log files, you might want to check your log files when that happens, the Viewer might be spamming an incredible amount of log entries (we are talking hundreds of megabytes in a couple seconds, up to gigabytes of log data) which can cause the Viewer to stall to a point it doesn't recover until the situation is solved (e.g a disconnect breaking you out of whatever function or loop that is causing this spam).I have started getting regular crashes in busy places. I think the Viewer is recovering because its getting disconnected, thus breaking out and ending whatever it is that is causing the Viewer to freeze in the first place. ![]() ![]() But I had nothing suggested how to test that beyond the before-mention AV troubleshooting. I did have someone suggest in a Firestorm support chat that it might be hanging trying to access a cache or a log file. Different graphics cards, one AMD, one NVIDIA Issue even persisted after an unrelated OS reinstall Running viewer alone without other software running I am quite confident that the issue is NOT AV at this point) Making sure viewers are excluded from AV (Please note I have already gone through a session of AV related troubleshooting. This is a pretty beefy system, and I am no where near maxing out any resources when the viewer locks-up. This leads me to believe that this is not related to GPU drivers or similar. If I have two instance of the viewer running, only one will hang. ![]() I see no pattern to these random instances other than it happening more often on crowded regions. But it also happens when just hanging out on the grid. It does seem to happen more often when I open up dialog boxes such as user profiles, and especially the texture change window when changing textures on objects. Not sure if this actually is doing anything, but it at least feels like it is. I have tried opening another window and minimizing the hung window repeatedly. After a variable amount of time from a couple of seconds to a couple of minutes, it will come back, but often when it does it has been long enough that the simulator has not received communication from my viewer for long enough that the simulator terminates my login session, I guess thinking I DC'd. Viewer will at times hang, windows will report viewer as not responding. Storage viewers installed on: M.2 SSD 1TB GPU: RX 5700XT (Also happened under a GTX 970 as well) (Prior builds on both, don't remember numbers off top of head) Viewers also effected: Previous FS versions. I've been having an intermittent freezing issue that has been really annoying me for months.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |