Jonny Shaw Posted December 29, 2017 Share Posted December 29, 2017 Hi all, been reworking a slot prototype to use offscreen rendering using RenderTexture, so far so good and performance seems a massive improvement, but having problems with Chrome on OSX with constant flickering on the stage. Windows and android both seem fine. Im using the app.renderer to render the textures, (not sure if a second renderer is required here?) Struggled to find much in the way of information on the best way to set a system up for this. Also noticed that the containers that are being rendered appear in the chrome pixi inspector extension as soon as they are rendered (but outside the stage) and remain there but not visible, is this the normal behavior? It almost seems that these are the cause of the flickering on OSX as it seems to be in blocks that match that pattern Any advice greatly appreciated! Quote Link to comment Share on other sites More sharing options...
ivan.popelyshev Posted December 29, 2017 Share Posted December 29, 2017 Oh, right, that thing happens on some devices. Yes, you are supposed to do it throught single renderer, it contains data on many textures and other renderers cant access it, RenderTexture's really aren't shared between them. In general, chrome team keeps breaking stuff: https://bugs.chromium.org/p/chromium/issues/detail?id=786945 There are some esoteric settings that can help it: renderer = new PIXI.WebGLRenderer(800, 600, {transparent: false}); https://github.com/pixijs/pixi.js/issues/4470 . You can also try " transparent: 'notMultiplied' " Sometimes, "antialias:true" helps. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.