X@COM

Remember those eerily vacant farms? Wading across cornfields and searching barns while looking for the UFO crash/landing site? Modder 10101 has done an excellent job of recreating that experience in his aptly-titled mod "Farm".

This mission varies widely in scale since your squad lands in either a Skyranger, Lightning, or Avenger and begins with tech-level appropriate equipment as you face off against any of the possible UFO types including the scout, harvester, supply ship, terror ship, or even a massive battleship. (It's an impressive job considering the current limitations of the modding system.)

HQ will notify you of the class of UFO at the site (which may be either crash-landed or on the ground carrying out its own mission) and you can opt to press F10 to randomize the mission. As usual, beware facing off against against psionic races since they won't hesitate to mind control your soldiers with perhaps dire consequences for squadmates...

While the experience should be very similar to the original, at least one tactical difference I noticed while playing is that you'll be able to smash through hedges instead of always shooting your way through (jumping over low walls and fences would've been another option, but we decided to postpone the parkour functionality). Then of course there's the fact that we have gravity in X@COM, so you can literally bring down an entire barn with explosives if you like, or collapse upper floors by shooting out lower walls.

Get it on the files page, of course.

Can you guess what's on top of those four round things?

Hear that?

It's the
hum of nearby power cores,
the twittering of alien terminals,
the footsteps of soldiers making their way across a lawn, pushing their way through foliage, and trampling crushed glass as they investigate a decidedly large opening in the side of a now-abandoned house, or the sound of aliens sneaking down a wooden hallway towards that very opening. Or not sneaking. You'll definitely know a sectopod when you hear one--let those mechanical steps strike fear into the heart of many a brave field commander!
It's the
charging of powerful laser cannons,
brick walls crumbling from an explosive impact,
spent shells rattling across the concrete,
bullets ricocheting off UFO hulls,
grenades bouncing down the hall (if you're close enough to hear this one, um, was nice knowing you),
glass storefronts being blown out (try the pressurized gas explosion of a small launcher for the coolest effect--since it just gets the windows ;p)
falling furniture smashing into a lower floor,
a growling reaper that must be right around the corner,
and the roar of a massive... well, you'll hear it when you do (hopefully before you see it so you still have time to run).

And that's just the beginning.

Weighing in at 850 sounds, R9 is the true beginning of creating the sense of immersion I envision as being core to the X@COM experience.

It's been a while since we had a nice whole number release following the modding bonanza that was R8 (which resulted in some very beneficial iterative development).

The highlights of this release are a super fast (relatively speaking) engine refactor (old post) and, of course, the new sound system, which I've posted a bit about recently, but here's a quick overview:

• Ambient sounds are sourced from objects in the surrounding environment (area-based ambient sound will come at a later time when the map generation supports it)
• Volume is distance-based, and allows for different falloff models depending on what makes the most sense
• Weapons and explosions currently use a temporary set of sounds, a quick job meant just to cover the basic X-COM content
• The system is, as usual, easily moddable: there are hooks in the data/code for weapons, destruction, various types of impact, death and injury, ambience, item interaction, etc.
• Sound is also integrated with the event/ability scripting system, meaning just about anything can be audible if necessary

Among the smaller additions, melee attacks that fail to destroy terrain objects now show messages indicating how effective the hit was. This was a great community suggestion, since you generally don't have any idea whether what you're using to bash down that heavy door is going to knock it down anytime today. Later this will be slightly less of an issue once you can examine damage and integrity values in-game, but for now it could save you some time, especially useful in Rookie's Tale where melee items are the norm.

The log now implements message folding, so consecutive identical messages will just increase the count on the first one by using a suffix: "<x#>"

Proxy grenades now require priming as in the original. Don't drop them at your feet after priming them! Dropping them and picking them up again will deactivate them (of course you can only do that if you haven't moved from their location, or you use some kind of psionics to move them, entirely possibly one day as we've seen in Rookie's Tale--unlike the original, flying units cannot drop down to pick them up.) The game still supports grenades that auto-activate when thrown, for modding potential (that and X@COM smoke grenades still automatically explode).

On the scary side, aliens can use grenades! Oh my... This feature has not been retroactively added to old missions, though--it's only available in mods, and only where the modder intends it (by putting 'nades in alien hands ;p). At least there's only a *chance* they'll throw it at you.

So you want to finally hear all these new sounds? There are currently three ways:

• The simplest (though not quite as fun) is to download the demo and run the sandbox, where you can play around with the weapons, shoot the house, etc.
• You can also replay the old demo missions, but because game sounds are *deactivated* by default, you'll have to turn them on manually by editing the mission's .bat file: add the "-fullSound" command line switch. I recommend against this option since the experience will be fairly inconsistent given that they contain additional non-standard content for which there are no sounds.
• Or... play this new mod created specifically to show off sound effects!

Welcome to Ground Zero.

So after years of playing X-COM you're a pro at taking on one landed UFO, sure, but how about multiple UFOs at once?

The weakest opposition you could face will be two medium scouts, plus whatever has taken up defensive positions in the surrounding structures, plus whatever else decides to show up depending on your performance. On average there will be around 3-4 UFOs, though, among them sometimes a large scout or even a terror ship.

As usual, expect some surprises along the way, though this is still a more traditional tactical mission, so don't bother using anything in the environment--I didn't go crazy with that system like I did when testing it in Rookie's Tale.

Beware of sectoid and ethereal leaders, since some of them may be capable of mind control (requires LOS though), and also try not to bunch up too much lest a well-placed alien grenade wipe your whole team out.

If you feel outgunned, Malachai can be a useful ally if you can find him early. He'll join you and follow around, hopefully covering your back with his minigun and super deadly skill with throwing knives (close combat only). Once he's joined, shift-f to highlight his position since he's an allied unit not under your control. (Malachai is one of our fans from YouTube whose enthusiasm for R9 has earned him a place in this mod =p)

Like exodus, completing this mission "successfully" shouldn't be too difficult (you could always hide, wait most of it out, and at least survive...), but scoring well will be quite difficult due to the various penalties for failure to achieve objectives.

Your primary goal is to take out power sources, and for that purpose you have a good number of remote charges. As a reminder of how to use them, (p)rime them with an empty hand to create a detonator, then place the charge and (u)se the detonator when ready to set it off. Make sure to place/throw them close enough to the power source to be able to destroy it!

This mod also includes a special new kind of remote explosive, the Hull Breacher, designed specifically for breaching UFOs and giving you a different point of entry for alternate tactics. Make sure you place them immediately adjacent to a UFO hull or wall, flip the switch, and surprise some aliens from behind!

Jackpot! Look at all those power sources...

So now's your chance to command a newly audible heroic squad to prevent the equivalent of a local Armageddon. Good luck if you're forced to land at night...

My advice: Move quickly, because the longer you take the harder it will get.

X@COM is finally getting some truly video-worthy content (sound makes a huge difference), and I was working on a Ground Zero compilation to show off this release, but lacking the time to edit and polish it I've put that aside for now. In any case, you can always download and play a round if you'd like to experience it now, or wait until I do get a video out there--now that sound is mostly in place the visuals/UI are going to start improving in leaps and bounds.

I'll be leaving for a couple weeks soon so there won't be any new posts for a while, but when I return in late April there will be a brand new sound-enabled mod ready from one of our modders.

More than 750 sound effects later, I'm done (for now).

This phase of development only goes as far as implementation of the core sound system, and inclusion of a majority of the "generic" sound effects that we know we need:

• bullets/projectiles colliding with different materials
• spent shells hitting the ground (again, material based)
• item throwing and colliding/landing/falling/dropping (not all the same thing)
• melee swings and strikes (dependent on object struck--and whatever is swung, but for now that's mostly the same metallic objects)
• door manipulation
• grunts/screams from injury (pretty limited for now, esp. on the alien side)

So nearly none of the "unique" content you see in the demo scenarios has sound, instead all I've done so far are the parts that are sure to go into the final game. Obviously as you heard in the recent video there are sounds for the core weapons and explosions, for testing and, of course, fun :)

As for ambient sounds, while I had previously labeled them "unlikely", they are just so easy and beneficial to the atmosphere that I had to implement them, too. So now your soldiers can hear the pulsing hum of the UFO power core, beeping of terminals, wind in the trees, and fire. More will come later with the actual game content, although yesterday I couldn't help myself and added an event-based sound that plays on mission start if you have a Skyranger: the sound of the craft bay doors opening and lowering the ramp. Ambient sounds are heard by the currently selected unit, if any, and fade in slowly when selecting a new unit so as not to get too annoying while cycling through many units.

Check out this debug shot visualizing the volume of ambient sounds heard around a UFO:

Obviously you have the UFO power generating the strongest source of source in there (though it falls off quickly), with the terminals on the left chiming in. Outside is a tree, and if you're not too far away from it you'll hear a gentle breeze occasionally blowing through the leaves.

As mentioned before, sound volume is distance based, so the amount of control the engine now provides over falloff rates (attenuation) is useful for making different kinds of ambient sounds more realistic and changes in distance sound less harsh as units move nearer/further. The engine supports linear, logarithmic, reverse log, and inverse rates (you can read about them and see their graphs here). They don't work absolutely seamlessly, this being a grid world with discrete positioning rather than one with the more fine-grained resolution you'd see in a normal 3D game, but they get the job done well enough.

As with everything else, the entire sound system is controlled through text files. You just drop files in the audio directory, add their path to the sound definitions (along with their ranges and falloff model), and use them wherever in the data. The engine also supports the creation of sound channel groups for more precise control through particle script commands.

For the player, sound control is divided into three groups, UI, game, and ambient, which you'll be able to toggle and set volume for individually, though for now I'm not going to include commands for that since it will be handled through an options menu.

With this R9 is pretty much done, though I'm thinking of creating a quick mod that can better showcase the sound system, as all these cool new sound effects will be deactivated in the normal demo scenarios (you can manually activate them, but the overall experience will be inconsistent).

So this "dark cloud" previously mentioned, the one that was threatening to hinder development in a big way (= stop it for a year), has thankfully dispersed! I'll still have to be away for a couple weeks next month dealing with related matters, but once that's done nothing will stand in our way!

Okay, maybe there is another little cloud brewing out there, just about the only other thing that could get in the way... like the funds to continue at a good pace.

To date I've put all my own money (+= lots and lots of time) into this project, but it just so happens that my current sources of income are drying up in a few months and rather than looking for more of the same type of work I've been considering using the opportunity to try something different. I'd love for that to be game development, but X@COM is probably not something that can really make money, and working on an alternative simpler game would essentially mean putting this project on hold, which we obviously don't want. So after a few months development may start to slow down depending on how the money situation develops.

I may open up the project to donations and see how that goes--who knows, maybe we'd be surprised. Given that the game is generally well-received, a full-on crowd-funding campaign (assuming the necessary re-branding of the content) would almost certainly be successful enough to work full time long enough to bring the project to completion, but non-U.S. citizens can't use Kickstarter which is still the only truly viable platform these days (barring a few exceptional projects), making that a non-starter for me.

We'll see what happens. For now it's back to regular development and we'll see about getting R9 out there before I have to take that short leave.

Progress: I'm still expanding the sound system, which is now almost complete and includes some great stuff, but I'll save the juicy details for another post when everything's in place.

There's finally something new worth a video: sound effects! Hear footsteps, guns firing, shooting through windows, blasting down walls, a stompy colossus wrecking houses, and finally the almighty blaster launcher.


The video doesn't include all the new sounds (by far)--for that you can play with the R9 sandbox (when it's available).

The weapons and explosions you hear are quick placeholders I put together for testing, but footsteps, destruction, and impacts are about where I want them to be besides still needing to be expanded. Right now there are 372 sound effects that fall under the above types, with still more categories to be added.

Sound effect volume is based on distance from the nearest unit under your control (and the inherent range of the sound itself), but most of the action takes place up close so you won't really notice it here.

As we're all aware, atmosphere is an integral part of the X-COM experience, and an important element for building that atmosphere is sound. The sound of unfriendly footsteps echoing through the darkness; civilians screaming as the aliens find them before your squad does; hearing gunfire pierce the silence as unseen aliens fire on your position, but miss their mark so you still have no idea where they are. These add to the suspense, while also making the "hidden movement" phase that much more interesting (and informative).

This aspect of the game has been on the back burner for quite some time while we squared away the core mechanics, and with that done it's now time to decide what needs to be heard.

Items:

• Weapon fire / attacks
• Projectile impacts (projectile+material-dependent)
• Explosions 
• Throwing/landing (latter could be material-relative)
• Dropping (essentially same as landing)
• Picking up
• Melee swings / misses
• (Ammo loading/unloading probably unnecessary for now since only possible through inventory window, which has its own sounds)

Units

• Footsteps (usually terrain-based, but units may override that in special cases, such as flight or huge stompy aliens)
• Death

Terrain

• Footsteps (us. material-based)
• Door open/close
• Destruction (us. material-based)
• Falling prop impacts (unbroken, us. material-based)

Aside from the lists above, the sound system is already accessible through special abilities scripting, so sounds can be connected to just about any game element to create unique situational sounds like a terror unit roaring on spotting a target, or a chryssalid screaming on injecting a victim, etc.

Much of the functionality already exists, as particles and anything that uses them (attacks, explosions, throwing, melee...) are already capable of playing and controlling sounds (which is how the UI emits sound). We still need control for sounds related to non-particle objects, and to [elegantly] deal with various issues like the extreme cacophony that would result from huge explosions destroying wide areas of terrain, footsteps out of sight (it will slow down turns to always have NPC unit steps heard--not sure by how much), and many more I no doubt have yet discover.

After that it's mostly a question of putting together the assets, but I won't be doing all that now, just a core set used for testing/R9.

Fortunately I have handy a nice library of 157 footstep sounds I put together for an old game, so hopefully they'll work well for X@COM without too many adjustments (although I may have to edit them all--doh--to get them to work with the faster movement speed than the game they came from). Categories include dirt, grass, gravel, metal, mud, puddles, water, wood, rocky, snow, stone, and undergrowth. Because you need something other than my wall of text to look at, here's a color-inverted shot of one of the snow footsteps in Audacity (my primary sound editing tool):

*crunch*

Another issue at hand is to determine what level of control the player needs over sound. Besides the obvious option of muting the game entirely, will it be sufficient to split sound effect control into two categories, UI and game? That's what the plan is, in any case.

Other features under consideration (any opinions?):

• Dynamic sound effect volume based on the distance of the source from the nearest unit under the player's control
• Music isn't appropriate, but some kind of ambient drone or beat as heard in X-COM can help set the mood (as long as it's not too intrusive).
• [Unlikely:] Very subdued map-wide ambient/background sound effects, like distant shouts and screams in a densely populated urban map, wind through the trees in forests, etc.
• [Unlikely:] Environment sounds emitted by props, and heard only by the currently selected unit; examples would include fireplaces, gushing streams, machinery, alien facilities, etc.
• Radio chatter?

I'm not going to press forward on all this immediately. First there are a few little items sitting on the to-do list that need cleared away while awaiting any comments/input you guys have to offer.

The game has always been a bit demanding on older computers when sub-windows are open (it causes those funny graphical anomalies you see with the text and borders), and I figured now was a good time to deal with that.

Of course the first option that comes to mind is... hardware acceleration! So I spent the previous weekend attempting to integrate OpenGL into Rogue Engine X. It sure brought back memories of the times I used DX9 in years before, trying to figure out what the heck was going on in the background when all I wanted was some simple result. Several days later, after fiddling with OpenGL and pulling my hair out, I pulled the plug on that idea.

After all, this is a 2D game, so using the GPU shouldn't be entirely necessary.

Approaching the problem from a different angle, I decided to profile the game code itself and look for bottlenecks. (Bonus: I learned of an awesome application profiler called Very Sleepy--so easy to just attach it to a running program and go! And it should perhaps be called "Very Fast", because it really is. Before I was always copying the source over to my XP VM and testing it with a very old profiler.)

As suspected, the engine code handling preparation of the screen data to be sent to the renderer was eating up a majority of the processing time. It was using a method I called "drill blitting", checking for all screen objects positioned over a single cell and blending them together to create the screen's final appearance at that location. It was the easy way to write the code back when the engine was first created, but the game has become more complex since then with lots more objects to handle. So I completely re-thought the way the screen is drawn and switched from cell-wise to layer-wise blitting, merging one horizontal layer at a time rather than doing it cell by cell.

Hell yeah!

This was tested on a full-sized, fully-revealed Rookie's Tale map using the default font, the first time with just the default map view open, and the second with a simple inventory open on top of that.

As you can see, the more window objects on the screen the bigger the savings, so opening the inventory and other sub-windows won't cause as big a hit to the FPS as it used to. FPS used to take a 23% hit while the inventory was open; now reduced to only 3%! (We're definitely going to need this boost, because the new UI will have a lot more little windows and interactive parts.)

Obviously your actual FPS will likely be lower unless you've got one of these wicked core i7 chips (or whatever better stuff has come out since). I captured those shots from my title bar FPS readout (F5), but you won't see values this high unless you uncap your FPS (Ctrl-F5).

I'm guessing it's possible to improve on this even more with some tricky OpenGL shaders, but that's beyond me--we'll be sticking with software rendering for the foreseeable future.

As there always is with any rendering WIP, there were several blooper-worthy screenshots (from the OpenGL attempts).

Rookie's Tale intro, as written in alienscript.

Complete mess.

More alienscript.

Inversion of foreground and background colors.

These were the fun ones. The most annoying, and prevalent, screen was the seizure-inducing flashy yellow one. Ouch my eyes!