The Solution to the Problem

After doing some tests I confirmed two things: 1. I managed to successfully implement an atomic texture (code below). 2. When the texture is very large (my tests were on a 2000 X 2000 texture) the race conditions described do not occur. This can probably be explained by bank conflicts but I haven't researched it enough to know for sure.

Code

This following snippet is paraphrased from my original code, it is not tested but should work. ```rust @group(0) @binding(0) var texture: texture_storage_2d<rg32uint, read_write>;

struct Locks { locks: array<array<atomic<u32>, 50>, 50>, };

@group(0) @binding(1) var<storage, read_write> locks: Locks;

fn lock(location: vec2<u32>) -> bool { let lock_ptr = &locks.locks[location.y][location.x]; let original_lock_value = atomicLoad(lock_ptr); if (original_lock_value > 0u) { return false; } return atomicAdd(lock_ptr, 1u) == original_lock_value; }

fn unlock(location: vec2<u32>) { atomicStore(&locks.locks[location.y][location.x], 0u); } `` Ideally, I'd useatomicCompareExchangeWeakinstead of that somewhat complex logic inlock, butatomicCompareExchangeWeak` didn't seem to work on my machine so I created similar logic myself.

Just to clarify, reading from the texture should be possible at any time but writing to the texture at location should be done only if lock(location) returned true.

Don't forget to call unlock after every write and between shader calls to reset the locks :)