Francisco Javier Santos Maximiliano
Comments
Then I'll have to wait for another patch to come out to see if they already solved it
So it is a bug since 1.16.20, which you have not been able to resolve?
Reporting that the error still persists even with the update of 1.16.40; it keeps giving the same error