@Brecht Van Lommel (brecht), mind having a look here? Thanks!
Here's what I've got so far...it builds successfully and exports valid Alembic files, but abcls doesn't find the mayaColorSet=1 flag so I'm still doing something wrong.
Alembic::AbcCoreAbstract::MetaData md; md.set("mayaColorSet", "true"); OC4fGeomParam param(prop, name, true, kFacevaryingScope, 1, 0, md);
Yes, I forgot to update part of the code, will fix.
Confirmed, also happens with Glass BSDF. Any idea @Brecht Van Lommel (brecht)?
Caused by rB4f1c0a1. Will give a closer look on what's wrong in that commit later.
Implemented import & export of camera focal length in FBX now, so will re-assign to @Sybren A. Stüvel (sybren) for the Alembic part of it…
This shouldn't have been closed yet.
May or may not be related to T53914.
Sorry, it's been a while. :)
If you're checking, then please triage the status.
Discussed with other developers about ways to process here.
Confirmed, and also https://builder.blender.org/download/#hop doesn't seem to do anything... (on chrome Version 64.0.3282.167 (Official Build) (64-bit))
Will check on that. Thanks for the report!
Can confirm the bug.
Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.
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?
Sun, Feb 18
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,