You're running Windows 10 there, so N/A is appropriate for your Windows. If you ran Xiret on anything below Windows 10 the gaming score would be returned. I have made it so people understand the 9.9 is a sentinel value. Instead of showing a static 9.9, I have made it return N/A on Windows 10 only. Does this help?
Ah I see. I thought you were aiming towards displaying the assessments results relevant to the OS on which the assessment was running.
No, the application only displays N/A when Windows 10 is detected as it's designed to pick scores in the system, but I understand if you migrate scores from another PC, or upgrade and restore (win7 example), you should re-run the assessment again as Win10 will always display N/A. I wonder now if having the N/A is a bad idea...
No need to send that assessment XML. It's just how the VBox adaptor reports its memory. After all, it's not a physical but only a virtual device that might assign resources on-the-fly. Just have the display of video memory round the result to 2 numbers following the dot. Like 383.62MB instead of 383.62109375MB As for the N/A problem, just use a simple AND logic: IF OS is Windows 10 AND the actual value is 9.9, THEN display N/A. Alternatively, just include the original value in the tooltip.
I am now done here until after the holidays. I hope everyone has fun, gets drunk, eats well and spends time with their family. Please do not forget about those less fortunate; and bare a though for them, if you will.
I have now picked up where I left off. Some more changes are ready for B6 which are as follows: - Fixed DPI scaling issues - Fixed updater core bug - Fixed UI framework bug Scaling: I bit the bullet and added TableLayoutPanels. Why I didn't do this before is beyond me. All panels now show with their single pixel space in my tests and should provide a better overall experience. I've pretty much solved all scaling issues as 100%, 125%, 150% and 175% are all fine for me. N/A for Windows 10: I'm going to leave the "N/A" code how it is. If you change your machines operating system, the test is not valid so it's not a relevant issue. I will however add the suggested changes to the coming addition where you can view past scores. UI Framework: The terrible radio buttons have been overhauled. Unfortunately the outer diameter wasn't being rendered properly, which has been fixed. These changes include the fix for off-center text in RadioButtons and CheckBoxes. Save as text option: As requested some time ago, I have edited the "Save as text" option to include your lowest subscore(s). You can see the restructure below. Code: Windows Experience Index scores generated by Xiret on 31/12/2018. Base Score: 8.1 Processor Score: 9.1 Memory Score: 9.1 Graphics Score: 9.3 Gaming Score: N/A (The D3D tests are not scored on Windows 10) Disk Score: 8.1 (*) (*) - Lowest subscore Regards, QB.
New version available! Link removed - Version superceeded. Archive structure and checksums: Code: Xiret2b6.exe * D0349F21B1AA38E25C8CECD82BC5DA79B00DE5C2821D31C3E8FD85061682C869 virustotalbeta.txt * 8E3630E6B5FE07B367BA15FA63C717B348DA821538E5BA01A368A1E8235D1993 betachangelog.txt * 4E14D7C0416436FE7B3CF7F7FB01CCBD5FD528BD0FF239E0BC7E3A9A83A010C3 Archive Checksum: DE1827147779D2846B5CBEB99904B9EE87A8A6C1FAC28A809381847064D5FE1E Changelog: Code: Enhancements: 1. UI Framework improvements 2. General UI improvements 2. Replaced link to Bitmight with link to the MDL support forum (environment window) 3. Much better DPI scaling 4. Changed the "Save as text" function to include lowest subscores 5. Added developer menu so users can test tool windows, etc (beta addition only) 6. Made option controls more defined 7. Sped up form animations Bugs: 1. Fixed label heights (main form) - ItielMaN 2. Fixed label text cut off issue caused by UI framework (about section) - ItielMaN 3. Fixed misc UI framework issues - NoFace 4. Fixed see-through form issue related to WS_EX_COMPOSITED (main form) - ItielMaN 5. Fixed incorrect form names in the taskbar - ItielMaN 6. Fixed missing form icons in the taskbar - ItielMaN 7. Fixed IO exception - Carlos Detweiller 8. Fixed update core issue - NoFace 9. Fixed escape key not closing certain windows (repair window, environment window, update window) - NoFace Misc: 1. Updated copyright Some changes may not be listed. What happens next?: 1. I take a break to play through Rise of the Tomb Raider in 4K 2. User wait period 3. Finishing and enabling the following:- - Metrics - View past scores - Assessment Mode - Portability - New assessment code - Still maybe, Vista support - So far, it's working my side. A few patches to Segoe UI are needed Regards, QB.
Unfortunately, I don't use Vista anymore. I still have test VMs with Server 2008 SP2 (Vista kernel), but I found that servers do not seem to have any WinSAT component, and thus the tool does nothing on them. Oh, yes, another thing to consider: The results can unfortunately not be compared between the OS. Vista scales 1.0 to 5.9 Win7 uses 1.0 to 7.9 Win8 and 10 1.0 to 9.9 AFAIK. Would be nice if it was possible to display what OS generated the data record. No idea if that information is included.
Xiret displays the scales in the top uncategorised label, which I have realised is incorrect on vista (will be fixed). The main form is only used to get the current scores, not previous scores that were generated on a different OS with different information. Now Xiret does not use the XML files I will add what you requested to the view past scores addition. Which OS the file was generated on is stored in the XML and can be queried with XML or API.
Another proposal for the future: Show how the current scores changed from the previous ones, e. g. show how my new piece of hardware managed to increase the figures (usually you need to re-calculate when you change hardware).
Awesome, B6 looks pretty good 1. In the repair window, there's double spacing between "system" and "scores". 2. Uploading scores to Imgur / exporting them to a file includes the bottom separator in the image (see comment 349). Is that intended? 3. Is there a way for you to disable Win+Up arrow key, or ignore such combination while in the app?
@ItielMaN 1. Repair window to be deprecated in B7. It may be brought back when the addition to view previous scores is added. 2. You're right it looks odd, I'll move it out of the print-screen bounds. 3. I see what you mean, yes I'll block it. I remember discussing this before but it must have gone over my head. Thanks for testing buddy. @Michaela Joy Thanks. This should do it. I'll be on to chat soon. @Carlos Detweiller Maybe a compare with previous score addition is a good idea. May as well make it the best WEI tool out there
Preliminary changelog for B7: Code: New: 1. Vista compatibility 2. New 'non-versioned' WSR* update Enhancements: 1. Redesigned about section 2. Better date format for 'last update' (main form) 3. Better detection for unrated systems 4. UI Framework enhancements 5. General UI enhancements 6. Disabled WinKey+Up on all forms Bugs: 1. Fixed update core issue (NoFace) Misc: 1. Updated copyright 2. Updated acknowledgements 3. Removed repair window as it's no longer necessary *WSR (WinSAT Reader) is used to power the Xiret Core and contains all information needed to read current WinSAT information. This version no longer utilizes the WinSAT output XML in %WINDIR%\Performance\WinSAT\DataStore and instead utilizes API.
Run assessment is working in Vista, 7, 8, 8.1 and 10. However currently the code is like spaghetti. Once I have written it in properly, b7 will follow. - Completed. Vista compatibility is complete. Good to go on B7 within a couple days. Xiret now writes its own log, example below from W10. This will help me to troubleshoot with users. Code: --- New Test Started Monday, Jan 7 2019 05:14 AM, Xiret 2.0.0 Windows: 10.0.17134.376 Winsat: 10.0.17134.1 Winsat API: 10.0.17134.466 Reader: AsyncOut(W7+) Windows System Assessment Tool > Running the Formal Assessment > Running: Feature Enumeration '' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 1 -alphaw 2 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock' > Assessing Desktop Graphics Performance --- End of test (InterruptedByUser) --- New Test Started Monday, Jan 7 2019 05:14 AM, Xiret 2.0.0 Windows: 10.0.17134.376 Winsat: 10.0.17134.1 Winsat API: 10.0.17134.466 Reader: AsyncOut(W7+) Windows System Assessment Tool > Running the Formal Assessment > Running: Feature Enumeration '' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 1 -alphaw 2 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock' > Assessing Desktop Graphics Performance > Run Time 00:00:10.55 > 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)' > Assessing DirectX Batch Performance > Run Time 00:00:00.13 > 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)' > Assessing DirectX Alpha blend Performance > Run Time 00:00:00.13 > 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' > Assessing DirectX Texture load Performance > Run Time 00:00:00.11 > 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' > Assessing DirectX ALU Performance > Run Time 00:00:00.11 > 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)' > Run Time 00:00:00.00 > 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)' > Run Time 00:00:00.00 > 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' > Run Time 00:00:00.00 > 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' > Run Time 00:00:00.00 > 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' > Run Time 00:00:00.00 > 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' > Run Time 00:00:00.00 > 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' > Run Time 00:00:00.00 > MOOBE Run Time 00:00:11.83 > Running: CPU Assessment '-encryption -up' > Run Time 00:00:03.05 > Running: CPU Assessment '-compression -up' > Run Time 00:00:10.08 > Running: CPU Assessment '-encryption2 -up' > Run Time 00:00:03.05 > Running: CPU Assessment '-compression2 -up' > Run Time 00:00:10.13 > Running: CPU Assessment '-encryption' > Run Time 00:00:10.22 > Running: CPU Assessment '-compression' > Run Time 00:00:10.20 > Running: CPU Assessment '-encryption2' > Run Time 00:00:10.19 > Running: CPU Assessment '-compression2' > Run Time 00:00:10.17 > Running: System memory performance assessment '' > Run Time 00:00:05.16 > Running: Storage Assessment '-seq -read -n 0' > Run Time 00:00:02.38 > Running: Storage Assessment '-ran -read -n 0' > Run Time 00:00:00.16 > Running: Storage Assessment '-ran -read -n 1' > Run Time 00:00:12.16 > Running: Storage Assessment '-ran -read -n 2' > Run Time 00:00:13.80 > Running: Storage Assessment '-ran -read -n 3' > Run Time 00:00:11.83 > Running: Storage Assessment '-ran -read -n 6' > Run Time 00:00:15.47 > Running: Storage Assessment '-ran -read -n 7' > Run Time 00:00:16.41 > Run Time 00:00:00.00 > CPU LZW Compression 875.13 MB/s > CPU AES256 Encryption 4068.32 MB/s > CPU Vista Compression 2277.18 MB/s > CPU SHA1 Hash 2255.82 MB/s > Uniproc CPU LZW Compression 172.19 MB/s > Uniproc CPU AES256 Encryption 544.53 MB/s > Uniproc CPU Vista Compression 467.99 MB/s > Uniproc CPU SHA1 Hash 588.41 MB/s > Memory Performance 22035.63 MB/s > Direct3D Batch Performance 42.00 F/s > Direct3D Alpha Blend Performance 42.00 F/s > Direct3D ALU Performance 42.00 F/s > Direct3D Texture Load Performance 42.00 F/s > Direct3D Batch Performance 42.00 F/s > Direct3D Alpha Blend Performance 42.00 F/s > Direct3D ALU Performance 42.00 F/s > Direct3D Texture Load Performance 42.00 F/s > Direct3D Geometry Performance 42.00 F/s > Direct3D Geometry Performance 42.00 F/s > Direct3D Constant Buffer Performance 42.00 F/s > Video Memory Throughput 118480.00 MB/s > Dshow Video Encode Time 0.00000 s > Dshow Video Decode Time 0.00000 s > Media Foundation Decode Time 0.00000 s > Disk Sequential 64.0 Read 504.93 MB/s 8.1 > Disk Random 16.0 Read 463.28 MB/s 8.2 > Total Run Time 00:02:36.39 --- End of test (NoError)
B7 changelog updated (EDITED 08.01.19) Code: New: 1. Vista compatibility 2. New 'non-versioned' WSR* version 3. New way of assessing the system added 4. Assessment logger added 5. Added option to reload scores 'Options > Refresh Scores' (In case user runs winsat externally and leaves the application open) 6. Added option to view the log 'Options > View Log', 'Assessment Windows > normal | Verbose' 7. Added new menu item 'Main Form > Tools' which adds shortcuts 'Run Assessment (Normal)' and 'Run Assessment (Verbose)' Enhancements: 1. Redesigned about section 2. Better date format for 'last update' (Main Form) 3. Better detection for unrated systems 4. UI Framework enhancements 5. General UI enhancements 6. Form do not maximize with Win+Up 7. Assessment core now ignores D3D elements when Win10 is detected 8. Added icons to frames on all forms 9. Made all forms moveable Bugs: 1. Fixed update core issue (NoFace) 2. Fixed issue causing application to crash and give no error (Error reporter) (NoFace) 3. Fixed form exit button(s) scaling at 100% DPI Misc: 1. Updated copyright 2. Updated acknowledgements 3. Removed repair window as its no longer necessary 4. Enabled 'Settings > Assessment Mode' *WSR (WinSAT Reader) is used to power the Xiret Core and contains all information needed to read current WinSAT information. This version no longer utilizes the WinSAT output XML in %WINDIR%\Performance\WinSAT\DataStore and instead utilizes API.
Due to some mitigating factors I've delayed release a few days. It's fixed now but I have to test on all OS. This is what happens when you write 180 lines of code whilst half asleep. I'm very tempted to make the version 2 release open source. Then others can help make it better.