A result seems to vary according to a form of color depth of the png file so that you say.
This just makes it so Alt+RMB selecting always selects the entire interior loop.
Using UpdateMesh() for changing triangle mesh shapes now, even in unshared case (instead of SetMesh()), because of possible ignoring the RAS_MeshDeformer. Thanks to @panzergame for pointing this out.
Also fixed a crash with bvhTriangleMesh (happened even before replaceMesh()), there the new unshared case was not treated correctly.
Closed by commit rB7f25da650943.
Yes, it happens with factory settings too.
Here's the blender -d output, although I don't see any screams of pain in it: log.txt
To reiterate: we just load the blend, select the texture, tick "Normal", and it crashes. We've investigated with several files and various images, and crash is inconsistent: some files work fine, while others crash.
AFAIK this issue is fixed already, could you test using our latest build from buildbot?
Hello, why we can't call SetMesh with a RAS_MeshObject without DerivedMesh ? I think it can cause porblems if the mesh is deformed without deformer (RAS_Deformer) like from python.
What's the real difference between SetMesh and UpdateMesh ?
Yes, i was use 'onboard', but only to show this trouble. It is exactly demonstrate how laptop's keyboard not work normal. See all comments above...
@hg1 Why you don't call GPU_mist_update_* in a function in RAS_OpenGLRasterizer ?
Maybe it's better to past uniform blocks to the shader than many uniform.
Hehe, well Blender grows almost as fast as the internet... Hard to keep track of both ;)