SPE broken in 118dev

The Shader Particle Engine worked just fine in r117
Now the console it saturated with errors like:

THREE.WebGLProgram: shader error: 0 35715 false gl.getProgramInfoLog Must have an compiled fragment shader attached.
THREE.WebGLShader: gl.getShaderInfoLog() fragment
ERROR: 0:254: ‘texture’ : function name expected
ERROR: 0:254: ‘=’ : dimension mismatch
ERROR: 0:254: ‘=’ : cannot convert from ‘const mediump float’ to ‘highp 4-component vector of float’1: #version 300 es
3: #define varying in
4: out highp vec4 pc_fragColor;
5: #define gl_FragColor pc_fragColor
6: #define gl_FragDepthEXT gl_FragDepth
7: #define texture2D texture
8: #define textureCube texture
9: #define texture2DProj textureProj
10: #define texture2DLodEXT textureLod
11: #define texture2DProjLodEXT textureProjLod
12: #define textureCubeLodEXT textureLod
13: #define texture2DGradEXT textureGrad
14: #define texture2DProjGradEXT textureProjGrad
15: #define textureCubeGradEXT textureGrad
16: precision highp float;
17: precision highp int;
18: #define HIGH_PRECISION
19: #define SHADER_NAME ShaderMaterial
20: #define HAS_PERSPECTIVE true
21: #define COLORIZE true
WebGL warning: linkProgram: Must have an compiled fragment shader attached. three.min.js:83:143
WebGL warning: useProgram: Program must be linked successfully. three.min.js:129:247
WebGL warning: drawArraysInstanced: The current program is not linked. 30 three.min.js:36:134
WebGL: No further warnings will be reported for this WebGL context. (already reported 32 warnings) three.min.js:36:134

Michael, the backwards compatibility ?

1 possible answer(s) on “SPE broken in 118dev

  1. I just pushed a commit that makes SPE compatible with three.js r118
    To use it, in your package.json dependencies section just write:

    "dependencies": {
        "shader-particle-engine": "blaze33/ShaderParticleEngine.git#d019c8bf3766997f39dccda943fcee9586e84d94",

    Seems like the original author no longer maintains SPE, though I haven’t found a better library as of now…