Re: the material texture error bug is real in Naboo
Posted: Thu Jan 12, 2023 2:02 am
Mike, the server delivered the correct assets to your viewer from the start and hasn't stopped doing so. The changes in how they appear are differences in the object data not in the assets data that the viewer used when rendering the object. It's the object data that tells the viewer which assets to use, specifically which textures assets are used by the mesh.
The viewer used the wrong object data initially in Naboo, you clicked it and that caused it to switch to using the correct object data immediately (according to your own report). Note that your viewer could not have been able to do so if it didn't already have the correct asset data cached already. At this point the viewer cached that correct object information and used it when you rezzed that object in SPACE FORCE. You teleported to your home, waited 5 minutes and returned to find the viewer using the old object data that it initially used in Naboo before you clicked the object. What changed is that the viewer, for whatever reason, stopped using the most up-to-date object data it cached just a few minutes earlier and switched to using the old object data.
When Koshari entered SPACE FORCE her viewer got the same object data from the server that your viewer got when it didn't have the proper object data cached so of course she should have seen the same thing that you have. My question, that you've still not answered, is whether you clicking the object after she's standing next to you and sees it inworld with the wrong texture causes both your and her viewers to then display the object with the proper texture.
---
Now let's consider how that could have happened. When you teleported back to SPACE FORCE the viewer either asked the server for object data information and used whatever it got from the server or it used the object data that it had cached a few minutes ago. If it used the cached object data information and now rendered it differently then that's a viewer bug.
If, however, it downloaded the object data from the server again and rendered it improperly then that means that either the server doesn't hold the correct object data, in which case clicking the object wouldn't have resulted in the viewer having the correct data to use to properly render the object. Or, the server holds the correct object data but the viewer, for a TBD reason doesn't use that object data and instead uses something else that looks like the object data with some changes but starts using the correct object data after the object has been clicked.
This last case is what's happening and the question is why. As stated in my previous comment, when we investigated similar issues when we upgraded to OpenSim 0.9.1.1 we found that there were bugs in both the viewer and in OpenSim that relate to the Viewer Object Cache mechanism. We couldn't fix all those issues without also fixing the viewer bugs that caused them so we used the OpenSim.ini SceneObjectGroup.IsViewerCachable setting to disable this mechanism which resulted in the elimination of those problems in Kitely with the viewer versions that existed at that time.
However, it's not impossible that later viewer versions changed how they implemented the Viewer Object Cache mechanism and that this resulted in new issues. It's also possible that the specific issue you're encountering was never fixed even when we disabled the Viewer Object Cache mechanism in OpenSim. Whatever the case, that doesn't change the fact that the viewer seems to be reacting to the same nudge when an object is clicked inworld. A nudge that it shouldn't need when the viewer is working properly. I asked you to upgrade the viewer version you were using because it was old and more recent versions fixed issues that may have been related. That, unfortunately, didn't solve this issue but upgrading the viewer is often the first thing you should do when you encounter rendering issues.
The viewer used the wrong object data initially in Naboo, you clicked it and that caused it to switch to using the correct object data immediately (according to your own report). Note that your viewer could not have been able to do so if it didn't already have the correct asset data cached already. At this point the viewer cached that correct object information and used it when you rezzed that object in SPACE FORCE. You teleported to your home, waited 5 minutes and returned to find the viewer using the old object data that it initially used in Naboo before you clicked the object. What changed is that the viewer, for whatever reason, stopped using the most up-to-date object data it cached just a few minutes earlier and switched to using the old object data.
When Koshari entered SPACE FORCE her viewer got the same object data from the server that your viewer got when it didn't have the proper object data cached so of course she should have seen the same thing that you have. My question, that you've still not answered, is whether you clicking the object after she's standing next to you and sees it inworld with the wrong texture causes both your and her viewers to then display the object with the proper texture.
---
Now let's consider how that could have happened. When you teleported back to SPACE FORCE the viewer either asked the server for object data information and used whatever it got from the server or it used the object data that it had cached a few minutes ago. If it used the cached object data information and now rendered it differently then that's a viewer bug.
If, however, it downloaded the object data from the server again and rendered it improperly then that means that either the server doesn't hold the correct object data, in which case clicking the object wouldn't have resulted in the viewer having the correct data to use to properly render the object. Or, the server holds the correct object data but the viewer, for a TBD reason doesn't use that object data and instead uses something else that looks like the object data with some changes but starts using the correct object data after the object has been clicked.
This last case is what's happening and the question is why. As stated in my previous comment, when we investigated similar issues when we upgraded to OpenSim 0.9.1.1 we found that there were bugs in both the viewer and in OpenSim that relate to the Viewer Object Cache mechanism. We couldn't fix all those issues without also fixing the viewer bugs that caused them so we used the OpenSim.ini SceneObjectGroup.IsViewerCachable setting to disable this mechanism which resulted in the elimination of those problems in Kitely with the viewer versions that existed at that time.
However, it's not impossible that later viewer versions changed how they implemented the Viewer Object Cache mechanism and that this resulted in new issues. It's also possible that the specific issue you're encountering was never fixed even when we disabled the Viewer Object Cache mechanism in OpenSim. Whatever the case, that doesn't change the fact that the viewer seems to be reacting to the same nudge when an object is clicked inworld. A nudge that it shouldn't need when the viewer is working properly. I asked you to upgrade the viewer version you were using because it was old and more recent versions fixed issues that may have been related. That, unfortunately, didn't solve this issue but upgrading the viewer is often the first thing you should do when you encounter rendering issues.