Cycles renderer only loads 1 texture when set to GPU compute #113521

Closed
opened 2023-10-11 00:11:08 +02:00 by iris · 6 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: AMD Radeon RX 7900 XTX ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.3.230915

Blender Version
Broken: version: 3.6.4, branch: blender-v3.6-release, commit date: 2023-09-25 13:24, hash: 21bfc5e7fe3f
Worked: None

Short description of error
After installing a Radeon RX 7900 XTX, when I set Cycles to GPU compute, only a single texture is loaded, and is applied in place of every other image in the scene. Everything except the textures renders normally, and the textures are fine if I switch back to CPU. So far I've tried:

  • reinstalling my drivers (I even tested it out on a fresh installation of Windows, with no luck)
  • reinstalling Blender 3.3.4 and 3.6.4
  • updating, rolling back, and reinstalling Adrenalin
  • disabling/enabling tiling, and increasing tile size
  • disabling/enabling HIP RT, and disabling/enabling the experimental feature set
  • increasing/decreasing/setting to 0 the texture time out limit

Exact steps for others to reproduce the error
Open the file and make sure Cycles is set to GPU compute. Problem should be evident in both the viewport and in final renders. I think this is probably a hardware issue, so I'm not sure you'll see the issue on a different computer.

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: AMD Radeon RX 7900 XTX ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.3.230915 **Blender Version** Broken: version: 3.6.4, branch: blender-v3.6-release, commit date: 2023-09-25 13:24, hash: `21bfc5e7fe3f` Worked: None **Short description of error** After installing a Radeon RX 7900 XTX, when I set Cycles to GPU compute, only a single texture is loaded, and is applied in place of every other image in the scene. Everything except the textures renders normally, and the textures are fine if I switch back to CPU. So far I've tried: - reinstalling my drivers (I even tested it out on a fresh installation of Windows, with no luck) - reinstalling Blender 3.3.4 and 3.6.4 - updating, rolling back, and reinstalling Adrenalin - disabling/enabling tiling, and increasing tile size - disabling/enabling HIP RT, and disabling/enabling the experimental feature set - increasing/decreasing/setting to 0 the texture time out limit **Exact steps for others to reproduce the error** Open the file and make sure Cycles is set to GPU compute. Problem should be evident in both the viewport and in final renders. I think this is probably a hardware issue, so I'm not sure you'll see the issue on a different computer.
iris added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-10-11 00:11:09 +02:00
Member

Hi, thanks for the report. Unable to confirm in 3.6LTS on Windows + NVIDIA. Do you get any error in console?
Launch blender from command line with --debug-cycles or --debug-gpu, see if that generates any relevant info about missing textures.

**System Information**
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03
Hi, thanks for the report. Unable to confirm in 3.6LTS on Windows + NVIDIA. Do you get any error in console? Launch blender from command line with `--debug-cycles` or `--debug-gpu`, see if that generates any relevant info about missing textures. ``` **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03 ```
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-10-11 05:51:58 +02:00
Author

I got an error message when I used --debug-gpu at the top of my attached debug_gpu_start.txt: ERROR (gpu.debug): GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9
The program didn't crash and was able to successfully render the scene, albeit with the wrong textures.

I've included 3 logs, the first two for starting blender and switching to the rendered viewport with both commands, and the last for an actual render after --debug-cycles
As far as I can tell the textures aren't missing - they are fully visible in other rendering views and none of my shaders have been altered.

I got an error message when I used `--debug-gpu` at the top of my attached debug_gpu_start.txt: `ERROR (gpu.debug): GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9` The program didn't crash and was able to successfully render the scene, albeit with the wrong textures. I've included 3 logs, the first two for starting blender and switching to the rendered viewport with both commands, and the last for an actual render after `--debug-cycles` As far as I can tell the textures aren't missing - they are fully visible in other rendering views and none of my shaders have been altered.
Member

Hi, could it be due to high resolution textures on other two objects? Can you check their size? This is known issue currently for HIP:

Image texture size is limited, could detect this and resize or show user better error (#94057, #93109)

Textures are missing in provided file could you pack them and upload file again?: File > External Data > Pack Resources -> save .blend

Sorry for the delayed reply, your notification slipped somehow.

Hi, could it be due to high resolution textures on other two objects? Can you check their size? This is known issue currently for HIP: > [Image texture size is limited, could detect this and resize or show user better error (#94057, #93109)](https://projects.blender.org/blender/blender/issues/91571#:~:text=Image%20texture%20size%20is%20limited%2C%20could%20detect%20this%20and%20resize%20or%20show%20user%20better%20error%20(%2394057%2C%20%2393109)) Textures are missing in provided file could you pack them and upload file again?: `File > External Data > Pack Resources` -> save .blend Sorry for the delayed reply, your notification slipped somehow.
Author

Hey! Funny enough I finally managed to solve this last night - it was a display adapter problem that happened when my partner upgraded our graphics card.

Opening Device Manager - there are two display adapters listed, AMD Radeon RX 7900 XTX (the new graphics card) and AMD Radeon(TM) Graphics (the CPU's embedded graphics processor). The embedded processor was previously disabled, but was re-enabled when we upgraded the graphics card for some reason.

When both the embedded processor and the new graphics card were enabled, the embedded processor was listed as a possible cycles render device, separate from the CPU itself. Whether I selected that option or not, the GPU wouldn't work properly while that was available as an option. After disabling the embedded processor in Device Manager, only the CPU and graphics card are options, and everything works again!

Also if it helps - the textures I used for the demo were 256x256 pixels - I'm not sure what I did with them. Now that the graphics card is working again it's handling 4k textures with no problem at all.

Hey! Funny enough I finally managed to solve this last night - it was a display adapter problem that happened when my partner upgraded our graphics card. Opening Device Manager - there are two display adapters listed, AMD Radeon RX 7900 XTX (the new graphics card) and AMD Radeon(TM) Graphics (the CPU's embedded graphics processor). The embedded processor was previously disabled, but was re-enabled when we upgraded the graphics card for some reason. When both the embedded processor and the new graphics card were enabled, the embedded processor was listed as a possible cycles render device, separate from the CPU itself. Whether I selected that option or not, the GPU wouldn't work properly while that was available as an option. After disabling the embedded processor in Device Manager, only the CPU and graphics card are options, and everything works again! Also if it helps - the textures I used for the demo were 256x256 pixels - I'm not sure what I did with them. Now that the graphics card is working again it's handling 4k textures with no problem at all.
Member

Strange. Should work even when iGPU is detected. But good to know that you found the culprit on your side.
I think we can close the report now.

Strange. Should work even when iGPU is detected. But good to know that you found the culprit on your side. I think we can close the report now.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-01-04 05:31:27 +01:00

Hey! Funny enough I finally managed to solve this last night - it was a display adapter problem that happened when my partner upgraded our graphics card.

Opening Device Manager - there are two display adapters listed, AMD Radeon RX 7900 XTX (the new graphics card) and AMD Radeon(TM) Graphics (the CPU's embedded graphics processor). The embedded processor was previously disabled, but was re-enabled when we upgraded the graphics card for some reason.

When both the embedded processor and the new graphics card were enabled, the embedded processor was listed as a possible cycles render device, separate from the CPU itself. Whether I selected that option or not, the GPU wouldn't work properly while that was available as an option. After disabling the embedded processor in Device Manager, only the CPU and graphics card are options, and everything works again!

Also if it helps - the textures I used for the demo were 256x256 pixels - I'm not sure what I did with them. Now that the graphics card is working again it's handling 4k textures with no problem at all.

Hello. Indeed this is a workaround here. We don't want to recommend it to people though obviously they might be using the embedded graphics as well, but if you're able to that it's a good workaround for now.

> Hey! Funny enough I finally managed to solve this last night - it was a display adapter problem that happened when my partner upgraded our graphics card. > > Opening Device Manager - there are two display adapters listed, AMD Radeon RX 7900 XTX (the new graphics card) and AMD Radeon(TM) Graphics (the CPU's embedded graphics processor). The embedded processor was previously disabled, but was re-enabled when we upgraded the graphics card for some reason. > > When both the embedded processor and the new graphics card were enabled, the embedded processor was listed as a possible cycles render device, separate from the CPU itself. Whether I selected that option or not, the GPU wouldn't work properly while that was available as an option. After disabling the embedded processor in Device Manager, only the CPU and graphics card are options, and everything works again! > > Also if it helps - the textures I used for the demo were 256x256 pixels - I'm not sure what I did with them. Now that the graphics card is working again it's handling 4k textures with no problem at all. Hello. Indeed this is a workaround here. We don't want to recommend it to people though obviously they might be using the embedded graphics as well, but if you're able to that it's a good workaround for now.
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
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#113521
No description provided.