debraspicher

Laptop results MSI PE60 6QE Windows 10 Intel Core i7-1600HQ @ 2.6Ghz RAM 16.0 GB (2133mhz) GTX960m /w Intel Graphics

Hmm. I'm just using the standard D.O.C.P profile for my mobo, so nothing special there. I did install the Ryzen chipset drivers and with them, they include the Ryzen power plans that can be enabled in Windows 10 and are optimized for performance. I am using the Ryzen High Performance version. In looking up articles related to it, I noticed that 3000 series (3700X being well-noted) had issue(s) with reaching advertised boost early on launch and so AMD released BIOS fixes at some point after release. My BIOS is upgraded fairly close to latest, so maybe that is a factor as they update ADESA as well. AMD releases tweaked power profile for Ryzen users on Windows 10 https://www.kitguru.net/components/cpu/matthew-wilson/amd-releases-tweaked-power-profile-for-ryzen-users-on-windows-10/ AMD's Ryzen 3000 Boost-Fixing BIOS Leaks Out, We Test With Ryzen 9 3900X and Ryzen 7 3700X https://www.tomshardware.com/news/amd-ryzen-3000-boost-frequency-bios-fix-agesa,40359.html

Interesting. I'm on a Ryzen 5 3600 and my vector section tested significantly higher. They should at least be comparable. Rastor Multi-CPU was in the inverse though. Differences in RAM maybe?

Microsoft Windows 10 Home (Build 19041) AMD Ryzen 5 3600 @ 3600Ghz; Mobo: Asus X470-PRO 32GB DDR4 (3000Mhz) NVIDIA GeForce GTX 1060Ti 6GB

Thank you all for everything you do. Downloading updates now from account page.

For what it's worth, I'm on driver ver 6.3.38-2 ... my model is in my signature. No problems here (so far). I've had issue(s) with Wacom drivers on Windows in the past that required a downgrade, so it's not unheard of.

Limited tests on my end show better performance with the tablet. Seems quite smooth.

I'm on a dual screen setup. I haven't noticed this issue (yet). A question, but is the monitor it is moving back to set as the "main" display. Many of us use the main display for our applications and secondary maybe for less important, so it's possible others may not run into it as often. Since you're using a Wacom, if that is a secondary display then maybe something changed in the software to trigger this. You can use use Windows Key + Shift + Left/Right Arrow to switch windows between screens instead of dragging. That doesn't move the floating panels I don't think, but maybe you can have a workspace saved that you can "reload" when this happens. At least until it is fixed.

It does, unfortunately. I played around with Coverage Map to make it look better, but didn't try to export it. Hard to know how often I will need to use that workaround.

This is what I needed. Thank you!

I saw a "solution" (painful) that involves changing Coverage Map in Blend Options. This helps with the anti-aliasing issue and doesn't pick up in pixel view as far as I can tell.

Is it possible to add a global swatch from your currently selected fill? I have been using dropper to add.

Maybe someone can explain what is happening here. In support area it was suggested this is an anti-aliasing issue. The black is showing underneath the green layer. The object used as a mask is the same Crossguard object. Theoretically, they should cancel each other out enough that it nothing should show through? Unless I am doing something wrong. Source file: sword.afdesign

So it is a bug?

I searched forums. I still can't figure out how to correct this. It's showing a black line. The object that is being used as mask is over bounds and I have "precise clipping" enabled (not sure it matters), so not really understanding why it is causing an outline. sword.afdesign

My tablet can paint fine at first. Color picker will sometimes freeze the window. It will stay on the tool cursor and I can't interact with UI, change layers, undo, nothing. Sometimes it is when I change brush size. It is fairly frequent. I seem to be able to paint fine with pressure sensitivity... as long as I don't do much else. The solution for me has been to minimize and then re-maximize the window and then I can have more time to work until it freezes again 😶

I add my vote.

Understood. This thread was meant to report potential bugs for the beta, not meant for troubleshooting. I noticed in your screenshots you are using the regular A.Photo to test, so you may not have seen we are in the beta reporting section.

Bug #1/screenshot 1 is my boo boo. The Beavis layer was originally full color in the file I was working on (like the second screen so that's odd), but somehow got changed to greyscale. I have no idea how that happened. So that explains why I was getting the grey then! Thanks. The second screen, I'm not so sure if it's intentional or not. You'd have to look at the Layer panel to see how it is done as I did not include it in the .aphoto file in order to keep it from being confusing and to save bandwidth on my side. The difference is the "secondary layer"/"sublayer" is modifying the original image without Layer Fx, but instead of being limited to what is opaque, it is clipped to the layer "viewport". This may or may not be intentional. I was attempting the first method because the second was not working as intended (or so I thought) and so I discovered the second in a roundabout way.

Result expected: Gradient blending win. Result achieved: Gradient color to grey blendy mess. I only discovered this because I couldn't also add a sublayer(?) to the image itself to achieve the same effect because it effected the entire "rectangle" space even though the only pixel/opaque values are the cartoon obviously so this was meant as a workaround... Not sure if this is intended or not: fire.afphoto

There's a way to do 50% grey in Photoshop by setting input/output values numerically. It would be nice to be able to at least see the numeric change in Affinity as well for the input/output nodes (the "dots" on the right/left). I believe it is an input/output ratio (128, 128) in PS for 50% gray. I honestly don't know for sure what it was called in that field as I don't have PS anymore. It's very useful to be able to type in/note because at 50% grey, one can alter the Curves adj layer in a linear way by changing layer to Soft Light/Overlay masks with no change to appearance. It allows for a more linear/subtle change to histogram since 50% is essentially "no change" in that mode. It is difficult to tell if it's "true" 50% gray without numeric values displayed, but having ability to type the number in when making other adjustments to curve is useful as well. The preset function is fine for this for now. Obviously can't tell for sure if it is "on" without a numeric output. Looks like I am slightly off on the right side in bottom example but can only tell zoomed in! It is what it is. :^P Sorry if this is a strange request. Hopefully I've explained it clear enough. Adjustment Layer set to "Normal": Layer Set to "Soft Light" and example...

Hard to tell with image compression, but it doesn't look like there is subpixel rendering in AP UI text when compared with desktop text. At least in the screenshot.

Have you reported this as a bug?

I think a great first attempt. A small tip to help you with troubleshooting: Try creating a version in black/white, especially something that translates well to stamp sizes. It is not only helpful to have it on hand for situations where you can't print/utilize full-color, but also you will also see more easily what can be simplified. You'd be surprised what limiting yourself will do for your designs as it forces us to think critically.

Yeeah... this is pretty much 100 reasons I think Serif shouldn't ever buy a license from them.