-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mesh not showing up inworld #298
Comments
I am suing you already did this, have you tried to reproduce with multiple OARs that have mesh in them (different OARS of course) just to be sure it is not that particular OAR? |
@emperorstarfinder Yes, for some reason it just stops rendering these mesh items. I've tried it with multiple OAR files, even created a clean one just to check. I am not deep into Mesh to know what this marker 110 exactly stands for, perhaps that might be also part of the solution |
can you email me the oars and ill test them if possible? I might be able to figure out whats going wrong If it is an OpenSim created OAR then that might be a problem we may not have a marker they do as well. |
I'll grab the OAR from my development machine when I am back home. |
This looks like a problem in the OMV libraries. |
I will test it on weekend on my local grid ;D |
This is why I am having him email me the OARs so I can see what happens when the OAR loads. the 110 marker is a marker we should already have which is why I want to see what happens when I try to load the oars. |
is this fix yet? |
Steps to reproduce
Expected behaviour
The Mesh should appear rezzed
Actual behaviour
The Mesh isn't showing up
Server configuration
Operating system:
Ubuntu 16.10 / x64
Web server:
Nginx
Database:
MariaDB
WhiteCore version:
Master
Logs
Binary LLSD parsing: Unknown type marker: 110
Apr 04 03:23:12 - Failed to decode mesh asset
Apr 04 03:23:12 - System.NullReferenceException: Object reference not set to an instance of an object
at OpenMetaverse.Assets.AssetMesh.Decode () [0x00040] in :0
The text was updated successfully, but these errors were encountered: