Stage3D proxy is null in Filter3DRenderer when setting filters3d property about away3d HOT 3 CLOSED

Example project to replicate error: https://github.com/jasonsturges/openfl-away3d-filter3d

Filter is added at line 132

Looks like the proxy is set after the first frame's render, but I believe I should be able to add a 3d filter before frame 2. Maybe this is by design.

Not to further complicate this, but when the filter is added on frame 2, mac64 target throws

Program3D.hx:332: fragment: ERROR: 0:18: Incompatible types (float and vec4) in assignment (and no available implicit conversion)
ERROR: 0:18: Use of undeclared identifier 'va0'

Error : Error compiling fragment shader: ERROR: 0:18: Incompatible types (float and vec4) in assignment (and no available implicit conversion)
ERROR: 0:18: Use of undeclared identifier 'va0'

from away3d.

Just a quick note (not a complete solution - sorry).

In your example, stage3DProxy is indeed null and as such causes the error. The reason for this is that the stage3DProxy is only requested when the view is added to the stage. In your Away3DViewport class, moving the addChild(view) from the end of the initialiseListeners (ln95) to the end of initializeEngine (after ln65) instatiates a stage3DProxy before adding the filters and fixing your error.

Now the next problem is that the DepthOfFieldFilter3D is causing a GL error at the moment at runtime which I've not yet looked at. I tried the BloomFilter3D and that seemed to work ok after moving the addChild reference.

See what you think but it might be easier to close this item (after you've checked it) and create a new issue for the DepthOfFieldFilter3D for clarification.

from away3d.

That makes total sense - sorry about that.

Cool, let me track down the exact issue with the DepthOfFieldFilter3D and log that here, or appropriate project if root cause is Lime or OpenFL.

Thanks, again.

from away3d.