Closed WhiteCoreWebUI closed 6 years ago
Screenshots might be beneficial here.
On Sat, Mar 17, 2018 at 4:38 PM ThunderLife notifications@github.com wrote:
ok before i start this: i reverted my changes to all files about messing with caps etc and started with a complete fresh install of halcyon on a new OS however i see the same problem , mesh is either invisible or corrupted, testing with the ruth v2 avatar and several items i made in blender they either show with holes (LOD Settings to max no affect) in alchemy or inworld3 viewer, invisible on firestorm and with yellow funny triangles on Singularity , guess its my stupidness again but what could cause this? Aperture is running and also wingridproxy reports calls and answers to the getmesh cap
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/InWorldz/halcyon/issues/432, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGoaBsDNxJwggMIYDl1GMz8f5HBIORXks5tfZ6CgaJpZM4SvAf- .
By now i think firestorm does the same as singularity only doesnt show the triangles.
Can you start with a file you know works (its been uploaded to InWorldz or SL or some other grid)? Verify thats correct first. There are 2 code paths involved. A Cap for uploading of assets which includes the code path to compute the Land Impact for the mesh and a seperate to actually do the upload. If you're getting those LI numbers back then the server thinks its received a valid mesh and should store it as an asset. The GetMesh call is redirected to Aperture by default and its used to retrieve the mesh data out of the region server.
The holes you describe often happen with meshes with too many faces. The uploader will try and correct that by splitting the mesh but doesn't always get it right. Could also be flipped normals. But as I said I'd try with a known working case first.
You're using whip for asset storage? Does the log show the asset hitting the whip server?
yes the ruth body i have tried in several grids opensim/sl etc only here it does not want to work at all
the fun part is, after the install it worked for like 4-5 logins and then started this, i assumed it was my cache that got corrupted but that was not the case after clearing it it got even worse
Ok, I've made the body available in IW personally so I know that works. You're uploading using the DAE's that shin made? Or starting from the blend file and your own export?
the ones that shin made including the physics DAE box, i hear the sound rezzing, i see it in object search but it stas invisible
I have seen those triangles before but they go away when that piece rezzes.
A thought I did just have is I had forgotten to make sure the CPU for each virtual machine was at least 2 vCPUs, so if you have it set up similar to how we set up our Halcyon test grid on my team's test architecture servers, you might need to increase the number of vCPUs available to each machine. That might be slowing down the rezzing of the content for you.
it is running on a 8 core machine, i figured it though it was a misconfigured nat that caused wrong packets to be send back
Very cool to hear you got it sorted. Now time for me to get back to work on my main grid. You do already know how to get a hold of me if you need anything. Second Galaxy does now have a lot of components from halcyon running on it along with our Halcyon test grid so feel free to test stuff there too if you are unsure if its an issue with your grid setup or not.
Looks like this was resolved, please re-open if I'm mistaken.
ok before i start this: i reverted my changes to all files about messing with caps etc and started with a complete fresh install of halcyon on a new OS however i see the same problem , mesh is either invisible or corrupted, testing with the ruth v2 avatar and several items i made in blender they either show with holes (LOD Settings to max no affect) in alchemy or inworld3 viewer, invisible on firestorm and with yellow funny triangles on Singularity , guess its my stupidness again but what could cause this? Aperture is running and also wingridproxy reports calls and answers to the getmesh cap