Thomas Holder

I can't reproduce this (macOS 10.14). Running from shell (bash) or from perl gives the same result for me.

This is not a bug, but a limitation of the current implementation. `b` is not implemented as an atom-state level property. The only way to have per-state b-factors is by...

It's currently not implemented. Pull requests welcome :-)

Is this with the DMG from https://pymol.org/#download ? Does it happen with any load or save location or only with specific folders?

Does it make a difference if you change **light_count** and/or **spec_direct** settings? They are blacklisted for "GDI Generic" driver. https://github.com/schrodinger/pymol-open-source/blob/master/modules/pymol/__init__.py#L325 Also looks like **use_shaders** is off, try if enabling it...

**use_shaders** won't work with Remote Desktop. Does the same happen with the Windows ZIP archive from https://pymol.org/#download ?

Seems to be a problem in [TriangleFixProblems](https://github.com/schrodinger/pymol-open-source/blob/95a44ada8bacfe345905a5df0a70376eb1b455b1/layer0/Triangle.cpp#L2007) (fantastic name!). If I comment out that function, it doesn't crash and the surface looks correct as far as I can tell.

Thanks for the additional info. This is really strange, in principle all those subunits are identical, but the only subunit that crashes is `surf1_unit1_str0_119`. Applying some random rotation to `surf1_unit1_str0_119`...

Scenes do not store any [settings](https://pymolwiki.org/index.php/Category:Settings). It's a reasonable feature request and we certainly accept contributions. Things to consider: - What's a user friendly API? Automatically storing all currently changed...

Yes correct, I would suggest to modify the `MovieScene` class, and maybe `MovieSceneObject` to support object-level settings. There are two ways to store settings, either with an instance of `CSetting`...