
Fayabella depicted the issue perfectly.
As stated in the first post it happened only once on the very first start after a fresh install with 0.17.0T-A-R wrote: Thu Feb 28, 2019 2:27 pm I guess they only look to the latest update. did updating to 17.2 fix the problem for you?
Thanks!T-A-R wrote: Wed Feb 27, 2019 6:39 pm OP, please add version number to the title if possible in [square brackets].
I encounter the same playing [0.17.2]: