In this house we follow the church of Grey

Amen dude

Porygon > any polygon Otherwise yes

All praise our lord hexagon.

scrolled too far to fin this xD

And one can always extrapolate a tilemap into 3D objects~

@@AGreatTsunami Wait, what? Would you happen to know of a video or article detailing what you mentioned?

However, those hexagons are not accurate

what is the game at 0:47 ?

@@NominativoUnivoco Why aren't the Grid Component hexes inaccurate? I have a game that needs hex grid

Hi, can you check my code, i thing ive done big wrong :8 nothing works

thanks for the comment I had missed him rewritting that part haha

Is It Possible You Can Show How To Use Axial instead of Offset coordinate system?

Microsoft's CLR (the C# virtual machine) is able to optimize away the call to sqrt(3). It might not bother in debug builds though. That being said, you use sqrt(3) often enough `SQRT_3` might be more legible than `Math.sqrt(3)`

Allocating memory for the list at every tick probably has a much bigger performance impact here. But honestly is it such a big deal for a prototype like this? Nobody cares.

@@Neph0 maybe newer game devs that don’t know the best practices and or why this wouldn’t scale well into a big project? I definitely am interested in hearing points like this…

what is the game at 0:47 ?

@@vinhnghiang1273 That game is called, "Before we Leave".

Watchout for part 2 😉

@@GameDevGuide subscribed and notified!

@@GameDevGuide Whens Part 2??

what is the game at 0:47 ?

I'm having trouble setting up the innersize, outersize, and height. Can you help?

@@HaoaHaNa8513 [SerializeField] private Material material; [SerializeField] private float innerSize; [SerializeField] private float height; [SerializeField] private float outersize; then set them in the inspector

what is the game at 0:47 ?

You can also just use "mesh.RecalculateBounds()" right after "mesh.RecalculateNormals()" in the "CombineFaces()" method.

@@GregX999 Awesome, didn't know this - thanks!

I typed up the code seen in the video but Unity is giving me a bunch of errors. Is there something that I should be doing that's not being covered?

@@SpankytheEvilMo I've only completed generating the hex. The code in the video works. I haven't started coding the grid yet.

@@rutchjohnson Huh, then I wonder what I'm doing wrong. Researching, it seems that this may be a custom editor and I missed that fact.

@@SpankytheEvilMo I’m not using a custom editor.

Thank you! Been debugging that one for the last couple of hours :)

You probably need to create a new GameObject (named "Hex") and add component > script (HexRenderer) to get to the next point in the video.

I thought the same thing but realised it’s always good to know the derivation of those constants too… some game engines don’t have them, and not all programmers use them.

@@j.j.maverick9252 I agree

Bruh, i'm getting this error, and i don't know how to fix it (i'm more than a noob in programming), can you write here the code correction please?

@@OBrownie_ sorry I don't have the code any more - but from memory, instead of calling DrawMesh() in OnValidate(), just set a bool flag to true, and then in Update(), if the flag is true, then call DrawMesh(). This ensures that the mesh is only created in the Update phase, and never before Awake (which can happen sometimes because OnValidate() can be called before Awake() is). Hope this helps.

I had the same issue, another commenter wrote the solution. In "OnValidate()" add "&& mesh != null" in the if statement, after Application.isPlaying

@@blizzzard900 cant confirm myself(not using the project anymore), but if anyone reading and trying this, please confirm if true

@@Tin_Protopixel I had the same problem, and using the check made it go away.

6:24

If you start out with an empty project, do the following: 1) add an empty gameobject 2) attach the HexRenderer.cs to it 3) position the camera so it looks at the object 4) press the Play button to run the scene Also, check the other comments to sort out some issues since there are changes done to the code that are not highlighted in the video.

I'm having the same issue, did you manage to fix it?

@@jamesmamaliga4824 No

Did you try it with a newer version? Try changing it to: tile.transform.SetParent(transform, true); Maybe it helps.

@@MrYTThor Thank you!

The created tiles are not deleted. To achieve this, you can add a ClearGrid() to the onValidate(): Add a List of the created tiles: private List tiles = new List(); Add all created tiles in the LayoutGrid to this List: tiles.Add(tile); Create a ClearGrid function: private void ClearGrid() { foreach (GameObject tile in tiles) { Destroy(tile); } tiles.Clear(); } Call the ClearGrid(); before LayoutGrid(); in your OnValidate().

I have the same problem. Were you able to fix it?

i have the content downloaded from patron it just made it worst. i just want this thing to show up in scene lol.

I have the same problem that there is no output but two errors.I cant find any difference between video and my codes.

Glad I'm not the only one. I've tried the fixes put forward by other commenters and none of them work. Would be nice to see the script in full at the end of writing. :/

@@junjiepeng Two Errors. Perhaps we have the same ones. HexRenderer does not contain a definition for SetMaterial, and same thing for GameObject ... Set Parent. If I find solution, I will post it here. Just starting to get back into code after years and years haitus, and I was never that proficient, so I expect to run into a lot of errors. Copying the code from the video is really difficult, it changes slide to slide as he fixes errors between shots. This is not to mention that I have no doubt mistyped something, it makes following the tutorials and actually getting something working to play around with very difficult, but I just can't learn on theory only. Would be good to see the final clips of the script.

Okay I've found the problem. At some point, UnityEngine stopped allowing a bunch of the components of GameObject to be referenced. Don't know how long ago this change happened, can't find any documentation on the update itself. SetParent is now part of Transform, so the correct line here is tile.transform.SetParent(transform, true); The SetMaterial on the other hand doesn't exist at all, only as part of a CanvasRenderer. This line just appears to be completely wrong. In this part of the code we are creating GameObjects of type HexRenderer, referencing the variables at the top of the HexRenderer script, and assigning to them the variables in this script. So the material should be the same pattern as all the other variables we used. hexRenderer.material = material; I think, I could be wrong, but the errors go away with these changes. Hope this helps. Annoying that the video is either already out of date after a year, or just riddled with mistakes. Clearly a lot of work has been put into making the video, but its a big barrier to learning that videos need to be basically perfect and released a day ago to be even functional. Even after fixing these errors, I still have a lot of tweaking to do to even get Hexagons appearing, which I see is a problem many others were having.

@@Liamneedham29 Got those same 2 errors

Thanks

o after that you showed the creation of public float innerSize codes okey ı am fine now :D but how can you do that unity drawing things ı couldnt see that

OPUS MAGNUM

Iv'e got this problem, did you find a solution?

​@@dptgames2254 I had this problem, I think I needed to create an empty GameObject to attach the script to

So this decision is mostly due to the way UV Mapping works in Unity. If you want clean UVs easily you need to define unique vertices. If you don't care as much about UVs, sharing vertices is a lot more optimal.

You can actually go as low as 6 vertices and 4 triangles per hex.