I’m trying to do something I’m pretty sure I’ve done for years without problem in Acorn – simply erase some pixels on a layer (in order to let something from another layer show through). Sometimes it works – see the left side of first image. Other times it decides to garbage up the works with a mask – or mask – layer – or who knows what. Regardless, it renders the image completely unusable – see the right side…
Sorry about the problems. Can you tell me a little about this image (or give me a screenshot of the palette when you press the ‘v’ key twice? That’ll bring up some info including pixel dimensions and bit depth that’ll help me diagnose).
And can you tell me what kind of Mac hardware you’re using, as well as what version of MacOS you’re running?
This looks like some sort of rendering problem, but I’ve never seen things go bad like this (usually there will be fills of black where things go wrong, not strange blues and greens).
One other thing to try- what happens if you change the Renderer: option in the Fussy Stuff tab of the Preferences? (You’ll have to close and re-open your image for the new renderer to kick in).
Changing the pixel processing profile appears to fix the problem – changing just the renderer worked a little in OpenGL (even though any of the options show in Info as OpenGL) before the attack of the blocks began again.
After fiddling with settings, I set the renderer back to Metal (default) and pixel profile to none, and now it’s working fine (if slow).
Hi Gus, not starting a new subject since apparently this is my “box” issue, even with 16GB of RAM. Acorn is simply unworkable at this point: lag is typically 10-20 seconds, and even a simple action like making a circle with a brush overwhelms it:
It’s a shame. Enthusiastic as I am about Acorn’s compact size (my needs are relatively simple), it can’t even do the basics at this point. I should mention, too, that getting it to even do this fragmentary brush strokes requires “fussy” tweaking from the default settings. This is a simple brush circle after a fresh reinstall, with no tweaking:
Do you remember what the last version of Acorn was that worked fine for you? Maybe I can narrow down what changes occurred. Here’s some links to previous versions if that helps as well:
That’s really interesting! If you have time, can you grab a couple more builds to see if they have the same issue? This will help me narrow down where the bad change was made.
We’ve got this fixed for the next release of Acorn, as well as in the latest builds which you can grab from here: http://flyingmeat.com/download/latest/
