Closed teleportingtortoise closed 6 years ago
This was my bad. The latest Alpha should work if you check right now. Well, a couple things-- you should be looking through the history and NOT downloading "pull request" builds unless you really want to try some wizbang feature. On the other hand, I shouldn't be spamming the builds with these builds that don't work. It's Pull Request 853 that is broken, so just avoid that one.
So, I'm going to refrain from any more commits on 853 until I can figure out what's wrong with that particular branch. Sorry about that!
Thank you for the quick reply! AppVeyor doesn't list anything newer than the last version I tried which was 332 / pull request 897 (though, yes, most of the ones I've tried were pull 853). I can always return to 324 for now, so it's not a big deal, but I thought I'd bring it up. AppVeyor history lists every build as a pull request so not fully sure what I should be grabbing? The Windows build on the MyPaint website is still at 1.2.1 so it's missing a couple features I've gotten used to having. I will admit I got in a (bad) habit of constantly updating MyPaint for no real reason from my time in ArchLinux though haha.
Oh, also there seems to be an issue with files being saved with an relatively large margin of unused space for quite a few of the AppVeyor versions now, should I create a separate issue for that?
It's all good! I've always been impressed by the fast responses and work of the MyPaint team. Thank you again!
Actually, I think #902 is baaaaack
Yes please make a new bug for the other issue. Although, if you are using 324 that is another pull request with perspective mode, so make sure you note what version you are using. Build 275 seems to be the latest version of the official master branch, and it seems to work.
The newest build 333 and onward should be fixed now. I tested 333 for sure.
334 works too, feel pretty good about this
Thank you for letting me know which is the latest build from master.
334 works great, thank you!
Builds after that refuse to start and throw an error. Here's the log from the debugger.
Running Windows 10 x64 latest update.
Thank you for your time and sorry if this is a duplicate. I looked around but the only ticket I found with this error was old and closed.