-
Notifications
You must be signed in to change notification settings - Fork 8
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
Text cleanups #250
Text cleanups #250
Conversation
Motivations for doing this move: - it makes the node code only responsible for the pipeline and GPU data update code - the logic of the text unit cannot be reused with a different geometry logic so it makes sense to have these computations together - the CPU data allocation logic related to characters can be shared with the existing one currently used for effects - having the geometry information available there will allow more advanced logic with regards to how we work with transforms in the future
This function also refreshes the effects data buffers, this is not limited to the geometry data.
This structure now also contains the geometry.
This is similar to what's being done in fill_default_data_buffers(): ptrs.* contains locations in the same buffer, so this prevents random accesses.
Did you measure any gain in practice ? |
No, nothing noticeable with my hardware, I'd probably have to use a large amount of data to spot this. It just makes the buffer reading completely linear since it has the following layout: Edit: it would be a different story if we used a buffer of structs which would interlace the data |
No description provided.