Hi all,
I still appear to be getting this bug:
Is it not fixed in 5.1 release? I wasn’t getting it when I was using the beta. Sorry if I’m not posting this in the right place.
Hi all,
I still appear to be getting this bug:
Is it not fixed in 5.1 release? I wasn’t getting it when I was using the beta. Sorry if I’m not posting this in the right place.
I wish “fixed in future releases” read “Fixed in releases X, Y, Z”
it is fixed in 5.1p1
My Version is the 5.1.0f3 Personal and the error persists.
5.1p1 is newer than 5.1.0f3. It is a patch release.