P: Changing shape fill color scales path instead

Thanks all for your patience. This issue has been resolved and will be availabe in the next release.

Hey @J453

Now I think I figured out what is the source of the issue and it's quite abstract. "Live shapes" don't like dual monitor setup (possibly with different refresh rates or resolutions)

Steps to reproduce the issue:

1. Use dual monitor setup with different resolutions / refresh rates

2. Create new document

3. Create an ellipse.

4. Duplicate the ellipse.

5. Merge the shapes to a single layer.

6. Rotate one ellipse by hand to some uneven value like 20.6 dgr.

7. Without changing selection to the other ellipse, try changing fill - you get scale paths bug pretty much infitnie amount of times with every click. I think the program tries to snap points to pixels or something like that, but calculates it incorrectly so tries to redo it every time.

8. Undo the "Scale paths" operations. Convert the rotated ellipse into a regular shape, to do that: add a shape within the rotated ellipse, select both shapes (don't touch the not-rotated ellipse), use "merge shape components" in pathfinder to turn live shape into a regular shape - it looks the same now, the rotated ellipse is just not a live shape anymore. Click the fill color. The "scale paths" operation might happen once or twice as the points snap to pixels, but it ends at that.

I'm not 100% sure if dual monitor setup (different resolution / screen refresh rate) is crucial to that, but I assume it is, I didn't have this issue when I tried working on a single monitor as a troubleshooting step in the past (although I didn't know specific steps to recreate it) and I think if it wasn't part of the source of the problem, more people would report it.

User @paolor94677584 confirmed they use dual monitor setup with different resolutions and refresh rates and that the steps reproduce the issue.

@sboxle @Noah24222334l7ij can you clarify if you use dual monitor setup and if the monitors resolutions / refresh rates are different?

So it looks like I can recreate the issue. This has happened to me many times. 
Make many shapes on one layer. Then roatate just one of them. Click on Fill at the top and it will Scale Path

By @łukaszz35275447

Yep, this is often my approach and I keep encountering this scale bug. 
Just had it happen after duplicating one shape on the same layer and rotating it, then trying to fill.

Often occurs when the aspect ratio is locked，Unlock and return to normal.

So it looks like I can recreate the issue. This has happened to me many times. 
Make many shapes on one layer. Then roatate just one of them. Click on Fill at the top and it will Scale Path

When it happens to me, selecting the Shape tool allows me to change the color. 

I can't believe Adobe 2D software are the top world has to offer in 2022. This bug persists despite many people reporting it, there's no major breakthrough in both PS and AI for at least last 7 years. This industry needs it's 2D Blender. I can't believe I can just as well use PS 2017, even better - there are no bugs like this one, there are far less graphical glitches like layer not refreshing it's visibility etc. By now we should have a node editor, which is a standard in any 3D software even for 2d parts (textures). Instead I can't even keep swatches in a library in a way that changing the swatch changes the color wherever it's used in the document. Having ability to for example dynamically combine masks using live data from other layers and applying transforms based on specific calcualtion I want to make using inputs I choose - It would be a dream, while it's a standard in shader editors in not only 3D software, but even in Unity or Unreal Engine.

At least make it so it's better and less buggy than a version from 5 years ago. You took away Adobe Preview, you added some stuff that's rarely needed, like AI filters and the library feature that's not even dynamic as I mentioned. But the main difference is a bunch of bugs and stability worse than the 2017 version I'm using. 2D software looks like car companies before Tesla and like Autodesk stuff before Blender. But they at least tried to not break it, while not caring about big improvements. The worst part is I don't expect you to try and match setups with one of us to find the issue. After all, where do we go, to competition? Prove me wrong.

Sorry (not sorry?) for the rant, but Adobe is the most expensive software I'm using in last 5 years and it's the software that improved the least. I'm worried about Substance Painter now, but in 3D you actually have some competition to be wary about. I don't think I'm getting the value I'm paying for if I have to resort to using 5 years old version, because you can't fix issues that multiple people are reporting.

Hi. I tested today, it seemed to be working fine with a single display. Now I have both monitors connected to the same GTX 1080, one by DP and the other one by HDMI and the issue is back. They have different resolutions and different refresh rate, alhough I don't see how different refresh rate could be connected to the issue. Moving PS to the secondary display doesn't fix the problem.

So it looks like many people reporting this issue (probably all of them) use dual monitor setup.

@łukaszz35275447 Displays plugged into different graphics cards can cause problems. I wouldn't expect this to be the type of issue that would cause (usually it's crashing or scrambled images/redraw issues). Can you plug both monitors into one card? If not, can you try with one monitor to see if you can still repro?