Smart Defrag 歷史版本列表
更新時間：2023-02-01
更新細節：
更新時間：2023-01-31
更新細節：
更新時間：2023-01-25
更新細節：
What's new in this version:
Main:
- Minor, cosmetic bugfixes
Enterprise:
- FIX : The serial numbers for some components were missing in the JSON report
更新時間：2023-01-19
更新細節：
更新時間：2023-01-14
更新細節：
更新時間：2023-01-09
更新細節：
What's new in this version:
Main:
- Fixed : The upload would still occur if it was disabled in the settings
- Added a fallback to another endpoint to the upload in case it fails
Monitoring:
- Engine updated
更新時間：2022-12-21
更新細節：
更新時間：2022-12-13
更新細節：
What's new in this version:
Main:
- Improved upload error logging
Main:
- Fixed: The GUI would refuse to start if no GPU was detected
Cpu:
- Instruction Set: Auto will be set to AVX2 instead of 512 as this option has proven to be much better at error detection ( for now )
- Gpu3DAdaptive
- The initialization time won't be counted in the global timer anymore. This means the test will apply the loqad change roughly 2s after starting, time for it to initialize
Gpu3DAdaptive:
- Fixed: Much smoother curve on older GPUs
Gpu3DAdaptive:
- Fixed: the load was set too low on RTX4090, resulting is a steep jump between 99% and 100%
- Gpu3DAdaptive
- The test will have a much better scaling on newer GPUs ( RTX4090 especially )
Benchmark:
- Fixed: uploading would fail in edge cases ( those issues are tough to reproduce )
StabilityCertificate:
- Fixed: a rare bug would prevent stability certificate from uploading properly
Enterprise:
- Fixed: OCCT Command-line would error out when loading its config file and revert to the default values
更新時間：2022-11-14
更新細節：
What's new in this version:
Vram:
- Fixed: The memory available for testing was reported as 1GB instead of its real value
更新時間：2022-11-11
更新細節：
What's new in this version:
Main:
- Fixed the upload issue - the previous fixes from 11.0.14 are now back in the main branch
Main:
- Revamped the way OCCT is listing GPUs for better compatibility with ARC GPUs
Cpu:
- Fixed : threads were competiting too much for a single resources, resulting in a loss of efficiency in high thread, small data set scenarios
Report:
- Fixed : If a duration was exactly 00:00:00, the report would display it as "invalid duration" in the log