Jump to content

Roxfall

Members
  • Content Count

    18
  • Joined

  • Last visited

About Roxfall

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I was messing around with Perlin noise to create a random topographical map, combining multiple pixel layers with different octaves of said noise. I noticed that there's a barely visible ray coming from top left corner of the image going at a 45 degree angle down all the way across. I believe this is a bug in Perlin noise code, since the ray becomes more visible the more layers of Perlin noise you combine in one image. Example here: https://i.imgur.com/IeMTDWd.png
  2. I second this notion. I wish I could just middle-click the "fx" symbol to turn them all off. Right-click to open and then click on a bunch of different windows is time-consuming.
  3. If it's not supposed to go on the master page, why can I add text to the master page?
  4. I have my text of the book in the master page. If I duplicate any of the regular pages to add another single page, the whole text of the book gets duplicated. When you do this multiple times it leads to 2>4>8>16>32 etc copies of the text of the book back to back.
  5. Correction: the copy-relink process appears to be multiplicative. Since I added about 10 pages to my document, I now have... maybe over 100 copies of the book trailing off the last page? No idea how to fix that other than start over OR sweep it under the rug with blank spaces. My workaround was to save a copy, Ctrl-A to select all, delete whole thing, then paste one copy of the text from the backup. Deleting one page at a time was far too slow.
  6. I noticed a severe drop in performance when the last page of my text document did not have a "crossed red eye", resulting in text running off the bottom of the page. Once I clicked on the red eye icon to "cross it out", the performance drop decreased, allowing me to resume work. With the eye icon uncrossed, the document became unresponsive: after every text edit, the program would hang for 15-30 seconds. What had happened to arrive in this state was my copying pages and relinking them in order to expand the document with a single text field. Every time I copied a page, it would copy all the text from the master page, and when I relinked them, instead of removing duplicated text, it would add the whole book to the end of the text stream, resulting in 20 or copies of the book in the same text stream, trailing off the last page. My expectations for relinking pages would be that the text would not be copied. Needless to say, cleaning up 20 copies of the book from the last page of the document, one page at a time, with 30 second pauses after each delete is a very special personal hell :)
  7. If this is what's causing it, then the default functionality should be: rasterize all layers first, then merge them. If you're hellbent on having a "merge a blurry mess" function, then call it that, and make it a separate thing. I'm done arguing for common sense, you've lost a customer over this program-defining "feature". I'll check again next year to see if it's fixed yet, will be using different software in the meantime. Yes, it's that big a deal. Affinity Photo: just like photoshop, but you can't merge layers.
  8. Dear developers, I wanted to love this program. This bug made me look for alternatives. You want to compete with Photoshop? Fix it. This is a program-defining bug. Right now, "Affinity Photo is just like Photoshop except YOU CAN'T MERGE LAYERS". That's all I remember about the software, which is a shame, because it has a ton of good things going for it. I would rather be able to say "Affinity Photo is just like Photoshop but it doesn't ask for your firstborn." But I can't say that, because of this thing. Will check in next year to see if it's fixed yet. It's unusable for me until then. I'm angry because I care, not because I hate you. I love you all, and I want you to be more lovable.
  9. It is a bug plain and simple. Nobody uses misaligned layers for anything but corrupting merged layers. Fix it please for the love of all that is unholy and right with the world. ;)
  10. It has a nice preview, but when you hit apply, the image goes back to what it was before, so nothing changes. Workaround: take a screenshot after disabling all other layers, then paste it and hope. Not pretty.
  11. Apparently this issue went away after I enabled force pixel alignment and restarted the program. Something is wonky, I don't know how to reproduce the problem again.
  12. Suffering from the same problem. Also I can't figure out how to transform/mirror a layer without dragging it imprecisely by hand, which might be what's causing it. Is there a way to purge history?
  13. Here's an illustration. The line was drawn using the shift-click command to draw what the program considers a 'straight line' between two points.
  14. I am using Microsoft Surface with Touch screen turned off to prevent accidental smears. My touch sensitivity is also turned off to use 1x1 pixel brush. What I am seeing is that there are certain columns of pixels that are ignored when I tap on them, no matter how zoomed out or in. What's worse is a column near such a blank column always draws on both columns, resuling in a 2x1 block instead of a 1x1 block. This happens in both regular and alternative mode (erase). Thus there are columns in the picture where drawing pixel-perfect art or even a straight line at an incline is impossible, resulting in jagged appearance that cannot be fixed by hand. It's the whole column of the screen like this... they happen every 5-10 pixels. I've gone through a lot of options and I can't find one that would turn off this "feature". Please advise.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.