I believe that I might also be suffering from this bug.
I am experiencing same behavior.
The title of this issue should be renamed to "Crashes on Edit-mode or mesh creation"
I've been running 2.79rc2 since August for hours at a time. Still works and is very reliable.
After the blender crash, I updated my graphics driver using the Windows driver update, rebooted, blender does the same crash.
I copied the opengl32.dll (linked above) into the same directory with the blender.exe. Same crash behavior.
I set the startup to factory settings, same crash behavior.
OK, progress--I can build Blender from source with Alembic enabled. Next step, @Dario Seyb (daseyb) says for Unity he used the following to add the Maya color set flag:
AbcGeom::MetaData md; m.set("mayaColorSet", "true"); m_colorSet = AbcGeom::OC4fGeomParam(m_scheme.getArbGeomParams(), “Cd”, true, AbcGeom::GeometryScope::kFacevaryingScope, 1, m_tsi, md);
Could you help me adapt this for Blender?
Ok, so this is about GLSL material display.
You can update the change by selecting different frame or continuously by playing animation.
It looks like crash does not occur with new dependency graph.
Are we talking about the previews in the node editor? Those are not expected to update when changing the object index, they are only previewing the material in isolation, the object(s) in the scene have no influence.
flame_smoke_color controls the color of smoke produced by fire, and this simulation has no fire so it has no effect.
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFE9F829ADB
Module : C:\WINDOWS\SYSTEM32\atig6txx.dll
This is expected behaviour. It was not created to handle collapsing of modifiers from "Generate" category after keyframing.
Sat, Feb 17
If I wanted to recompile Blender's Alembic export module with the mayaColorSet=1 flag added, where in the source should I look?
To do some troubleshooting:
The “Steps” parameter is specifically for kink=Spiral, and appears to affect only the presentation of the spiral,
Problem only occurs into master. No change in 2.79aRC.
Confirmed with master 5bc2c17.
Presets files are stored in a 2.79 directory. In this case it is located into a location that looks like
Confirmed on ubuntu 16.04 64bits NVIDIA Titan Black
Well, Carve was actually a good fall-back method when Bmesh boolean failed. It would be good to remove fallbacks when the main is polished and covers all the cases the fallback did?
Fri, Feb 16
ts highly likely that this bug is specific to your hardware/driver configuration. These kinds of display issues are often caused by OpenGL driver bugs.
- open blender
- delete cube
- add text
- change font
- extrude font and set size to desired
- check font for errors
- the font might have errors in the text
- if font has errors, fix all errors (text should not have any errors)
Old dependency graph does not report dependency cycles happening inside of the rig. The fact that rig works in old depsgraph might be co-incident.
Please don't triage reports yourself and leave that to developers.
Nothing changed with the opengl32.dll.
However, I couldn't say if the Intel graphical drivers are up to date (it's a company computer and I'm not admin on it).
It seems to be crashing in the AMD OpenCL code. Please try running clinfo from the command line (install package if needed) and attach its output here, so we can see the exact OpenCL implementations and versions installed.
Pitty it's already archived.
The texture that you can see in the render is in fact the entire texture, its not being cut off its being scaled. I will upload another blendfile with a blurry circle texture, this will better illustrate the problem.
Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker).
Launch Blender from the command line with -d option and attach as text file here any error printed out in the console (do not paste it directly in comment).
Try to run Blender through Software OpenGL, this will be much slower however, if everything works then it means that the bug is spefic for your GPU/Driver and you should report the bug to your GPU vendor instead.
It makes a bit more sense with the default empty cross shape, then the image is in the corner.
Please create a new bug report, with attached .blend and exact steps to redo the problem.
@Manuel Rais (g-lul) Nope, in fact if a bug does not affect current master, there’s no point in reporting it, since it has already (presumably) been solved. :)
@Bastien Montagne (mont29) Apparently, the "relocate bug" is not in the 2.79 release but in the 2.78a.
Should I report it nonetheless ?
Hi! I am still encountering this issue on Windows 10. I am using 2.79
Not a bug. +U and +V are also correct but when it goes -U and -V, its being limited off by the extrapolation of the image textures (clip instead of repeat)