-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old bug - Viewport GPU rendering crashes. #924
Comments
Hi! I cannot reproduce the error. For me, GPU rendering works. Keep in mind, that for the first time, CUDA needs to comile the render kernel. This process needs several minutes to complete but this is a one time delay. Can you give more information on the used hardware and give a detailled error message? |
[JUST NOTICED this morning! A vital piece of information is missing! Sorry! Thanks for having a look!
I made sure to wait - it took a bit over 10 minutes. I made sure not to try clicking buttons or alt-tabbing out. I've included the details for what I could find - but the error doesn't get very detailed from what I could see? The full details are below, and in the crash.txt I included. Graphics card: RTX2060 OS Name Microsoft Windows 10 Pro Blender: blender-4.1.1 Blender crash . txt: |
A bit more information: Anyway - If I get it to crash, I'll report back and mention what crashed it! I was unable to make it crash, even after adding many Lux Core models from the LoL. The ONLY time it crashes is when the Lux Core examples scenes are loaded! |
I've tried saving the Leaves example in 4.1.1, then reloading the scene. Hoping that it would "re-format" the internal data perhaps. GPU Viewport rendering still crashes. Hmmm. |
Ok, so using the leaves scene, it only STOPS crashing when I delete 2 of the 3 leaves, all but the single material node of the texture and the Subsurf modifier, and all of the lights, background, and focus. It seems like there's multiple "issues" in the demo file that cause the GPU Viewport to bomb out. I'm going to leave it here, because the demo scenes are only meant to be rendered and tinkered with, there's no big reason to use GPU rendering with them. =) Close if you like! |
Are you using this version? |
I am! Additionally, I'm trying to download various files from years ago - the example files are old aren't they? LuxCoreRender/LuxCore#403 the file volCaustics.blend.gz from 2020 works fine in Path trace GPU mode too. I wonder if it's all down to some issue with file format - moving from an old file save for the example files, straight to V2.9 Alpha 1? |
I tested the procedural leaves scene and it works with GPU rendering on my system. Is your scene the original one from the repository? |
Yes it is, directly from the site. If this is just an odd edge case with my PC, I'm happy if it's closed? No point wasting time on an issue that's obscurely based on 1 hardware setup! |
.blend file:
Any with more than a cube in it. Looks like it may need a few material nodes.
Steps to reproduce:
1: Select Lux Core Rendering.
2: Select GPU Viewport rendering.
Error message from Blender console:
Python backtrace
File "C:\Users\sarah\AppData\Roaming\Blender
Foundation\Blender\4.1\scripts\addons\BlendLuxCore\engine\viewport.py", line 13 in start_session
OS: Windows 10
Blender version: 4.1
LuxCore version: BlendLuxCore v2.9 alpha 1
Of note - a question?
Is this a "Won't fix" issue, due to the excessive physical delays in piping edited data back through to the GPU?
I've read a couple of posts where moving light meshes with GPU viewport rendering is very slow due to that overhead of recalculating lighting from the meshes and material changes and such?
(In other words - Is GPU viewport rendering a no-go because the render time saved by hardware acceleration is lost by the frequent scene changes when editing a scene?)
The text was updated successfully, but these errors were encountered: