You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is actually more obvious on Bigbrain Surface Viewer (which shares almost the same core) since we tend to load a larger number of shapes.
In some situations, the opacity slider does not work and makes some shapes visible or totally hidden, partially transparent is not possible. For example, the shape 253-white cortical surface right from BigBrain experiences this issue.
After investigation, BrainBrowser core does not seem responsible for that and the problem seems to rather be on THREE.js side. I made a test using a recent version of THREE (rev 76) in BigBrain Surface Viewer and the shape 253-white cortical surface right now plays well with opacity but some other shapes do not anymore.
No matter which version of THREE, the shapes that don't play well with opacity seems masked (or partially masked) by another shape rather than completely invisible. I noticed that with a rotation, some parts of the invisible shapes become visible.
Here are the possibilities that come to my mind (other than THREE has a bug):
the mesh encoding (in the json file) could be responsible
the normal vector is in the wrong direction
a shape can be masked by an invisible shape
The text was updated successfully, but these errors were encountered:
To illustrate the last point "a shape can be masked by an invisible shape" , here are some snaps where the green shape continues to hide the grey shape even though it is invisible. It is especially clear in the the last image where we can see the demarcation at which the grey shape is not visible anymore. This border matches exactly the position of the green shape.
Though, in some other cases, overlapping several shapes that are all partially transparent works just fine.
This issue is actually more obvious on Bigbrain Surface Viewer (which shares almost the same core) since we tend to load a larger number of shapes.
In some situations, the opacity slider does not work and makes some shapes visible or totally hidden, partially transparent is not possible. For example, the shape 253-white cortical surface right from BigBrain experiences this issue.
After investigation, BrainBrowser core does not seem responsible for that and the problem seems to rather be on THREE.js side. I made a test using a recent version of THREE (rev 76) in BigBrain Surface Viewer and the shape 253-white cortical surface right now plays well with opacity but some other shapes do not anymore.
No matter which version of THREE, the shapes that don't play well with opacity seems masked (or partially masked) by another shape rather than completely invisible. I noticed that with a rotation, some parts of the invisible shapes become visible.
Here are the possibilities that come to my mind (other than THREE has a bug):
The text was updated successfully, but these errors were encountered: