Soon I will release an update. Other additions coming. I may push a release and have following builds include additions as I'm still strapped for time. This will include open source. So RC1 will be good for testing soon.
Added some more updates, etc. Frame buttons are larger and more defined. Synced animations so not to cause reloading of the form accidentally. I'm back from my adventures to hell, so forgive me for the lack of communications. I am still working on this and it's coming on great. It's good to come back fresh, I just need to check my work against my iterated list.
This is not a bug. Microsoft Windows 10 simply does not test that component, anymore. The 9.9 displayed in the old Xiret version is completely bogus, it is ALWAYS 9.9 on anything Windows 10. New Xiret hides it, as it bears no actual information, whatsoever. Take N/A as "Test skipped".
As @Carlos Detweiller mentioned, 9.9 is a sentinel value so I coded the N/A with a message (hover the n/a label). And thanks for testing, the 9.9 has been added back for RC1 which is literally around the corner. Man, v1.22 was FUGLY.
Wasn't that bad, just kinda big and clunky. It has evolved since then, just don't look back all the time. Don't forget to remove the update check in the final version, or it could hammer your server for years to come.
Forward not back, agreed. The update system has been completely revamped. Details will be available on release. The system is now automatic and users will be prompted to check for updates every now and again, but not in an annoying way. There's really not much to finish, everyone is probably looking at RC1, RC2 then a final release to public. We currently have a very solid application, it just needs finalizing and a full check over before RC2. I promise you're not looking at weeks, you're looks at days for RC1 availability, a week maximum. A week later RC2 and then a final (finally). I've just had no time for projects. Once a final has been released then open source will follow soon after, just excluding some proprietary code like error reporting and update checking.
I'm onto themeing Metrics which is the final stretch. I had an issue with parsing speed which has now been solved. Image attatched. Sorry about the scrollbar, but I haven't added my implimentation yet. My resources are going into getting the app pushed out. QB.
RC1 ready, although Metrics will stay disabled as I did not complete it within my time window. You'll see Metrics in RC2 which is the last version before release. Give me a few hours and it will be up. I have to do some ops on the server first.
When starting under Win7, I get the following error: The GUI appears, nonetheless. Didn't test any further, so far. Edit: Wiping out the old settings seems to have fixed that one. Looks like beta7 settings are incompatible.
BETA settings should be deleted. %AppData%\Xiret, delete settings.xir, restart. Or Xiret > Tools > Cleanup > Purge Application. Alternatively you can add this to settings.xir to fix it... Code: <!--0:XML 1:API--> <HardwareMode>0</HardwareMode> This happened due to a new XML node that wasn't accounted for across BETA > RC. EDIT: You got it.
Code: [INFO]: New Test Started on Friday, Jul 5 2019 12:53 PM [INFO]: Xiret v2.0.0 (8492) [INFO]: OS: Windows 7 Professional (Kernel: 6.1.7601.18015) [INFO]: Arch: x64 [INFO]: Winsat EXE v6.1.7600.16385 [INFO]: Winsat API v6.1.7600.16385 [XIRET]: Method: AsyncOut [SAE] [XIRET]: Mode: Verbose [XIRET]: Validity Int: 3 [WINSAT]: Windows System Assessment Tool [WINSAT]: > Running the Formal Assessment [WINSAT]: > Running: Feature Enumeration '' [WINSAT]: > Run Time 00:00:00.00 [WINSAT]: > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock' [WINSAT]: > Assessing Desktop Graphics Performance [WINSAT]: > Run Time 00:00:13.60 [WINSAT]: > Running: WinSAT Direct3D Assessment '-aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' [WINSAT]: > Assessing DirectX Batch Performance [WINSAT]: > Run Time 00:00:07.57 [WINSAT]: > Running: WinSAT Direct3D Assessment '-aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' [WINSAT]: > Assessing DirectX Alpha blend Performance [WINSAT]: > Run Time 00:00:07.39 [WINSAT]: > Running: WinSAT Direct3D Assessment '-aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3' [WINSAT]: > Assessing DirectX Texture load Performance [WINSAT]: > Run Time 00:00:07.60 [WINSAT]: > Running: WinSAT Direct3D Assessment '-aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3' [WINSAT]: > Assessing DirectX ALU Performance [WINSAT]: > Run Time 00:00:07.71 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' [WINSAT]: > Assessing DirectX Batch Performance [WINSAT]: > Run Time 00:00:07.47 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' [WINSAT]: > Assessing DirectX Alpha blend Performance [WINSAT]: > Run Time 00:00:07.39 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3' [WINSAT]: > Assessing DirectX Texture load Performance [WINSAT]: > Run Time 00:00:07.36 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3' [WINSAT]: > Assessing DirectX ALU Performance [WINSAT]: > Run Time 00:00:07.50 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1' [WINSAT]: > Assessing DirectX Geometry Performance [WINSAT]: > Run Time 00:00:10.14 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1' [WINSAT]: > Assessing DirectX Geometry Performance [WINSAT]: > Run Time 00:00:09.28 [WINSAT]: > Running: WinSAT Direct3D Assessment '-dx10 -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6' [WINSAT]: > Assessing DirectX Constant Buffer Performance [WINSAT]: > Run Time 00:00:07.22 [WINSAT]: > Running: Media Foundation Playback Assessment '-input C:\Windows\Performance\WinSAT\winsat.wmv -nopmp' [WINSAT]: > Run Time 00:00:02.92 [WINSAT]: > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_MPEG2_HD_15mbps.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps' [WINSAT]: > Run Time 00:00:07.83 [WINSAT]: > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog' [WINSAT]: > Run Time 00:00:07.32 [WINSAT]: > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_480i_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps' [WINSAT]: > Run Time 00:00:07.77 [WINSAT]: > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_480p_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog' [WINSAT]: > Run Time 00:00:07.63 [WINSAT]: > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog' [WINSAT]: > Run Time 00:00:07.41 [WINSAT]: > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps' [WINSAT]: > Run Time 00:00:07.39 [WINSAT]: > Running: Media Decode/Encode Assessment '-input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx' [WINSAT]: > Run Time 00:00:04.27 [WINSAT]: > MOOBE Run Time 00:02:35.67 [WINSAT]: > Running: CPU Assessment '-encryption -up' [WINSAT]: > Run Time 00:00:10.19 [WINSAT]: > Running: CPU Assessment '-compression -up' [WINSAT]: > Run Time 00:00:10.03 [WINSAT]: > Running: CPU Assessment '-encryption2 -up' [WINSAT]: > Run Time 00:00:10.09 [WINSAT]: > Running: CPU Assessment '-compression2 -up' [WINSAT]: > Run Time 00:00:10.02 [WINSAT]: > Running: CPU Assessment '-encryption' [WINSAT]: > Run Time 00:00:10.33 [WINSAT]: > Running: CPU Assessment '-compression' [WINSAT]: > Run Time 00:00:10.27 [WINSAT]: > Running: CPU Assessment '-encryption2' [WINSAT]: > Run Time 00:00:10.27 [WINSAT]: > Running: CPU Assessment '-compression2' [WINSAT]: > Run Time 00:00:10.30 [WINSAT]: > Running: System memory performance assessment '' [WINSAT]: > Run Time 00:00:05.20 [WINSAT]: > Running: Storage Assessment '-seq -read -n 0' [WINSAT]: Unable to open the drive or device. [WINSAT]: Error: Failed to properly assess the disk. [WINSAT]: The parameter is incorrect. [WINSAT]: > CPU LZW Compression 648.83 MB/s [WINSAT]: > CPU AES256 Encryption 335.68 MB/s [WINSAT]: > CPU Vista Compression 1069.20 MB/s [WINSAT]: > CPU SHA1 Hash 2614.42 MB/s [WINSAT]: > Uniproc CPU LZW Compression 85.95 MB/s [WINSAT]: > Uniproc CPU AES256 Encryption 47.98 MB/s [WINSAT]: > Uniproc CPU Vista Compression 135.70 MB/s [WINSAT]: > Uniproc CPU SHA1 Hash 331.53 MB/s [WINSAT]: > Memory Performance 14312.07 MB/s [WINSAT]: > Direct3D Batch Performance 1899.55 F/s [WINSAT]: > Direct3D Alpha Blend Performance 1929.14 F/s [WINSAT]: > Direct3D ALU Performance 927.55 F/s [WINSAT]: > Direct3D Texture Load Performance 986.51 F/s [WINSAT]: > Direct3D Batch Performance 2188.35 F/s [WINSAT]: > Direct3D Alpha Blend Performance 2218.97 F/s [WINSAT]: > Direct3D ALU Performance 1043.99 F/s [WINSAT]: > Direct3D Texture Load Performance 1127.11 F/s [WINSAT]: > Direct3D Geometry Performance 2675.81 F/s [WINSAT]: > Direct3D Geometry Performance 3915.09 F/s [WINSAT]: > Direct3D Constant Buffer Performance 2295.46 F/s [WINSAT]: > Video Memory Throughput 62860.70 MB/s [WINSAT]: > Dshow Video Encode Time 1.25692 s [WINSAT]: > Media Foundation Decode Time 0.94544 s [WINSAT]: > Total Run Time 00:04:02.41 [XIRET]: ProcessWatcher Wait... [OKAY]: ProcessWatcher shutdown complete [ERROR]: The assessment ran with 1 error(s) [XIRET]: ExitCode: 1 [XIRET]: Validity Int: 3 [INFO]: Process finished Not a Xiret error, it also errors out if running: Code: C:\UserProgramFiles\Xiret>WinSAT.exe diskformal Windows System Assessment Tool > Running: Feature Enumeration '' > Run Time 00:00:00.00 > Running: Storage Assessment '-seq -read -n 0' Unable to open the drive or device. Error: Failed to properly assess the disk. The parameter is incorrect. > Total Run Time 00:00:01.14 C:\UserProgramFiles\Xiret> As explained in the linked topic, it is a long standing bug with avast! AV.
Good to see Xiret is still alive and kicking 1. In any sub-window, when hovering the close button, the X appears to be slightly off-center. 2. After changing Default hardware mode from XML to API (and vice versa) and clicking Okay in the Settings dialog, the listed hardware doesn't refresh unless you disable and re-enable "Show hardware". 3. Hovering links across Xiret results in a non-native hand cursor. I'm on Windows 10 and I see a small (probably because I'm on 150% DPI) Windows XP hand cursor. 4. Any chance for "OK" instead of "Okay" in Settings? 5. The shortcuts seem to have too much dead space on their right.
@ItielMaN thanks for testing. I'm not currently home but will look into these. I picked up on the hardware issue last night so thanks for confirming. Will reply in detail later on today. Good to see you about. @Carlos Detweiller is there any chance you could disable avast and test? Regardless of it being an issue with avast, I can always impliment a fix around avast
1. I have made some adjustments, they should be much better now. 2. I've fixed this ready for RC2. 3. This is normal as it's the default cursor within VS. 4. Yes, I'll agree since Okay derived from OK, Since it's the same within Win anyhow. 5. I know what you mean but this is built into the control spacing and is a reserved space for the dropdown arrow. 2px margin and 16px for the arrow. I will see if I can shave off 16px but it may cause issues.