I am looking for a Unity developer to refine an existing project related to the implementation and correct comparison of different types of shaders. Currently, the project already contains a basic implementation of several types of shaders (Vertex, Fragment, Geometry, Tessellation, Compute) and one test scene; however, the comparison structure is implemented incorrectly, as shaders performing different functions are compared without considering their purpose and identical conditions.
It is necessary to redesign the project so that the comparisons are logically justified and categorized. Separate comparison groups need to be implemented: firstly, comparison of lighting models (for example, Phong or Blinn-Phong vs. PBR) on the same model and scene; secondly, comparison of shader creation approaches (Built-in Shader, Surface Shader, custom HLSL shader, Shader Graph) with as similar visual results as possible; thirdly, comparison of geometric changes (objects without tessellation and with tessellation); fourthly, comparison of computations on CPU and GPU using Compute Shader (for example, in the context of animation or particle systems).
In all cases, it is necessary to ensure identical testing conditions: the same lighting, the same camera, the same models, and the absence of external effects that may influence the results. The difference should be caused solely by the type or implementation of the shader.
Several scenes need to be created (2–3 or more), each responsible for a separate type of comparison (lighting, geometry, performance). The scenes should not be minimalistic but complete: with several objects of varying complexity (simple geometric shapes and complex 3D models), different materials, and a clear visual structure. The project should look like a finished demonstration system, not just a set of several test objects.
Basic camera navigation (rotation, zooming, movement) needs to be implemented so that objects can be viewed from different angles. A simple user interface (buttons, dropdowns, or other elements) should also be added to allow switching between different shaders or comparison modes.
A separate performance testing system needs to be implemented. For this, Unity tools should be used, including Unity Profiler for analyzing CPU and GPU load, Frame Debugger for analyzing rendering, and the Stats window (FPS, draw calls, batches). Key metrics (FPS, frame time, number of draw calls) should preferably be displayed directly on the screen as text. It is also necessary to provide the ability to test under load, for example, by increasing the number of objects in the scene.
The visual part needs to be improved so that the results of the comparisons are obvious. Simultaneous display of two variants can be implemented (for example, split-screen or placing objects side by side), or quick switching between them. It should be clear which shader is being used at any moment.
As a result, there should be a ready, structured Unity project with several scenes, correct comparison logic, the ability to interact through the interface, implemented testing tools, and a sufficiently developed visual part. It is also desirable to add a brief description of the project structure and the testing procedure.
