Something I discovered people are quite floored by when I demo Miranda is when I zoom out from my base, then it switches to map view and then just keeps zooming out. While I don't yet have the full 300x300KM map, even my 20x20KM test map gives a pretty good sense of how big the environment is. So that needs to be in the trailer. The map has been working for a long time, but when I took a close look at it this week, I found a few little things that needed to be addressed.
Every once in a while being a programmer is a useful skill.
For years I fought with Pixela's broken ImageMixer software to try to get it to download videos from my Canon Vixia HF S100 camcorder. The software worked about 30% of the time, which was enormously frustrating. Recently the PC with that software had a hard drive failure. I couldn't find the original software CD. Canon's website now recommends CameraWindow, ZoomBrowser and ImageBrowser for the HF S100, but after finding the camera box with the serial number and entering that, downloading and installing the three packages, not one could see the attached camera. I'd had enough.
While watching TV with the wife last night, it took just four hours to write new Windows software to locate the attached camera (or storage card,) download the videos, thumbnails and photos from the camera and copy them to a PC with a naming scheme consistent with what I used to get from ImageMixer. I should have done this years ago.
Recording game video is not as easy a problem as you might think. You likely want to record at 1920x1080 resolution, 60FPS so that's 1920x1080x3x60=373,248,000 bytes every second (373MB/s.) My disk drive is pretty quick, it can do around 85MB/s, some newer hard drives can break 100MB/s. My first video recording system wrote every frame as a PNG and I liked to call it the crash-the-game-button. It would record about ten seconds of video before it ran out of memory and crashed, however once I had half a video recording system, I kind of wanted to finish it. Actually, that's not true. The reason for all this work is that I'm not satisfied with the quality of video produced by screen capture programs. The trailer for Miranda needs to look as good as I can make it.
I've been working on the first trailer for Miranda pretty much continuously for six days now. Sometimes when you get a good idea, its hard to leave it alone. The first ten seconds took four days, the next five seconds I've got two days in and counting.
The first shot of the trailer is fully CG. I've tried CG work before, but never was really satisfied with what I produced. It was OK, but not good enough to show anyone. I put the new shot together with Blender
which I've grown to appreciate is kind of amazing. Blender used to have a terrible, terrible user interface. It doesn't anymore, a change which really surprised me.
Today The Imperial Realm::Miranda passed 250,000 lines of C++ code!
That doesn't include other types of source (HTML/CSS/XML/JS etc.) libraries I didn't write, or Chrome (which itself is around 4M lines of code.)
That's an average of around 42,250 lines of code per year. I feel pretty good about that. I'm always amazed at claims that the industry average is around 3,300 LOC/year - that's a lot of overhead.
There is nothing like trying to get software running in an environment that is actively screwing with it.
[Rolling Strike Force Alpha]
I borrowed a laptop with a 3K (3200x1800) screen from a friend to do some debugging on high resolution displays. Bugs like Windows reporting the 3K laptop's screen resolution as 1067x603?!?! (I wasn't calling SetProcessDPIAware early enough.) There were an assortment of minor issues I was able to quickly fix, but when I went to test them, things really started to go off the rails.
I needed some special characters for Miranda and after investigating simply inserting bitmaps inline, I realized it would be better to have a custom font. Tonight I built a font for Miranda using Gimp
. It was super-easy. Design characters in Gimp, export to SVG, drag and drop onto Glyphter, name the font, save a ZIP and you're done. Glyphter exports EOT, SVG, TTF and WOFF as well as a CSS file supporting all of them.
My new characters:
A new build of The Imperial Realm::Miranda is finally live. It has been a while since the last update, mainly because there were a couple of big changes to the game that I wanted to finish. The really exciting thing for me about this build is that with a full complement of units for the Independents, it is the first one that really tests a lot of the game features I've been building.Note: The database on the test server has been wiped. Testers will have to create their accounts again using the same Secret Lair Code as previously.
This screenshot shows all the units that can be built from the Independents' default inventory before the player needs to start shopping at vendors or hunting for crates.
I hate it when I hit Friday afternoon and I haven't finished what I was working on that week. I like to be able to do demos on the weekend. It looks like that's going to work out for me this week.
Since the end of July I've been working on a full set of units for Miranda's Independents faction. It took an amazing amount of time to figure out just how to get all the game elements I wanted, and put them into the framework I've set up for Miranda. I've worked on lots of other things as well - I can only spend so many hours in a spreadsheet without doing any programming - but an initial full set of units for the Independents was the big goal. After doing a lot of research and game testing and building a stack of messy spreadsheets, that goal is now mostly achieved (although many units' special abilities have yet to be implemented.)
[ATVs on the move, Hover Tanks & a Few of the Independents' New Units.]
Friday I had what I believe is the first new feature that didn't require a single engine change: I made a new explosion (the one in the middle.) All that was required to add this was a script file change and some new art. I now have all of the elements I need to make some nice explosions:
- Animating, color changing particles for fire and smoke.
- Hot spark particles.
- Debris particles.
- Spherical particle emitters (smoke and fire, shockwave rings.)
- Ballistic particle emitters (sprays of sparks.)
- Camera shake.
- Screen whiteout (not shown in these explosions.)
- Audio propogation delay (farther explosions take longer for you to hear.)
I'm not totally satisfied with these yet, but now it is mainly a matter of adding to and tweaking the art. The plan is to have a few more explosion effects in the finished game.
There are a few more explosions now. And a variety of sound effects. I'll be putting some more effort into sound soon.
It worked fine for me :D just looking back through your blog posts :p are these still the blast effects? because they look cool also what is the sound for this blast effect?
Upgrades - 2016-04-09 07:13:38 (1 comments)
Yeahy can't wait for the next dev blog. Sounds like you have had some bad luck with windows 10 it worked fine for me with the previous updates which fixed most of my problems. It makes me happy to hear you have a better machine now :p.
Hey Robert, it is great to hear an update! loving the resources and ideas. I like the sound of a nice sparkly effect on the resource fields. Looking forward to a public test :p. thanks again for the update :).
I'll write up the whole story when its done.