Page MenuHome

Annotations don't work with 2.79 settings
Closed, ResolvedPublic


System Information
Operating system: Microsoft Windows 7
GPU: ASUS Strix Radeon Vega 64
CPU: Intel(R) Core(TM) i7-5960X
RAM: 32.0 GB
Full System Information: Here

Blender Version

Broken: 2.79b > 2.80, blender-2.80.0-git.2a79e3463130-windows64
Worked: 2.69 > 2.79b

Short description of error

Settings from 2.79 are kept as is, when opening in 2.80, but are not editable with the UI being striped down.

This is a problem when layers are locked or opacity is zero etc...

Exact steps for others to reproduce the error

Event Timeline

Christopher_Anderssarian changed the visibility from "Public (No Login Required)" to "Christopher_Anderssarian".
Christopher_Anderssarian triaged this task as Needs Information from User priority.

I pressed enter by accident...

I really don't understand this bug report. Could you provide more details, a test file and the steps to reproduce it.

Christopher_Anderssarian changed the visibility from "Christopher_Anderssarian" to "Public (No Login Required)".
Christopher_Anderssarian raised the priority of this task from Needs Information from User to Needs Triage by Developer.

@Antonio Vazquez (antoniov) Yeah, I pressed Enter after writing the title which submitted the report before I had filled it in.

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.

The actual issue that I'm trying to report is (for example) that GPencil layers can be locked in 2.79 and when opened is 2.80 are uneditable.

This is also true with opacity:

Original GPencil Image2.79 with yellow at 0% opacity2.80 with yellow at 0% opacity that can't be changed

From what I can see this only affects: Opacity and Lock layers.

@Christopher_Anderssarian Could you open a new report for the lock problem. It's better to have one bug by report.