You have the right idea there, with a parallax shader. It's all good, it's just the way you combine colors that needs changing a bit. There isn't one correct way of doing it, it depends on what you want it to look like. The most common way would be something like:

vec4 mainColor = mix(color, color2, color2.w);
mainColor = mix(mainColor, color3, color3.w);
mainColor = mix(mainColor, color4, color4.w);
gl_FragColor = mainColor;

However, you may want to do something different for example by mixing the colors xyz components like this, and simply add the w components together. That is also quite common, not sure which one you prefer.

One thing to be aware of, is that if you use custom shader parameters (I can see mixtext there), then your draw calls will no longer be batched. If you just use uDiffuseSampler and more sprites, it's going to be faster.

In fact you probably don't need separate textures, just combine both textures into the same file and adjust uv coordinates accordingly.

Taking this idea a bit further, you can have a single texture with all the different rock variations in it, and sample it many times with different sets of UV's. I wouldn't just offset the uv's, you will get a better effect by also scaling and rotating them.

It'd be good to see a screenshot when you get this working.

I have two textures - the larger asteroids I insert as a sprite and the smaller ones I just pass through uniforms

I tried your scheme - for some reason there is only one layer left

but I am tormented by another question - how to convey adequate movement on the screen?

I transmit information about the player's movement through the speed and angle uniforms

uv2.x += speed*sin(rot)*(time * .4);
uv2.y += -speed*cos(rot)*(time * .4);

but to be honest what kind of bullshit it turns out to be. Adequately only along the axes, when turning and when braking some incomprehensible devilry

Yes I know what you mean. Don't use speed and angle multiplied by time - this would only work if you have constant linear motion.

Instead, pass an offset that you calculate on the CPU. At each update step, update the offset by adding speed * rot * dt. In the shader, just uv += offset.

did as you said - everything is fine with turns - but how to normalize the speed of movement of the background and the player? the background is moving too fast, and I need its top layer to move like a normal layer with the transformation parameters 1 1

**fixed the speed  - pass maximum speed of player to shader

uv2+=offset/maxspeed;

.it looks like it's taking out the paralax

vec4 mainColor = mix(color, color2, color2.w);
mainColor = mix(mainColor, color3, color3.w);
mainColor = mix(mainColor, color4, color4.w);
gl_FragColor = mainColor;

it feels like the dynamics are lost and all the layers are moving the same way

it is easier to add 4 objects for layers )) why bother with mixing

**the best on this moment is

			vec4 maincolor = max(color4,color3);
			maincolor = max(color3,color2);
			maincolor = max(color2,color);
			gl_FragColor = maincolor;

dynamic, but semi-semi transparent

**update #10000

it seems that this is almost what is needed

vec4 maincolor = max(color4, color3*4.) - 3.*color3;
maincolor = max(maincolor,color2*4.) - 3.*color2 ;
maincolor = max(maincolor,color*4.) - 3.*color;
gl_FragColor = maincolor;	

probably it would be the best but not the most productive option to use not textures - but a couple of asteroids and already combine them with different layers

at the moment, the result is as follows. everything looks a little angular with sharp edges, and lacks realism

Looking at it at that resolution, it looks alright to me - I can't see the sharp edges. However I would suggest using the built-in blur effect to avoid sharp edges (also, as a cheaper, quick and dirty alternative you could pre-process your asteroid textures by baking-in some gaussian blur).

If you want to use the built-in blur effect, use wade.setLayerBlur and perhaps change the amount depending on camera speed