I have not explored the Edge Animate setting, or even if its 'wired' to work, but once enabled have a look at this doc
on how to enable it in Chrome as well.
Hopefully, a dev member can provide a better answer than what I provide.
1 person found this helpful
We enabled gpuAcceleration to improve performance of our output files for some of our supported platforms. If I recall correctly (and this was done quite a while ago), a couple of our mobile devices performed a lot better with gpuAccelerate switched on. You probably won't see that much of an improvement (if at all) with your desktop devices.
Hope that clears things up!
Hi Darrel, hi Elaine!
@Darrel: I'm aware of the hardware (GPU) acceleration options in different browsers/systems. I'm just wondering _what_ the boolean in the script output of Edge actually does.
@Elaine: But _when_ would it switch on GPU in the animations and _where_ (which browsers/platforms)? There's no documentation I've found so far about it and the var is included in every animation with default 'false'.
And what are the possible pitfalls?
After beautifying edge-1.5.0.min.js it seems that it just enables the translateZ trick for (some) Webkit based browsers.
if (this.gpuAccelerate && f.style && (typeof n === "undefined" || n === "" || n === "none")) f.style.webkitTransform = "translateZ(0)";
But Edge does anyways already use 3D transitions in its animations?
Message was edited by: Volker_E