OpenSimWorld is the directory of 3D Virtual Worlds based on OpenSimulator and connected through the HyperGrid. Learn More
New Members
KajunBabe, 99okunitedstateofcinema, ArnasSoderstrom, Sparky, Rabea2024, Layla_Lynn, Calvinux, TeriYaki93, Rhian_Kalinakov, Tonykasjohny, Stevey87, ShaylinBrook, Gordloon, LunaGarcia, Trini, KittyCarbon, Rrita, SerenaLightwell, Stefano, WebRainLikes
Certain assets broken all over the Hypergrid?
I've been encountering a strange phenomenon for quite a while now.
Firestorm reproducibly does not texture certain surfaces. They're rare, but they're always the same.
One example that comes to mind: Swiss Cafe (in case you know it), second ground floor window from the left, the "non-moving" parts. They're always "textured" plain white. Even on derivatives of this building, and regardless of on which sim on which grid they're located.
This happens to two different avatars of mine from two separate grids each (two avatars on one grid, two avatars on another grid). It also happens on two separate computers, both booting Debian testing, but I don't think the underlying OS has any influence. This rules faulty cache content out.
In fact, it even happens after I've completely deleted the cache manually outside Firestorm.
I've tested various Firestorm versions from 6.3.9 to 7.1.9 today, and they all show this strange behaviour. That is, I do recall having seen the Swiss Cafe properly with all textures in the past, using Firestorm.
A while ago, I tried saving the general settings and all avatar settings, then deleting the entire ~/.firestorm_x64 directory. It didn't change anything.
Eventually, I tried the Cool VL Viewer. It doesn't render that texture either. So it's actually independent from the viewer as well.
Can it be that assets can be damaged by faulty asset servers or something, and that damage spreads all across the Hypergrid and wrecks all copies and all derivatives of the affected content?
Firestorm reproducibly does not texture certain surfaces. They're rare, but they're always the same.
One example that comes to mind: Swiss Cafe (in case you know it), second ground floor window from the left, the "non-moving" parts. They're always "textured" plain white. Even on derivatives of this building, and regardless of on which sim on which grid they're located.
This happens to two different avatars of mine from two separate grids each (two avatars on one grid, two avatars on another grid). It also happens on two separate computers, both booting Debian testing, but I don't think the underlying OS has any influence. This rules faulty cache content out.
In fact, it even happens after I've completely deleted the cache manually outside Firestorm.
I've tested various Firestorm versions from 6.3.9 to 7.1.9 today, and they all show this strange behaviour. That is, I do recall having seen the Swiss Cafe properly with all textures in the past, using Firestorm.
A while ago, I tried saving the general settings and all avatar settings, then deleting the entire ~/.firestorm_x64 directory. It didn't change anything.
Eventually, I tried the Cool VL Viewer. It doesn't render that texture either. So it's actually independent from the viewer as well.
Can it be that assets can be damaged by faulty asset servers or something, and that damage spreads all across the Hypergrid and wrecks all copies and all derivatives of the affected content?
Liked by: 
Comments
Just now see this in FS site:
"Sometimes, blocking is a necessary kindness.
There are occasions when a block is probably best for everyone. As an example, we can consider the recent 6.6.16 release, which had the potential to mess up inventory. That needed to be blocked to stop people from “hurting themselves” and causing ourselves and Linden Lab undue support overheads. Those occasions are quite different from blocking an otherwise stable viewer because it is “old”. “Stable” in this context means that people are familiar with the specific bugs and foibles of a given release and are happy to live with it and that it has no undue impact on others."
https://www.firestormviewer.org/firestorm-6-6-17-will-not-...
Now if they understand that problem exists and in 6.6.17 all will look excelent:)
like(0)
"Sometimes, blocking is a necessary kindness.
There are occasions when a block is probably best for everyone. As an example, we can consider the recent 6.6.16 release, which had the potential to mess up inventory. That needed to be blocked to stop people from “hurting themselves” and causing ourselves and Linden Lab undue support overheads. Those occasions are quite different from blocking an otherwise stable viewer because it is “old”. “Stable” in this context means that people are familiar with the specific bugs and foibles of a given release and are happy to live with it and that it has no undue impact on others."
https://www.firestormviewer.org/firestorm-6-6-17-will-not-...
Now if they understand that problem exists and in 6.6.17 all will look excelent:)
Well, I seem to be the only one who sees the Swiss Cafe broken. I've recently seen an in-world picture from someone else in which it's okay.
like(0)
Before 4 months i try to warn about this FS bug.
https://opensimworld.com/post/106551#cmt59567
Peoples continute to not understand whats happen.
Last 3 versions of FS contains bug and when owner edit assets FS broke assets on server.
Keep wide closed eyes and wait:)
like(0)
https://opensimworld.com/post/106551#cmt59567
Peoples continute to not understand whats happen.
Last 3 versions of FS contains bug and when owner edit assets FS broke assets on server.
Keep wide closed eyes and wait:)