emissive ignored when importing .obj #63778

Closed
opened 2019-04-21 11:25:43 +02:00 by François · 6 comments

System Information
Operating system: linux
Graphics card:GeForce GT 440

Blender Version
Broken: 2.79b
Worked: (optional)

Short description of error

The "Ke" line in .mtl file is ignored when importing a .obj file.

Exact steps for others to reproduce the error
Start from default scene, delete cube, import attached .obj file.
Open the active object properties panel, material tab.
Emissive reads 0 whereas (if I'm not mistaking) it should read 2.

Regards and thank you !

test2.mtl

test2.obj

**System Information** Operating system: linux Graphics card:GeForce GT 440 **Blender Version** Broken: 2.79b Worked: (optional) **Short description of error** The "Ke" line in .mtl file is ignored when importing a .obj file. **Exact steps for others to reproduce the error** Start from default scene, delete cube, import attached .obj file. Open the active object properties panel, material tab. Emissive reads 0 whereas (if I'm not mistaking) it should read 2. Regards and thank you ! [test2.mtl](https://archive.blender.org/developer/F6963636/test2.mtl) [test2.obj](https://archive.blender.org/developer/F6963635/test2.obj)
Author

Added subscriber: @fanfan70

Added subscriber: @fanfan70
Member

Added subscribers: @mont29, @lichtwerk

Added subscribers: @mont29, @lichtwerk
Member

Will confirm for now [because atm. it is indeed ignored].
There was 94c9c4ee33, but since the move to Principled BSDF it is ignored and this seems to be a known issue.
There is also a warning already:
WARNING, emit value unsupported by Principled BSDF shader, skipped.
It is a bit unclear how to handle this properly.

@mont29: should this just mix in an Emission Shader? Or should we just live with the fact that emissive does not fit well the current workflow?

Will confirm for now [because atm. it is indeed ignored]. There was 94c9c4ee33, but since the move to Principled BSDF it is ignored and this seems to be a known issue. There is also a warning already: `WARNING, emit value unsupported by Principled BSDF shader, skipped.` It is a bit unclear how to handle this properly. @mont29: should this just mix in an Emission Shader? Or should we just live with the fact that emissive does not fit well the current workflow?

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-04-23 10:08:37 +02:00

We'll add an emission socket to the principled BSDF later, for now this is not considered a bug but a known limitation.

We'll add an emission socket to the principled BSDF later, for now this is not considered a bug but a known limitation.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#63778
No description provided.