You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I working on web application where Pixi used as rendering backend for graph editor.
App structured such way that there could be more than one editor opened.
Currently I use v7, and as far as I know, you couldn't share resources between WebGL contexts. That creates two problems:
excessive memory usage, because all shaders, atlases and fonts should be loaded per App.
lags on opening new graph editors (because app should load everything from scratch).
I am planning to migrate to V8 in near future. V8 provides WebGPU rendering backend, which certainly could render into multiple canvases according to this article.
So, my questions are:
Is it possible to use single PIXI app with webgpu renderer to draw into multiple canvases?
If so, would it work well, if I render multiple scenes one per each canvas, or it would break some internal Pixi state/optimizations because of constant scene switching?
If not, how hard will it be to implement such rendering flow?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I working on web application where Pixi used as rendering backend for graph editor.
App structured such way that there could be more than one editor opened.
Currently I use v7, and as far as I know, you couldn't share resources between WebGL contexts. That creates two problems:
I am planning to migrate to V8 in near future. V8 provides WebGPU rendering backend, which certainly could render into multiple canvases according to this article.
So, my questions are:
Beta Was this translation helpful? Give feedback.
All reactions