"I've seen [formations] done really well ... but the guy did spend something like 4 to 6 months on a 2d grid working on just that problem all by itself. And he had done it before."
The one thing you really need to nail with an RTS is unit movement. Unit movement has a surprising number of elements that all have to come together brilliantly to produce smart looking unit behaviour on the screen:
- Long-distance pathfinding
- Short-distance pathfinding
- Collision avoidance
- Collision resolution
- Steering & Animation
The Imperial Realm :: Miranda - Formations
This screenshot shows Miranda's new unit movement systems in action. I still have some work to do on collision resolution, but it is already looking pretty sweet. First, you will notice that the tanks are moving in a square formation. There are some units that are out of position because they've just gone around those buildings (you can tell from the dust trails,) but they'll all eventually get back into a neat grid layout. In the bottom left corner is the formations flyout menu ready to select one of the available formations. Once one is selected, the menu shrinks to display just the selected formation.
I'm feeling a bit snarky this weekend since I haven't been able to try The Elder Scrolls(R) Online
beta. The up-side is that I've learned a whole bunch of things about how to run an MMO Beta program that will be really helpful for Miranda
After all the time I spent playing Skyrim, I was really excited when I saw PC Gamer was giving away beta keys on Thursday, so I hurried over, signed up for a PC Gamer account and lucky, lucky -- I got a key in the email a few minutes later. Hooray!
For whatever reason, Ctrl-Tab in Visual Studio 2010 has been broken for a long time. You have to press Enter to select the new window to switch to it. For ages I hunted for a solution to this problem, enduring the frustration of an extra keystroke but no longer
. The problem seems to involve Magnifier, but Magnifier isn't really the problem. I've read "solutions" that involve completely removing Magnifier (doesn't work.) But here is the solution I've gone with (since the problem comes back after every reboot.)
- <Windows Key> +
- Click on X to close magnifier.
[City of Fire]
I'm working on the trailer for Miranda with G'Mic
and GIMP. This is a reject, but a really cool one.
I had need of a good spatial searching data structure. I found a pseudocode example for a quadtree on Wikipedia
although it had a few key parts missing which is sort of inconvenient, so I've filled those out and decided to post the full C++ template code here.
This is a leafless quadtree
as opposed to a quadtree which has both internal (points to children) and leaf (contain all data) nodes. I'm not yet sure what the performance implications are of the two types other than that the leafless quadtree is going to do more data comparisons than the traditional quadtree during deletion.
This is still somewhat a work in progress and there are some things I'm not entirely happy with. For example, Move could be made faster by avoiding a second search if QuickMove fails. Also see the comments above the Combine method. That said, I've run unit tests against this and can't find any more bugs in it.
The only code missing from here is my vector template used by Query. You can replace that easily enough with an STL vector or the equivalent.If you are here looking for answers to your homework - go figure it out on your own!
It has been a little quiet on the blog the last month. Back at the start of January I came up with a really smart solution to my movement/collision/formation/pathfinding issues which also has the gigantic benefit of reducing the bandwidth needed for unit movement almost to zero, so I've been super-busy getting that put together. I've also been thinking a lot about the viability of Free-to-Play as a business model for Miranda...
Since I started development, I've been planning for Miranda to be Free-To-Play (F2P). F2P makes a lot of sense for smaller developers. It has really solid economic theory behind it (if you're not already familiar, read up on "demand curve" and "consumer surplus") and by making a game free, you can get a lot of people to try your game who probably wouldn't if they had to pay for it.
That's the theoretical upside, but lately I've been reading a lot of articles about failed F2P games. They all had good reasons why they failed, so there is something that can be learned from them, but the statistics shared about those failed games has got me thinking that there are other forces at work in 2014.
It's time for my third annual
look at the past year.
Looking at my work log, the biggest part of my year was spent getting systems that kind of worked into final working condition, adding features, fixing corner cases, bugfixing, polishing and improving performance (I did a lot of work on loading and rendering performance.) While I thought I was mostly done with rendering last year, I still put a lot more effort into making the game pretty this year. I added more normal mapping, distance fog, smoke to damaged units, dust to moving units, a sandstorm effect, two factions worth of buildings (21 of them,) 23 rocks, fields of flowers, the sky, distant terrain rendering, a rusty container-ship setpiece, color correction and heat refraction post-effects and at long last: rubber-band rendering for the mouse. Adding Object culling was the biggest rendering performance win.
For some time now I've suffered with abominable build times on my optimized builds. A full rebuild of just the client in Debug takes 160,825ms but in Release it takes 371,462ms. So for less code, that's a whopping 231% increase in build time just for optimization!
I build three different configurations of my game. Debug is a build with all debugging features enabled, ASSERT's on and debug trace output. Release has full optimization, no ASSERT's or trace output. I also have an Abort built which is fully optimized with ASSERT's and no trace output. I use the Abort build often, but the 6 minute build times even for a one-line change make it super-inconvenient to iterate.
I've spent quite a bit of time the last couple weeks piecing bits of different articles together to figure out how to implement normal mapping in the Lair Engine. The problem I encountered is that there is a huge variation in the methods and terminology used for normal mapping. This makes it a very confusing topic for non-math-lovers like myself. So here I'm going to explain the three common techniques for normal mapping for the mathematically uninclined.
// For AMD Enduro this should do it on 13.35 and later drivers.
__declspec(dllexport) int AmdPowerXpressRequestHighPerformance = 1;
Berkelium isn't maintained anymore, might want to consider Chromium Embedded Framework
instead. I'll probably switch at some point since drag and drop is broken in Berkelium.
Signed up for the email list, still very interested in this project
Hey Tripleskit, your answer is here
When will this game be accessable for open/close beta/alpha