For few months now, I've been obsessed with game feel. Having fun juicing up a thing and another here and there...

It turns out that I'm practicing writing on my spare time too. Working on a novel for few years now (yeah, it's very slow progress 😅. Probably because many hours of work often result my novel having LESS words than before I started the session 😆).

But, gaining experience with game feel, I started to see relations between this concept and what's called "show don't tell" in writing... I don't know if it's the standard approach, anyway I feel like it really helps me on picking the effects I'll implement.

So I wanted to share that. If you are interested, this is a ~25min tutorial where I explain how I think about game feel (by the prism of "show don't tell") and the line of thought behind each juice decision I made in this combat scene (so you can adapt to your own game).

The Render Graph API gives you a lot of control over how texture resources should be used in your post processing effects, and all custom post process effects in the most recent versions of Unity URP should use it. In this tutorial, I made three effects covering a range of shader techniques you'll need for post processing: color manipulation, sampling the depth texture, and sampling adjacent pixels.

Making Custom Controls in UI Toolkit has never been easier!

Hello guys,

As many/all of you, I as well am a big gamer boy. I have played games for most of my life, still enjoy them even though a little bit less now I guess compared to the younger days. But my interest has shifted towards creating games for other people to enjoy.

I would really appreciate any recommendations towards tutorials/guides as how to get to know unity. Any favorite YT guides, even if there are any online courses that y'all have good experience with and can vouch for.

I have not studied game dev or even IT neither, but I would say I get to learn stuff pretty quickly. I have dabbled into Blender a while ago, just some introductory stuff. I have only done the tutorial in Unity.

Not expecting this to be any easy matter, but I can really get deep into stuff I enjoy doing. Love for the games has always been somewhere within me.

Thanks for any suggestions. ;)

Templates? Custom Controls? At first glance they seem like similar concepts trying to achieve the same thing... Here's how and when you should use Templates versus Custom Controls in UI Toolkit!

I extended a previous tutorial about PBR shaders to include tons of other features: alpha clipping and alpha-blended transparency, shadow casting and receiving, and automatic toggles between metallic and specular workflows. With a custom material GUI, you can choose which keywords to enable whenever you change the value of a property, and you can display only the relevant properties based on whether certain settings are enabled - you don't need to show an alpha clip threshold if alpha clipping is disabled.

Templates are a powerful feature of UI Toolkit - they allow us to create reusable bits of our UI and inject them easily into other UXML documents. Making them is super easy too - simply make a new UXML file of your desired component - then you can use it in any other UXML document! Easy!

I have a whole live series I have been doing on my Facebook page.check it out and all the previous live building of this build.

Scale Modes are powerful built-in functionality that automagically handle scaling your UI from a reference resolution to any other resolution and aspect ratio. When using UI Toolkit, Expand "just works" the best in my opinion.

Do you use a different one? If so why does that one work best for you?

I hope you like theses little exercises 😇

The default scaling mode for UIs in both UI Toolkit and UGUI is "Constant Pixel Size" - which effectively makes YOU fully responsible for managing different resolutions and scaling. That doesn't mean it's not useful - if you're sizing and positioning elements based on mouse movement, like a drag select - this is a great option!

Learn more about UI Toolkit Scaling Modes here

En estre proyecto programare un motor con fisicas de destrucción basado en objetos y materiales, asi como también, sistema de fluidos, luces volumetricas, entornos autogenativos, sistemas de particulas avanzadas.

Todo esto, escrito en lenguaje C++ desde cero, sin utilizar APIs o librerias de terceros.
Quizás más adelante, agrege APIs como OpenGL, ImGui, etc...
Aunque por el momento, todo va a construirse desde cero.

It is not that professional, and there are already similar tutorials out there. But i tried to make it more accesible and fast as possible. Thoughts are welcomed!

Hi. I've been following this tutorial by git-amend and have run into errors with this part specifically:

https://www.youtube.com/watch?v=jSauntZrQro&t=1106s

This is my code:

My IPredicate script look like this:

And the class derived from IPredicate, "FuncPredicate" looks like this:

I have no idea what is wrong, and half of the stuff in the tutorial goes right over my head. Can somebody please help me? I've been following this stupid tutorial for months and still have nothing playable to show from it...

🎥 Watch the full video here

I also built a very cool mini golf game using Codex and Unity CLI. Then I remotely control the game directly from the terminal. You’ll want to see this! ⛳

Second exercise of the series is out, planning to publish one each week. Hope you like it !

I genuinely think this is the easiest way to work with the new input system in Unity. It works with a scriptable object you reference wherever you need to react to player input. In contrast to the old input system, you won't have to cram everything into update, but instead this works with event based architecture. Give this a try if you struggled with setting up the new input system, I am sure you'll enjoy it!

Topics: Creating a "default" input asset if you don't have one yet, creating a scriptable object as a relay for input, using said relay and a few helpers and examples.

I made a video showing how I use AI in game development. In this video I cover using Google Gemini to brainstorm game ideas and Bezi to create a game design document and build an implementation plan.

With over 400 pages available in both English and Spanish, this has been the largest publishing project I've worked on so far. Updating the entire book for Unity 6 and Shader Graph took much longer than I originally expected, but I'm happy with the result.

I started writing the first edition in 2021. At the time, many shader courses were quite expensive, often costing well over $170. I wanted to create a practical, affordable resource that would make shader education more accessible to developers and students.

Since then, the Unity Shaders Bible has helped over 10,000 technical artists and game developers around the world. To everyone who has supported the project over the years, thank you.

Here's the book in case someone is interested 🔗 https://jettelly.com/store/the-unity-shaders-bible

Hey there,

So, I'm experimenting with that "code review" format and wanted to check out if there is any interest for it.

Ability to read code, spot and find bugs is a very important skill for all devs, both as sole developer and as team member. It can help you level up your skills as junior or keep sharp as more advanced.

Thanks for feedbacks :)

The brand new Unity CLI bridges the gap between the Unity Editor and your runtime environment, allowing you to manipulate game state and execute tools both in the Editor and in standalone builds. In this tutorial you'll learn how to install and configure the Unity CLI and its accompanying Pipeline package. You'll walk through the process of registering custom commands with the CLI and explore running those commands both in editor and in your standalone game build.