- User Since
- Nov 12 2018, 9:42 PM (52 w, 2 d)
Nov 19 2018
Thanks! Might be Windows specific then.
I could reproduce this on multiple Win10(64) systems. Both with Nvidia and integrated Intel videocards.
I'll try to upload more info later. But it is really simple, try the following:
I thought it is a feature, not a bug :)
Nov 18 2018
Nov 16 2018
Can't wait to try it.
Nov 14 2018
Yes, just tested it: it also happens with the --threads 1 commandline option.
But it is not Nvidia GTX specific. It also happens on integrated Intel HD graphics.
I can confirm this. Happens every time on my machine.
Win10(64), latest driver GTX670, latest daily build 2.8
Nov 13 2018
Sorry, I accidentally assigned this to myself :)
But I can confirm the bug.