Author |
Message |
GeoffEarnshaw
Joined: 2014-09-25 22:10:40 Posts: 135 Location: Colorado
|
Hello Henri Well I seem to be having issues, surprise I have been crashing today when trying to login and thats after I crashed when I was on the DN grid. Not sure what the issue is. I'm sure its something to do with my computer however. Because I tried FS and it crashed on me too and said I had some sort of hardware configure issue. Not sure what it meant by that. I haven't done any software upgrades to my computer in weeks. But I did just update the GeForce graphics driver just now and I still crashed when trying to login. I looked in the logs and not sure what its telling me. I was hoping if you could tell me what the log says in plain English. Here is my system info and log files. Also, I just checked the Windows Event Viewer after I just posted the above and saw this: Event 1000, Application Error Thank You! Geoff
|
2017-08-16 17:43:57 |
|
|
GeoffEarnshaw
Joined: 2014-09-25 22:10:40 Posts: 135 Location: Colorado
|
OK I might have fixed the issue. I had forgot the other day I enabled "Allow HTTP pipelining in OpenSim grids". I remember this just now and disabled it. So far I was able to login and haven't crashed yet! cross my fingers.
Geoff
|
2017-08-16 18:19:17 |
|
|
GeoffEarnshaw
Joined: 2014-09-25 22:10:40 Posts: 135 Location: Colorado
|
Never mind, had the same issue, but this time the log file grew to 98.6 MB Takes awhile to open this file. https://drive.google.com/open?id=0B9sV-iciXiMUU3dPTjc4V3F0TEkI think I might try the previous version of CLV. Geoff
|
2017-08-16 18:40:10 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
That setting is very unlikely to have anything to do with your crashes (I just logged in in Dream Nation with HTTP pipelining enabled and I did not crash), even if pipelining is probably not yet implemented in OpenSim grids. It could be a driver issue that got triggered by a specific object. Without the dump file (CoolVLViewer.dmp file, in the same directory as where the logs are stored), I cannot tell where the viewer crashed exactly. So, next time, please do provide this file in excess of the corresponding CoolVLViewer_NNNN.log file... EDIT: Yep, that's a (bunch of) crasher object(s), or invalid UDP messages sent by the sim... Try enabling the KillBogusObjects debug setting before logging in, and see what happens. Also, please, send me the grid coordinates (sim name) of the crash.
|
2017-08-16 18:42:34 |
|
|
GeoffEarnshaw
Joined: 2014-09-25 22:10:40 Posts: 135 Location: Colorado
|
Well I do not have current CoolVLViewer.dmp file for the crashes. Seems Windows 10 is automatically closing the viewer when it crashes. I did enable the KillBogusObjects debug and I am on for the time being. I also sent you a LM where the crashes where happening inworld. Geoff
|
2017-08-16 22:00:48 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
No, it closed it before it actually crashed (and it would probably not have crashed at all without Windoze's stupid assumption), probably as a result of graphics driver "freeze" or large delay in returning from a call... Please, provide the log. Well, I'm not crashing there, with KillBogusObjects enabled... However, I do see a massive slow down in the fps rate (from 50+ to 8-10fps !) when facing the lagoon with a 512m draw distance, from the LM point you gave me: on a weaker system than mine (Linux desktop PC with a 4.6GHz Core-i5 2500K and a 1.5GHz GPU/4GHz VRAM GTX 970), it could definitely bring your video card to its knees and look like a "problem" for that Mickey Mouse OS which is Windows... What is your draw distance ?
|
2017-08-16 23:10:24 |
|
|
GeoffEarnshaw
Joined: 2014-09-25 22:10:40 Posts: 135 Location: Colorado
|
OK, so here are the logs, including the not current *.dmp files I have in the logs folder. https://drive.google.com/open?id=0B9sV-iciXiMUZFdNcXhtMlhfdWcMy draw distance is set at 128m. My FPS is always between 5 and 15 fps. Jumps around a lot and It has always been that way and I figure its because of OpenSim. I do have a GTX 970M however. And it does appear that enabling the KillBogusObjects debug has worked. Thank you for helping me. Geoff
|
2017-08-17 01:12:30 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
Alas, this dump file does not correspond to the current version (v1.26.20.30), so it is of no use at all for me. That's pretty low... Well, mega regions are fps killers, but otherwise, OpenSim is the same as SL for fps rates... Which got about half the performances of a non-overclocked GTX 970... Mobile GPUs are not great performers, and neither are mobile CPUs... Keep it on: I'll make it the default for next release. It'd be interesting to know what are those bogus objects however, and to understand why they are bogus... You will find their UUID in the viewer logs, so you could tell about them to the sim owner.
|
2017-08-17 07:40:45 |
|
|
GeoffEarnshaw
Joined: 2014-09-25 22:10:40 Posts: 135 Location: Colorado
|
Hey Henri,
So the sim is not a mega region (varrigion) but a 256x256 sim. I basically the owner of the sim, well part owner. Almost everything you see I placed there. Never had any issues with any of the items in the past. But I am trying to identify the objects in the log, UUID in the search isn't having much success. However, we think there was an issue with the robust and asset server yesterday. They will be investigating the issue to see what happened, if there was an issue that is.
Geoff
|
2017-08-17 18:06:01 |
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 5550
|
The culprit items get derendered by the viewer when KillBogusObjects is TRUE, so they won't appear in the "Area search" floater...
|
2017-08-17 19:09:40 |
|
|