Jump to content
Search Community

Sergio Daroca

Members
  • Posts

    1
  • Joined

  • Last visited

Posts posted by Sergio Daroca

  1. I'm developing a slider with parallax effect, using TimelineMax. And it's joy ride with GSAP !

     

    But, my intention was to deploy using node-webkit, and I'm getting quite inconsistent performance results.

     

    In the codepen I show just the basics, next and previous buttons and you should be able to swipe left and right. (Have to add much more, later, more content on each slide, probably dragging (with Draggable) and make it an infinite slider thing...)

     

    As for now, sometimes it just works beautifully, others, it's just a bit jerky, mostly at animations end, when slowing down.

     

    I've tried different easings, tried to thin the KBs of images, force3D: true, etc...

     

    Only thing is I get a better result, but still not allways smooth, if just open the page in chrome, instead of using node-webkit.

     

    I'm about to go back to Flash CC, AIR and Actionscript, (the animation code would virtually be the same) but I'd really like to do this in javascript and HTML5.

     

    wondering wether I'm getting hardware acceleration I tried chrome://gpu inside node-webkit, I get the same as just in chrome:

     

    Graphics Feature Status
    • Canvas: Hardware accelerated
    • Flash: Hardware accelerated
    • Flash Stage3D: Hardware accelerated
    • Flash Stage3D Baseline profile: Hardware accelerated
    • Compositing: Hardware accelerated
    • Rasterization: Software only, hardware acceleration unavailable
    • Threaded Rasterization: Disabled
    • Video Decode: Software only, hardware acceleration unavailable
    • Video Encode: Hardware accelerated
    • WebGL: Hardware accelerated
    Driver Bug Workarounds
    • clear_uniforms_before_first_program_use
    • exit_on_context_lost
    • texsubimage2d_faster_than_teximage2d
    Problems Detected

     

    It's a 16 GB RAM machine with a GTX 770 card, but the inconsistency has appeared almost identical on other machines with less resources, so I'm guessing it might not be a hardware issue ?

     

    Any ideas ?

     

    See the Pen rayJbR by SergioDaroca (@SergioDaroca) on CodePen

×
×
  • Create New...