Oscurart Tool exception when rendering without scene camera (compositor) #78651
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#78651
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-4.15.0-101-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21
Blender Version
Broken: version: 2.83.1, branch: master, commit date: 2020-06-25 09:47, hash:
8289fc688b
Worked: never
Short description of error
The bundled Oscurart addon will throw the following exception when rendering without scene camera (compositor)
This in turn causes problems for other addons, which try to do just that.
Exact steps for others to reproduce the error
Added subscriber: @MACHIN3
Thanks for report!
FIXED.
Changed status from 'Needs Triage' to: 'Resolved'
I've noticed that Blender 2.90, doesn't seem to have this problem anymore, yet Blender 2.83.5 still has. So can we get this fix into 2.83 LTS too? Also, why hasn't the version changed at all?
Hi, I'm in 2.9.
I don't know the reason why it doesn't work, I didn't test it.
My addons will always be for the latest version.
For me it was a bad idea to have to do double development.
Added subscriber: @jesterking
Right now, Blender 2.83 is the latest stable release. Please consider getting this into 2.83 as well. 2.83 is the long time release and will be supported for the next 2 years. Since your addon is officially supplied with Blender, and since this is just a fix, not a new feature, it should go into the next bugfix release, so 2.83.6.
Maybe talk to @jesterking?
Try downloading de 2.9 version and copy paste to 2.83.
I'm going to work for the latest version. I regret the decision to do double duty.
I can't be doing things twice.
Look, you have your addon supplied with Blender. You are responsible for it.
You are currently at version 4.0.0. However, the 2.90 4.0.0 version differs in various places from the 4.0.0 version in 2.83. One of the differences is the bug I've posted here about, and which is fixed in 2.90, but not in 2.83.
Both version also claim to work for Blender 2.80 in the bl_info. I won't tell you how do do your development, but this is bad practice.
Please refer to https:*wiki.blender.org/wiki/Process/Addons in regards to your duties as the maintainer of this addon. And also https:*www.blender.org/download/lts/ in regards to the LTS release cycle.
I recommend that you pay attention to how you talk to me.
A greeting.
Added subscriber: @ideasman42
Hi @ideasman42, can you take a look at this please?
I suggest this addon to be removed from 2.83 LTS, if the maintainer refuses to fix it.
Added subscribers: @Jeroen-Bakker, @lichtwerk
For reference, this is probably about this commit blender/blender-addons@955332bf02
@Jeroen-Bakker : should this be considered for LTS?
@MACHIN3 : Not sure there is a hard rule to backport every fix to LTS? (we are also not backporting every non-Addon fix either, so this is more of a decision process than a rule?)
But sure, LTS is a promise to provide critical fixes, so this might be one of them.
@lichtwerk I'm not sure either so I appreciate the input. The addon throws and exception when rendering in the compositor, the fix is easy and done already. So why not bring it to LTS, considering it will be in use for the next 2+ years.
I'm also not sure where the resistance to this is coming from.
Hi everybody!
I prefer that they remove the addon from the repository.
I will continue use my addons locally.
I want to avoid this type of discussion, I don't have the time or the desire.
Thanks !!!
@EugenioPignataro : I remember LTS should not be a burden for devs, so lets just check if we can backport this and leave you out of the extra-work? Would that calm the waters?
Added subscriber: @ckohl_art
Added subscriber: @Raimund58