Google Chrome has an interesting approach to this problem. Just another way to think about a solution

Actually, this is a really excellent point.

I have thoughts about why this is the problem. It seems that layers are being controlled by several different matrix systems.

Just running another test here is the blend file

actually, I have no idea what going on here it's just broken. This shouldn't be this bloody hard.

Doing more test I have realized this particular grease pencil was built in 2.93 and opened up it up in 3.0.
Recreating this in 3.0 seems to be working right now.

I don't know what you're planning for, so I will just throw this out there.

I have no idea what to say to you? What I can say is that I genuinely have good intentions.

Taking a look at all of this quickly and honestly I can't help but think blender compositor needs to be completely separated from blender and the whole thing just needs to follow some industry commonalities.

I love this idea
It makes it easer to focus on moving from one keyframe to the next

That makes a lot sense

Guys I am wondering if we should even have a to 2D mode?

Hey mate as much you want to do this with one fill it probably not the best way to work

Just thought should it say,

This is in response to the current development going on in: https://developer.blender.org/D9839/new/

Making grease pencil not so hidden and more accessible.

I wonder if this was set up for working through the camera? have you checked that?

woaaah thank you and sorry.

well done mate

yeah

I guess it doesn't matter if its a bug or not. This same idea is already respected in other areas of blender and works.

Bloody hell mate yes you have. Sorry that my testing has slowed down I am kinda busy with work.

yeahhhhh baaaaaaaaaaaaaaaaaaabeeeeeeeeeeeeeeee 💃 💃 💃 💃

Hey, mate, I took another look at this. Sorry that I have been busy.

I will take a look at this and see if I can get it to do the funky chicken. I will report back and let you know the results of the test.

In T73717#869858, @Ankit Meel (ankitm) wrote:

https://developer.blender.org/maniphest/query/advanced/

Ahhhhh gees now that ones worth writing home about isn't it.

Here is a single layer test as well

Ummmm gees guys i don't want to sound like an ass or being difficult, but what does that description actually even mean?

Ahhhhhhh yep. I see that now. Thanks mate.

Cambel can I ask how do you quickly search to find similar or matching reports.

ahh sorry about that guy I thought it worked with everything.

You need minions and a huge bloody award.

The stroke fill is a tileable texture.
That texture is driven by the position of the bone. This way it looks like it's driven on every frame.
The Appearance of the stroke is controlled by the scale of the array.
The Translation values should be left at 0.
This is what gives the appearance of the stroke.
The illusion of a stroke this way offers a very controllable stroke thickness.

Is it ok to say I think you might be incorrect?

Even though I filed the report I think with the refactor that has happened it should be a known issue just in case anyone else decides to report it since 2.83 is 4 to 6 months away.

Just an update on this. I tested this out on v2.80.75 and it seems to be working. I hope this can help.

In T73013#861247, @pistol ioan (pistoltoto) wrote:

lol, you want developers to watch 2 videos which include a video of 28 minutes to understand your problem?
And not to mention you also "cry" on twitter after this...

In T73361#860124, @Antonio Vazquez (antoniov) wrote:

I'm going to change this to Know Issue because we are thinking to refactor this feature.

Yeah, that looks about right. I just tested it out.

The next 15 seconds shows the problem with selections as well https://youtu.be/AhZGuuLzV1k?t=316

The blende file was zipped up. Here it is again as just a blend file. Attached is also the system info.

I think you're being hasty in closing this report. This is only one issue reported here.

Apologies for not being clear. It's just the icons in the material stack.

Sorry guys I think I missed this.