Releases: sp00n/corecycler
Releases · sp00n/corecycler
v0.8.1.0 RC3
Fixed some problems with the case sensitivity.
v0.8.1.0 RC2
Release Candidate 2 for version 0.8.1.0
- There's now an
auto
setting for theruntimePerCore
, where it will test all FFT sizes before continuing to the next core - It's now possible to define a custom FFT range in the
FFTSize
setting (e.g.8-24
) - Improved error detection when CPU usage was too low
- Changed the
verbosityMode
setting tologLevel
and added two more options
v0.8.0.0
- Updated Prime95 to 30.5 build 2
- Support for Aida64 and Y-Cruncher! You can now define which stress test program to use (Note: see the readme.txt for more infos on Aida64)
- Restructured the config file to support Aida64 and Y-Cruncher. Old config files will not work!
- Added a new "suspendPeriodically" setting, which is activated by default. This setting tries to simulate load changes by periodically suspending and resuming the stress test program
- Added a new "coreTestOrder" setting, which defaults to "Alternate" (for more than 8 cores/2 CCDs) or "Random" (max 8 cores/1 CCD). You can also define a custom order for the sequence in which the cores should be tested (e.g. "5, 7, 5, 1, 0, 7, 4")
- Added more presets for Prime95: "Moderate", "Heavy" & "HeavyShort". See the config file for additional explanation about these presets
- The priority of the stress test process is now set to "High" to prevent other processes from "stealing" processing power and produce false alarms due to low CPU usage
- Starting a stress test program will not steal the focus anymore (or give it back immediately to the last opened window)
- The script will now try to close the stress test program after pressing CTRL+C, if it is still running and using CPU processing power
- The title of the terminal window is now set to "CoreCycler"
- The approximate CPU frequency is now visible in the verbose output (but unfortunately it's not as accurate as e.g. HWInfo64 or Ryzen Master, which is why it's not in the main output)
- All logs are now in the /logs directory
- Added an "analyze_prime95_logfile.ps1" script to the /tools directoy, which can be used to determine the time it took for all FFT sizes to appear at least once for each iteration within a Prime95 log file
- Added "CoreTunerX" to the /tools directory. See https://github.com/CXWorld/CoreTunerX of what it can do
v0.8.0.0 RC5
Still intended for beta testing only.
- Updated Prime95 to 30.5 build 2
- The analyze log file script now autodetects if one or two threads were used
- Fixed a bug where Aida64 did not close correctly
- Fixed a bug where the test run for a core was not immediately stopped when an error occurred. This could cause a loop where an error was thrown over and over again until the runtimePerCore was reached
v0.8.0.0 RC4
Still intended only for beta testing.
Some more bug fixes and improvements, hopefully without introducing new bugs.
You can now define your own custom testing order by providing a comma separated list to the coreTestOrder
setting.
v0.8.0.0 RC3
Still intended only for beta testing.
Fixed a couple of issues, especially the affinity not being set correctly for 2 threads and the Y-Cruncher window not recognized correctly (at least I hope so).
v0.8.0.0 RC2
Pre-release for version 0.8.0.0, only intended for beta testing.