Originally Posted by netllama
Thanks for clarifying. I was able to reproduce both of these problems with 1.0-8756, however both no longer reproduced using the latest internal development driver. The next released driver will, unfortunately, not include this fix, however the driver after that should.
Do these upcoming driver versions have version numbers assigned to them yet? It would be really nice if I knew which version number (even if it's coming up in a month or two) will work correctly so I can tell VMD user's what version to wait for when the subject comes up.