moedgehog

Stop. This is 100% weird now that this thread has derailed this much. I already got the answer I'm looking for and it's 100% fine that you and anyone else who seems fixated on derailing this thread wasn't able to provide it. But if this discussion persists then it has absolutely nothing to do with me anymore because I already got my answer and I'm fine with that so my part in this is done. Have a good one.

At this point it feels like this is getting personal and becoming incredibly inappropriate. I had someone who was kind enough to take the time to understand what I was trying to say and the issue I was running into, and was also kind enough to both explain and introduce me to a feature in the program that I didn't even know existed to help me resolve the question I had. I'd like to assume that this is all done in good faith but at this point there's only two conclusions to come to - that there's a weird amount of embarrassment over not fully understanding what I was trying to communicate or there's an ingrained theme within this community that seems fixated on trying to find ways to shame new posters. I asked a question, I asked again for more clarity. I made it clear from the start that I've been open to understanding and communicating. Everything about this just feels really gross and there's no reason why this post needed to escalate to this point. Thank you again to the kind user (I won't tag them because I don't want them dragged into this) that was respectful and understanding enough to answer my question. To the rest of you - I really hope this made you all feel better to randomly bully someone on a forum who was willing to be curious and vulnerable enough to ask questions. Have a great rest of your day and take care.

Oh my god. Oh my %#(* god you are a fricking life saver. I didn't even know about the Protect Alpha feature. That was 100% what I was looking for, I really really really appreciate you taking the time to break this down for me. It's definitely a bummer that there doesn't seem to be a way to adjust the color of something without using an adjustment layer but this at least cuts down so much of my layer pile up by exponentially so WOW yeah wow thank you!!

Thanks but this doesn't have anything to do about what I asked. It also contradicts what they emphasized in their own response.

Oh! It's all line work that's been generated in Photo.

Whoa there. I was just asking a question. If you or no one has the answer that's 100% fine but I was just confused as to why screenshots would be relevant for something like this, eesh. Have a good day I guess?

Why would that be necessary? I guess to be more clear - I'm asking about if it's possible to do something akin to color holds on Photoshop.

Been using Affinity Photo for a month and can't seem to find a solution to this that doesn't make a file incredibly messy with layers. Is there an easy work flow to color line art and adjusting the colors selected without using HSL layers and layer masks/stacking layers? I've tried experimenting a number of ways but each time yields the same result - a file with way more layers than is needed and also an inability to even merge something until it's completed since it seems like merging a group of layers with HSL layers included impacts them all? Any help on this would be appreciated, thanks.

Ahh sorry about this 'cause I think there's been some confusion @Chris B! The file that I sent is actually the near finished version of the illustration rather than the version I was working with at the time that I made this post. In the version shown in the video, there's few adjustment layers and overlays that are in place. It's literally just me working with the flats and line art. I used the HSL layers for that version to properly adjust the flats before I move forward with the rest of the coloring like shading and lighting adjustments. Let me try to do away with the final version of the character art and re-upload what was actually present so that hopefully there'll be a clearer understanding.

Great! I've gone ahead and uploaded the file. I took the time to make sure that all of the HSL adjustment layers were turned off when color selecting. Not sure if adjustment layers that are underneath will impact it but also made sure to turn those layers off too just in case.

Okay, opened up the Beta and for the most part it actually seemed to work out a lot of passive issues I've been having with Affinity. However, I did manage to capture the random glitch I've been running into with the eyedropper. It's very subtle but you can see the color being picked up as being a bit lighter than the original color selected. I thought that it may have been a color adjustment layer underneath impacting it so I turned it off and that, for the first time, actually made the color that was picked up accurate again. I then turned the color adjustment layer back on underneath just to double check to see if it was that adjustment layer messing with it and it continued to pick up the same color. Hopefully this makes sense! I'll keep an eye out for the issue with the canvas moving as well - https://recordit.co/3vYEVLAmKN ETA 3 hours later: Okay. I spent the last 4 ish hours on and off messing around in BETA and here's what I've found: As far as I can see, the issue with the canvas drag tool seems to be resolved? In the original version it tends to happen within an hour or so of me working and I managed to get nearly through an entire piece without it happening. The issue with the eyedropper tool still seems to be there in the BETA, however there seems to be a resolution that isn't there in the original. From what I can see when the color picks up odd, if I just turn the layer that I'm trying to pick the color from off and on then it seems to resolve it. Didn't have to reboot the program once though it is kind of a bummer that this is happening. Hopefully this provides some more concise information on the issues I've been running into! Let me know if you need more.

Thanks for this! I've downloaded the Beta and will test it to see if I end up running into the same issue. These issues tend to pop up regularly while I'm working so I'll try and mess around with it for a while and report accordingly whether I come across the issues again or not!

Okay, so I managed to at least catch the program when it just stops allowing me to move the campus. The trigger for it is honestly random. Right before this happened I merged a few layers together, the program halted for a moment and then when I went to move the campus to readjust my view it just stopped working - https://recordit.co/qSBTFzmOyV I'll have to restart the program to get it to work again but I'm going to presume the eyedropper tool will also stop working at some point and hopefully I'll be able to also catch that.

It does unfortunately! I was thinking something similar but other things like not being able to move the canvas around (which will happen even if I'm using the mouse) will also randomly happen while I'm in the middle of working. Next time I can definitely try to find a different way to record it to show what's going on the next time it starts to happen but I do worry it's a compatibility issue.

It's definitely a weird one that honestly I haven't run into before! Essentially what happens is: I'll use the eye dropper to select a color in the image. I've tried to have this set to both Global and also to the specific layer that's been selected. I will then use that color from the eye dropper to color on the image and it will end up being a color that's much lighter than what I selected. Eventually it just seems to stop working entirely and just selects black even if black is absolutely no where to be found where I'm using the eyedropper tool. I can try to increase the radius to see if that will impact it but this seems like more of an actual bug considering what's selected eventually stops working. The only way for me to get it to work again is for me to completely close down Affinity Photo and reopen it. Then it will start working correctly again. Edit: To add to this, another issue I'll run into is that after a while I'll no longer be able to move the canvas. It's another issue that seems to only get resolved once I restart it. I'm not sure if this is a compatibility issue but my computer specs (brand new build) are: - Processor: AMD Ryzen 7 2700x Eight-Core Processor 3.70 GHz - Ram: 32.00 GB - Using a Huion Kamvas Pro 20 (2019 edition) - WIndows 10 pro, 64 bit Any assistance on this would be appreciated. Thanks.