CUDA error with Cmake build #45575

Closed
opened 2015-07-27 14:15:47 +02:00 by Tom Pov · 13 comments

System Information
Win7 x64 GTX580 newest driver

Blender Version
Cmake build
Broken: c27a1cf or earlier but after 7ad9ca7 - and up to the newest cdf2dbe
Worked: 7ad9ca7

Short description of error
Because the latest win64 scons build is several days old (and now even vanished) I tried the Cmake builds, but, at least for me, it's not possible to render with gpu even the default scene (and any other) neither with f12 nor in render preview.

Exact steps for others to reproduce the error
I've attached a screenshot from the system console output.

CUDAerror.jpg

**System Information** Win7 x64 GTX580 newest driver **Blender Version** Cmake build Broken: c27a1cf or earlier but after 7ad9ca7 - and up to the newest cdf2dbe Worked: 7ad9ca7 **Short description of error** Because the latest win64 scons build is several days old (and now even vanished) I tried the Cmake builds, but, at least for me, it's not possible to render with gpu even the default scene (and any other) neither with f12 nor in render preview. **Exact steps for others to reproduce the error** I've attached a screenshot from the system console output. ![CUDAerror.jpg](https://archive.blender.org/developer/F213059/CUDAerror.jpg)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @tompov

Added subscriber: @tompov
Author

Oh, if I try the factory settings by creating a config folder in the 2.75 folder under the blender.exe then the default scene renders fine. But without this config folder even a simple cube fails to render. Needs the Cmake build its own new userpref.blend ? But no, it worked in 7ad9ca7 ...

Oh, if I try the factory settings by creating a config folder in the 2.75 folder under the blender.exe then the default scene renders fine. But without this config folder even a simple cube fails to render. Needs the Cmake build its own new userpref.blend ? But no, it worked in 7ad9ca7 ...
Member

Added subscriber: @MartijnBerger

Added subscriber: @MartijnBerger
Member

I am not seeing the connection to the buildsystem.

Do you have a 1.5 or a 3gb gtx 580 ?
Are you using the experimental or normal kernel ?
Do I understand correctly that it works if you restore the factory settings ?

"Needs the Cmake build its own new userpref.blend ? But no" No there is no change in userpref.blend and yes the cmake and scons build are the same in this regard and use each others settings .

I am not seeing the connection to the buildsystem. Do you have a 1.5 or a 3gb gtx 580 ? Are you using the experimental or normal kernel ? Do I understand correctly that it works if you restore the factory settings ? "Needs the Cmake build its own new userpref.blend ? But no" No there is no change in userpref.blend and yes the cmake and scons build are the same in this regard and use each others settings .
Member

Could you also test and report if the latest official blender ( that one is build with cmake) is broken for you in this regard ?

Could you also test and report if the latest official blender ( that one is build with cmake) is broken for you in this regard ?
Author
  • 3GB GTX580.
  • Feature set: supported.
  • Yes, if I create a "config" folder in the "2.75" folder under the installation folder (with the blender.exe) then it works fine.

I just tested 61e4800 and unfortunately the same CUDA error happens.

- 3GB GTX580. - Feature set: supported. - Yes, if I create a "config" folder in the "2.75" folder under the installation folder (with the blender.exe) then it works fine. I just tested 61e4800 and unfortunately the same CUDA error happens.
Author

...
I just tried another machine, winx64 GTX580 3GB too, and the same error happens ...

Btw, what's the meaning of "connection to the buildsystem" ?

... I just tried another machine, winx64 GTX580 3GB too, and the same error happens ... Btw, what's the meaning of "connection to the buildsystem" ?
Author

A new finding:
I always use the zip installations/extractions.
So, I have a Blender Scons folder and another Blender Cmake folder.
If the original Blender Scons folder is present the Cmake shows the described error.
But if I rename or delete the Blender Scons folder all seems to be fine with Blender Cmake, even with my own userpref and startup file !

Hope this could be a help !?

A new finding: I always use the zip installations/extractions. So, I have a Blender Scons folder and another Blender Cmake folder. If the original Blender Scons folder is present the Cmake shows the described error. But if I rename or delete the Blender Scons folder all seems to be fine with Blender Cmake, even with my own userpref and startup file ! Hope this could be a help !?
Author

OK, I don't know anymore if this is realy a bug or my fault !?
Nevertheless the reason for the described behaviour is the path in the userpref for the scripts under the Filetab. In case I use the same userpref, and so the same Scriptspath, the "error" happens.
So the solution, at least for me, is simply to ensure each installation has its own path to its own Scriptsfolder.
Or make the Scriptspath relative.

Thank you !

OK, I don't know anymore if this is realy a bug or my fault !? Nevertheless the reason for the described behaviour is the path in the userpref for the scripts under the Filetab. In case I use the same userpref, and so the same Scriptspath, the "error" happens. So the solution, at least for me, is simply to ensure each installation has its own path to its own Scriptsfolder. Or make the Scriptspath relative. Thank you !

Added subscriber: @Sergey

Added subscriber: @Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2015-07-28 11:36:59 +02:00

If you're trying to re-use same scripts folder for different blender version you might really easy to run into issues like CUDA kernel being compiled from much older sources than newer build expects it to be.

If you're trying to re-use same scripts folder for different blender version you might really easy to run into issues like CUDA kernel being compiled from much older sources than newer build expects it to be.
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#45575
No description provided.