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

Photo 2.2 Missing Brush Size Input


Recommended Posts

As the title says, the brush size input from the brush editor is missing on version 2.2. I'm usign Windows 11, haven't checked any of our Mac devices yet.

- Enrique

 

affinity_missing_brush_size.png

• Frankentoon Studio - Tutorials and Resources for Designer, Photo and Publisher

Follow us on Instagram  |  Follow us on Twitter |  Like us on Facebook

Link to comment
Share on other sites

This has been logged as a bug

 

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

9 minutes ago, carl123 said:

This has been logged as a bug

 

Whoops, I'm sorry I missed that one.

 

Maybe a moderator could delete this post? Thanks!

- Enrique

• Frankentoon Studio - Tutorials and Resources for Designer, Photo and Publisher

Follow us on Instagram  |  Follow us on Twitter |  Like us on Facebook

Link to comment
Share on other sites

6 hours ago, Frankentoon Studio said:

Maybe a moderator could delete this post? Thanks!

Not necessary. They'll just link this one to the same bug report.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

  • Staff

Just to confirm, I've 'bumped' the development report for the issue with this thread now - I can also see that it's been tentatively fixed by our team already, pending internal testing & therefore should hopefully be resolved in the next update :)

Please note -

I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time.

Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible.

Many thanks!

Link to comment
Share on other sites

58 minutes ago, Dan C said:

Just to confirm, I've 'bumped' the development report for the issue with this thread now - I can also see that it's been tentatively fixed by our team already, pending internal testing & therefore should hopefully be resolved in the next update :)

Hi Dan, thank you!

- Enrique

• Frankentoon Studio - Tutorials and Resources for Designer, Photo and Publisher

Follow us on Instagram  |  Follow us on Twitter |  Like us on Facebook

Link to comment
Share on other sites

  • 4 weeks later...
  • Staff

The issue "[Win] Brush dialog is missing the input field for brush Size" (REF: AF-380) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Link to comment
Share on other sites

58 minutes ago, iconoclast said:

I installed the update to version 2.2.1 some minutes ago, but the input field is still missing. Windows 10.

First, to @-tag a user, you need to:

  1. Type the @ and start typing the user's name
  2. Select the name from the popup menu.

It must show as a highlighted field in the post, or the tagging did not work.

But second, as the post from Serif Info Bot said, 

On 10/18/2023 at 9:55 AM, Serif Info Bot said:

fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta

And it will soon be available as a beta. Installing 2.2.1 won't get you a fix.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

I would assume that 2.3 is going to start at the beginning of next week.

Lenovo IdeaPad 5 Ryzen 7 5700U Rx Vega 8 graphics 

16GB RAM (15.3 usable) 

Acer KB202 27in 1080p monitor

Affinity Photo 1.10.6

Affinity photo 2 2.4.2 Affinity Designer 2 2.4.2 Affinity Publisher 2 2.4.2 on Windows 11 Pro version 23H2

Beta builds as they come out.

canon 80d| sigma 18-200mm F3.5-6.3 DC MACRO OS HSM | Tamron SP AF 28-75mm f/2.8 XR Di LD | Canon EF-S 10-18mm f/4.5-5.6 IS STM Autofocus APS-C Lens, Black

 

Link to comment
Share on other sites

13 hours ago, walt.farrell said:

First, to @-tag a user, you need to:

  1. Type the @ and start typing the user's name
  2. Select the name from the popup menu.

It must show as a highlighted field in the post, or the tagging did not work.

But second, as the post from Serif Info Bot said, 

And it will soon be available as a beta. Installing 2.2.1 won't get you a fix.

Hi Walt and thanks for the tip! I was afraid that I did something wrong. Strange enough, I just opened my post to edit it and did nothing else, but it seems to work now.

Concerning the second point: I got a Mail from Serif some days ago that claimed that the problem would be solved with the next update and is already solved in an actual beta. And that I shall write a post here if the bug is not fixed with the next update. So that was what I did. But it's no problem for me to wait for the next update. This is not the worst bug I ever met. Thanks anyway!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.