-
Notifications
You must be signed in to change notification settings - Fork 11
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
bug when zooming in with mouse wheel #55
Comments
Hey @tischi, thanks for your report! I have not seen this (up to now :-D). So it happens everytime you scroll, or only under certain conditions? What is your hardware configuration and what OS are you using? |
Hi Tischi,
To solve the issue, press key ‘m’, this will deactivate the multi-pass rendering algorithm.
The multi-pass algorithm speeds up rendering but it seems that there is a multi-threading
problem and sometimes the clearing of the buffer is not performed when the view is changed,
leading to the effect you noticed…
With Ulrik we are working on ClearVolume 2.0, will take some time as it is a full redesign,
hopefully we can iron out some lingering bugs.
sorry for that!
Loic
On 02 Mar 2017, at 09:43, tischi ***@***.***> wrote:
Hey!
The specs are from a comp of one of our users:
<https://cloud.githubusercontent.com/assets/2157566/23499482/9aba19be-ff2c-11e6-93fa-b1eadfafed1f.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AByMkg7B4cRJbSNT5IZ_10x1DkBKb803ks5rhoE6gaJpZM4MPwbk>.
Dr. Loïc Alain Royer
Post-Doc - Myers Lab
Max Planck Institute
of Molecular Cell Biology
and Genetics
Pfotenhauerstr. 108
01307 Dresden
Too short? Here's why: http://emailcharter.org/
|
Great! Thank you for the information! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
when we zoom in and out we sometimes get a smear in the data (see attached "artifact" image).
Are you aware of this issue?
The text was updated successfully, but these errors were encountered: