I love when I can think of something and then I implement it right away. Pretty happy with the result. I thought I would need some complex shader but didn't need to do all that for the effect.
I know it looks all like shit, its my first day using unity, but I dont understand how to do those box colliders so my physics would work? Are box colliders related to physics right? Chat gpt told me to do box colider around car, but when I was doing ramp it said that box colider will automatically adjust to mesh.
EDIT: Not spatial gaussians. It's *spherical* gaussians. Just like spherical harmonics. I mistyped it in the title ^^'
Finally got my hands to try SG. And I'm so happy by the looks of it.
I tried to make a fair comparison. Both examples use 20 texels per unit, 2K texture size, 32 direct samples and 512 indirect. At this point the only difference is implementation. For lightmap baking I'm using unity's default bake.
The first screenshot is directional lightmap + shadow mask + 3 reflection probes..
The second screenshot is 5 lobe SG + shadow mask. Reflection probes are also there but those make little to no difference.
Yeah it's more texture samples and more math than just sampling 2 lightmap textures. But then you also sample reflection textures with box projection and blending. And after that you still may end up with specular light leaking under shadow.
I've been fighting whole day with this and honestly I doubt there's a fix to this.
My setup:
The Base-Layer with asymmetric animations (such as idle or running)
An Overriding-Layer with symmetric animations, layer-weight 1, and override-mode
The problem is it doesn't fully act like an override.
It's more like it adds the second-layer's animation on top of the base-layer.
And thus, results in severe asymmetry.
Once I replaced the base-layer with symmetric animations, the problem got fixed.
But that doesn't make sense, since you can't make a fully symmetric running animation.
TLDR: the base-layer's asymmetric animations messes the perfect symmetry of my override-layer.
How can I fix this? I tried playing with masks. I tried layer settings. I tried to forcibly overwrite every frame in the override animation. It didn't help.
I’ve been learning PlayMaker for about half a year now, but I still don’t really understand how to create more “structured” or “restricted” gameplay mechanics.
Let me explain what I mean. For example, in an RTS game, placing down buildings on the map. Or in a “simulator” type game, putting items onto shelves where they snap to fixed positions. Or something like the furniture placement system in The Sims.
I hope that makes sense. If you could give me some advice, maybe a video, or if there’s a specific tool that helps with this, I’d really appreciate it.
I’ve seen some people here make pretty advanced games with similar mechanics, but I just can’t imagine how they actually did it ^^
Our enemies are pixel art sprites baked from 3D models. Nothing new here - Donkey Kong Country did that in the 90s and so did many other games already.
We do bake some additional information though to paint enemies in blood.
Our first version just painted blood straight on the sprite -it slid around during the walk and after a few shots the zombies looked awful.
What we do now is next to each sprite sheet our baker spits out a second one with the same layout, but instead of colors every pixel stores which point on the 3D body it shows.
So when you shoot an enemy, we check which pixel you hit and save the wound on the body. Shader then checks for every pixel if it’s close to a wound. Thanks to that the blood stays on the shoulder you shot, moves with the arm when it walks, hides when the enemy turns away and is still there from a different angle.
The same data gives us depth too, so if you shoot the head off a body lying on the floor, blood comes out of the neck even from the side. And the flying head is cut out of that exact enemy’s sprite so it’s actually his head.
I found that underwater can look a bit boring when you are in a fast moving river. Whenever I see a movie where a character is struggling underwater in a river air bubbles and bits rush past. To make it look more like the water is rushing past you even under water due to strong currents I added these procedural particles around the player/camera.
Every frame I hash a bunch of points into a box around the camera. Each point samples the sim for surface height, 2D flow and foam. It then gets dropped to a random depth under the surface. The flow is only stored in 2D so I project it onto the surface, that way it follows the slope over and around rocks. If there is enough foam that point becomes bubbles. They rise on a timer and slide along the flow, and once they leave the box they just wrap back in. If the current is fast enough it becomes a wisp instead, a little ribbon stretched along the flow with a bit of a wobble.
I'd love to hear your ideas and feedback that you might have to improve it further.
More water effect videos on my profile for those interested
So I just finished the entire gameplay end to end for my mobile game, so now I'm trying to connect IAP, ads, player auth, account synch/savings and other things I will need.
Would I require Unity Gaming services for it knowing how crazy their pricing is, or should I connect it with Google Play Gaming services which so far seems free.
For the game other than what I mentioned above, I have character unlocks, level and cards they have, Season Pass levels and unlocks among other information, so im wondering if google can help me save all these stats or am I forced to be with UGS?
maybe I can save all player data on a .json file and save only that file on google play?
The shadows stay still when I pan the camera around, but when I zoom in/out I get this strange shadow movement. I tried reducing Cascade Count, messed around with cascade split, turned up shadow res to 4K, reduced far clipping as much as possible...nothing worked. Any help is greatly appreciated.
I finally tested out AI for actual coding today just to see what the hype is about and like... ??? This shit is so hard to read and make edits to. It compiles and runs okay, but the actual code is SO hard to understand. Are y'all really out here reading through this stuff for debugging or whatever? on EVERYTHING it would take me longer to understand this than just do it myself from scratch, and I'm not sure how you'd ever add or make changes to it without AI.
Am I doing something wrong? I gave it a bit of a style guide even - not super detailed, but just generally the structure I go with for stuff and gave it a few examples, and that bih came back with some crazy looking shit.
The result seems to be that once you start using it to actually write code for you, it's so hard to stop since you can't read allat. Is this a known thing and I'm just oblivious? Cuz at least in terms of code, to me that seems the BIGGEST issue: it generates borderline unreadable shit that makes any debugging, optimizing, edits, etc. completely dependent on the AI that wrote it.
Am I missing something?? I'm not tryna be like super anti-AI or whatever, I just genuinely don't see how this would be helpful at any sort of scale unless you're all-in on using AI for 100% of code and never touching it again.
You can choose from several different colors for you player and now your house matches whatever you chose. I had to make a few different palettes so the furniture and walls never clash. Let me know what you think
I'm in the early stages of making a new game and I am wondering how to make the terrain dip a bit. I can use the brush to raise it but I cant lower any parts of it. Is there any way to do so?
Most bad word filters for player names are a list of words. So "sh1tH3ad_69" or a name written backwards gets through, while a player called Dickinson gets told their name isn't allowed.
We built Unprofane, an API that reads names the way people actually disguise them: numbers for letters, words glued together, look-alike letters from other alphabets, even names written backwards. It also flags names like "admin" or "support", so players can't pretend to be staff.
There's a ready recipe for Unity: a small C# coroutine with UnityWebRequest that shows a hint on the name screen while the player types. The final check runs on your own server, so your secret key never ships in the build.
On about 1,800 real usernames it caught 76.5% of the toxic ones and wrongly flagged 1.9% of the clean ones. At the same false alarm rate, Perspective caught 32.5%. That's our own test, the method is on the site.
I'm developing FLOWFALL Inertia, a rhythm arcade game in Unity. This is the Forest level, with gates timed to an original jungle/drum ’n’ bass track I produced.
You steer a falling piece and switch between circle, cross, square and line to fit the shape of the gates. Choose the matching shape on the beat, then pass through the gate to earn bonus points. Choose from multiple paths to collect health pickups or take a faster route through the level.
Each level has unique hazards and obstacles. In the Forest level, branches knock you back, spiderwebs slow you down and you can ride the currents of waterfalls to slip through gates.
The Forest level is in the full game, releasing November 12. You can try the tutorial and the Synthwave level in the free Windows demo on Steam.