I came across this: http://plepers.github.com/Instagal/#bench on FlashDaily.net. If implemented instead of AgalMiniAssembler would this mean an instant performance boost? Are there advantages/disadvantages of using Instagal instead of AgalMiniAssembler?

Using Instagal doesn’t change anything to rendering performance (overall fps), but it can improve materials initialisation/update speed.

If you have a complex scene with 50 different materials, it will took up to ~80ms to compile them, creating a visible lag. This can be annoying if you want to switch from scene to another, often disposing and recreating materials, or making several changes in materials params, forcing shaders invalidation.

I’ve already implemented Instagal in Away for this project
http://www.nissan.fr/FR/fr/vehicles/crossovers/juke/personalisation.html

It’s lot of boring changes but it’s quite simple. ( i’ll push it to GH soon)

Instagal use domainMemory opcodes, which is not a “premium feature” anymore, but i havn’t tried what happen on old runtimes.

Instagal use apparat : MemoryPool, and modified version of StaticChunkStrategy, so it’s possible it create side effects on projects already using apparat for other purpose.

L’exec est tellement belle, j’aurais presque envie d’acheter une nissan
Bravo Pierre!

Hi Pierre

This is a awsome away3d project.

very nicely done!