(02-15-2014, 02:50 PM)JMC47 Wrote: [ -> ]It's very likely that whatever the netplay branch is doing costs performance. Are you sure it's any better than just running it in single core if it's really laggy and slow?
In the case of Skies of Arcadia, yes. The Netplay branch is faster than the last dev version running single thread.
And I'm done with people telling it's an overheating issue when it's obviously a bug with code that has now been verified.
My CPU is also a Core 2 Duo and it DOESN'T THROTTLE. It's not an i5-i7 with variable frequency. My CPU is at 3Ghz, always. And it can run under 100% load for HOURS without any stability problem. Whereas I can make Dolphin crash within SECONDS if I try hard or if there's something lagging it.
It's CPU timing that is bugged, under stress it breaks, but not because of hardware issues. And also because Dolphin is basically just two threads, that's why I'm getting full speed (on PAL) in Xenoblade even with this old PC that is merely dual core at 3Ghz.
(02-16-2014, 12:06 AM)DJBarry004 Wrote: [ -> ]Not just a verified bug but a "completely clear" performance issue due to using an old, outdated CPU. If anyone already said this, consider this reply as a "ninja´d".
We play with words now?
A crash isn't a "performance issue" in my vocabulary. If the multicore code works on very powerful CPUs only it is not because there are no bugs, but merely because the bugs aren't showing even if they are present.
I really find baffling this hostile attitude toward someone who's reporting a factual problem. What's this infantile attitude?
Other people aren't getting the same problems as you are and That's why they're saying it's a problem on your end. I don't get crashes
even on the most demanding games and my CPU is not the greatest.
Not to even mention that I wasn´t referring to the crash at all; I was referring to the slowdowns seen in "older" posts on this tread (the last ones on page 1).
There may be no fix; you realize. Dualcore Netplay breaks hundreds of games and fixes very few while being very invasive to how Dolphin works; it's not possible to enable/disable it really. You could just use synchronize GPU feature that should fix issues in most of those games, but it comes at a fairly high performance cost.
(04-27-2014, 09:30 AM)Fadeout Wrote: [ -> ]Just reporting that in two months nothing changed for this threading bug.
We are waiting for you to submit a patch.
(04-27-2014, 11:50 AM)JMC47 Wrote: [ -> ]There may be no fix; you realize. Dualcore Netplay breaks hundreds of games and fixes very few while being very invasive to how Dolphin works; it's not possible to enable/disable it really. You could just use synchronize GPU feature that should fix issues in most of those games, but it comes at a fairly high performance cost.
I don't expect the dualcore branch to be merged, but I'm hoping it can be useful to isolate and track the issue so that it could be eventually fixed on its own.
And when I "report" nothing happened in two/three months I don't mean that I demand devs working on this right now. Just that whatever code was added didn't affect directly this issue.
Since no devs seems really caring about this (and Delroth was quick to mark it as "low priority" to send the massage he couldn't care less), my actual hope is that it is *incidentally* fixed by some other patch that ends up affecting this. Hence the need to test the new versions from time to time to see if something happened or not.
You don't seem to understand; it was marked as low priority because there probably isn't a fix for it. It's just because dualcore mode is a huge hack to speed up the game. There is a fix already in the emulator called sync GPU, that you can turn on in the game properties window. Any fix to these games would slowdown dualcore mode, which a lot of people won't like (for those games that don't crash) and any other fix than syncGPU probably can't be merged without screwing up a ton of stuff.
Quote:Since no devs seems really caring about this (and Delroth was quick to mark it as "low priority" to send the massage he couldn't care less), my actual hope is that it is *incidentally* fixed by some other patch that ends up affecting this. Hence the need to test the new versions from time to time to see if something happened or not.
It's low priority because indeed, no one cares about it. You don't need to report if it's not fixed, unless there is reason to believe it was fixed, but actually isn't. Otherwise just wait and if it ever IS fixed and we don't realize, let us know then.