- User Since
- Oct 2 2014, 3:13 PM (124 w, 6 d)
Mon, Feb 20
Sorry, this is not the right place for end user support, please seek user support on user forums like blenderartists.org or blender.stackexchange.com.
Please do not assign priority your self,
Fri, Feb 17
My bad, i could have sworn we used the internal noise functions from osl. I stand corrected.
Thu, Feb 16
Not sure diverging from what OSL is doing is that good of an idea, even for 2.8, We either have to re-implement cellnoise+Voronoi in osl scripts which will be significantly slower, or patch osl while we're building it to keep consistent results between SVM and OSL. Is it really a problem worth solving?
Bugs can be frustrating, but please try to remain civil , there is no need for name-calling.
Wed, Feb 15
Tue, Feb 14
I remember looking into this, the problem was audaspace is being shutdown on the mainthread, but then the render thread does a audaspace call anyhow, null-refs and takes down the process.
Sun, Feb 12
Seems alright here, are you by any chance also getting a message from windows about the graphics driver being restarted?
Sat, Feb 11
allocates a buffer 1280(w)*720(h)*1(d) but
-t 1 doesen't help , but i was able to grab a stack trace
Yup was able to repro it on a clean win7 VM, but not with a debug build, so feels like a race condition somewhere
Could be anything really, but unless we can reproduce the issue it'll be very hard to point a finger at something.
try running "blender.exe --factory-startup"
i am running win7
With latest buildbot ( 38155c7 ) win64 , did i miss anything?
Thu, Feb 9
I'm unsure what you are trying to say, is the problem solved?
Hard to say what is going on without a blend file or more information, if i have to guess and i have to admit I AM guessing , you're hitting a display driver timeout which restarts the display driver causing blender to crash. Try reducing your tile size, and see if the problem goes away.
Wed, Feb 8
Duplicate of T50001
Tue, Feb 7
Known issue, fixed in the upcoming blender 2.78b, in the meantime you can grab a daily build from builder.blender.org to work around the issue.
Sat, Feb 4
Fri, Feb 3
Using latest buildbot builds ( 9f67367 ) it only happens to the AVX2 kernel
Interesting, with my 'default' startup, it works fine, however if i start blender with --factory-startup i can repro the issue on win7/x64.
Thu, Feb 2
can confirm it's fixed with the latest libs.
Tested on win7/x64 with 3ab8895 , seems fine here, could be an addon causing issues, try starting blender with the --factory-startup parameter and see if it's still an issue.
Tue, Jan 31
Can't reproduce all 3 seem to render just fine? (Win7/x64/gtx670)
Best I could find is that the the 965 express chipset only supports opengl1.5 ( http://www.intel.com/Assets/PDF/datasheet/316273.pdf ) so the error message is correct and your video card is too old to be used with blender.
Mon, Jan 30
you were the last one to touch this bit @Germano Cavalcante (mano-wii) , can you take a peek?
Sun, Jan 29
Wasn't related to the recent osd upgrade (I always test the libs on all configurations before uploading them), the landing of D2367 which phased out the use of find_package was the culprit.
Will look into this.
Fri, Jan 27
Can easily repro on windows, even with a debug build.
Thu, Jan 26
hey sometimes it crashes
soo what are you doing?
can't tell you
Wed, Jan 25
Updated with your macro, much nicer.
This is a known issue, and the good news is: fixed already! if you need the fix urgently you can grab a build from http://builder.blender.org otherwise this fix will be included in the next official update.
Jan 23 2017
You are correct, did a build this morning without the sub modules, both locale and addons warn on their own, and it produces a runnable build. no idea what this guy on irc was up to then..
Known and fixed issue, if you want the fix right now, grab a daily at http://builder.blender.org otherwise this will be included in the next release.
Jan 21 2017
Can confirm the compile error with uint on windows as well, however if i manually fix the error, I'm also greeted by a linker error
Jan 20 2017
Jan 19 2017
There's very little to go on here, try using something like process monitor ( https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx ) to see what's going on.
Jan 18 2017
This issue has been reported before, and the good news is: fixed! You can grab a build from http://builder.blender.org if you want it right now, or wait till the next release which will include this fix.
Jan 17 2017
ng.outputs.new("NodeSocketColor", "color") ng.inputs.new("NodeSocketShader", "shader")
will probably work.
Jan 15 2017
mont29, thread gets created here
Good news! This issue is already fixed! If you want the fix head over to https://builder.blender.org/download/ and grab a nightly, otherwise this will be fix in the next official version!
Jan 14 2017
Tried 2.78a on 32 bit windows 10 also unable to reproduce....
Jan 13 2017
In all fairness asking for a .blend is not a form victim blaming, sometimes it's just easier to reproduce a problem that way, what's always happening to you, might not happen to us, I just tried to reproduce this report, rendered my default cube, Full Sample on, off, didn't matter, rendered with no problem. messed 5 minutes with various options trying to trigger it , couldn't make it happen, Now if I had a .blend that would have crashed as soon as I hit render, I could have spend that time actually fixing the problem. So it's not a 'we don't believe you! prove it!' it's more of a 'help us to help you'
Can't repro either, please upload a sample blend, so all we have to do to trigger the crash is enable dupli verticles?
Can you try forcing vsync on for blender in the nvidia settings?
Jan 9 2017
Not sure why, file is bigger now, but still missing textures,still the wrong layer selected and still no crashing behavior.. please resist changing the priority your self, it's easier for us if we manage that.
Jan 8 2017
The sample file is missing some textures (be sure to use file->external data->pack into blend before uploading) , also there's nothing to render on the layer selected? When changing to the first or second layer, it renders fine with both 2.77 and 2.78a. Please provide a better test case.
Jan 7 2017
this is a known issue, good news: it's fixed already! Pick up a build from builder.blender.org and you'll be allright!
Yup, that's TDR in action :) If you still want to render with a larger tile size here's how to change or disable the timeout value (but naturally anything you do is at your own risk)
mont29 you know the relink code better than anyone else, mind taking a peek here?
Jan 5 2017
Can't repro either, but given the scene is very slow to render, i'm guessing he hit the TDR timeout on his gfx driver, try rending with a smaller tile size.
Yeah not much we can do about this, get more ram is my best advise.
Jan 3 2017
added brackets to one-liners that needed it.
changed fmax to fmaxf some compilers did not have the float overload for fmax and caused a compile error.
Jan 2 2017
Updated codesyle with feedback and fixed the gsgl shader with dingto's tip
Dec 25 2016
please don't triage your self. Also please attach the file you are having problems with.
Dec 24 2016
closed by committing rB3a9c490531556c1bad6e1f6e8cd7cd7f026b8437
Dec 23 2016
Helped out on irc, but just for future reference, "bf_draw wasn't added to the SETUP_BLENDER_SORTED_LIBS macro in buildfiles/cmake/macros.cmake"
Dec 19 2016
Your sample file renders fine here, what exact steps need to be done to make blender crash with this file?
It got updated after 2.78a got released, try a nightly from builder.blender.org
Dec 17 2016
Update: With this fix and D2367 applied , x86/2015 passes all of our tests tests.
Dec 15 2016
This is fixed already, please try a nightly build from https://builder.blender.org/download/
I'm open for an alternative for the monstrosity that is the python path, it's the only way i found that supported both the release and debug version on windows, while also not breaking on linux.
Dec 13 2016
Dec 12 2016
@Kévin Dietrich (kevindietrich) Tricky one to reproduce, there's some subtlety to it. I can repro the bug but only if import the .abc file with 2.78a .