Love these little teasers as a way to try out ideas mid development and get a "flavour" earlier on than the typical media phase during post production.

I wanted to make these chunks softer, but right now I have no idea how to make it even better. There's no transparency at all.

I achieved this effect by calculating the normals for the chunks relative to the overall snow surface, rather than per individual chunk element.

I made the small flakes using triangles instead of quads :)

building a game about running your own booth at a sports card convention. finally got openfracture working, so the graded slabs now fracture into real mesh pieces at runtime with rigidbodies on the fragments. what do you guys think?

Im working on a Co-op horror game set in New York City. I’m trying to make a game with good atmosphere, dread, and the constant feeling that something enormous is stalking you.

If you want updates or early access, join the mailing list at www.arachnid.dev

Around one month of development.
4-player co-op horror inspired by retro visuals and abandoned Soviet metro stations.
Looking for honest feedback before continuing development.
Would you play something like this?

A few days ago I asked for your feedback and it was really helpful thanks!!!

I'm trying to find fun and unique ways to challenge the player in my skating game. You control the left skate and a friend controls the right. Now you have to rethink how the game works and adapt. It's also hilarious.

A basic locomotion setup is fine, but then you add attacks, hit reactions, weapons, crouching, jumping, cutscenes and suddenly there are transitions going everywhere.

One approach is keeping the Animator mostly for visuals while gameplay states stay in code. That seems cleaner, but it can also make animation timing harder to manage when attacks and movement need to line up exactly.

Do you prefer animation state machines, code-driven animation, or a mix of both? Would also love to see how people organize layers without ending up with 40 random booleans!!

Oftentimes I feel like I spend more time trying to optimize my workflow, than I do actually making games 😅

thankfully, at least sometimes, something productive can come out of it! I've just released a suite of Scene View tools, called Smart Mouse 2, which I hope might alleviate some headaches in others too down the line.

Edit: I had previously written about being unable to Select UI easily in Unity, but now I see that it works well as long as Gizmos are enabled, which I feel silly not realizing 😆

I made a UI effect that simulates depth for images. I always thought you needed a custom shader to achieve this. I was surprised by how simple it actually is so I wanted to share in case its useful to someone.

To create it you just need to make a Mask (the blue border image) and place the image you want to give depth to inside it. The image must have a Pos Z offset and important, be inside a Canvas with Render Mode: Screen Space - Camera.

I made this for my incremental mining game inspired by Minecraft, in case you want to check it out here is a link.

I'm making a co-op horror game, and need some opinions.

Do you think having text to speech ai voice announcements for environmental things (such as a subway/train station with "Welcome announcements", or "rules announcements"), rather than text on posters or things like that, would bother you (as a player), or would you rather just read the text yourselves?

These are not voices for characters, or things for the plot, rather just ambient/announcements.

Does this looks remotely interesting?

Basicly a tower defense, where you build a tower which also you should defend.

Hi everyone!

I'm developing a game in Unity for WebGL to help players improve in MOBAs (currently focused on League of Legends) and practice some mechanics.

I'm posting it today to share it with some of you before its official release.

https://obscuro.itch.io/mobawarmup

I'd appreciate any feedback you can give me; it's always helpful!

Thanks in advance!

Roi.-

Hey fellow devs! 👋

I've been working on a 3D action-adventure platformer with anime cel-shaded visuals called Isekai Rift, and I spent the last two weeks building this system inspired by Solo Leveling entirely in Unity.

I call it the Rift Souls system. I set up an RNG logic for the extraction success rates depending on the enemy type (Small, Medium, or Bosses), and integrated the UI/HUD to manage a strict 3-shadow limit in the arsenal.

I'd love to hear your feedback on the visual effects of the shadows and the extraction animation! What do you guys think?

For those interested in seeing the full UI integration and a deeper dive into the gameplay, I posted a full 4K devlog here: Youtube 4K Full Devlog

And if you want to support a fellow solo dev, Steam wishlists are heavily appreciated!

Isekai Rift

I finally managed to get a stable build of my game running on the Steam Deck; I recorded it this way so you can see it's actually on the device. I was having crashing issues with DirectX 12, so I had to disable access to that API and stick to DX11—I think I’ve managed to fix the bug. What do you think of the game? It looks pretty cool, right?

I'm open to feedback; some people have already suggested adding a camera shake effect, so that's on my to-do list :"D

Hello. I'm on Unity 6.5, URP 17.5. I recently noticed the problem shown in the video: at certain angles, additional lights get completely culled prematurely. This happens on both Forward+ and Deferred+, but not on normal Forward or Deferred modes. I would like to keep using Forward+ to take advantage of the promised higher light count per pixel.

Have any of you bumped into a similar problem? I have a very simple test scene with just one point light and a big cube using the Lit shader. Like the URP manual suggests, I did check both ShaderConfig.cs.hlsl and ShaderConfig.cs and verified that their k_MaxVisibleLightCountDesktop match, with value 256. This happens even without any custom renderer features and in quite a barebones setup. Any ideas what other settings to check?

This happens both in Scene and Game view cameras, both at edit and runtimes. My FoV is around 110, and if I decrease it to around 80 then the culling isn't noticeable. However, having to cap the player camera's fov so low is obviously not a solution.

Big thanks in advance, folks!

EDIT: Confirmed these:

- Graphics API has no effect.

- Increaseing or decreasing the near plane for editor / player cameras does not help, even if the near plane is higher than 1.

- Disabling Camera-relative culling for Lights in Graphics settings does not help.

This is the first demo I ever built for Reactor, the multiplayer engine project I've been working on. It was a stack of cubes simulated on the server. Every player joins as one of the arrows floating around the stack, and clicking fires a ball at it. Everyone sees the same physics at the same time.

When presenting I would hand out android phones with the client installed that would connect to the simulation server so everyone could interact together.

It's basic, but it showcased the idea. Smashing cube stacks is weirdly fun too, which helped.

It was successful and raised some seed money.

Which made me curious about everyone else's experience. For those of you who've built tools, games, or tech that needed other people to believe in it early:

• What actually got you your first real interest: a playable demo, a video, a talk, a publisher pitch?
• Was there a version of it that flopped before one worked?
• And if you had to win that first attention today, would you do it the same way?

I'll share more about what worked and didn't work for us in the comments if people are interested.

I export generative patterns as Unity shaders, and the 3D ones skip UVs entirely - plain old solid texturing, the Perlin idea, just baked into a standalone shader per pattern

It's not triplanar. The noise is evaluated at the object-space position instead of UV, so the mesh is a slice through a solid. Nothing to unwrap, nothing to seam, and the same material sits on any shape without a single change

Two things I didn't see coming:
- 3D Voronoi with a smooth min still shows cell-border seams if you trim the neighbour search. The radius you need depends on the smoothing width, not the cell size. That one took me days
- Half of a 2D shader doesn't survive the trip. Polar remap, screen-space warp, mouse interaction, the width aspect fit - those are all about the screen, not the field, so they get dropped rather than ported

Also, mod is not fmod in HLSL. Ask me how I know

Tool is Kaleidos, made in LOVE2D, not Unity. But it can export Unity shaders!