Fix for Mesh missing after TP. Assume MeshRezEnabled if SimFeatures not yet received #4078
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses one of the causes of the increased missing meshes following a TP. I do not believe it will fix the "missing mesh on login" which may be related but still occurs. It has completely eliminated the loss of body parts and other meshes going missing after a TP in all of my testing and regular usage.
The check in llvovolume for gMeshRepo.meshRezEnabled() has the side-effect of testing the region asset caps. After TP this is frequently failing and any mesh items in rebuildGeom at that moment will be excluded.
Another option is to remove the check in llvovolume.cpp but as that was deliberately added as part of SL-5161 it is not clear whether that would be acceptable.
Monty Linden confirmed that no current server version will decline that asset cap.
Note that all this does is change the expected response to optimistic. If the region returned false, subsequent updates would be treated correctly.