Images dissappearing #66201

Closed
opened 2019-06-28 06:28:25 +02:00 by Ahmad Bilal · 16 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-24 18:46, hash: c0c1b4542f
and blender-2.80-5dd8c3f0cb83-win64 (upto my knowledge)
Worked: (optional)

Description of Error
So .. I have 4 images as planes .. in my scene.. but I'm using a emission shader in place of a diffuse shader (which is added by default when you import images as plane). Everything works fine when you set it up. But after I save and close blender. On reopening blender, they are not there! dissappeared! Even in the render it is not there.

No, the image is visible in viewport (eye icon checked) .. and same goes for the render (camera icon) .. and No .. the collection itself is not hidden either. What proved it to me.. that I'm looking at a bug for sure .. is the accidental fix I found for it .. in a peculiar way.

If I add .. a diffuse shader .. and NOTE .. that I have not even connected it to anything, and try to connect the color setting of the image texture node to the diffuse shader.. voila.. my images are back! .. and I'm not even touching the shader for all of them! See my 2 screeshots for proof. Note that, simply adding the diffuse shader .. is not enough.. I have to try connecting it .. for the fix to work.

I have checked two latest versions of blender .. having this bug.

Bug1.png

Bug2.png

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-24 18:46, hash: `c0c1b4542f` and blender-2.80-5dd8c3f0cb83-win64 (upto my knowledge) Worked: (optional) **Description of Error** So .. I have 4 images as planes .. in my scene.. but I'm using a emission shader in place of a diffuse shader (which is added by default when you import images as plane). Everything works fine when you set it up. But after I save and close blender. On reopening blender, they are not there! dissappeared! Even in the render it is not there. No, the image is visible in viewport (eye icon checked) .. and same goes for the render (camera icon) .. and No .. the collection itself is not hidden either. What proved it to me.. that I'm looking at a bug for sure .. is the accidental fix I found for it .. in a peculiar way. If I add .. a diffuse shader .. and NOTE .. that I have not even connected it to anything, and try to connect the color setting of the image texture node to the diffuse shader.. voila.. my images are back! .. and I'm not even touching the shader for all of them! See my 2 screeshots for proof. Note that, simply adding the diffuse shader .. is not enough.. I have to try connecting it .. for the fix to work. I have checked two latest versions of blender .. having this bug. ![Bug1.png](https://archive.blender.org/developer/F7552965/Bug1.png) ![Bug2.png](https://archive.blender.org/developer/F7552966/Bug2.png)
Author

Added subscriber: @SomeAB

Added subscriber: @SomeAB
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

Hello @SomeAB,

Can you provide us with a minimum blend file that shows the issue including the steps to take to reproduce it?
Which render engine do you use? Is it also the case for other render engines?

Hello @SomeAB, Can you provide us with a minimum blend file that shows the issue including the steps to take to reproduce it? Which render engine do you use? Is it also the case for other render engines?
Author

I'm using Eevee. In cycles, there is no issues.

I can't post the blend file publicly, but maybe privately.. it can be shared if it is needed (maybe).

I'm using Eevee. In cycles, there is no issues. I can't post the blend file publicly, but maybe privately.. it can be shared if it is needed (maybe).

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

Without a .blend, it is difficult to debug the problem.
Try to create a minimal example .blend with different images.

Without a .blend, it is difficult to debug the problem. Try to create a minimal example .blend with different images.
Author

Dissappear.blend

Here is a minimal file, I tested it in yesterday's build as well "blender-2.80-648e8a1f1d4a-win64".

I open the file in blender, in eevee .. clicked on the circular icon for 'display render preview' .. and only one of the images is visible

Edit: I also noticed, that this only happens when I reopen blender. If I simply revert my blend file .. after applying the fix I mentioned above .. it remains fixed. However, if I didn't fix it .. it will remain broken even after revert.

Also, the fix seems to have changed a bit now. Simply trying to connect the image to diffuse (only drag a line to it) doesn't seem to be enough in the latest build. I need to connect the image to diffuse node .. for it to get fixed. After that I can simply remove it, and it remains fixed.

Also, this bug seems to be related to the 'color' input/output .. since I tried a similar fix using a 'glossy shader' and a 'add shader'. The fix worked in the case of glossy shader, when I connected the color output from image to its color input. Add shader didn't work though.

[Dissappear.blend](https://archive.blender.org/developer/F7557160/Dissappear.blend) Here is a minimal file, I tested it in yesterday's build as well "blender-2.80-648e8a1f1d4a-win64". I open the file in blender, in eevee .. clicked on the circular icon for 'display render preview' .. and only one of the images is visible Edit: I also noticed, that this only happens when I reopen blender. If I simply revert my blend file .. after applying the fix I mentioned above .. it remains fixed. However, if I didn't fix it .. it will remain broken even after revert. Also, the fix seems to have changed a bit now. Simply trying to connect the image to diffuse (only drag a line to it) doesn't seem to be enough in the latest build. I need to connect the image to diffuse node .. for it to get fixed. After that I can simply remove it, and it remains fixed. Also, this bug seems to be related to the 'color' input/output .. since I tried a similar fix using a 'glossy shader' and a 'add shader'. The fix worked in the case of glossy shader, when I connected the color output from image to its color input. Add shader didn't work though.

Added subscriber: @ZedDB

Added subscriber: @ZedDB

You didn't include any images. So the the planes are simply pink:
screenshot.png

You didn't include any images. So the the planes are simply pink: ![screenshot.png](https://archive.blender.org/developer/F7558189/screenshot.png)
Author

@ZedDB

Did I prepare the minimal file wrong? Just confirm, this for me. Here is what I did it... selected the planes in my original, copy and paste in new blend file and save. If I open this minimal file now... by going into render preview mode, and after applying the fix, I can see all 4 images properly. Do I need to provide you image files seperately?

@ZedDB Did I prepare the minimal file wrong? Just confirm, this for me. Here is what I did it... selected the planes in my original, copy and paste in new blend file and save. If I open this minimal file now... by going into render preview mode, and after applying the fix, I can see all 4 images properly. Do I need to provide you image files seperately?

You need to pack the images into the blend file. Otherwise it will use the external image files (that you didn't include).

File->External Data -> Pack all into .blend.

You need to pack the images into the blend file. Otherwise it will use the external image files (that you didn't include). File->External Data -> Pack all into .blend.
Author

Dissappear.blend

Ok thanks. Here is the file now

[Dissappear.blend](https://archive.blender.org/developer/F7561614/Dissappear.blend) Ok thanks. Here is the file now

All the images are visible to me it seems:
screenshot.png

Are you using the latest AMD driver and blender beta?

All the images are visible to me it seems: ![screenshot.png](https://archive.blender.org/developer/F7561650/screenshot.png) Are you using the latest AMD driver and blender beta?
Author

Yes, I'm having AMD driver 19.6.2 (Stable) .. and blender-2.80-648e8a1f1d4a-win64

Edit: (20 minutes later) .. I just downloaded blender-2.80-ef750790d261-win64 .. and issue seems to have been fixed.

Please note, that blender-2.80-648e8a1f1d4a-win64 is the version for 1-2 days ago .. and it was broken for me. I have not updated anything in the meanwhile except blender, so now you should be able to pinpoint .. what caused this .. based on the latest commit (I hope ?).

Yes, I'm having AMD driver 19.6.2 (Stable) .. and blender-2.80-648e8a1f1d4a-win64 Edit: (20 minutes later) .. I just downloaded blender-2.80-ef750790d261-win64 .. and issue seems to have been fixed. Please note, that blender-2.80-648e8a1f1d4a-win64 is the version for 1-2 days ago .. and it was broken for me. I have not updated anything in the meanwhile except blender, so now you should be able to pinpoint .. what caused this .. based on the latest commit (I hope ?).

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sebastian Parborg self-assigned this 2019-07-03 17:01:14 +02:00

Glad to hear it has been solved,

Here is the commit log: https://git.blender.org/gitweb/gitweb.cgi/blender.git/shortlog

Glad to hear it has been solved, Here is the commit log: https://git.blender.org/gitweb/gitweb.cgi/blender.git/shortlog
Sign in to join this conversation.
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
4 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#66201
No description provided.