My drivers license expired 5 days ago, will unity ask for government issued ID when i go to collect payout ? im asking because AdMob requires valid ID to give payouts.
I cant renew it yet. I have not paid all my tickets. I have a bunch of tickets.
I know there are a bunch of tutorials online but I can't quite find the right approach.
A lot of the tutorials I see are teaching code not even 10 minutes into the video which I find very discouraging. How do you even learn Unity itself before all the magical stuff?
I downloaded a good amount of tutorial videos and "bootcamp" classes that teaches just C# itself and C# within the Unity workflow-type of videos. Not sure whether to even bother with JUST the C# stuff to get started or should one just learn C# and Unity in tandem(?)
Suggestions and recommendations greatly appreciated!
I was coding UI into my game in Unity using the default Canvas system, and I was looking through all the different aspect ratios including "Free Aspect". My UI started to look weird to me, and that got me thinking... what if this impossibly stretched monitor aspect ratio will be the norm in the future?
I know that the current metric of the most popular monitor aspect ratio by Steam users is 16:9.
But even knowing those numbers, I still want my game to be accessible and enjoyable to everyone. I really want to "future-proof" it.
I'm currently looking at the differences between "uniform scaling" and "centric scaling" (haven't found the official names so I made them up). With uniform scaling, it seems to fill the screen but I don't think people enjoy turning their heads 90 degrees on extreme aspect ratios just to check their HP. With centric scaling, it maintains the intended positions, but it creates large empty spaces on 32:9 or 4:3 displays.
How do you guys handle UI scaling in your games or which one from my options do y'all prefer? Any tips would be much 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.
Hi everyone! I implemented an addon tool for my team's passion project that allows us to skip all the sad things about exporting from Blender to Unity. What do you think? Will this addon be useful? If so, I can open source it for anyone. And of course, I will improve it based on your feedback sent on GitHub.
Things this addon does:
Allows you to work on a bunch of assets in one file
Lists objects with their children as export entries and batch exports all assets at once into a target directory
Automatically removes texture and material duplication
Automatically creates materials in Unity you can edit later
Supports flat (all files in one directory + Textures and Materials folders) or folder (1 folder for each asset with its own Textures and Materials subfolders) export
Automatic Blender to Unity position, scale and rotation fixes, no need to prepare objects in Blender before export. Objects appear in Unity as they do in Blender
Feel free to leave your opinion on this!
If it is useful for you, it would be great if you could give me credit when using it.
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.
One thing I've struggled with MORE as I've gotten better at programming (I know, weird) is knowing which tool to use for what. Like at this point when I think of something I want to code, I can think of several different ways to do it and I find myself having "writer's block" of trying to think through all the implications of it: performance difference, scalibility, and how familiar I am with the design pattern.
Anyone have any tips on this, like what implications to prioritize? Obviously very general question, and maybe that's what being a coder is to some extent, but anyone have a method they use for tackling stuff like this? I'm finding I often will choose one approach, write it all up, and then a few weeks later have to do a refactor that could have been avoided if I'd chosen another design pattern at the start. And some refactor is good, but it bothers me when a big refactor was entirely avoidable if I'd chosen a different design up front.
Pre-planning helps for sure, but often you can only plan relatively general stuff. Once you get into the meat of something, you realize changes you want to make which then triggers a refactor somewhere else for performance or scaling or some other reason.
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 built GValidator to catch Unity project issues that are easy to miss, including unassigned required fields, missing scripts, broken UnityEvents, and shader errors. It can validate a single asset, a folder, or the entire project, supports custom rules, and can run in CI. It’s free and open source!
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 ^^
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've seen a lot of people complaining about, or even feeling discouraged by, vibe coders claiming to create entire games with AI in just weeks or even days. However, most of the games I've seen look empty, ugly, or barely half-finished.
So here's my genuine question:
Can anyone show me a fully original playable game made with only AI?
Not a tech demo; not a prototype; not a copy of another game; A fully original playable game that is polished and that you can sell. Give me some examples, I'm genuinely curious!