![]() Fixed the artifact counter bug in the GPU burner donut v2 demo when artifact scanner was enabled.The stress test / benchmark is stopped if the number of artifacts is greater than max artifacts Added max duration for stress test (settings box).Added max artifacts counter (settings box).The stress test / benchmark is stopped if the GPU core temperature is greater than max GPU temperature Added max GPU core temperature protection (settings box).Added the control of the GeForce GTX LED logo by GPU core temperature, by GPU usage, by GPU power or manually (settings box).Updated configuration file with selected test, window size, anti-aliasing mode.Fixed a bug in Furry E memory burner module when selecting a test that requires more memory than available on the graphics card.Added new demo: PhysX 3 Fluids (GPU PhysX or CPU PhysX).Added new demo: PhysX 3 Rigid Bodies (CPU PhysX only).Updated particle demo with 4 million particles.Added support for latest GeForce cards (GTX 780 Ti, GTX 760).Added a section with experimental demos (no benchmark, demo mode only). ![]() Added new multi-GPU Test: OpenCL Julia4D. ![]() Benchmark scores can now be submitted to an online GPU database.Added support for latest graphics cards.Fixed a bug in artifact counting in memory burner demos.Fixed a bug in the display of artifact counters.I hope this helps someone, as this was an annoying as F problem as I was trying to get things tuned for SW:Squadrons. In any event, leave it at Never, manually check for an update every month or so, and you'll be good. Perhaps, on Windows 10, X1 gets messed up if multiple NICs are available when it tries to check for updates. That was most likely this check getting lost in some sort of Windows 10 Task Scheduler limbo, which, after causing X1 to crash, would then later boot your PC about 15 seconds after a full shutdown.because it was trying to execute this stupid check.Ī contributing factor may also have been that my Wireless Adapter was enabled in recent weeks, which is non-standard for me (I'm usually on wired Ethernet only and disable the Wireless NIC to keep things simple). I also suspect that this was what was behind my recent uncommanded PC boot-ups. But once you open it and set it to check "On startup" or any of those other options, as I was doing, it will now crash whenever that check happens.which could seem very random, due to some of the settings (such as "On startup weekly, or monthly, etc."). The problem goes away after an uninstall/reinstall because the default for the check fequency is Never. I am on X1 version 1.07 standalone version btw, with a 1080ti FE.Īfter a week+ of utter frustration with this problem after moving from XOC to X1, I was very happy when the light bulb suddenly went off last night.which was when, after yet another uninstall/re-install, after which it would stay open "the first time, but that was it", I actually clicked the "Check now" button (to check right there for a newer version), and the app disappeared, just like it always was doing at startup. Set that to Never, which is the default at install, and then it's fine. X1's "Check Updates" feature is what's causing it to crash. ![]() Answer to Precision X1 "disappearing" right after launch in Windows 10:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |