-
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
In-progress strokes are invisible when the camera is panned too far from the origin. #28
Comments
Thanks for reporting this issue and a possible solution. I'll try this. |
I have a branch for my personal use (https://github.com/patowen/lavagna/tree/my-preferred-fixes) that contains fixes for some of the issues I've reported (along with unrelated changes based on my personal preference of using stable rust). I'm not really in a position where I'll have time to be a contributor for this project, but I have no qualms against you referencing or using the code I wrote there if/when you decide to work on this. That being said, please let me know if you would like me to try to polish up some of these fixes and write a PR. This applies to #16 as well. |
Sure! I'll try to polish anything up that needs polishing (especially given that the math in |
Describe the bug
In-progress strokes are invisible when the camera is panned too far from the origin. I believe the root-cause is related to frustum culling (See additional context).
To Reproduce
Steps to reproduce the behavior:
POINTS_CHUNK_THRESHOLD
)Expected behavior
The in-progress stroke is visible no matter where the camera is.
Additional context
I believe the root cause is bevyengine/bevy#4294. I was able to resolve this locally by editing
make_chalk
to add theNoFrustumCulling
component to in-progress strokes.The text was updated successfully, but these errors were encountered: