Any optimizations to be made on large for loop?

Unity Engine
1

Hello, I have been developing this image effect for quite some time now and it has gone through many iterations to get to this point (no pun intended). I was wondering though if there were any ways to speed it up still? It is pretty taxing on my system (it is only a laptop ATM) and I feel it could still use some work. I have tried using GameObjects, then object pooling, then the Graphics Library, then Compute buffers, and now here where I am using the GL library. This is the image effect:

and these are the two scripts:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class GLRect : MonoBehaviour
{
    public int speed;
    public float width = .1f;
    public float height = .1f;
    public float xMult;
    public float yMult;
    static Material lineMaterial;
    public Camera cam;

    private void Start()
    {
        if (!lineMaterial)
        {
            Shader shader = Shader.Find("Hidden/Internal-Colored");
            lineMaterial = new Material(shader);
            //lineMaterial.hideFlags = HideFlags.HideAndDontSave;
            // Turn on alpha blending
            //lineMaterial.SetInt("_SrcBlend", (int)UnityEngine.Rendering.BlendMode.SrcAlpha);
            //lineMaterial.SetInt("_DstBlend", (int)UnityEngine.Rendering.BlendMode.OneMinusSrcAlpha);
            // Turn backface culling off
            //lineMaterial.SetInt("_Cull", (int)UnityEngine.Rendering.CullMode.Off);
            // Turn off depth writes
            lineMaterial.SetInt("_ZWrite", 0);
        }

    }

    void startGL()
    {
        lineMaterial.SetPass(0);
        GL.MultMatrix(transform.localToWorldMatrix);
        GL.Begin(GL.QUADS);
    }

    void OnRenderObject()
    {
        startGL();
        for (int i = 0; i < speed; i++)
        {
            Vector2 v = getRandCoords();
            Vector2 colorGenCoord = new Vector2((v.x / xMult + 1) * xMult, (v.y / yMult + 1) * yMult);
            Color32 c = textureHandler.getPixelColor(colorGenCoord.x, colorGenCoord.y, xMult * 2, yMult * 2);
            GL.Color(c);
            GL.Vertex3(v.x, v.y, 1);
            GL.Vertex3(v.x, v.y + height, 1);
            GL.Vertex3(v.x + width, v.y + height, 1);
            GL.Vertex3(v.x + width, v.y, 1);
        }
    }
    private Vector2 getRandCoords()
    {
            Vector2 v;
            float theta = Random.Range(0, 2 * Mathf.PI);
            float a = Random.Range(0, 1f);
            v.x = a * Mathf.Cos(theta) * xMult;
            v.y = a * Mathf.Sin(theta) * yMult;
        return v;
    }

}

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class textureHandler : MonoBehaviour
{
    public static int resolution = 256;
    public RenderTexture rt;
    private static Texture2D tex;
    private static byte[] colorArray = new byte[resolution*resolution*4];
    public static int abberation = 4;
    // Start is called before the first frame update
    void Start()
    {
        rt = new RenderTexture(resolution,resolution,0);
        GetComponent<Camera>().targetTexture = rt;
        RenderTexture.active = rt;
        tex = new Texture2D(rt.width, rt.height);
    }
    private void OnRenderImage(RenderTexture source, RenderTexture destination)
    {

        tex.ReadPixels(new Rect(0, 0, tex.width, tex.height), 0, 0);
        colorArray = tex.GetRawTextureData();
    }
    public static Color32 getPixelColor(float x, float y, float camWidth, float camHeight)
    {
        byte iX = (byte)Mathf.RoundToInt((x / camWidth) * tex.width - 1);
        byte iY = (byte)Mathf.RoundToInt((y / camHeight) * tex.height - 1);
        int index = (iX + iY * resolution) * abberation;
        Color32 color = new Color32(colorArray[index],colorArray[index + 1],colorArray[index + 2], 255);
        return color;
    }
}

As you can see, the first one is the main script and is attached to the camera you actually see, the second script is attached to a camera that gets input and renders it to an array. I don’t really know how else to optimize this and I’m sure you guys know something. Thanks!

2

The first improvement you’d get us by not doing this. Render your quads using a material that takes the source render texture. Then calculate the UV position for the center of the quad and assign that for all 4 vertices. Reading the render texture back to the CPU is brutally expensive.

After that the next best option might be to not construct a new mesh every frame on the GPU. Make it once with the number of quads you want and jitter them with their vertex shader.

After that, stop using a bunch of quads and use a compute shader or vertex fragment shader using texture bombing to get the jittered positions.

1 Like
3

Thank you for the reply! I had an idea that something like this may be the case since I’ve heard reading pixels is extremely intensive and the larger the texture the exponentially larger the task is especially every frame. Quick question though, how would I go about doing this? I’m slightly familiar with shaders but how would you get one to render quads like that? Also how would you get them to calculate vertex position? (I’m guessing a vertex shader of some sort but just making sure).

4

For that first option, a basic transparent unlit textured shader or particle shader would work. No custom shader would be needed if the mesh data you’re rendering is appropriately setup.

For the second option, yes, you’d need a custom vertex fragment shader with the position of the quads being adjusted in the vertex shader part of the vertex fragment shader. The idea is you’d still be rendering a mesh that’s a bunch of quads, just one you generate once when you first need it or the number of quads you need changes, with a regular grid of positions & UVs, and reuse rather than one you’re creating on the CPU and reuploading every frame. The later is what you’re doing when you use the GL.Vertex() calls. You can write very similar code to what you already have to take the UV and _Time.y or some other shader uniform float you update every frame to jitter the positions. Then it’s only a Graphics.DrawMeshNow() every frame instead of the massive loop of GL.Vertex() calls and you’re done.

The last option and to answer the question:

Search for the term “texture bombing” and you’ll find a ton of resources. Admittedly they’re old and I don’t think any are Unity specific, but they’ll describe the concept both using mesh quads like you currently are doing and using a shader that can make a single triangle look like it’s covered in hundreds or millions of “quads” (and the number doesn’t significantly affect how expensive the shader is).

5

Hey, I’ve been trying to work at this for awhile, I got the RenderTexture part to work, however, unluckily, it seems like the most intensive part of the program is drawing the Quads. I was wondering however, since it seems like you’re much more experienced than I if you could had an example of how exactly to accomplish what you’re saying? I’ve been working on trying to get this to work for awhile and it seems to just not want to. Any help is appreciated, thanks.

6

I would write a texture bombing shader that uses _Time as a random hash seed and skip almost all of the c# side of things.