Jump to content
You must now use your email address to sign in [click for more info] ×

altae

Members
  • Posts

    149
  • Joined

  • Last visited

Posts posted by altae

  1. Mapping two different keys for the size decrease/ increase command works but that's only a suboptimal workaround and not a solution. I would have to change the mapping for every single tool that makes use of the size decrease/ increase command. The question remains: I have not changed the default settings of the wacom driver and this setup works flawlessly in Affinity Photo 1. Why wouldn't it work in Affinity Photo 2?

  2. But the brush size function comes with [ ] by default. And I cannot manually program a keystroke with [ ] as my keyboard (Swiss layout) lacks dedicated [ ] buttons. I would upload a screenshot to proof it If I could but unfortunately I keep getting an error message (Error 200). And if it was my configuration why would it work in Affinity Photo 1 but not in version 2? It's the same keystroke.

  3. In this case the "bug" is the fact that the default grid cannot be changed by the user. For example I need a grid to determine if certain lines in my photos are straight. I have no use for a tiny pixel grid that can only be seen at ridiculous zoom levels 😉 Serif should really reconsider and at least give us the option to set the default grid size to something more useful.

  4. The title says it all. Why is ctrl + y not the standard keyboard shortcut for the redo command? This is contrary to almost any (Windows) software out there where ctrl + z undoes the last command while ctrl + y redoes a command that has previously been undone. I know I can change the keyboard shortcuts but I would like to know the reason behind this deviation from the de facto Windows standard.

  5. I use the aforementioned tablet to edit my photos. It comes with a control wheel that has 4 functions: auto scroll/zoom, cycle layers, brush size and rotate. Auto scroll/zoom, cycle layers and rotate work as expected but brush size does not. Instead it also cycles layers. I've tried all three input methods (low precision, high precision and Windows Ink) but the problem remains. With Affinity Photo 1 the brush size function works as expected.

  6. Today I tried to import a few macros into the stable version which I created with the above mentioned beta version. When I opened the dialogue to import the macros none of them where showing up even though I was in the correct folder to which the macros were exported. I took a closer look and realized that both versions (beta and stable) export macros with the file extension .afmacro while for importing macros they expect files with the extension .afmacros (with "s" at the end). Is this behavior on purpose? Or is it a bug/ an oversight?

    It gets even worse: Renaming the files to .afmacros does not fix the issue. It does let you select the files (contrary to files with the extension .afmacro which do not even show up in the dialogue) but trying to import them leads to an error message "Unexpected Macros Format". So it's currently impossible to import macros into Affinity Photo that were previously exported.

    P.S. I'd love to attach a screenshot but the forum still gives me an error message "-200" when I try to ☹️

  7. The current beta (in fact the last one suffered from the same issue) shows artifacts when using the Shadows & Highlights filter (legacy 1.6, live filter as well as normal filter) while OpenCL hardware acceleration is active. Deactivating hardware acceleration fixes the issue.

    Btw: It's only the legacy version of the filter that shows these artifacts, the standard version seems to be fine.

    P.S. I'd love to upload a screenshot but unfortunately I cannot upload my .jpg files (an error message saying "-200" appears). I'd love to document this error message with another screenshot but: "-200" 😉

×
×
  • Create New...

Important Information

Terms of Use | 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.