r/Unity3D
•
u/choufchouf123
•
29m ago
Game After 6 years of working non stop with Unity, I am excited to announce that I am releasing my first game with my friends!
Technical summary:
The planet is divided into chunks with their own mesh and collider. It's a cube mapped on a sphere and basically it stores one height per vertex. When you destroy the terrain, only the modified chunk updates. The environment is an asset we have used before called Point Grass Renderer. (I know it looks awesome)
The complicated part of the digging was conserving the mass (in a kind of realistic way). So the solution my friend came up with was just saying that each vertex you lower gives you x kilograms and each vertex you raise uses x kilograms, and that x is computed once when the planet is generated. That's not explained very well because I make it seem like the same variable, I ll drop the code for the technical people out here:
float VertexArea(float pCubeX, float pCubeY, float pAngleStep, float pPlanetRadius, float pEdgeShare)
{
float lCellSide = pPlanetRadius * pAngleStep;
float lCentreCellArea = lCellSide * lCellSide;
float lStretch = (1 + pCubeX * pCubeX) * (1 + pCubeY * pCubeY);
float lSquash = Mathf.Pow(1 + pCubeX * pCubeX + pCubeY * pCubeY, 1.5f);
return pEdgeShare * lCentreCellArea * lStretch / lSquash;
}
float lCubeX = Mathf.Tan((lColumn / (float)_gridSize * 2f - 1f) * Mathf.PI / 4f);When you dig, the rock you get is the height you removed × the vertex's area × the rock's density. Cells near the edges of the cube end up about 30% smaller once projected onto the sphere, so without this correction, digging there would give you around 40% more rock than you actually removed.
Almost all vfx work with GPU instancing instead of the particle system, because when you have 8 players working at the same time and hundreds of robots paving as well we far exceed the limit of what's possible with the particle system. So for all the people having a problem with that, GPU instancing is your solution. (However if you are a new dev don't do it, it's too complicated in my opinion. You can opt for other solutions like just reducing the number of things that generate particles)
Multiplayer is done with Mirror, that works through steam. (FizzySteamworks)
The stupidest decision we made was having the planet be actually round 😢 💀 Never do that, or not unless you are ready to face the challenges that come with it:
1- Everything had to work like real gravity, so get pushed down towards the center of the planet and stay upright relatively to the ground underneath it. Let me tell you it was hell. The players kept going into orbit after getting hit with the vehicles 😂 (yes you guessed right, implementing knockback was another one of our stupid decisions). Conclusion we should have used a shader, but we didn't and I think on smaller planets it gives us a truly unique experience. I suggest that less experienced devs use a shader to "round" flat terrain.
2- The planet itself is an equi-angular cube-sphere, I am sorry that's the best way I can describe it. Basically, if you want to dig into a sphere you need a grid on it, and every way of putting a grid on a sphere distorts it somewhere. The way we did it is we projected a cube onto a sphere, but the grid points are spaced by equal angles (we used a tan() mapping). If we had used plain projection we would have had very uneven cells. So look into it if you want to project a grid onto a sphere, it's a cool way to do it.
The pavers were a separate problem, because you can't tile a sphere with squares. So we pave in rings around the planet's axis, 1.5 m wide, with round caps at the poles. Each ring is split into stretches, each ending in one column of pieces cut to size, and those columns start at a different spot on every ring so they never line up. We used AI to help write the algorithm that helped fix this problem.
3- The hubs were the hardest part. The planet is curved so the buildings have to adapt to the curvature, and the host picks the planet's size, so the curvature changes every time💀 We tried splines for the base and bezier curves to place key parts, SPOILER ALERT: it didn't work. What worked was modelling the hubs based on the smallest planets, and while the game was loading, every vertex was moved onto the real one, keeping its distance along the ground from the hub's center and its height above it. The final result means that everything is bent: collider, mesh, normals and tangents. We used AI to help write the algorithm that helped fix this problem.
4- For conveyor belts we did use bezier curves. Basically how it works is we calculate how it should be placed with a regular cubic bezier 3d then every point is pushed from the center of the planet towards the surface (so the radius) otherwise since the curvature of the planet is real, the conveyor belts would sink underground when placed.
We still have some optimization problems during the late game, because of the thousands and thousands of pavers placed and the robots working and the automation machines doing their thing. It is still a work in progress even though the release date is approaching very quickly. If anybody has optimization tips/secrets please do share.
I am curious about one thing though, how do you people implement volumetric lighting in unity ?
(since URP doesn't come with it, we made our own render pass feature but it's not the best in my opinion. If you have some tricks or article on how to obtain a good result please share)
About us:
We are students and friends in our 5th year of game design and development major, and we have been working with unity since the start of our journey. It has been an insane dev journey for us, and I don't think we would have gotten that far without this engine. It is the only engine so far that felt like a fun and productive environment to work in.(for all the people that tried Unreal and hated it you know what I mean).
If you want to check out the full game (and maybe give us a little wishlist 😄):
https://store.steampowered.com/app/5551820?utm_source=reddit


