@michael campbell (3di) Try setting Large Cursors.
May 13 2019
May 12 2019
May 10 2019
If the Blender logo (in the Blender UI) got removed, what about fullscreen? There wouldn't be any indication that this was Blender.
On removing the icon from the window, double-clicking to close is too convenient for me.
Sounds like the same root issue as: T57758: Crash when appending Grease Pencil object and switching to 2D Animation workspace
@Antonio Vazquez (antoniov)?
May 6 2019
The startup.blend file will need to be updated as I can still crash 32-bit with invalid brushes in the 2D Animation template.
May 3 2019
@Antonio Vazquez (antoniov) Thoughts?
May 2 2019
May 1 2019
Apr 30 2019
@Thomas Kress (AnimationXYZ) You'd have to share a .blend file for us to see what exact issues and the extent of them are.
Not 100% sure, but if this is not a problem with 64bit builds and only happens on 32bit builds, then I guess this is expected?
Apr 29 2019
Hmm, I just tried with blender-2.80-337cac760ba9-linux-glibc224-i686 on my Ubuntu VM and I got a crash...
Apr 26 2019
Apr 24 2019
blender-2.80.0-git.1b839e85e142-windows64 same behaviour as T63481#658801
Maybe if the alignment wasn't offset?
I guess the global header toggle just needs to be removed...
Actually there needs to be a easier way to bring the the tool setting back. The only way in the viewport is to right-click close to a header icon...
Apr 21 2019
That's fine :) If you plan to fix bugs you are more than welcome to get involved.
P.S. Thank you very much for the footer. This is going to help so much.
@George Vogiatzis (Gvgeo) If your going to triage reports then it's best to assign them to the respective developer and not just mention their usernames, as notifications get overlooked.
Apr 18 2019
Ah I see...
AttributeError: 'Mesh' object has no attribute 'use_stroke_edit_mode'
Apr 16 2019
Actually I can crash x64 (edc1b0167518-windows64) with a file created in blender-2.80.0-git.e2102e991764-windows32 without ...\Blender\2.80\config\startup.blend and 2D animation template:
Apr 12 2019
Once this is decided blender.org, the release notes and user manual need to be updated.
Well I think that's it. I can't get it to crash anymore.
So are the template files going to have to get updated, as opening 2D Animation still crashes 32-bit?
Ahh... yes, the template files bundled with Blender would have the 'bad dna'.
After more investigation it looks like you can't open blend files (with GPencil data) on different architectures than what it was made on.
Apr 11 2019
- Open and press tab
Apr 10 2019
Thank you @Antonio Vazquez (antoniov) I'll see you in the Annotations todo task ;)
What I want to do is keep all 2D editors equal.
Yes, that's what I'm saying.
How are you making the UX more complicated? I'd argue it's more complicated now because there's no consistency in the Annotations Tool.
The topbar is Empty and we're talking about removing an option we already don't have...
I get even worse glitching when animating the camera:
Oh wow, I was not expecting the colour to be fixed, I assumed the new layers to be incompatible with the old GPencil colour pallet, but taking the last colour from the pallet seems like a excellent compromise considering only one colour per layer is allowed in 2.80. I originally made the blend file for the colour issue, but I'd thought it would be a limitation.
That's right, It's because you can't draw (in 2.79) on an empty image, so it reverts to the View. I'm not sure if there are technical reasons to this, the strokes are still visible after removing the image.
Apr 9 2019
@Antonio Vazquez (antoniov) Yeah, I pressed Enter after writing the title which submitted the report before I had filled it in.
I pressed enter by accident...
Apr 8 2019
I'm now getting a crash just by opening the 2D Animation template:
Apr 2 2019
No crashes on start-up for me.
Also after File > Load Factory Settings while in the 2D Animation workspace?
Also after File > Load Factory Settings while in the 2D Animation workspace?
If so, does it also happen when adding a new grease pencil object?
Well, this task has sort of lost it's identity, with crash being fixed already.
But I still have the damaged brushes as seen in T61413#646242.
Mar 27 2019
Mar 22 2019
Mar 20 2019
Yeah, I see where your coming from...
Mar 12 2019
The default in 2.79 is 3D View.
Maybe what's shown at the beginning when you first select annotations?
What group policy do you have set up exactly?
Are you sure a standard user account can't create a file on the C Drive?
C:\Users\notadmin\AppData\Local\Temp is the default temp directory for Blender and many other programs and they would break if it was Read-only...
I can render both files on my Vega 64.
Full system specs: Here
Mar 11 2019
Mar 8 2019
@Brecht Van Lommel (brecht) Are crashes getting a priority bump?
Mar 7 2019
@William Reynish (billreynish) Shouldn't Annotations be there?
Mar 6 2019
Yeah, I understand...
I just don't like finding errors/bugs that (even though the correct and rightful solution) need be to removed/disabled....
You can see the screenshot in the report for what is was at the time, but it looks like it has been removed in the meantime...
When you use the annotation inside draw mode of grease pencil, the draw mode is disabled and set as Object mode (it's not logic do an annotation while you are drawing, they are incompatible things). After releasing the D key, the annotation is done, but the toolbar is still on the GP draw mode and the brushes are not found.
Mar 5 2019
Mar 4 2019
You were too fast Brecht :)
Hey @Clément Foucault (fclem), I can't reproduce anymore, is this resolved?
Feb 27 2019
Feb 25 2019
Is there a task stating what the functionality / settings exposed should be for the annotation tool in all the other editors? (Has this even been agreed upon?)
The implementation/feature-set across editors varies wildly and I'm wondering if the original plan of "2D editors will have a similar level of functionality to the 2D GPencil in 2.7x" is still in the process of being implemented.
I definitely have a few concerns for the usability of annotations ATM, mainly not having the option to Continuously Draw.
But yeah,... I'd like to see some discussion around this.
Feb 21 2019
Most likely a VSync issue, especially if it's exactly 120Hz. Try disabling it in the Nvidia control panel.
But also: What playback sync do you have set?
Feb 20 2019
Yep, can confirm...
It's in the playback dropdown.
Will a binary of Blender with this patch applied help?
Something for @Sybren A. Stüvel (sybren)?
It still crashes in -855b3e68ef27-
FYI: I use one of my production files for this test and a camera bind is at the beginning, so when this is fixed I will be able to continue rendering out the project and possibly find more bugs.
If your saying that it's slower without the prefetch, then yes that would be the case.
Decoding video backworks is more complicated then forwards.
Interframe compression only saves full i-frames every now and then so decoding it backwards means decoding it forwards, caching the frames, then playing them backwards.
Yes, this is still an issue. It's a minor inconvenience for me, but others may find it a blocker in their work flow.
Feb 12 2019
Feb 11 2019
Okay, new update, I had been running with --debug (I'm having the same problems as reported in T60089 and with debug is the only way to run Blender)
For some spontaneous reason, Blender* launched (without the debug command)
Here's what I found:
Launching Blender's 32-Bit & 64-Bit build (-69b2f5268114-) both with --debug --factory-startup show different results:
Feb 9 2019
Can you reproduce the crash?
Your file was also rendered without problem
Does this file crash on your system(s)?
(Nothing special; trying to standardise on a test file)