I need to know the file that this function is contained in before I can do that though.
|
Hyrule Field Slowdown Observation
|
|
03-29-2010, 12:53 PM
I need to know the file that this function is contained in before I can do that though.
Class view => Search YieldCPU():
[color=#696969]..\Core\Common\Src\Thread.h => 216 inline void YieldCPU()[/color] That one? Is just _mm_pause .. O_O"
03-29-2010, 01:53 PM
(This post was last modified: 03-29-2010, 01:59 PM by Xtreme2damax.)
I don't think that is it, that doesn't seem to do much of anything if it does anything at all. The code would likely be in the C++ file, but I can't seem to find YieldCPU() in thread.cpp, so the actual function might exist in a different file. I'm going to check the Fifo.cpp and Fifo.h to see if this function exists in there.
Scratch what I mentioned above, upon examining the files and the functions a bit more I was aware of what they were for. Fifo.cpp references thread.h, YieldCPU() functions exist in both these files. If there is anything you would like me to test skid, be sure to let me know.
03-29-2010, 02:21 PM
I think we are passed the point of testing and at the point of needing some coding being done. I enjoy testing things just as you seem to, but since the problem is already known but is just not quite fixed yet, no amount of testing is going to magically make the correct code appear in the emulator.
Asus Laptop: K53TA
OS: Windows 7 Home Premium, 64-Bit - SP1 CPU: AMD Llano A6-3400M, Quad-Core, 1.4GHz-2.6GHz (Overclocked) GPU: AMD Radeon HD6650M, 1GB GDDR3 (Catalyst 13.1) RAM: Samsung 4GB DDR3-1333 03-29-2010, 02:38 PM
(This post was last modified: 03-29-2010, 02:39 PM by Xtreme2damax.)
I realize that, I was thinking of anything skid could suggest changing in the YieldCPU(); function that way I can test to see if it has any impact on the slowdowns and report back, this way it saves the developers some work since they have already done some amazing work on the emulator.
03-29-2010, 03:13 PM
(03-29-2010, 01:11 PM)KrossX Wrote: Class view => Search YieldCPU(): Yes, that is the one. The fix is to replace it with something better than _mm_pause. What to replace it with? dunno. 03-29-2010, 03:27 PM
Quote:#ifdef _WIN32 Is this code commented out in thread.h? If so, why is it commented out? 03-30-2010, 12:19 AM
(This post was last modified: 03-30-2010, 01:20 AM by Starscream.)
(03-29-2010, 03:13 PM)skid Wrote:(03-29-2010, 01:11 PM)KrossX Wrote: Class view => Search YieldCPU(): How about __yield http://msdn.microsoft.com/en-us/library/2b2h26kx%28VS.80%29.aspx
Asus Laptop: K53TA
OS: Windows 7 Home Premium, 64-Bit - SP1 CPU: AMD Llano A6-3400M, Quad-Core, 1.4GHz-2.6GHz (Overclocked) GPU: AMD Radeon HD6650M, 1GB GDDR3 (Catalyst 13.1) RAM: Samsung 4GB DDR3-1333 03-30-2010, 01:19 AM
I did a bit more testing and it seems the slowdowns do in fact occur in single core mode.
03-30-2010, 03:47 AM
(03-29-2010, 09:05 AM)skid Wrote: It is generally known what is causing it to slow down, but a suitable solution has not been found. And is it only found in this game or is it also known or suspected for others? (might get some clues through this)
Intel i5-4690k (Devil's Canyon) @ 3.5 GHz (+Scythe Mugen) / Gainward GTX 1070 Phoenix (OC'd) / ASUS Z97 PRO GAMER / 16GB G.Skill DDR3-2400 CL10 TridentX / X-Fi XtremeMusic / Win10 Pro 64bit / Dell S2716DG Monitor / 3x original WiiMote+MotionPlus+Nunchuk
|
|
« Next Oldest | Next Newest »
|