Unfortunately the recommended fix mks.vsync= "1" does not work in my situation where I run a MokaFive player on VMware Fusion. The MokaFive player appears to fetch a config file from the MokaFive server which overwrites the mks.vsync= "1" in the VMX file. So whenever I start the MokaFive player, the parameter is overwritten.
It would really help if this issue got fixed properly and not with a workaround. At the moment, I plug a Thunderbolt Ethernet adapter into the Thunderbolt interface (no kidding!) and that gets rid of the flicker. But, come on, that is not a real solution! Any other suggestions?!