debraspicher

What specific use case do you need 1% -/+ usages for? Just curious. Maybe others can advise a better solution. This may or may not help either, but if these are very specific zoom/positioning situations. The Navigator lets us set "View points". These can be stepped iteratively through using F-keys/etc, but have to assign it in the shortcuts area. That won't work for fluid situations, but if you're frequently having to go back and forth to one portion of the piece, it can be set on a per-document basis. We can rename those viewpoints as well.

Same behavior here, but it took a moment to reproduce. I don't use scroll wheel for zoom. Scroll wheel will not work on my setup unless I hold it down while zooming. It does a micro-pan vertically instead (similar to website behavior). 23.02.06_01-21-47-PM_NV12_1920x1080.mp4 I did check scroll wheel settings to see if the increments there impacted the percentages. Seems to be same steps/increments as yours regardless of mouse settings. Edit: BTW, this is Monitor 1 on my setup (125% DPI/4K)

Do you have Gsync or Freesync (AMD) on? NVidia drivers did similar to my display when I had it on for windowed mode.

That's been their auto-reply on Twitter, basically.

Their text engine needs a rework it seems, for many international features to be added. This is the context for some of the commentary that you're seeing on here: Re: eventual RTL support:

No issue here. Just used File > Export > PNG [Preset=PNG] Result:

There is also Feather and other options in Select Menu itself. Just in case others wanted to know where else to find the option.. I use it a lot for pen tool created selections and if I need just a bit of fuzz

Seems to only be an issue with the MSIX version. The "white" might actually be the OS color setting (in my case, bright green). The App version has the colored background like the top right of the search results, just as an example. My desktop icons are usually disabled as well. I launch everything through taskbar and Windows Search. Windows 10 Search: MSIX Version MSI version

Agree 100%. Hold off on purchase until it is supported if it is super important for you. So far, the word is it will take a long long time (mind the clickbait-y title below):

I would still ask the artist to be sure lol

It does work for multi-stroke and multi-fill scenarios. (Please forgive my trespasses with the color design work here)

Surprised no one has mentioned the Style Picker Tool:

While I know it's not exactly what you are looking for, this has some resources in it that could prove useful for your use case. It is a free pack for Affinity owners. https://affinity.serif.com/en-us/store/free-content/ And just so you don't miss these, this is a content pack that was issued for all V2 owners that can be also be claimed.

It's brushwork. Disabling the texture layer and then playing around with the actual Pixel layers, it's definitely visible. To me it looks like a simple round or maybe variation of it. I personally like painting in ovals at a 45ish-deg tilt for creating quick brushwork and that's initially what I thought it looked like.

They are on Artstation if you want to find and ask the artist. This piece is up there but I didn't see any commentary about brushes anywhere. I don't see this in my Samples as an option. My samples are far fewer in quantity so wondering if maybe they came with one of your brush sets? The one time the new brush history feature might've justified itself lol... Of course there's no icon for it in the Layers panel.

They could certainly try that to see if it can achieve consistent results, but then both displays will suffer in being limited to sRGB capability, sadly. It's like calibrating a Ferrari to run with a Pinto. (I'm not a car person, but that sounds accurate) FWIW, I prefer Adobe RGB as well for image output these days. Browsers and even many applications are way better now about color management and so can easily read embedded ICC profiles. 10-bit displays are also becoming more common place. And since mobile tends to be ahead of the curve in terms of display technology, then high gamuts displays will become even more the norm. sRGB is certainly safer for web design, etc, but for illustrations/etc, I still have sRGB in my presets because it's absolutely necessary to work in it and some applications will do special handling in certain areas (such as thumbnails). (Edit) I basically do not want the application handling any sRGB conversion, it'll look like crap). However, I prefer to "work in" and proof for Adobe RGB in 99% of cases. That extra "pop" in color is much more pleasing to the eye than trying to work out compatibility in sRGB. So I'm OK in those situations to convert workspace (Adobe) to sRGB on output using a preset and it works out much better than the application/browser handling it itself and that is where dull colors, etc is virtually guaranteed. (I'm not an expert in this area, btw, just an enthusiast) I still do calibrate in ICC v2 because I remember for a long time, v4 support lagged behind v2 in many applications and some browsers. It's probably changed for the better now, but I keep it there in case I open something that it doesn't support. It's still the default in X-rite's bundled app for whatever reason.

OP's question was very straightforward I think. "What do these lines indicate by color/behavior?", essentially? Maybe I am misrepresenting their query. I do feel like I sometimes interpret intention differently than my fellow users and that's maybe a flaw. (BTW, cool dog photo, @Janabanana). My bigger trouble is sometimes determining what a user is actually asking. If I can get to the meat of it, my style is to avoid too much nerd talk and word vomit and to just give them the straightest answer that I can think of. Sometimes it ends up (my answer) being too straight forward and it leads to cross-talk or the user asking something else related that I could've answered, but sometimes that's preferable if other users may know more than me on any given topic. Add to this, the forums can also be intimidating or even annoying to participate for new members. Add another layer on top of that apprehension, they are already maybe frustrated by a software issue and have come here as a "last resort" to deal with perfect strangers. They may not be people people. So IMV (not in any way, shape or form gospel), it's not always necessary to point back to documentation, though I think that Affinity's videos and documentation as good as they are are under-shared, underappreciated and valued. So for me, feedback is about quality, not necessarily what I "think" the other side should be hearing. To give documentation instead of straight answer to simple questions can leave the feeling that we are suggesting they do a self-examination before attempting to get help. That may not be the intention, but that's how it can come across. I try to consider other's intent, but I have personality quirks like anyone else, so I may even get it really wrong sometimes. Though, adding links to documentation to point them another direction for further reference is rewarding in its own way and is a way of sharing another person's perspective. (So I think just do what you're doing already whatever that is). It's a good way to encourage them towards using documentation. I use screenshots personally when I know there's something super specific already in documentation and that's my way to encourage them to go look there for the answer. Let's also not forget though, we do all this for free. So basically, do what you will with your time. I'm frequently battling a toddler running amok in the background while trying to be productive, and so sometimes I'm not in my best form when posting and especially with reading comprehension. My worry is I misunderstand something on here and get it completely wrong on intent, but also, I think these forums can be weirdly competitive in terms of "helpfulness" department. Like there's an unsaid bar being set and that if we don't get it exactly right, there's a participation trophy we miss being handed out (those thanks trophies, for example). It's quite OK to get it wrong sometimes and I wish sometimes the vibe could be more relaxed. Also, last but not least, some people are just plain crazy on the internet and will yell & scream at the first person in line and while that's entertaining at points, most of the time it's just another hassle. TLDR: We badly need an 'off-topic'/'work discussion' whatever forum so we can brain dump and that way, people can learn off each other how they actually use the programs, instead of small snippets. Basically, word of mouth but in more vivid details. I do think that people come here for more than just FAQ information.

❤️ Thanks. Yes, I misread it as first display since it is the first attachment. (When I read first time, I thought they were in order) The secondary monitor then is using the sRGB IEC61966-2.1 profile which is a color standard, not a monitor profile ("sRGB Color Space.icm"). See below, it is in my system as well: That's why I also said I may not understand their "aim", because setting as default profile may be intentional. Color management is very complicated, so there may be other ways of doing things even I'm not aware of and I'm open to that. Still, I get good results with additional displays and leave sRGB/Adobe/etc color proofing to applications (Affinity, etc). Last time I tried to a default sRGB profile configuration (during my CRT days), it only produced a dull display.

Thank you for clarifying. In short, your first display is using a profile not designed to be used for color management in monitors. In this case, it's more for output (web browsers, for use in applications, distributing media, etc). It's also being contrasted against a profile with significantly higher color gamut (more saturated). I own an X-Rite but I'm not familiar with the software you are using. I recommend to use a hardware calibrated ICC profile for the first one, not anything OS-provided. It will likely limit your contrast. I've color managed quite a few displays over the years and I can get multiple displays (2-3 at a time) to be fairly close provided the monitor itself is up to it. sRGB was intended to be a "web safe" profile to keep imagery consistent across multiple display configurations. As it is, monitors have gotten much better over the years that sRGB is not a real struggle for them. (So you shouldn't have to target it specifically) Another issue that can sometimes crop up (if this does not apply, just ignore...), if one of your monitors is using HDMI output, be sure that its black level is set correctly in the OSD. Sometimes when using calibrator software, it knocks that setting back out and it will utterly destroy contrast. sRGB vs AdobeRGB (Edit) More information on this topic for people who may find later in the forums: https://ninedegreesbelow.com/photography/srgb-bad-monitor-profile.html

You know, I never "notice" these colors. I saw the very blue line ("ack, It's blue! I like blue but not that blue) today when opening a preset so was a bit amused upon seeing this topic. No idea if that is the color it's always been. It's just there and I've become accustomed to it.

Maybe I'm not understanding what you're aiming to do. As I see it, the sRGB profile for the first display in the OP is an "out of the box" profile, iirc. It's not a display calibrated profile. In Affinity, if you required sRGB, you would load it within the program, but your monitors use the ICC profiles that are color managed for the appropriate LUT values so that that profile (Affinity->sRGB) displays correctly across displays. sRGB will limit the gamut to a "safe range", so it's not surprising you are seeing a dramatic shift in contrast. It's been so long since I've "hand calibrated" anything, so hard to know what I would recommend for the OS profile. If you were doing hardware calibration (not by the buttons on the monitor but an actual device), it should've generated ICC profiles and those are the ones you would be using for the OS. Then whatever your "output" profile (sRGB, etc) within Affinity.

VRAM is increasingly important for 2D. I don't recommend to skimp on it as that may just introduce another bottleneck. I'm using 12GB and I've almost filled it at times with editing one simple RAW, having multiple Affinity apps up and running. I'm sure other things as well, but Affinity takes a mighty big chunk out of GPU memory. 1-2 it would gobble up no problem. Basically, I know never to have these apps open anymore if I do decide to run a game. The benefit of adding another card as a secondary and setting it to primary renderer in Affinity though is theoretically it will have sole discretion of its VRAM, so there is that. We don't know what the OS does with memory management with two dedicated cards (probably not hard to google). Laptops might be a different story entirely.

On top of what @walt.farrell stated, if it is a driver crash out, it will show up in Event Viewer as such but also it should recover to a "safe mode" driver that won't have acceleration, but your display should come back. It should give you a delightful message alerting you to this behavior in Windows each time. The way to check if it is hardware-related would be to stress test it with something like Fur mark and keep an eye on it overtime for crashes. That could completely kill the card though so I don't recommend unless you have an adequate replacement lined up. You could try re-seating the card and that you are not using daisy chained PCIE power (for 2x connections). AMD drivers don't talk nicely with Affinity to begin with. The thread I linked is extensive, but in short, the cards are not pushed to their limit based on poor driver support, so hard to say how "stressful" the programs really are on the cards. However, Affinity loves loves loves VRAM... so if your VRAM is on the way out, that could be explaining the intermittent issue(s) you are having.

Each display must be calibrated individually. It can be done manually or with hardware (x-rite, etc). Hardware creates an individualized ICC profile for each monitor that contain the adjustments required for the LUT table to match. No match is perfect though, so there will always be some variation. Generally, this is done monthly because monitors change over time or as often as the user requires. For example, projects that require working with delicate spot colors. https://www.cambridgeincolour.com/tutorials/monitor-calibration.htm

I wish it worked similar to other programs. That is where the expectation has been set. An option to enable a "more realistic" preview comparable to other 2D programs would be ideal. I get the speed is a major factor for some, for sure, but even on a 4K, when I work large res, it's impossible to work with "preview" a full image without exporting. For your style of work, it's a particular point of pain because you have 1) a high texture work-piece 2) collisions of items highly dependent on edges for this texture "to work" 3) high contrast color and detail work To complicate the issue, there's also differences in "preview" pre-export when elements are rescaled (1). Pixel layers in particular don't suffer from degradation like in other programs when resized (2), so there's behind the scenes logic to consider there. There are real world trade-offs obviously.