I had just implemented that workaround and was seeing great improvements, when an update to the intel driver came through.
EXA now seems to be fixed and is working smoothly in the latest build.
So this bug should be 'fixed'?
I had just implemented that workaround and was seeing great improvements, when an update to the intel driver came through.
EXA now seems to be fixed and is working smoothly in the latest build.
So this bug should be 'fixed'?