| Author |
Message |
|
Lance Corrimal
Joined: 2009-03-18 09:32:02
Posts: 246
|
 I'm having the same issue a lot recently:
I log into SL, and I'm getting "clothing not in database" resp. "Body part not in database" for every single pice in my appearance that is not an attachment.
clearing cache and relogging doesn't help.
As soon as i log in with the original viewer, i can put on the outfit parts in question with no problems.
I relog to the CoolViewer and everything is fine for a while... then it starts again until i login once to the original viewer with a clean cache.
Anybody else experiencing this?
edit:
system specs:
Second Life 1.23.5 (3) Nov 1 2009 18:48:33 (Cool SL Viewer)
RestrainedLife viewer v1.22d (Cool SL Viewer v1.23.5.0)
Versionshinweise
Built with GCC version 40102
Sie befinden sich in 293917,7, 278830,5, 62,0 in Gwarl located at sim8861.agni.lindenlab.com (216.82.41.37:13006)
Second Life Server 1.34.0.140927
Versionshinweise
CPU: Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz
Memory: 1918 MB
OS Version: Linux 2.6.31.5-0.1-default #1 SMP 2009-10-26 15:49:03 +0100 i686
Graphics Card Vendor: Tungsten Graphics, Inc
Graphics Card: Mesa DRI Mobile Intel® GM45 Express Chipset GEM 20090712 2009Q2 RC3 x86/MMX/SSE2
OpenGL Version: 2.1 Mesa 7.6
libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3 c-ares/1.4.0
J2C Decoder Version: KDU
Audio Driver Version: (none)
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.28936 (Mozilla GRE version 1.8.1.18_0000000000)
Packets Lost: 34/8666 (0,4%)
|
| 2009-12-10 14:12:20 |
  
|
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51
Posts: 5550
|
I never encountered such a problem with the Cool SL Viewer, aside from asset server problems in SL itself, and I use it everyday for hours since over two years now... Beside, there is no change in the inventory code (when compared to the official viewer) that could possibly lead to caching failures (no change in the caching code).
My guess is that you could have a corrupted cache directory (like, physically corrupted on your disk, or logically in the partition): try using a different cache folder.
|
| 2009-12-10 19:10:27 |
|
|
|
Lance Corrimal
Joined: 2009-03-18 09:32:02
Posts: 246
|
Well, it happens on several different computers... I guess that rules out the "currupt filesystem structure" unless it actually gets corrupted by something in CV.
|
| 2009-12-11 11:06:36 |
|
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51
Posts: 5550
|
Please, provide proper info (log file), since apparently no one but you can reproduce this supposed bug...
|
| 2009-12-11 16:34:11 |
|
|
|
Lance Corrimal
Joined: 2009-03-18 09:32:02
Posts: 246
|
i just had that effect again. Logged out immediately, to be able to find it near the end of the log file. here's what i believe to be the relevant lines of the log:  | | | | Code: 2009-12-12T10:31:18Z INFO: idle: Kills on unknown objects: 33
2009-12-12T10:31:23Z INFO: idle: Kills on unknown objects: 79
2009-12-12T10:31:24Z INFO: display_stats: FPS: 33,50
2009-12-12T10:31:28Z INFO: idle: Kills on unknown objects: 130
2009-12-12T10:31:33Z INFO: idle: Kills on unknown objects: 127
2009-12-12T10:31:34Z INFO: display_stats: FPS: 31,90
2009-12-12T10:31:38Z INFO: idle: Kills on unknown objects: 31
2009-12-12T10:31:43Z INFO: idle: Kills on unknown objects: 31
2009-12-12T10:31:44Z INFO: display_stats: FPS: 35,00
2009-12-12T10:31:48Z INFO: idle: Kills on unknown objects: 81
2009-12-12T10:31:53Z INFO: idle: Kills on unknown objects: 679
2009-12-12T10:31:54Z INFO: display_stats: FPS: 14,90
2009-12-12T10:31:58Z INFO: idle: Kills on unknown objects: 680
2009-12-12T10:32:03Z INFO: idle: Kills on unknown objects: 309
2009-12-12T10:32:04Z INFO: display_stats: FPS: 13,60
2009-12-12T10:32:08Z INFO: idle: Kills on unknown objects: 32
2009-12-12T10:32:13Z INFO: idle: Kills on unknown objects: 32
2009-12-12T10:32:14Z INFO: display_stats: FPS: 26,70
2009-12-12T10:32:18Z INFO: _queueDataRequest: Starting transfer for 81aaa9dd-afeb-97e3-ce2f-f47aca8fa9b4
2009-12-12T10:32:18Z INFO: idle: Kills on unknown objects: 56
2009-12-12T10:32:18Z INFO: processTransferInfo: Receiving a928e044-7ef1-de11-9308-dbc2925dafbe, size 613 bytes
2009-12-12T10:32:18Z WARNING: importFile: Bad Wearable asset: bad parameter, #0
2009-12-12T10:32:18Z INFO: LLNotificationHistoryChannel::savePersistentNotifications: Saving open notifications to /home/mathias/.secondlife/user_settings/open_notifications.xml
2009-12-12T10:32:20Z WARNING: LLFunctorRegistry<boost::function<void ()(LLSD const&, LLSD const&), std::allocator<void> > >::getFunctor: tried to find 'FailedToFindWearable' in LLFunctorRegistry, but it wasn't there.
2009-12-12T10:32:20Z WARNING: LLFunctorRegistry<boost::function<void ()(LLSD const&, LLSD const&), std::allocator<void> > >::log_functor: log_functor called with payload: {}
2009-12-12T10:32:20Z INFO: LLNotificationHistoryChannel::savePersistentNotifications: Saving open notifications to /home/mathias/.secondlife/user_settings/open_notifications.xml
2009-12-12T10:32:22Z INFO: LLNotificationHistoryChannel::savePersistentNotifications: Saving open notifications to /home/mathias/.secondlife/user_settings/open_notifications.xml
2009-12-12T10:32:22Z WARNING: LLAlertDialog: Alert: Wirklich beenden?
2009-12-12T10:32:23Z INFO: requestQuit: requestQuit | | | | |
I believe the relevant part is this line: "Bad wearable asset: bad parameter, #0".
|
| 2009-12-12 10:38:43 |
|
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51
Posts: 5550
|
It looks like a corrupted item in your inventory... The difference between the Cool SL Viewer and "normal" viewers, is that the former automatically loads and caches the inventory in the background after you log in, so that inventory operations are faster afterwards (and more reliable, in the case of RestrainedLife). You could get the equivalent with a normal viewer by opening your inventory immediately after login and selecting the "Recent items" tab (which also got the effect to trigger the background loading of the full inventory list).
Should corrupted items be found while the inventory loads, then you would get the corresponding message, but it's not related to the viewer itself. To check, you may disable background inventory fetching in the Cool SL Viewer, by disabling RestrainedLife and unchecking the "Automatically fetch inventory in the background after login" option, in the "Cool features" tab of the Preferences floater. Note however that even if it "fixes" the errors (i.e. hides them), you'll get them as soon as you open the inventory folder containing the missing and/or corrupted items. You might therefore want Lindens to run their magic inventory repair script on your avatar...
|
| 2009-12-12 17:51:15 |
|
|
|
Lance Corrimal
Joined: 2009-03-18 09:32:02
Posts: 246
|
the point is this:
- as soon as i relog the item is not corrupt anymore
- it doesn't happen with a stock viewer
- the f*cking lindens won't give me the time of day about it anymore, i had them run their "magic database repair script" any number of times, by now all i get from them is "you're running a 3rd party viewer, go away."
|
| 2009-12-12 18:28:30 |
|
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51
Posts: 5550
|
That is why you must first reproduce the bug with the official viewer (just force the loading of your inventory via the selection of the "recent items" tab of the inventory floater) or find which item is corrupted/missing...
|
| 2009-12-12 19:57:44 |
|
|
|
Lance Corrimal
Joined: 2009-03-18 09:32:02
Posts: 246
|
AFAIK there is no "corrupt item"... When it happens it happens with any randomly chosen non-prim item, after that it happens for ANY non-prim item. relogging temporarily fixes it, and it has not happened so far with the regular viewer at all...
|
| 2009-12-14 09:11:50 |
|
|
|
Henri Beauchamp
Joined: 2009-03-17 18:42:51
Posts: 5550
|
I'm afraid I'm clueless about this problem you are encountering... You seem to be the only person with it...
Try reinstalling the viewer and try removing some of the library files from its lib/ directory that already exist on your system (thinking about libELFIO.so, for example...): this could be a library incompatibility issue...
You could also try to recompile the viewer from scratch on your system (by using the cmake-SL script provided on the site, you could even tell what system library should be used, instead of LL's provided ones), and see if it makes any difference...
Also, do you remember if these problems appeared just after you updated some packages (security fixes and such) on your system ?.. if yes, then the issue could be related with the corresponding update (try downgrading to the previous version of the package in this case).
Finally, make sure to disable RestrainedLife in the Cool SL Viewer and see if it makes any difference... Oh, and do make sure you got "eyes" and "hair" (not just prim hair) bodyparts worn on your avatar (it is possible to remove them via double-click or restrainedLife in the Cool SL Viewer, but used to result in a not fully rezzed avatar for others, and could possibly explain why your issue affects only wearables, even if I can't reproduce it myself here).
Yet another thing: do you encounter this problem with different avatars or with just one ?
|
| 2009-12-14 15:41:35 |
|
|
