$16 for a *very* non-performant material? If this was intended for use in high-detail scenes, not meant for gameplay, one would generally just use a flipbook animation, or looping HD video texture (both of which are higher quality and available for free all over). I love options, but c'mon, that's pretty steep. $5, maybe. And you can loop in materials, using custom HLSL nodes. Also, there are better ways of doing this, all around. Somewhere on the forums, Ryan Brucks (of Epic fame) himself touched on this. I've personally been working on a cool water material (not "material blueprint", thankyouverymuch) and utility functions, and am close to the quality achieved here, sitting at ~180 instructions with everything "turned on". The kicker? It's pure procedural. No textures are needed. So this is cool, no doubt about that. In my humble opinion though, it's not "good". It doesn't run fast, and it's more complicated than it needs to be.
Lee is right - you can use a gradient effect when you vertex paint in your chosen 3d modelling platform (I've done it in max), meaning the wind effect shifts from nothing to maximum along the length of the leaf/branch/whatever.
I'm fairly certain you can vertex paint the bottoms of the foliage and control the movement using vertex colors along with the wind node. I did this in an earlier project and was able to create a scene with grass that moved less and less as it went down until stationary. I created the grass and painted the vertexes black to red (bottom to top) in Maya.
My „team” is just me. Elder Games is a one-man show at the moment with some freelancers occasionally helping out. In case of Meridian: Squad 22, a freelance graphic artist made the worker Drone for me, and Hexany Audio provided all sound effects.
I’ve always worked on my own games, never contributed to anyone else’s.
Features of Meridian: Squad 22
To me, the most important feature is the research system. In most other RTS games, when you play the campaign, you receive new tech in a fixed order. In Meridian: Squad 22, you can choose what tech to unlock next, allowing you to play the campaign in your own playstyle. This is a game where turtling in your base is possible as much as rushing your opponent. You can also focus on just producing infantry, or take out key components of the enemy infrastructure with your naval units. This kind of freedom provided by the research system is, I think, the best aspect of Squad 22.
Enemy AI and unit pathfinding were the two toughest things to get right. Another difficult aspect of development was the fact that Meridian: Squad 22 is the second Meridian game out of the four games planned. Squad 22’s story had to stand on its own, but also foreshadow a lot of events that will happen in future Meridian games. This proved to be a much bigger challenge than I initially anticipated.
Creating Battle Arenas
I’m hand-placing everything in every single campaign map, with great attention to detail. Most small details – radar stations, silos, vents with smokes, pipes – are exclusively modeled for just one small part of a single map. This is tough to do as I’m an indie developer with limited resources, but worth it, as it provides a huge amount of detail and variation for the maps.
Conquest mode is different though – those missions are procedurally generated for you every time you enter a battle, so I had to get the map generation algorithm right for that to work.
Unit design usually begins by thinking of a function, a role that none of the existing units fulfill yet. Eg. when designing the Wraith Bomber unit, it occured to me that no other unit has splash damage yet. So the Wraith Bomber has that, and it is an efficient counter to mass infantry. The thought process goes like this at first, but then I also have to think about the unit’s weakness. My main design principles are that no unit should be able to counter everything, every unit should be designed to have a specific role and most importantly, don’t add units just for the sake of adding them.
Because of these principles, Meridian: Squad 22 doesn’t have any unnecessary units, you can find a use for all of them. Which ones you’ll use simply becomes a matter of preference.
I usually think of a feature that I would enjoy. Let’s say this feature is having naval units. This is rare in sci-fi games anyway, so let’s add ships! I start by asking questions, then writing all my answers down. What kind of ships should there be? What roles do they perform? What kind of weapons do they have?
In the end, I went with one combat, one defensive and one economy-centered ship, all of which can help you a great deal. This is based on an existing core feature, research, which is also divided into these three categories.
So the Cyclone unit is an effective attacker, the Hellbringer’s attack is slow but can defend your base against all kinds of attacks, and the Scavenger collects the debris of destroyed ships and turns it into Shardium for you.
This is usually how new features are created – I think of something fun, then try to base it on one of the core features of the game so it integrates well with what’s already there.
In the Early Access phase, feedback is very important and fixes are frequent. Whenever someone encounters a bug, I usually try and fix it in a few days so it can be included in the next update. If there’s a feature request, I’ll try and find a place for that feature. If it would fit well with the rest of the game, I implement it. If it would fundamentally change what the game is about, I interact with the community to find a way to implement the request together.
Meridian: Squad 22 will hopefully be released in August!