davydka

Members
  • Content Count

    4
  • Joined

  • Last visited

Everything posted by davydka

  1. Haha, no nothing that special. Node was just part of the tools used on the project. Mainly node was used to pull down assets from a remote source and to act as a local web server. I locked everything down to their respective versions when I started the project so this is PIXI 3.0.9. Another tool extensively used was Greensock.
  2. HearstLive - https://www.youtube.com/watch?v=cBj5rGToDJ8 Permanent LED wall installation at Hearst Tower in NYC. The entire installation uses 7 million LEDs. It is more than 50 feet long and about 12 feet tall on both the 8th Avenue and 57th Street sides. Developed PIXI based display software running at UHD 4K resolution with 24/7 uptime. It integrates with a Laravel backend and is updated 4 x per day by an editorial team. Built with React, Node, Vim and PIXI You can see it at 300 W 57th St, New York, NY.
  3. Onsite installation for an LED wall.
  4. Hi this is my first topic so be gentle. I have a project using a wide and short canvas, around 4300 x 730. A strange thing happens with desktop Safari. Once the canvas hits a certain width, around ~2500, the fps drops down to a steady 30fps. When I switch to the canvasRenderer it jumps back up to 60, but I would like the ability to use webgl filters. Chrome handles everything just fine. I've tested on a new Mac Pro and my development machine is 2012 Macbook Pro. Both exhibit the same issue. var renderer = new PIXI.WebGLRenderer(4300, 730, { transparent: true, antialias: true });