HalcyonGrid / halcyon

Halcyon 3d virtual reality world simulator
BSD 3-Clause "New" or "Revised" License
20 stars 20 forks source link

Random textures missing or just not showing #103

Open Ana-Green opened 4 years ago

Ana-Green commented 4 years ago

Ana Green: Here I did assume also that the textures did not load as Dad however she said:

Myra FoilToday at 7:55 PM because they are in your inventory. you can double click on it and then a window will open to show the texture, only it will remain gray. after a relog you will see them. that's the gray texture bug that pops up sometimes when you're online for a few hours without a relog.

I forwarded this as I think we should look at it I could not reproduce it yet, but I see that somehow the textures do not load and therefore not visible because there are none to display, I could be wrong, (only it will remain gray) as she said. If she logs they are back as far I understood?

Any idea what I can tell Myra, and for her, it is a pain because she creates items for certain Halcyon Grids.

With Regards, Ana Green

emperorstarfinder commented 4 years ago

This is a known issue. It is being worked on currently. It has also been reproduced on other grids running Halcyon.

@kf6kjg please elevate this to a known bug.

Ana-Green commented 4 years ago

Thank you emperorstarfinder, I will pass it to her

With respect and regards, Ana Green

Ana-Green commented 4 years ago

Known bug, therefore, I will close this issue.

Regards, Ana Green

kf6kjg commented 4 years ago

Actually it's good to keep track of known bugs.

Ana-Green commented 4 years ago

@kf6kjg kf6kjg

re-open it, Ricky?

Regards, Ana Green

emperorstarfinder commented 4 years ago

I forgot the temporary fix to this is to wait about 30 to 60 seconds if you just uploaded the texture for it to go live. Also logging out and then back in with the viewer appears to correct this by updating the viewer's cache. This should fix it in the short term while a more permanent and appropriate fix is being worked on.

Ana-Green commented 4 years ago

Thank you so much emperorstarfinder, I will forward it to her

Regards, Ana Green

Yichard commented 3 years ago

I randomly found that in the debug.xml file of the viewer:

Comment in MB, when total memory usage above this threshold, minimum invisible objects are kept in memory Persist 1 Type U32 Value 1024

If I understand well, that would mean that when there are too much large textures they are not uploaded in memory. Not sure it relates to the present issue, but in case :-)

life777eternal commented 1 year ago

Has anyone found the cause of this disappearing textures issue?

Here's some pictures of my region on Sovaria Estates.

Dissapearing Texturesl_010 Dissapearing Texturesl_009 Dissapearing Texturesl_008 Dissapearing Texturesl_007 Dissapearing Texturesl_006 Dissapearing Texturesl_005 Dissapearing Texturesl_004 Dissapearing Texturesl_003 Dissapearing Texturesl_002 Dissapearing Texturesl_001

Thank you.

sonjamichelle commented 1 year ago

Really don't understand what it is you are trying to convey. Water Textures? Land Texture?

From your photos it looks like all the textures are there, but the terrain height or the object heights are wrong.

Are there prim or mesh based land masses with textures? Those are different than terrain. They are objects and are treated as such.

When was the last time you cleared your viewer caches? I would get white terrain textures from time to time and a cache clear solved those issues.

life777eternal commented 1 year ago

Really don't understand what it is you are trying to convey. Water Textures? Land Texture?

From your photos it looks like all the textures are there, but the terrain height or the object heights are wrong.

@sonjamichelle Object Textures, what else? Most of the textures are still visible there, but many of them are transparent. Building textures, runway textures, taxiway textures, blast pad textures. The prims are still there, but the textures become transparent. This same thing used to happen at the region I had on the previous "Amaryllis Grid" ... and it's probably happened prior to that as well. Also I can't edit the objects where the textures are transparent, it's like I'm trying to edit the ground, but I can edit the other part that is still visible, and the transparent parts become highlighted.

And the central building with the helipad is not too high above the ground level.

Runway-Taxiway-Selected-Firestorm-Releasex64 6 6 3 67470 - Edward Ashford

Thank you.

Transparent-house-textures-Firestorm-Releasex64 6 6 3 67470 - Edward Ashford

Transparent-Building-textures-Firestorm-Releasex64 6 6 3 67470 - Edward Ashford

Transparent-Building-Textures2-Firestorm-Releasex64 6 6 3 67470 - Edward Ashford

The only temporary fix for this is to teleport away to another region, and then teleport back(or relog). But it still happens again at a later time.

sonjamichelle commented 1 year ago

Are they mesh buildings? I would have that happen to my mesh structures most of the time. Not as often as regular prims.

I still see this from time to time on OpenSim as well. So, I don't believe it is truly a Halcyon issue. Most likely a viewer issue. The reason I say this is that I can be seeing the transparent issue as you describe but my wife on the same region sees what I don't see.

mdickson commented 1 year ago

Almost all of the grey texture, missing texture, yada yada texture issues are due to code added for caching back in IW days that creates a race condition between the asset fetching logic and aperture. Turn off aperture and let the region process do the texture fetches and many of these issues will go away or get much improved). The real fix would be to address the race condition but since most all of the Halcyon grids I am aware of are fairly small running without aperture (its a config setting) is a simple workaround. The real fix is much harder and will take some recoding.

life777eternal commented 1 year ago

Are there prim or mesh based land masses with textures? Those are different than terrain. They are objects and are treated as such.

When was the last time you cleared your viewer caches? I would get white terrain textures from time to time and a cache clear solved those issues.

@sonjamichelle I cleared the Viewer cache yesterday before I noticed this. No they're not mesh textures, they're prim textures. The buildings are prim, not mesh. Only that tower, lighthouse and dock are mesh.

Also I did have Osgrid logged in at the same time, in another viewer instance, so I'm not sure if that's related or not.

I still see this from time to time on OpenSim as well. So, I don't believe it is truly a Halcyon issue. Most likely a viewer issue. The reason I say this is that I can be seeing the transparent issue as you describe but my wife on the same region sees what I don't see.

Do you know which version of OpenSim that was on?

Thank you.

sonjamichelle commented 1 year ago

Having two viewers shouldn't be an issue I would think. But ya never know, with the way file permissions are getting these days on winblows.

It was some time ago with OpenSim that I say that issue, I would guess at least version 0.9.0. Just the other day I did clear a few transparent objects off a sim. That was most likely due to damaged or corrupted assets in the oar upload. This is with the latest dev branch of OpenSim, 0.9.2.2 1386 (not sure about the last four digits).

life777eternal commented 1 year ago

@sonjamichelle

Are they mesh buildings?

No those are not mesh buildings, they were imported from XML files with Singularity. And it's a bit surprising that only Singularity has the ability to import XML files, whereas Firestorm does not, and Singularity is based on Firestorm.

mdickson commented 1 year ago

This is a race condition between the asset server, the region and aperture. The easiest fix for this issue is to stop running aperture (the region will serve the textures and mesh). This was introduced late in IW development when performance of cloud storage prompted adding some caching and it wasn't well thought out. Given the size of most of the grids that are now affected the benefit received by running aperture is minimal and not running it fixes this race condition.

This is NOT a firestorm or viewer issue.

Ana-Green commented 1 year ago

This is NOT a firestorm or viewer issue. - indeed it's not @mdickson