04-30-2020, 10:49 PM
(This post was last modified: 05-04-2020, 04:57 PM by Hans Peter Augustesen.)
(04-22-2020, 11:03 PM)Hans Peter Augustesen Wrote: "Is anyone else having this issue?"
"Me too.. Exact same problem"
"Yes, this is a new bug, or so it seems"
"Same same - no solutions?"
Listen to the man (Dimitri Muskens in this very chat):
"It just might work in the future"
"not top priority to keep the service running."
Read the writing on the wall!
Fixed in latest 1.0.3703 client. [that last sentence must be some kind of error from my side - just ignore it]