Skip to main content

Useful Unity C# Extension Methods


Get The Most Flexibility Out Of Unity With Extension Methods

Unity3D comes with a lot of helpful classes and functions but sometimes you will encounter cases where custom implementations are required.

Rather than writing those functionalities as completely separate from the classes that already exist, We can just 'extended' those classes to have our custom functionalities.
This leads to code that is easily discoverable, clean and that can be re-used across multiple projects.

This is not a tutorial on extension methods, For that go, HERE.
In this tutorial we will go over some really useful cases where we can improve on the default Unity code base with extension methods.

1. Converting from Vector3 to Vector3Int
public static Vector3Int ConvertToVector3(this Vector3 vec3)
{
   return new Vector3Int((int)vec3.x, (int)vec3.y, (int)vec3.z);
}
2. Resetting the Transform
public static void ResetTransformation(this Transform trans)
{
   trans.position = Vector3.zero;
   trans.localRotation = Quaternion.identity;
   trans.localScale = new Vector3(1, 1, 1);
}
3. Rotating a 2D Vector
public static Vector2 Rotate(this Vector2 vector, float degrees)
{
   float sin = Mathf.Sin(degrees * Mathf.Deg2Rad);
   float cos = Mathf.Cos(degrees * Mathf.Deg2Rad);

   float tx = vector.x;
   float ty = vector.y;
   vector.x = (cos * tx) - (sin * ty);
   vector.y = (sin * tx) + (cos * ty);
   return vector;
}
4. Returning a normalized degree value
public static float RotationNormalizedDeg(this float rotation)
{
   rotation = rotation % 360f;
   if (rotation < 0)
       rotation += 360f;
   return rotation;
}
5. Setting children layer value recursively
public static void SetLayerRecursively(this GameObject gameObject, int layer)
{
   gameObject.layer = layer;
   foreach (Transform t in gameObject.transform)
        t.gameObject.SetLayerRecursively(layer);
}
6. Checks if GameObject has a certain component
public static bool HasComponent(this Component component) where T : Component
{
   return component.GetComponent() != null;
}
7. Destroys all children recursively of a GameObject
public static void DestroyChildren(this GameObject parent)
{
   Transform[] children = new Transform[parent.transform.childCount];
   for (int i = 0; i < parent.transform.childCount; i++)
        children[i] = parent.transform.GetChild(i);
   for (int i = 0; i < children.Length; i++)
        GameObject.Destroy(children[i].gameObject);
}
8. Children of one GameObject gets transferred to another GameObject
public static void MoveChildren(this GameObject from, GameObject to)
{
    Transform[] children = new Transform[from.transform.childCount];
    for (int i = 0; i < from.transform.childCount; i++)
         children[i] = from.transform.GetChild(i);
    for (int i = 0; i < children.Length; i++)
         children[i].SetParent(to.transform);
}
9. Checks if Renderer can be seen by camera
public static bool IsVisibleFrom(this Renderer renderer, Camera camera)
{
   var planes = GeometryUtility.CalculateFrustumPlanes(camera);
   return GeometryUtility.TestPlanesAABB(planes, renderer.bounds);
}
10. Checks if a Rect component intersects another Rect
public static bool Intersects(this Rect source, Rect rect)
{
   return !((source.x > rect.xMax) || (source.xMax < rect.x) || (source.y > rect.yMax) || (source.yMax < rect.y));
} 
Well I hope you learnt something of value.
Support Bitshift Programmer by leaving a like on Bitshift Programmer Facebook Page and be updated as soon as there is a new blog post.
If you have any questions that you might have about shaders, C# or Unity development in general don't be shy and leave a message on my facebook page or down in the comments.
For More Unity Tutorials, go HERE.
For C# Tutorials, go HERE.

Comments

Post a Comment

Assets Worth Checking Out

POPULAR POSTS

Pixelation Shader - Unity Shader

Pixelation Shader This is the correct way (one of many) of showing pixelation as a post-processing effect. This effect will work in any aspect ratio without any pixel size scaling issues as well as it is very minimal in terms of coding it up.

In order to get this to work 2 components have to be set up:
1) The pixelation image effect
2) The script - which will be attached to the camera

So let's get started by creating a new image effect shader.
We will take a look at our Shaderlab properties :
_MainTex("Texture", 2D) = "white" {} That's it, Everything else will be private and not shown in the editor.
Now we will see what are defined along with the _MainTex but are private.
sampler2D _MainTex; int _PixelDensity; float2 _AspectRatioMultiplier; We will pass _PixelDensity & _AspectRatioMultiplier values from the script.
As this is an image effect there is no need to play around with the vertex shader.
Let's take a look at our fragment shader:
fixed4 frag (…

Alto's Adventure Style Procedural Surface Generation Part 1

Alto's Adventure Style - Procedural Surface Generation This game appears to be a strictly 2D game but if you have played it enough you will notice that some of the art assets used look like it's 3D ( I don't know if they are tho ). If you haven't played the game you are missing out on one the most visually pleasing and calming games out there ( There is literally a mode called Zen mode in the game ).
Anyway, I am going to show you how to make a procedural 2D world ( without the trees, buildings and background ) like in Alto's Adventure.
But you may notice I have a plane which is in in the Z-axis giving a depth to the surface which is not there in Alto's Adventure but if you want to know how to do it then that will be in part 2.
To achieve the same effect of Alto's Adventure ( I'm leaving that up to you ) only minimal changes are needed to the code that I am going to explain.
We are going to be using the plane mesh in unity for creating the 2D surface as th…

Gift Wrapping Convex Hull Algorithm With Unity Implementation

Convex Hull Algorithm Convex Hull algorithms are one of those algorithms that keep popping up from time to time in seemingly unrelated fields from big data to image processing to collision detection in physics engines, It seems to be all over the place. Why should you care? Cus you can do magic with it and it seems so simple to implement when you first hear about it, but when you start thinking about it, you will realize why it's not such a straightforward thing to do.
Now that I got you interested (hopefully) and now we will see just what a convex hull is.
As you may have noticed a perimeter was made with the same points that was given and these perimeter points enclose the entire set of points.
Now we have to clear up the term 'Convex'.
Convex means no part of the object is caved inwards or that none of the internal angles made by the points exceed 180 degrees.
In this example of a concave shape internal angles go beyond 180 degrees.
What are those red lines for? Well...…

Toon Liquid Shader - Unity Shader

Toon Liquid Shader This is how the shader will end up looking :
This shader is pretty neat and somewhat easy to implement as well as to understand. Since we will be adding some basic physics to the toon water as it is moved about we will have to support that in the vertex shader as well.
So let's start by looking at the properties :
Properties { _Colour ("Colour", Color) = (1,1,1,1) _FillAmount ("Fill Amount", Range(-10,10)) = 0.0 [HideInInspector] _WobbleX ("WobbleX", Range(-1,1)) = 0.0 [HideInInspector] _WobbleZ ("WobbleZ", Range(-1,1)) = 0.0 _TopColor ("Top Color", Color) = (1,1,1,1) _FoamColor ("Foam Line Color", Color) = (1,1,1,1) _Rim ("Foam Line Width", Range(0,0.1)) = 0.0 _RimColor ("Rim Color", Color) = (1,1,1,1) _RimPower ("Rim Power", Range(0,10)) = 0.0 } Just the usual stuff that we are used to. The only thing that may stand out is the [HideInInspector] tag, This works j…

Shader Optimization Part 1

The process of shader optimization can seem like trial and error... in fact, that's how it is most of the time.
Most of the time shader optimizations could be boiled down to educated guesses because each time a shader gets compiled, the GPU driver of that specific hardware is what converts your code into actual machine code, therefore, the machine code generated will be different for each GPU and the driver itself might perform some optimizations on top of your's which won't be available on another GPU, thereby making it difficult to have a standard way of writing optimal shader code.

So the best way to know for sure is to actually test it on the hardware you are targeting.
With that said, Here are some universal best ways of getting your shader to perform better.😅 Do Calculations On Vertex Shader The most commonly used case for this is lighting, an example would be Gouraud lighting, where lighting calculations are done per vertex but at the loss of quality.

Some calculatio…