Posts by karolherbst@chaos.social
 (DIR) Post #B6SV2w6OXQN4zShZTc by karolherbst@chaos.social
       0 likes, 1 repeats
       
       "Fun bug of the month, mesa edition, episode may"so if you do "uint64_t some_var = 1 << 31;" in C you get "0xffffffff80000000" as the value, because that's super obvious and not confusing at all.It's pretty funny getting reminded how non-intuitive and broken C is from time to time.
       
 (DIR) Post #B6SVcpNL1cyqYKk1IG by karolherbst@chaos.social
       0 likes, 0 repeats
       
       @a1ba oh yeah, we also have tons of macros for all those things, but sometimes with refactors and such sometimes things fall through cracks.
       
 (DIR) Post #B6SVwG71qGvMyhNVfU by karolherbst@chaos.social
       0 likes, 0 repeats
       
       @a1ba it shouldn't tho 😭 this is just such an awful part of the language.
       
 (DIR) Post #B6nMayrISJ3DTqhvXM by karolherbst@chaos.social
       0 likes, 0 repeats
       
       @mary @drakulix I'm in happy tears
       
 (DIR) Post #B9phOMxxnRo2mrkq3M by karolherbst@chaos.social
       0 likes, 0 repeats
       
       @mntmn probably filing a bug would be the right course of action, but identifying a bug inside blender can be... rough.Though yeah, looks like vertex coordinates are somehow messed up and I guess it's either synchronization (though than it would have some randomness to it, sometimes) or some weird obscure driver bug, which is possible.
       
 (DIR) Post #B9pkUAq06PSGltUOfI by karolherbst@chaos.social
       0 likes, 0 repeats
       
       @mntmn yeah.. in Mesa most of the GL and VK drivers do not share state management or command buffer creation code, so there to be a difference between the drivers can easily happen.They share a lot of other things, just not that part.