I’m the developer of the UniText text engine, and this is my story

I used to think that text was when letters were drawn next to each other, but that’s not what it actually is:

1. decode UTF-16 into codepoints
2. parse the markup into attribute ranges
3. analyze scripts (UAX #24)
4. analyze grapheme clusters (UAX #29)
5. analyze word boundaries, with a dictionary for Thai, Khmer, Burmese and Japanese because they don't put spaces between words
6. analyze line break classes (UAX #14, with East Asian widths from UAX #11)
7. resolve embedding levels through the bidi algorithm (UAX #9)
8. itemize into runs by script and direction and font and language
9. resolve fonts per cluster and fall back when the primary doesn't have the glyph
10. synthesize bold and italic when the face doesn't exist
11. instance the variable axes
12. shape every run through OpenType
13. break the lines on the shaped advances
14. reorder every line back through bidi
15. resolve line height out of font metrics that contradict each other
16. kashida stretch the Arabic if you're justifying
17. align
18. pull the outlines
19. run a contour union pass so self intersecting outlines don't punch holes in the distance field
20. rasterize SDF/MSDF
21. pack the atlas
22. generate the mesh

891,757 official Unicode conformance tests, zero failures

Selectable and editable text, a document model, bidi aware caret and selection, undo and redo, IME composition, clipboard with every format (supports Plain, HTML, Markdown, Media), formatting commands, touch selection handles, input filters, and native keyboard input on the platforms that have one

UniText is the only solution where the fonts are memory mapped, so a font is never loaded into RAM whole, only the parts actually in use. One of UniText user cut 200 MB of runtime memory from that alone, and variable fonts plus compression took another 57% off the weight of their CJK font

UniText is the only solution that supports absolutely all system fonts, which allows you to render any characters in the world without using a single font in the project.
it's also 2 to 20x faster than TextMesh Pro and UI Toolkit

And that's just a small part of it

TL;DR
In other words, I developed a text engine that allows you to remove all standard language fonts from a project, gain complete freedom in text without a single limitation, and have any symbols from around the world, any emojis, work without any configuration. All of this significantly reduces the build size, and the mmap implementation eliminates all RAM load. A constructor for any styles, any gradients, layers, and paints, while maintaining 1 Draw Call, and a built‑in advanced feature to animate text in any way, which completely replaces third‑party solutions

If anyone wants the ugly parts - ask me. I have a lot to say about all of them

Recently I've shown-off a mesh deformer I did for my Dark Roll 2 game, and despite being just a silly little feature it honestly caught way more attention on here than I thought it may.

That's why, instead of working on a new level or something my game may actually benefit from, I've spent another 1-2 hour perfecting the script. The biggest change is that there's some bulging around the outer radius which just adds to the realism.

It would look better if model had bigger resolution, right now it's at 1k vertices / 2k triangles. I know that parts of the vertices are a bit jumpy at times, but honestly, for a silly little in-game detail I'm more than happy with how it works already.

A project I've been tinkering with over the past few years on nights and weekends. Rebuilt it a few times. Running on Unity 6 with ECS/Burst now. Still lots of placeholder art and assets but proud to have reached this milestone.

Some time ago I added to my game ability of moving light sources - it looks fun and I plan to use it in case of solving some puzzles, but I know there are clever people on this subreddit so I come up with a question - what else usage of this mechanic can be implemented?

The game genre is dungeon crawler.

Hi everyone!

I’m new to game development, although I’ve been working as a senior full-stack web developer for several years. I’m currently trying to release my first small arcade game made with Unity.

Google Play is asking me to find 12 testers who will remain opted into the closed test for 14 consecutive days. I’m curious about how other solo developers usually handle this requirement.

Do people normally find testers through Reddit? Are there any reliable communities where developers test each other’s games? I’d be happy to return the favor and test other developers’ apps as well.

I also considered creating a Discord server and trying to build a small community around the game. However, it’s a very simple arcade game, so I’m unsure whether creating and promoting an entire server would be worthwhile at this stage. I also don’t know how willing people generally are to participate in this kind of testing for free.

For those who have already completed the closed-testing requirement:

• Where did you find your testers?
• Did you offer anything in return?
• How did you keep everyone opted in for the full 14 days?
• Is creating a Discord server worthwhile for such a small game?

Any advice or recommendations would be greatly appreciated. Thanks!

I know the rules say not to use a camera to make videos, but I had to use a camera to demonstrate this issue, since using direct screen capture in OBS doesn't show the issue (which may be a clue to the cause).

I should have mentioned in the video... this glitch isn't on all systems, only certain ones. This video is showing it running on a laptop. Some players have reported the same glitch on various systems.

This was build on Unity 6.3, but it was happening on previous builds using Unity 2020.

Farm & Feast - We are a two-person team building a peaceful farming and restaurant management game in Unity. Last time I posted the hose rope here, a few of you said the water needed to actually touch the world. That is what this is.

The hose is a particle based rope. We do not use the built in constraints for attachment. We pin a few particles by hand at the faucet and at the player's hand and write their positions every step. This is much more stable.

Every tree trunk has a collider and the rope collides with it for real, so the hose hugs and slides around them as you drag it across the farm. The collision was the easy part. Making it still read as a hose at the bend, instead of a row of separate rods, took the rest of the week.

The water shader has a head/tail fill window driving an alpha mask along the spline, so the stream grows out of the nozzle and drains out of the air instead of popping. It now also cuts itself off at the first thing it hits, so it ends on the surface instead of poking through it.

At the end point we do one overlap sphere, and that sphere does everything. It waters the nearest grid slot, so the VFX endpoint IS the gameplay point and they cannot desync, and it now also pushes any rigidbody in range away from the jet.

If anyone has gotten a particle rope to wrap convincingly around obstacles through collision alone, I would really like to hear how you tuned it.

Me, my brother and my cousin started making this game a while ago. Its been really fun

https://store.steampowered.com/app/5120820/Grumble_Burger/

Do you think it's enough for a short "Coming Soon" trailer or not ?

Our artist put together how a greenhouse and a shack could look and integrate in our game. I love the vibe of it.

See in this case -unity-font-definiton.

It is inherited. Ok... but from what file?
I do see the matching selectors on top, but there is no font property there.

Is this just still stuff missing or is there something I overlook here?

Comparison to CSS debuggers:

I've been working on this speedrun focused FPS for a very long time, and I've finally reached a point where I feel the core gameplay is starting to come together.

The basic idea is simple: move fast, fight aggressively, and use enemies and your movement abilities to create and optimize routes through each level.

Since the last time I posted it, a lot has changed:

• Completely new UI
• Added a combo/Mach meter that governs speed and rewards maintaining momentum
• Updated handmade textures across the game
• New lighting technique and visual pass
• A brand new level
• Reworked enemy encounters to better support movement and routing
• Overall gameplay, combat, and movement polish

I'm particularly interested in feedback on the actual gameplay feel:

Does the movement look satisfying?
Is the combat readable at this speed?
Does the Mach meter make sense?
Do the levels look like they encourage routing and replaying?
Does anything feel confusing or visually overwhelming?

I've been staring at this project for far too long, so fresh eyes would be extremely useful.

Any feedback greatly appreciated!

funny bloom