dear remarkable devs.
For a product that is meant to be as close to paper as possible, the fact that there is no way to actually reliably erase the pixels directly under where your eraser went is somewhat unacceptable. When i erase, especially with stroked from the shader tool, it seems like it checks if my eraser covers some minimum area from a specific stroke to erase, rather than just erasing precisely the pixels i moved over. Now this would already be bad enough if the shader tool didn't encourage you to overlap stokes, but it does. This results in what I described above needing to happen to multiple stokes at once, meaning for certain sections of shading, they are virtually impossible to erase without destroying the project. Especially because, if say, i settle for erasing a much larger area than i want to in order to clear a certain spot, now when i fill back in the unwanted erasures, there will be uneven overlapping on the edges of that area.
I saw someone posting about this feature on the reddit, and a dev responded saying it was impossible because of how the stoke logic is programmed. Than it is your JOB to reprogram as much of the stack as necessary to make the eraser function usable. To get set-up with one of these tablets, it costs about $1000, plus a subscription to get syncing. For that price, and the level of polish that is promised, you need to do better than, sorry this basic functionality is "impossible."
also as someone with some development experience, you wouldn't need to reprogram very much at all! the quick and dirty way would be just to store the stroke as a bunch of smaller vectors right next to each other! no it wouldn't be pixel perfect to where you erased, but it would make it usable! as of now, you hav4 to treat any kind of finished product you make as drawing with pen and markers, because erasing simply does not work.
You have made a fantastic product, but seem to think that good enough is enough, when, at this price point, its not!
thanks,
keenan