Neither I said that it's an acceptable solution, or that it doesn't have to be fixed, it was purely troubleshooting.
But if I must be honest with you, I'm very less mad at them for having problems on a system that could use up to 12 cores, than companies locking their software at 1 or 2 cores telling you to just "deal with it".
I mean, I'm using an hyper threaded esa-core at 4.2 GHz, I might still be able to do it, but when limiting cores on lower frequencies, say, 2.7-3 GHz, you're really doing it wrong, and I've been on that part of the spectrum for a long time.
Again though, if you're having heavy troubles like I did, and could try the Process Affinity, it could really help them pinpoint the problem and fix it sooner. I still don't know if this works only for me and the other guy in this thread before, or for everyone. Knowing this makes a huge difference.
@Varstahl wrote:Neither I said that it's an acceptable solution, or that it doesn't have to be fixed, it was purely troubleshooting.
But if I must be honest with you, I'm very less mad at them for having problems on a system that could use up to 12 cores, than companies locking their software at 1 or 2 cores telling you to just "deal with it".
I mean, I'm using an hyper threaded esa-core at 4.2 GHz, I might still be able to do it, but when limiting cores on lower frequencies, say, 2.7-3 GHz, you're really doing it wrong, and I've been on that part of the spectrum for a long time.
Again though, if you're having heavy troubles like I did, and could try the Process Affinity, it could really help them pinpoint the problem and fix it sooner. I still don't know if this works only for me and the other guy in this thread before, or for everyone. Knowing this makes a huge difference.
Not trying to jump on you. I just want to underline that this is in no way a final fix because I am paranoid about EA taking this as an excuse to ignore the issue...they already marked on earlier thread on this issue as "solved" because of the disabling multi-core thing.
