New BETA version released today, has the following fixes:
 
Version 6.2.5.2 BETA

• Add support for Breathing Mode on backplate LED
• Fix switching from GUI skin causing auto fan control to stop worrking
• Fix Z10 display issue

 
Download Here

pstlouis
After a reboot overclock setting set to default. Need a fix.

Start with windows as selected?
 
 

EVGA_JacobF
New BETA version released today, has the following fixes:
 
Version 6.2.5.2 BETA

• Add support for Breathing Mode on backplate LED
• Fix switching from GUI skin causing auto fan control to stop worrking
• Fix Z10 display issue

 
Download Here

Thanks, will update this post later. 
 
Interesting to see that the backplate led breathing has been fixed, I assume with appearance led.
It works fine with LEDSync however.
Also it is a bit unclear to me what exactly has been fixed with the Z10 display.
 
Edit:
I found a small conflict with the previous 6.2.5.1 BETA and Dxtory/Avast!
 
This affects an earlier reported issue of EVGA Precision XOC not wanting to save screenshots in another folder, e.g fraps:

• [6.1.16][OSD] Changing screenshot saving location tends to be problematic, causing first screenshot save to fail and no longer work after.
  More info: https://forums.evga.com/FindPost/2713037

Turns out, I couldn't make screenshots (and likely video's) with Dxtory anymore in the same fraps folder.
Avast! Anti Virus ransomware shield just complained that PrecisionXServer_x64.exe tried to modify or remove the screenshot I tried to save with Dxtory in the fraps folder which never got saved
This is the first time I have seen Avast! complaining about this.
 
Screenshot:

 
Renaming PrecisionXServer.exe and PrecisionXServer_x64.exe solved the screenshot failures with Dxtory.
It also stopped being problematic turning off ransomware shield in Avast! while keeping the above executables intact.
 
If people wish to circumvent this issue, make sure Avast! ransomware shield is not protecting the folder you want to save screenshots inside.
It will allow Precision XOC to also save screenshots in that folder.
 
This is just something I wanted to report for now, the rest comes later, likely tomorrow.
 
 
UPDATE: Here is the feedback for Precision XOC 6.2.5.2 BETA:
 
Please note that I uninstall the previous version completely and do a clean install.
LEDSync is not uninstalled automatically with Precision XOC, so this will be overwritten.
 
Even though many will overwrite their old installation, when issues occur they are often advised a clean installation.
This is why I test using a clean installation of Precision to make sure the bugs do not come from old configuration files.
 
 
Feedback on releasenotes:

1. Add support for Breathing Mode on backplate LED
   
   • Issue not fixed on EVGA 1080Ti FTW3 using Appearance LED, but always worked via LEDSync.
     • [6.1.2][Appearance LED] Breathing mode for backplate LED 1080Ti FTW3.
2. Fix switching from GUI skin causing auto fan control to stop worrking
   • Semi-fixed, does not function for 'GPU fan' curve. New issue created:
     • [6.2.5.2 BETA] GPU fan does not follow software fan curve when starting Precision XOC or switching skin.
3. Fix Z10 display issue
   • Cannot test, remains untested by me.

 
New issues:

1. [6.2.5.2 BETA][iCX] Power and/or Memory fan ramp up to 50% or 100% fan speed when starting Precision XOC or switching from skin.
   NOTE: This only occurs with 'Enable Automatic Fan Control' enabled.
   EXTRA: Custom/Agressive modes will ramp to 100% even if fans should be OFF, Quiet mode ramps up to 50%.
   - Please also see below issue for GPU fan, this might be why this issue does not affect GPU fan.
2. [6.2.5.2 BETA] GPU fan does not follow software fan curve when starting Precision XOC or switching skin.
   GPU fan curve icon is lit but software fan curve does not respond unless re-enabled.
   Result: GPU fan will follow hardware fan curve and not software fan curve.
   Workaround: Re-enable automatic fan curve for GPU fan.
3. [6.2.5.2 BETA] Clicking on "Curve" button shows 'Enable Automatic Fan Control' as enabled even if it's disabled.
   NOTE: The same fan curve menu opened via Settings will show the automatic fan curve is OFF when turned OFF.
4. [6.2.5.2 BETA][LEDSync 1.0.9] Disabling backplate entry in LEDSync of the same videocard does not revert back to original Appearance LED setting.
   Explanation: Backplate Appearance LED setting is overwritten by LEDSync.
   It appears that with this version the first entry is for the badge and the second entry for the backplate for seperate control.
   Disabling the badge entry (#1) in the list makes it revert correctly to original Appearance LED configuration, but not for backplate (#2).
   

 
Fixed issues:

1. [6.2.5.1 BETA] Power and Memory fan automatic fan control show as disabled after restart or switching skin.
   More info: https://forums.evga.com/FindPost/2813356
   NOTE: New issue created for 'GPU fan' curve.
   • Related to issue: [6.2.4] Switching from GUI-skin stops automatic fan control from functioning.
2. [6.2.2][LED Sync 1.0.3] Pressing F1 on LED Sync window pops-up an error and launches Windows Help.
   More info: https://forums.evga.com/FindPost/2727988
   

 
Not yet fixed issues:

1. [6.1.8][OSD] PNG screenshot capture with Precision XOC shows image corruptions.
   More info: https://forums.evga.com/FindPost/2705146
2. [6.1.2][Appearance LED] Breathing mode for backplate LED 1080Ti FTW3.
   • Not fixed in releasenote of 6.2.5.2 BETA.
3. [6.2.4][OSD Settings][Skin] Not able to set individual system tray colours for each sensor in default skin.
   Workaround: Set tray colour settings in Kingpin skin OSD settings.
4. [6.2.4][OSD Settings][Skin] Not able to set minimum/maximum values for each sensor in default skin.
   This makes "Play alarm sound when value is out of range" useless.
   Workaround: Set minimum/maximum values in Kingpin skin OSD settings.
5. [6.2.4][OSD Settings][Skin] Not able to set alarms individually for each sensor in default skin.
   This may be useful to ignore some buggy reportings such as framerate.
   Workaround: Set alarms individually in Kingpin skin OSD settings.
6. [6.2.4][Hardware monitor] Buttons GPU1, System and others are not displayed when Precision XOC is minimized OR clicking inside Hardware monitor window while Precision XOC is open.
   More info: https://forums.evga.com/FindPost/2811618
7. [6.2.4][OSD] Games crash when Precision XOC is exited when OSD is (or has been) enabled in a game.
   More info: https://forums.evga.com/FindPost/2811618 (see edit of post)
   NOTE: Issue may have existed for much longer.
8. [6.2.4] Some games may crash if Precision XOC is exited. (OSD disabled)
   More info: https://forums.evga.com/FindPost/2813356

 
 Feedback required whether this is intended or not:

1. [6.2.4][iCX] EVGA 1080Ti FTW3 Power/Memory sensors not tracked by default in hardware monitor.
   More info: https://forums.evga.com/FindPost/2811618
2. [6.2.4][Skin] Kingpin skin is not updated to include or change the following:
   • Disabling the < > arrows at GPU/Precision Logo location.
   • OC Scan button is missing on Kingpin skin. (instead accessible via < > buttons)
   • Kingpin skin settings do not contain "OSD" and "Monitoring" tabs. (instead uses old OSD settings menu)
   • More info: https://forums.evga.com/FindPost/2811618
3. [6.2.4] Reported GPU in main Precision XOC window is not white:
   More info: https://forums.evga.com/FindPost/2811618
4. [6.2.4][Hardware monitor] Having a small width window open causes overlapping issues with sensor title texts and information:
   More info: https://forums.evga.com/FindPost/2811618
5. [6.2.4] Show FCAT overlay not functioning in every game.

Needs to be like BIOS changes.
ie save setting and re-load or cancel out with no changes.
 
Apply previous settings on load seems to mean we have a set of NEW setting some where ?

bob16314

pstlouis
After a reboot overclock setting set to default. Need a fix.

After making changes to clock speed, fan speed, profiles, and other settings, enable "Apply previous settings on load" and close Precision before restarting or turning off your your PC..Some changes aren't saved unless Precision is closed after making them, same as before..And click "OK" after making changes in the Settings tabs..Should prolly work fine by doing that, it does here, otherwise not..And if you want Precision to start with Windows, enable "Start With OS" and close Precision so that also sticks.

Best thing to do after making any changes is to close Precision, then open Precision again to make sure the desired changes/settings stick.

 "Apply previous settings on load" solved the problem. Thank you bob16314.

I'm happy to test anything that needs to be tested to improve compatibility with Corsair iCue (formerly CorsairLink and also still in beta). So far, they seem to be playing together nicely.