#transform.hasChanged in a job
1 messages · Page 1 of 1 (latest)
There is change filter, which indicates that chunk component data was changed
not applicable for specific entities
Im not using entities at all
oh
that said, i'd be surprised if they added a change filter to this
well, with this one you are in full control of modifying it
so you might as well implement that feature yourself
Im not sure what you mean. I can keep a cache of the prev frame values and do a check in a job sure, but I feel that will not be a perf gain. My end goal is to uploaded the transform matrices to a gpu buffer. Right now I upload all of them each frame and I want a way to minimise that.
memcmp is excellent for large change comparisons
if you can structure your data in a way to get it to work
what I mean - instead of using raw TransformAccessArray, make some kind of wrapper, which would require you to increase some internal version every time you access it for write operation
and then just compare cached version with current one