Skip to content
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: Objects' transformations don't appear in the frame buffer or get averaged out over time #8

Open
cszach opened this issue May 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@cszach
Copy link
Owner

cszach commented May 22, 2024

Currently, the vertex data (which contains global positions) gets updated only when the scene's stats become "outdated" (i.e. when an object is added or removed). This means for most scenes, objects that transform (translate, rotate, scale) don't appear as transformed in the frame buffer, because their vertex data is not updated.

This could be temporarily solved by uploading vertex data for every frame, but due to the way the frame buffer view works currently (each pixel accumulates colors over time and get averaged out by the frame count), the transformations appear as motion blur and eventually get so averaged out that they are not visible.

Some ways we could solve this moving forward:

  • Uploading the vertex data every frame has performance implications. We can instead switch to a buffer of model matrices as proposed in Feature: Model matrices #4.
  • Reset the frame count back to 0 when the matrix buffer is updated.
@cszach cszach added this to the First Public Release milestone May 22, 2024
@cszach cszach added the bug Something isn't working label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant