-
Notifications
You must be signed in to change notification settings - Fork 24
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
Clipping distance changes with zoom in arbitrary mode #7725
Comments
Not sure if this is related, but I noticed that the clipping in oblique and flight mode changes when zooming. If the clipping distance were in nm (which it is supposed to be) this shouldn't happen. |
@daniel-wer In #7732 you wrote that that PR contributes to this issue. What parts are still missing? |
I wrote this, because my fix didn't explain this observation
However, I did a quick test again and although the clipping changed during zooming I wasn't able to select invisible nodes, so I guess this particular issue (mismatch between what's displayed and the node picking) is resolved. What remains to be investigated is why the clipping distance in oblique/flight mode changes during zooming and doesn't seem to be in nm. |
Great, thanks for the clarification! |
Context
Skeleton nodes are only rendered when they are within the configured clipping distance. Further context in this GH discussion.
Expected Behavior
Only nodes that are visible should be selectable by the user.
Current Behavior
The clipping distance is not perfectly respected which is why you can sometimes select nodes that are not rendered.
Steps to Reproduce the bug
Your Environment for bug
jobsEnabled=true
inapplication.conf
)isDemoInstance=true
inapplication.conf
)The text was updated successfully, but these errors were encountered: