Joost Ellerbroek

Hi @uriibra, If I run your scenario directly in bluesky I get no errors. The code snippet you've posted is incomplete (your function `simulation()` isn't called for one), but other...

Ok, I also tried turning your code into a minimum working example: ```python import numpy as np import bluesky as bs from bluesky.simulation import ScreenIO class ScreenDummy(ScreenIO): def echo(self, text='',...

Well, it does for me: the `gh_test` file in my example is the scenario file you provided in your first post in this issue. Your problem therefore has to lie...

This has been reported once before, and seems to be related to an incompatibility between a shader setting and your video card driver. I can't reproduce this, so it's difficult...

Hi @rgovindjee, the only difference with other (working) GL functions that I can see is the use of `QOpenGLShaderProgram.setAttributeValue` to set a fixed scale for screen-coordinates shapes. I've just committed...

Yes, although it is not actively maintained, so it could be that incompatibilities exist. Could you let me know a bit more about the system you are having these issues...

Hi @rgovindjee, can you check if the size of the symbols scales with the zoom factor? Does the symbol size change when you zoom in/out?

Ok, in that case it looks like the `switch` statement in the shader is not honoured. Let's see if we can come up with an alternative approach.

Hey @TejEddineLakhal, thanks a lot, that's a useful suggestion!

@andubadea, @amorfinv: Could you help @Hehehedele out with this?