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

Mr. Doodlezz

Members
  • Posts

    571
  • Joined

  • Last visited

2 Followers

Contact Methods

  • Website URL
    https://wonderl.ink/@mrdoodlezz

Profile Information

  • Gender
    Male
  • Location
    Hamburg
  • Interests
    Cartoons & comics, logo & brand design, photo manipulation & digital/analogue drawing.

    Also video games – lots of them. :)

Recent Profile Visitors

3,553 profile views
  1. Found another workaround by chance: Group each everything together and the effect works like expected. 😅🤔🤷‍♂️
  2. Perfect, working on Windows right now. Do you maybe have the link? I'm afraid I'm not looking in the right place right now, I can't find it.
  3. Hey @MEB, oh yes, sorry, I had no doubt that you hadn't understood it! I was just wondering to myself why it behaves that way and tried other ways to achieve the desired effect (again, also for myself, to prove I'm not going entirely mad and that it actually worked as I expected at some point in history). 😅 And I also found the behaviour curious (copying the »new behaviour« into an older app version). Have a great evening Dennis
  4. Hey @MEB, thanks for confirming that there's an issue. I do not encounter that issue with the current By background layer I guess you mean a layer underneath, right? An additional observation: If I copy a layer from Photo 2.4.0 over to a fresh document in Designer/Publisher 2.3.1 the issue remains. However, if I use the »Revert defaults« button to reset the layer and apply the Bevel / Emboss effect and reduce the opacity to 0 the result is the expected one. Please check the attached file, saved from Publisher V2.3.1 (unfortunately I updated Photo and Designer already). Here's a preview, hope it helps analysing. Bevel_Emboss.afpub
  5. Hey @Callum, sure! I've attached a test file. Also here are some screenshots. In addition to the mentioned problem and while setting up this demo-file I also sporadically encountered the issue that I can't copy/paste the layer FX onto the other layers the way I used to via ctrl + V and ctrl + shift + V – the options in the Edit menu are inactive, despite having copied the previous layer. I also tried this in the previous version of Designer 2 where everything of the mentioned issues are not present and everything works just as expected (layer FX as well as copy/pasting layer FX to other layers)! Hope the files help figuring out what's wrong. Bevel_Emboss.afphoto
  6. Just noticed something odd. The layer thumbnail in the layers panel actually shows it right. It previews just the effect, with the content hidden, exactly how I expect it to work on the canvas – weird!
  7. Hey folks, I've noticed a problem in Affinity Photo 2, affecting both iPad and desktop versions, where changing a layer's fill opacity via the FX options from 100 % to anything between 100 and 0 % doesn't hide the layers contents as expected. Instead, the contents remain visible 100 % at all times. This seems similar to a previously mentioned, but seemingly solved issue with the 3D effect in Affinity Designer, indicating a possible consistent rendering issue with layer effects and fill opacity settings. To reproduce the Bevel / Emboss visibility issue, follow these steps: Open Affinity Photo 2 on either an iPad or desktop and create a new layer. On this layer, draw anything using any colour of your choice. Apply the Bevel / Emboss effect to the drawn layer. Reduce the layer's fill opacity to 0%. Expected Outcome: The layer contents should become invisible, leaving only the Bevel / Emboss effect visible. Actual Outcome: Despite reducing fill opacity to 0%, both the layer contents and the Bevel / Emboss effect remain visible, suggesting that the expected change in visibility does not occur. I'm looking for insights or workarounds from anyone who has encountered this. Any feedback or suggestions would be appreciated. Cheers Dennis
  8. @Callum alright, so there's probably no estimate, right? Anyway, thanks for your response and happy New Year. 😉
  9. @Callum anyone there? Still waiting for an answer and the issue still isn't resolved and by now is annoying as hell.
  10. Regarding the Stream Deck, I'm not familiar with its specifics, hopefully someone else can answer that question. Almost any other applications I use or have used have implemented keyboard navigation quite effectively. I’m so used to it by now, I’d almost already expect to work properly. (Well, even more so with a V2 release, tbh.)
  11. Despite announcements of improvements months ago, there has been little to no change regarding navigation with keys like tab and enter/return or other means in a very, very long time. I'm not sure what the cause is, but I guess fixing persistent issues that don't break functionality for most users has been ranked lower repeatedly in favour of implementing new features.
  12. Thanks, @NathanC, that indeed solved it! What a strange workaround. Is this knowledge expected of us users? I've been using the Affinity Suite every day (well, every app from day one, as soon as they where available, that is), and I've never encountered this behaviour or heard of handling this setting in such a way. 🤔 I guess you never stop learning. 😅 And I guess @NotMyFault was somewhat on the right track after all!
  13. Sure, I just tried – no difference in behaviour. 😕 But even if it would make a difference, setting it to No tips shared does seem like a workaround for the actual problem rather then the solution. Maybe I do want to share some aspects of brushes. RPReplay_Final1697990176.mov
×
×
  • 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.