Hi @Vyacheslav (hitrpr),
The environment reflections in Eevee are handled by cubemaps. You can increase their resolution in the Indirect Lighting panel.

Thanks, I can no longer reproduce the bug :)

@Philipp Oeser (lichtwerk) Ah, indeed it still occurs with rBc4ef90f5a0b1; thanks for your vigilance.

Hello Bastien,
thanks so much for the quick fix!
I agree that this situation should be avoided, but as far as I understand, it comes from the autorig add-on we’re using, Auto-Rig Pro.
I admit I don’t know the rationale behind this parenting…

Great! :)

Committed in rBACa140f066ac99.

Hello @Mehdi El Fadil (alc_ve), thanks for the report.
I changed the default behaviour of the add-on.
It used to be that you didn’t need to select a sky texture for the add-on to affect it, but this turned out to be confusing for users who didn’t know of the behaviour, activated the add-on and had the sky texture move without their consent.

Including Phabricator usernames in metadata would be extremely useful to automatically notify maintainers; I have to resort to searching reports for those add-ons I maintain once in a while, and some reports stay unaddressed for a bit.
Some information on maintainers is available from the manual’s add-ons section, but it’s far from complete, and possibly outdated.

@Antonio Vazquez (antoniov), I bisected this to rB11ba9eec70175b39e34943c8ffacb54c35cbb897.

For anyone encountering this bug, a workaround is to set the current frame to the first frame prior to rendering:

blender -b grease_pencil_render_bug.blend --python-expr "import bpy \
bpy.context.scene.frame_set(bpy.context.scene.frame_start)" -a

This appears to be fixed by the exact Boolean option from version 2.91.

This is not a bug. It comes from the “Pro Lighting: Skies.001” node in the world shading nodes. It is used as background emission, but it is missing a texture and emits in magenta.
Since the helmet is the only specular object in the scene, it is the only one reflecting the environment in rendered view. You can delete the Pro Lighting node, fix it by finding the missing texture, or use an emission colour for the helmet, as you’ve done everywhere else. If you really want to use the Principled BSDF, you must fix the world node tree.

Thanks for the report!

Hi @Jordan Matyka (oaaya),
I couldn’t reproduce this crash on Linux, and cannot test on Windows right now.
Does this still happen with the latest version of Blender?

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Instance was updated some time ago. Thanks!

I don’t believe modifying AnimAll is necessary. I could reproduce the crash with the following script:

Hello @Rob (robs_pangolin),
thanks for the report and workaround. This isn’t specific to AnimAll, but a known limitation of Blender’s animation system, which isn’t normally used to animate individual mesh (etc.) components. I don’t know if it’s desirable to support this either, since many types of data would need to be checked.

Hello @Ajlan Altug (jacobo),
do you still have this problem in the latest versions? I couldn’t reproduce it in either 2.83.9 or 2.90.1

Revert error in bl_info.

This bug seems to be have been fixed as of 2.90.

In D6543#194432, @Wayne Dixon (waylow) wrote:

Thanks for checking it out @Damien Picard (pioverfour)
I'm glad I didn't break it.

Are you the one who commits this to master?

In D6543#194298, @Wayne Dixon (waylow) wrote:

What's the best way for you to do that?
Should I make a patch? (I've never done that before)

Hi,
at the time I made that commit (rBA0f5738d9022c), the add-on didn’t select any transparency whatsoever, as seen in T67239. I just made the commit because the task had been sitting for a while, but the default wasn’t an opinionated choice from me; if a better one can be chosen, that’s good.
But I suspect there may be many usages for this add-on, so choosing a default may not be very easy, and I don’t know the implications of each setting well enough to help here, sorry.

• Rename focus_bone to focus_subtarget
• Use Brecht’s code for Cycles
• Expose the property in Cycles’ UI
  • Side note: the focus_object property does not display the same name in Cycles’ (Focus Object) and Eevee’s UIs (Focus on Object). I named the subtarget property accordingly (Focus Bone, Focus on Bone), but perhaps they should be unified.
• Update source/blender/editors/armature/armature_naming.c and source/blender/depsgraph/intern/builder/deg_builder_relations.cc
  • I don’t properly understand the depsgraph’s logic so I may have got it wrong:
  • the code in deg_builder_relations.cc doesn’t appear to have any effect
  • in armature_naming.c I call DEG_id_tag_update() on the camera data, which isn’t done elsewhere in this file.

In D7012#169725, @Ankit Meel (ankitm) wrote:

you didn't specify any reviewers here?

Ha ha right, but you are still the author! All right, pushing this with commit rBAf4cf9b00db36. Thanks.

@Wayne Dixon (waylow) @Brendon Murphy (meta-androcto) If that’s all right with you I’ll push this new rig to master.

Remove camera sensor width from drivers: this caused delays in the drivers. Also gets rid of two dependency cycles.

Error with previous diff.

• Expose the DOF focus object property in the 2D rig UI, since the Add Empty operator is irrelevant here
• Add @Flavio Perez (flav) as original author of the 2D Camera rig

There is a dependency cycle (unparent chest from ORG-spine.006). This is “not considered a bug” (cf. T69101, T71838, T66814…)

Based on @Jacques Lucke (JacquesLucke)’s answer, this crash actually seems to happen when any error popup is displayed.
For instance:

• Open User Preferences
• In main window, open a text editor and execute some invalid Python code
• Switch to the preferences window without moving the mouse (e.g. Alt + Tab)
• Open…
  • Don’t Save
• Crash

In T73487#861721, @Jacques Lucke (JacquesLucke) wrote:

By "immediatly afterwards" you mean while the error popup is still open? Then yes, I can reproduce it, otherwise not.

Yes, that seems to be the case. Updating description.

In D6543#157089, @Wayne Dixon (waylow) wrote:

git apply -R patch

to revert the changes of the patch.
I'm learning things!

Well, so am I! It makes sense that it exists, but I wouldn’t have thought.

In D6543#156867, @Wayne Dixon (waylow) wrote:

-I've noticed that when you add a rig, the camera doesn't automatically become the active camera for the scene.

Although it’s not Blender’s default behaviour, it makes sense for a camera add-on aimed at creating primary shooting cameras. I’ll do that.

• use object_utils so that objects are added to the Collection collection, as default
• root widget case
• fix root widget size
• set camera as active
• create rig at cursor
• add my name to authors

In D6543#154854, @Wayne Dixon (waylow) wrote:

Ok I think I got the patch applied.
I use git so thanks for that tip ;)

Fix error with MCH name.

Rename aim mechanism to Aim_shape_rotation-MCH

In D6543#154392, @Wayne Dixon (waylow) wrote:

I don't know how to easily download your diff and apply it at my end.
But I think I need to install arc, is that right?

In D6543#154202, @Damien Picard (pioverfour) wrote:

I renamed the camera object from Dolly_camera and Crane_camera to just Camera, because the distinction didn’t seem useful and to simplify the code slightly. Do you agree with that?

I meant to say that I’d like to do that.

Rename Crane_arm and Crane_height back.

In D6543#154194, @Wayne Dixon (waylow) wrote:

I haven't had a proper look at your code yet (I'm hoping to get a chance this Sunday)

Hi, no problem, take your time!

Cleanup: unused variables, indentation, line length, variable names.

• Add back focus lens, focus distance and aperture properties and drivers.
• Add icon for the Add Marker operator
• Increment version

In D6543#153709, @Wayne Dixon (waylow) wrote:

Great, this is exactly what I hoped would happen, someone would fix my errors and help me improve haha.

I like free software :)

D6424 fixed an openGL bug on macos.

Fixed by rBA95e98889aba9.

Fixed by rBA95e98889aba9, after D6424. Thanks!

Hi, thanks! This indeed fixes the bug.

Thanks! No problem at all as far as I can tell. :)

Hi, thanks, but I don’t have commit rights for the manual repo. Who should I ask? the documentation page about contributing doesn’t tell.

Fix typo
Update to reflect recent changes