Saad K
Saad K
That sounds great! > For each entity (when expanded) the storages are iterated and those in which the entity isn't available are discarded. For the others, an item is added...
@skypjack that sounds good If this is to become a feature, I would request some modularity with the type information i.e. on the one hand one can use the macro...
Thanks @skypjack. I'll try it out asap.
This caught me off guard where it was happening in the background and I did not know what happened to the files in conflict. With Git LFS enabled, merge conflict...
@stefanhaller I'd be happy to test it, however I have been relying on the binary builds. Are there a set of binary builds of the PR? If not, I'll try...
Was able to confirm that the above fix works as intended. LFS file conflicts are no longer auto-merged.
Thanks @xissburg I'll try that out > or perhaps even removed to avoid confusion If they are removed, how do we move the Kinematic bodies without these functions? Edit: oh...
@xissburg since I am using the `update_kinematic_position` function, I updated it to test whether the overlaps will work or not: ``` void update_kinematic_position(entt::registry ®istry, entt::entity entity, const vector3 &pos, scalar...
Same here. Discarding files in Lazygit is orders of magnitude slower than in command line.