Hi CandyFace, don’t know if this has anything to do with what Jose reported but I have noticed this also in the version before and maybe you are aware of it.
The problem is a lag in pen strokes directly after an undo. It only is the frist pen stroke after the undo that lags not the following pen strokes after that, they are as fast as they should be.
To see this problem you just have to draw a bit outside the canvas (I set the camera to 1920x1080 in my test) the further outside the canvas you draw the more clearly you will see the lag.
A video of me drawing and undo’ing some penstrokes:
Thanks for bringing that to my attention Manu, unfortunately there’s no easy way to fix that currently, at least not to my knowledge.
The delay is caused by the fact that the update of the canvas after undo’ing, requires a reset of the mypaint surface, because mypaint is not aware of undo/redo, that’s pencil2D state. This basically means removing all tiles and re-adding them based on the undo/redo image. As the image gets bigger and bigger, the operation takes longer.
Changing pressure graphs does not update the stroke placed on the canvas up until the attribute slider changes.
This has been fixed now.
Using the colorize attribute automatically crashes the app. Just try using the slider and the app closes.
This one is a head scratcher… it’s seemingly not a bug in pencil2D that’s causing the crash but a bug in the mypaint backend… i’ve looked into it a bit but i’m not certain what’s causing the behavior.
I will ask the mypaint developers… maybe they know what’s causing it.
Fixed brush base value would not be accounted for when modifying brush input in brush configurator
Fixed an internal bug in libmypaint that would cause a crash when using the colorize brush setting
Not all brushes have brush dynamics, eg. pressure, therefore now the brush mapping button is disabled for those settings, with a tool tip explaining why.
Many thanks for the update, I’ll start using it right away.
By the way this is probably a older bug but I thought I’d record a video of it anyway.
If I paint or skecth on a frame and accidentially change the frame ( with a keyboard shortcut key ) to the next while holding down the pen, it will ruin the frame I accidentially switched to.
Been playing with the MyPaint brushes. So far I found them to be stable. I’m really happy to get this Pencil2D upgrade. I’ll continue to flex it and report any problems.
Hi Jose. Two weeks ago I began looking into the underlying brush files and the settings. I couldn’t make your breaks happen and be stored like you said. But I did backup the brush directories and just reset them as I test. I did get some slow tracking and segment breaks on my wacom Intuos but not with the mouse. But! I’m pleased that this works and hope to see it become more stable. I’ll be installing my new cintqe this week and try again.
@gtmike Hey mike! thank you for taking the time to test this branch. I’m sure CandyFace will welcome more testing and feedback from an actual production workflow or detailed piece.
Overall the less issues we find now, the better will be once the engine is replaced in the main version of the software, so take your time with testing
We hope version 0.7 will be the one to host this incredible achievement
Good news everyone! today I had some time to bring the mypaint branch up to date with master.
This means that I can now distribute to all platforms again.
The palette bug should be fixed now. I’ve made some changes regarding to how the mypaint backend loads existing bitmap data, some of it may have slight performance impact… the change however should cause less lag in general when being ready to paint on a new frame, using undo/redo and the like because we don’t have to load an entire image but instead can only take the chunks that are being painted on.
There are still performance issues to look into, it simply doesn’t feel quite as smooth as i’d like, so I’ll probably be focusing on that for a bit.
Still have problems using my tablet. It seems Pencil2D have problems calculating the brushstrokes.
Still, it works fine using a mouse. I tried painting with it and I didn’t encounter any problems. I did only use a few brushes so it is not a comprehensive test.
@MrStevns I can confirm I’m having the same problem as Ralmon, and it’s actually pretty bad how the strokes lag. I recorded a video but I’ll upload it later.
Personally I also think this problem comes from the Master branch, since a very similar issue has been a problem ever since 0.6.0 version (remember the reed pattern arc, it comes since that time).
IIRC The TabletInputEvent fired by tablet devices on Windows has always been laggy compared to the mouse event. This affect various parts of the app as a whole. We might need to debug this again.
I can test whatever build you want me to in the future, however I currently don’t have Qt Creator nor the Pecil2D master repo in my current workstation, so I may not be able to help much with live debugging, but any other build I could test ok