GPU renders using .hdr environment maps fail with error #43118
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
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#43118
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?
Core i5 4440 / 8GB
GTX 970
Windows 8.1 64bit
GPU Driver version: Latest
Blender daily build, 2.73, Date: 2015.01.02 - Hash:
8a28895(Also reproducible on current official RC build)
Using a .hdr image as the environment map while GPU rendering is enabled results in the error:
Here is a screenshot of the console output: http://puu.sh/e2qjv/3fdbb800a3.png
I can submit the blend file which reproduces the error but when packed it's 102mb (because of the .hdr), so I need to know how to get it to you. However it can be reproduced by taking the default cube scene, switching to cycles, then attaching a HDR (preferably around the 100mb mark) as an environment map, switching to GPU rendering, and then attempting a render.
Changed status to: 'Open'
Added subscriber: @ciwolsey
As an addition here is a blend file to reproduce the bug:
http://tinyurl.com/lxrctpk
Added subscriber: @mont29
I would suspect your GPU is running out of mem? Sergey shall know more!
It's a 100mb .hdr lit cube on a 4gb GPU so I would say if it is running out of mem it shouldn't be.
File size != size in memory. Size in memory would be widthheight4*4 bytes (because it's RGBA float).
If that still fits into your GPU please publish the .blend file, .hdr all all the rest files needed to reproduce the bug. The link above doesn't quite work because i assume it's not marked as public or so.
HDR Width = 8192
HDR Height = 4096
4096 * 8192 * 4 * 4 = 536870912 bytes = 0.536871 gigabyte
It's a 4GB card so I assume it should fit then?
Here is an updated link for the blend which I have checked to be publicly accessible:
http://tinyurl.com/ok8a3ar
Just to add to your suggested way of calculating the in-memory size that when doing a CPU render cycles reports the "peak" memory usage as 512mb so it seems to back up the calculation.
Changed status from 'Open' to: 'Archived'
That's quite huge texture size. CUDA does have limit on the texture size which is much smaller than the total VRAM.
Thanks for the report, but it's just a hardware limitation.
I'm only experiencing this problem on windows. In linux I can use the same .hdr with no problem.
Are you using the same video driver in linux and windows?
Changed status from 'Archived' to: 'Open'
Tested on windows now. The file you've provided renders just fine here on gt520m. Used drivers 344.11 and then upgraded to 347.09 and it still works fine.
So make sure your drivers are all up to date and so.
Reopening as unconfirmed.
My drivers are the latest - just did a clean install of windows and latest drivers and still experiencing the problem.
Looks like I'm not the only one having this problem:
https://developer.blender.org/T43063
He's using the same hardware (GTX 970), and the same driver and version, and going to old driver version fixes it for him. Either there is a problem with nvidias driver/cuda or the way blender is using that particular version of the driver/cuda. If there's no fault in blender it probably needs to be reported to nvidia.
The driver version is 347.09 (the same version as in the other bug report).
Since you've tried a a different graphics card and not experienced the problem we can only assume that it's the combination of both the hardware and driver version. (GTX 970 + 347.09 + windows), and possibly other closely related cards.
I'll reboot to linux now and try to check 347.09 under linux.
Linux + 343.36 = Working
Windows + 347.09 = Problem
Both are the latest stable drivers for the respective OS.
I'll check an older version of the driver on windows as soon as I have time.
You can't compare behavior using different versions of drivers, they might easily have different limitations. Try installing 343.36 on windows and see if it makes scene to render for. That's the only fair comparison is the circumstances of the issue..
Added subscriber: @JulianEisel
The issue reported can't be reproduced so far, and has been moved to the BF Blender: Unconfirmed project.
If 2 other people aren't able to redo the bug after 2 weeks, it will be closed.
We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them.
If there is anything you can provide to help others to reproduce the problem, be sure to include it.
it might also help grabbing latest build from builder.blender.org and attaching system-info.txt generated by the newer build.
Changed status from 'Open' to: 'Archived'
No news since one week…
You reproduce the error by taking a GTX 970 and the latest drivers on windows, and setup HDR lighting under cycles. It really is that simple from what I've seen. Two people have reported the same problem now. One has said that reverting to old drivers fixes the problem.
Here is my system-info.txt taken from blender-2.73-1b1a6e0-win64.zip from https://builder.blender.org/download/
system-info.txt
And the .hdr I used is the smallest I could find:
5120x2560 RGBA float
Ok, one more thing: can you provide full error log from the console? To gather that you can do:
and then share log.txt.
Here you go Sergey:
log.txt
As I was writing this comment Nvidia released a new driver (347.25). The problem persists to this newer driver.
Added subscriber: @NikParo
I can confirm that I have the same problem and get the same error. "CUDA error: Launch failed in cuMemcpy2D(¶m)"
My system:
Core i5 4460 / 16GB
GTX 970
Windows 8.1 64bit
GPU Driver version: Up to date (347.52)
Blender 2.73
Using smaller HDR's works fine (e.g. 2000x1000px, http://zbyg.deviantart.com/art/HDRi-Pack-3-112847728)
Higher resolution HDR's does not. (e.g. 6000x3000px, http://3dericdesign.deviantart.com/art/Free-HDR-For-Studio-Render-157557355)
There's a bit more text in my log.txt though.
log.txt
Added subscriber: @CrazyEngine
same error over here... it's the driver ._. (GTX 970, newest driver from Nvidia 347.52, Blender 2.73a)
Added subscriber: @dopeless
same error
Xeon 1240v2
GTX 970
Win 8.1 64
GPU Driver 347.52
Blender 2.73
Added subscriber: @dre-1
same error
intel i5-4590
GTX 970
Win 8.1 64
GPU Driver 347.52
Blender 2.73a
reverted back to GPU drivers 344.11 and it works again
Added subscriber: @d_Fault
same error after updating nvidia drivers to 347.52
intel i7-2700k
GTX 970
Win 7 64
GPU Driver 347.52
Blender 2.73, 2.74 RC2, 2.74 release version.
Reverting GPU drivers fixes it, but that's not a solution. Seems it is related to Maxwell?
Good news, in the latest beta driver 347.88 big hdr maps are working normal again, at least for me.
Well spotted Robert, I can confirm the problem is resolved also for me using driver version 347.88.
Everything's working fine now. Glad that Nvidia fixed it :) (Driver 347.88)