Fixed: Pixels option is greyed out for Line tool Photoshop 22.0

[seanp99402617]

I'm liking most of today's update for PShop, thanks Adobe. 

But, I went to use the Line Tool (part of the Shape Tools) and the option to draw with pixels is grayed out. I can draw lines with paths and as a shape, but no longer with pixels. The pixels option is available for all the other shapes (square, ellipse, the new triangle, polygon, custom shapes, etc.), so I don't know why it wouldn't work for lines. 

Does anyone know what happened? 

{Moderator Note: PS-57177}

[goodboy juan]

The thing that blows my mind is it was effort to take away the pixel option for the line tool and make it needlessly worse.

As someone who does a fair bit of pixel-art, having no ability to quickly draw non anti-aliased lines is a genuine pain.

Can't say I'm optimistic about this ever changing judging by the age/length of this thread...

[Grant5C25]

yea and the complete lack of acknowledgement from Adobe - and the fact that this thread is marked as 'solved'

[dayzed007]

The trick here is that once an Adobe moderator marks it as 'solved' they never need to look at it again.  They will mark it as solved even if the community doesn't agree, as is evident in this thread.

The best way to make someone in Adobe read your concerns is via the feedback tool, not the community – which is evidently designed to shut the community up and just complain to each other (think screaming in space)

https://feedback.photoshop.com/

[Lucy5CA5]

I solved it...by installing Clip Studio Paint! The pen/ stroke method adds several steps to what was a simple drag and drop, and sadly with dire results (wobbly af lines). It just wasn't good enough for the pixel art I needed to do.

[joseb88794817]

I've been using it and love it. Maybe it was the brush you were using? I believe you can import PS brushes into Clip Studio. 

[charlielavoy1]

Yeah, wow I can't believe I've been working in this industry so long and I never gave Clip Studio the time of day. That's what I get for being a generalist for so long, I guesse. I tried it out last week after reading this, and it's pretty exciting to find such a robust tool that's so much more focused on drawing and painting. I'm migrating my current job - a children's book - over to Clip Studio immediately. Nice work Adobe, you lost another one.

[Lucy5CA5]

Yep, I was the same. I should have tried CSP sooner! Anyway, glad I was able to help. It's so much easier for the illustrations I need to do.

[Convergnt]

Love this suggestion for our pixel painters. Thanks.

[whistlerpro21]

It seems because Photoshop now supports stroke on the shape mode of the line tool, that the developers have removed the old 'go to' method most people used to get a line. Though frustratingly the stroke tool is seemingly set to 'inside shape' by default, so anyone using the line tool will have to find the option to change this before they can successfully create a line. If this fix was made by default, a lot of the complaining would disappear. 

[KazVorpal]

Yes, and that's a very amateurish development error.

1. It almost certainly means that the first time the developer was testing it, the tool didn't work but — having just made the change — he instantly knew to switch it to Outside, and then it worked.

2. Instead of taking the initiative to change it to default to Outside, he then showed it to the Scrum teammate that approves his item in the burndown chart, who responded "but it doesn't work" and he was like "oh, set the line tool to Outside", and the guy was like "oh, okay" and approved the item.

3. At the end of the sprint his manager tested it (one would hope), sent him an IM saying "it doesn't work", and he had to reply "set the stroke to Outside", and the manager said "oh, okay" and was satisfied.

4. At some future point the QA team was testing it, and needed that same explanation. They were told to set the tool to Outside, and for some insane reason they said "oh, okay" and accepted this disastrous quirk without question.

FOUR points of failure. 

FOUR development steps where any competent professional would have stopped and said "the end user won't know this" and taken some action.

A good development team does not take for granted that an explanation was necessary, because that means the user is going to need that explanation.

Either you:

1. Fix the damned tool to default to Outside (duh), or
2. Add a new development item to the board for next sprint, called "change line tool to default to Outside even for existing users", or
3. Set up some kind of tooltip/warning to explain to ALL users that they need to manually change it to Outside. And be 100% certain all users will be painfully aware of this exactly when they are first using the line tool. 

I am formatting all of the above steps with the assumption that Adobe is the kind of soulless bureaucracy who went from Waterfall development to the mindless, faux-agile bureaucracy of something like Scrum, ergo all the crap about adding items and having peoeple approve the mistake. Such a bad development environment does not encourage the creativity and initiative necessary for a developer to simply do things right, like with this line tool. He tends instead to do what he's told without question, his primary concern being to cover his ass. Same with the scrum teammates, manager, and QA. The bureaucrats in charge like this horrible environment of blind obedience, because it makes the blame game easier to play.

And that's how they ended up in the situation you describe.

Hmmm...

"Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied."

I don't know why I'd've expected Adobe to install a third party message board for their "community" that worked well. All I did was use the WYSIWYG tool to format the above message. I typed no HTML of my own. But it's so poorly made that it managed to break its own HTML insertion. I hope I'm not overlooking some subsequent change that makes my post harder to read. 

Oh, and now it won't let me save the post, even after it ostensibly removed the offending HTML it had inserted in the first place. The Post button simply does nothing, it doesn't even reiterate the warning.

I'm going to have to paste this into an editor that lets me see the underlying code, and fix it myself.

Okay, nth try at saving this, now with all formatting stripped out.

If this saves, it'll be another grand example of Adobe not even being able to handle a simple user-oriented graphics task.

[matsholmberg]

This is crazy! Adobe clearly don't understand how we use their products. Seeing how this issue still hasn't been adressed, in spite of numerous replies to this thread, is really bad. I've always considered Adobe as a company in touch with the users, but this issue made me doubt that notion. 

Fix the issue now, plz. 

[c.pfaffenbichler · Accepted solution]

In Photoshop 22.3.0 this issue appears to be rectified. (But the Pen Tool seems to be afflicted with other issues …) 

[Martin Sch]

The line tool works again with the latest update (Thank you Adobe for fixing it).
@  c.pfaffenbichler >   The pen tool seems to work fine as well.

[Akash Sharma · Accepted solution]

Hi All,

Good news, the Pixels mode is now back. For more details on adjusting line weight see Create lines and arrows using the Line tool

To update Photoshop to 22.3, click "Update" in the Creative Cloud desktop app next to Photoshop. See: More detailed instructions for updating

Let us know your feedback!

Thanks,

Akash

[Martin Sch]

Thank you for fixing it! It works perfectly - as before. 

[dayzed007]

Thanks.  It's 'almost' the same as the status quo from before (and the 25 years prior) (the preview is odd)

All I can say it that it's about time.  Assuming you guys work in agile I guess your sprints are 5 months in lenght 😞

sad/

[Anti-Alias]

@dayzed007  I agree, there's something weird with the preview. Although, it's better than not having it, things should have been put things back the way they were.

[JJMack]

Now weight can be 0 and Arrow heads are no longer a percentage of weight for  any percentage of 0 is 0 you need to do the percent thing for each weight in your head and set the correct number of pixels for width and length. One problem with the new line tool is Adobe did not limit the weight to 100 like the old line tool. How do you like the 400 px weight line?

If you do not do the math in you head and set good values for Arrowheads they will mess your work up if they are not a 100%+ percentage of weight.

Not as good as the old line tool but its can be used. It is more a wacky stripping tool now.

Line weight should be limited like the days of old and arrowheads setting should be relative to line weight not a number of pixels so you don't have to set arrowmead setting every time you change line weight.  Like daye gone bye.

[Buzzingbee]

Thanks Adobe. I really appreciate it.

[Convergnt]

I'm glad it's back. Thanks, Adobe.

[seanp99402617]

Thanks for listening to your users, Adobe, by restoring the pixel line tool. 

Let this be a lesson.

[ZsomborB831]

Hey 🙂 I found the '1 pixel black line' problem solution. simply click the Aling Edges and it will be only 1 pixel not 2 and  and it will be true black.

[PSDDude]

Thanks for asking this. The answer will go right into my how to draw a line in Photoshop tutorial [link removed] !

[arggggggggggggggggggggggg]

The option to load 22.3 doesn't appear on my CC app, and I can't use the pixels option of the pen tool.

[jane-e]

The option to load 22.3 doesn't appear on my CC app, and I can't use the pixels option of the pen tool.

By @arggggggggggggggggggggggg

You replied to a thread that started in 2020. Adobe offers the current version (now 24) and the one previous. You might want to start a new thread and include screen shots so we can better assist.

Jane