Jump to content
Search Community

Leaderboard

Popular Content

Showing content with the highest reputation on 05/12/2019 in all areas

  1. Here you go, I had some downtime today and decided to have a crack at it. https://codepen.io/dipscom/pen/JqKZbv
    1 point
  2. Hm, this isn't terribly helpful - we need to actually see it in context. An excerpt of code just in the <head> doesn't do it. For example, are you using the ES Module CustomEase.js file or the ES5 one? Is there a reason you're not using the minified one? Also, I definitely wouldn't recommend putting your JavaScript code in the <head> because the browser processes things from top to bottom, so none of the actual elements that you're trying to animate will even exist yet when that code executes. See what I mean? I'd recommend putting it at the end of the <body> tag. If you still need some help, please provide a reduced test case (ideally in codepen). If you're not sure how, see:
    1 point
  3. First of all, welcome to the forums @AnSVG. Looks like a pretty cool animation! It's difficult to pull everything apart and decipher all that code and I don't even really know what I'm supposed to see in that animation, but from your description it kinda sounds like it could be an overwrite issue. If a tween begins that affects a property on an object that's already being controlled by a different tween (so they're fighting over the same property), it kills the other one. Perhaps that's happening here? You can, of course, set overwrite:false on any tween or even TweenLite.defaultOverwrite = false to do it globally, but just beware that'll allow conflicting tweens to persist (and fight). Does setting TweenLite.defaultOverwrite = false resolve things for you?
    1 point
  4. 1 point
  5. Ah, it looks like Pixi changed some things in the new version, 5.0.x. If you swap in 4.x, it works well: https://cdnjs.cloudflare.com/ajax/libs/pixi.js/4.8.7/pixi.min.js I'll have to research what they did to move their API around.
    1 point
×
×
  • Create New...