Mathieu Anthoine

Members
  • Content Count

    68
  • Joined

  • Last visited

Posts posted by Mathieu Anthoine


  1. Ok I found the bug.

    In my homemade framework, I add a version number at the end of files I want to load: fileName.ext?0.1.0 for example

    When I add a new file in the loader during loading, if I add an extension to the file, the file is never loaded and the loading never finish

    When I remove the extension, the loading works well in pure JS or Haxe.

    In Pixi v3, thje loading was working well even with the version at the end of the filename.

    Maybe you have changed something in that way ?

    Do I need to add an issue on github ?

    PS: Adding a version number after a filename, works well when the files are added before loading, the bug occurs only in the special situation describe above


  2. Not sure it would be easy to show you the middleware but here the idea:

    1) After loading each resource the middleware checks if it is a json that describes a list of sounds

    2) if it's the case, the middleware reads the json and add the url of the sound files listed to the loader with add

    3) the middleware call the "next" method to continue the loading process.

    4) The process of loading continue correctly and seems to stop when it has to load the files added

     


  3. Hi,

    I'm working on changing a personal Loader class that inherits from the Loader PixiJs class.

    In Pixi v3, I use a middleware called by the after method to add new contents to load during loading and it works very well.

    When I try to do the same in Pixi v4, this error occurs: "Cannot add resources while the loader is running."

    Is there a way to do the same thing than in Pixi v3 ?

    Is it a restriction of Pixi v4 and why ? 

     

    Thank you for your help


  4. Hi there,

    Here is the first version of GAF Player for PixiJs. If you know Flump or Dragon Bones, take a look at GAF, it's so much more powerful  !!! https://gafmedia.com/

    At the moment, GAF Player for PixiJS is available for Haxe-Pixi but I will deliver a pure js lib soon .

    https://github.com/mathieuanthoine/PixiGAFPlayer

    Enjoy :)

    PS: I'm really interested in bug reports !


  5. The differences in the code that create the different behaviors are here (in the processInteractive method of InteractionManager) : 

    VERSION 3.1.0

                var child = children;
    			
                // time to get recursive.. if this function will return if somthing is hit..
                if(this.processInteractive(point, child, func, hitTest, interactiveParent))
                {
                    // its a good idea to check if a child has lost its parent.
                    // this means it has been removed whilst looping so its best
                    if(!child.parent)
                    {
                        continue;
                    }
    				
    				hit = true;
    				
                    // we no longer need to hit test any more objects in this container ...
                    //interactiveParent = false;
                    
                    // If the child is interactive , that means that the object hit was ...
                    // This means we no longer need to hit test anything else. We still ...
                    if(child.interactive)
                    {
                        hitTest = false;
                    }
                }

    VERSION 3.0.8

    
                if(! hit  && hitTest)
                {
                    hit = this.processInteractive(point, children, func, true, interactive );
                }
                else
                {
                    // now we know we can miss it all!
                    this.processInteractive(point, children, func, false, false );
                }

     


  6. In Pixi 3.0.8, if a Sprite (named "A") has its interactive property to true and has a function listening the "click" event, the sprites that are under "A" (with interactive to true and a function listening to click) don't fire a click event. "A" stops the propagation under it.

    In Pixi 3.0.9 and higher, sprites that are under "A", fire the click event.

    Is there a behavior change ? is it a bug ?

    Thanks in advance


  7. When I use a json (hash) to load a texture made for example in Texture Packer, I can manage the cache for the json file in adding some parameters after the json file url :

    myLoader.add("myTexture.json?0.1.0");

    But How can I control the extra png files (described in the json file) to be loaded again without using the browser cache ?

     

    Thank you 


  8. The  Texture.fromVideoUrl streams the video and doesn't wait to complete the loading.

    Whatever the response header has  access-control-allow-origin: *

     

    Here is the Response Header

    HTTP/1.1 206 Partial Content
    Date: Wed, 27 Jan 2016 20:23:46 GMT
    Server: Apache/2.2.22 (Debian)
    Last-Modified: Fri, 15 Jan 2016 23:14:45 GMT
    ETag: "c401e-5d69f2-52967919e6340"
    Accept-Ranges: bytes
    Content-Length: 6121970
    Access-Control-Allow-Origin: *
    Content-Range: bytes 0-6121969/6121970
    Content-Type: video/mp4
    Keep-Alive: timeout=15, max=100
    Connection: Keep-Alive

    And the request header

    GET /muUrl/movie_fr.mp4 HTTP/1.1
    Host: mySite.com
    Connection: keep-alive
    Pragma: no-cache
    Cache-Control: no-cache
    Accept-Encoding: identity;q=1, *;q=0
    User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.82 Safari/537.36
    Accept: */*
    Referer: https://myReferer.com/
    Accept-Language: fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4,ru;q=0.2
    Cookie: __utma=241289754.1724640338.1441224370.1452115023.1452769534.4; __utmz=241289754.1441224370.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)
    Range: bytes=0-

     


  9. CORS:

    The server returns CORS but are they proper, I'm not sure. Have you an examples of what is needed ?

    I put an .htaccess with at the root of the domain

    <IfModule mod_headers.c>
    <FilesMatch "\.(png|mp4)$">
        Header set Access-Control-Allow-Origin "*"
    </FilesMatch>
    </IfModule>

    crossorigin :

    Not sure where to set that. When I get the url of the video, I create a texture with Texture.fromVideoUrl

    After that I change the texture.baseTexture.source.crossorigin to "anonymous" and to finish I give the texture to a Sprite.

    Is that right ?

     

    But I still have the error

     


  10. Hi,

    I'm working on a game that needs to load images and videos from an other domain.

    It works fine with images after changing the request and response headers.

    With the videos it works when I'm on the same domain but when I call the video from an other domain I get this error:

    Uncaught SecurityError: Failed to execute 'texImage2D' on 'WebGLRenderingContext': The video element contains cross-origin data, and may not be loaded.
    
    [GroupMarkerNotSet(crbug.com/242999)!:ACB77C09]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

    If someone encountered this issue before and has the solution, please help me, I'm totally stuck !

     


  11. Hi,

     

    I have this bug with InteractionManager processInteractive method:

     

    Uncaught TypeError: Cannot read property 'visible' of undefined

     

     

    It seems to occur when children of a Container are destroyed during the loop of the processInteractive.

    Is it a known issue, is there a workaround ? 

     

    Or maybe is it possible to get a more solid test in the method ?

     

    instead of testing displayObject.visible maybe you can test the existence of the displayObject first ?

     

     if( !displayObject || !displayObject.visible )

        {

            return false;

        }

     

    Thank you for your help.


  12. yes, but i found that it wasn't pixi.js 's issue.

     

    when i turn off hardware acceleration in chrome. fps regularly works as 60.

     

    does anyone know about this issue?

     

    Yes I have the same issue :(
    If you search on the web, solution is to turn off hardware acceleration like you did.
    But you'll see that the issue will appear again with acceleration off. If you turn it on again, you'll get 60fps again.
    Few times after, the fps fall down again and you 'll start an infinite on/off loop trying to resolve the issue :(
    I didn't found any solid fix for this intermittent bug that occurs randomly on some computers :(
     
    PS: It's a chrome issue not pixi