This is basically completely about the build menu being more usable, and tooltips being more useful and legible. They still need a background to really be fully legible, but we got a lot of the other things with them. The unity ui is still… a learning process, sometimes.
This time around, I made a quartet of videos rather than Keith making them:
I wrote: A lengthy look with me at how to set up new GUI prefabs and then use them in code. This is shown while setting up the build menu to look better/clearer.
I wrote: A quick look with me at how to set up sound effects for buttons. It’s not a complete tutorial with everything in-depth, but there are tooltips for the bits that might not be clear, and this shows the workflow with greater clarity thanks to not going over every detail. At least that’s the goal!
I wrote: For Cinth and for modders, this is how you create new formations for ships of various scales to use in the game. I look forward to seeing a lot more creative and militaristic formations than my simple grids have been. 🙂
All that said, as noted in the release notes, I think there’s a way for us to work around the <sprite> tags in general and not use them. Even when those are working as well as possible, they still regularly show up improperly because we can’t control the exact relative scaling and offset per-font and per-font-settings.
Anyhow — major usability strides in this new build, although as always there’s yet more to do. Also a number of bugfixes.
I’m now back from traveling, and so is Keith, so that’s nice to be back to normal on that front. This new build includes a ton of backlog work that Blue and Cinth have done over the last couple of months that I’m only now getting integrated into the game proper — namely, visuals for 34 classes of ship in the game! That’s a pretty hefty chunk on top of what was already done, and there’s a lot more in the short-term pipeline on that stuff, too.
Beyond that, Keith has continued his testing-and-revising work, and that’s led to a number of quality of life improvements. Community member BadgerBadger has also made improvements to his Nanocaust faction, and those have been integrated.
Keith has also done another quartet of videos for this new version:
Keith writes: And now for something moderately different: some playtesting to help identify the main things in the way of the play experience. Ends predictably.
Keith writes: The day Galaxy Map Display Modes were unleashed on an unsuspecting universe:(probably not very unsuspecting, considering that AIWC had such modes, but they weren’t moddable!)
I’m not sure how many of you find 1h45m videos of coding “enjoyable”, but if so: enjoy 🙂 If not, an example of how to mod in a new display mode starts around 59:27.
Aside from Chris: I also just have realized, after working with Keith for literally 7 years now, that I’ve been pronouncing his last name wrong this entire time. In countless videos and interviews and podcasts and who knows what.
So, let’s review:
Keith’s name is spelled LaMothe, but pronounced lah-mont instead of lah-mow-th, which is what I’d been saying.
For anyone wondering, it is indeed Ar-ken games and not Arson or Arsen games. 😉
Keith writes: A quick change to mapgen to seed some nearby strategic objectives and make the early-early game decision of “which way do I expand?” more interesting.
At less than 20 minutes, this is a lightweight 😉
I’ve got another one that’s like an hour and 40 going through processing now, though, in case you have an excess of time to burn.
Keith writes: The Build Menu has an encounter with a chipper-shredder: You can see the current state of the menu around 1:30:05, if you’d like to cut to the chase. But there’s a lot about how to work with the UI system leading up to that. Iirc, 100% of the actual changes were in external code and xml, so stuff that’s possible for a modder.
Although, frankly for the details on “The Nanocaust,” you need to click through to the forum link where community member BadgerBadger explains his work. This is the first player-created special faction, and it’s something we’re building into the game as an option for anyone to use without having to do a special separate download or whatever else.
The other main thing from this build is basically pass #2 of Keith playtesting the game and revising based on his findings. This is overall a smaller batch of testing and revision work, because Keith was traveling for about a week and I’ve been doing the same. But overall it’s some solid stuff, and we’re marching onward toward where the game needs to be on a number of fronts.
Keith has also done a pair of videos, lately, and you can expect more in the future:
Keith writes: The modding tutorial on xml/code (tool links, etc) is still pending, but this contains a lot of info on modding itself, as many of the changes I’m making are functionally mods.
Keith writes: The initial bit on the dps formula and the overall balance architecture is interesting if you’d like to know more about that, but the addition of Badger’s Nanocaust faction is much more interesting, the real testing of that starts around 1:18:15 in the video.
Cinth and Blue have also been plugging away on their work, and I’ll be putting out a massive batch of their content changes (new shipn visuals, adjusted ship visuals, etc) early next week. 🙂
Release notes here! They are short and overall not that exciting, unfortunately. That said, if you’re modding the GUI, it’s a pretty titanic shift in terms of what you’ll find in there now.
So what’s up?
Basically over the last months we’ve learned a lot about what functions we do and do not need in our GUI in order to make it fit all the various screen resolutions and configurations, and to be as performant and attractive as possible. It’s still blocky and untextured right now, so the attractive part isn’t there yet, but with the changes from this week we’re now able to pursue “functional, well-organized, and non-overlapping” with renewed vigor.
There are a few other things in there as well, including some minor changes that make a huge difference in how the balance of AOE units affect things. There’s a few more of the voice acting audio clips that play now, and a few quality of life improvements with hotkeys.
Anyhow… this is one of those “iceberg” releases where it is actually a lot larger than it looks on the surface. 😉
The key quality-of-life improvements, in no particular order, are:
– You can now choose to start with the first planet already under your control, and thus skip that first battle that tended to be the same.
– Turrets and similar structures that you build now leave remains that you can rebuild, similar to AIWC. Not having to manually re-place turrets after every significant defense is very nice.
– Tech costs and various other numbers are now rounded to not be weird values like 1199 (instead 1200, in that case).
– BadgerBadger’s “Find Planet” function has been integrated. Thanks Badger!
– BadgetBadger’s improved campaign-based save/load system has been integrated. Thanks Badger! (I keep finding myself saying that) The structure of the campaign data is likely to change to something more robust before 1.0, but this is a definite step in the right direction.
Up next is more of the same troubleshooting: finding the trouble that gets in the way of the game being fun, and shooting it. For now I’m focusing on my own testing as it’s a tighter feedback loop in many ways, but that will be broadening out.
Still not time for “beta” status, or Early Access, just yet. If you’re waiting for the smooth gameplay experience, there’s still a bit to go — but that’s now squarely the next thing on Keith’s plate (and the GUI is a big part of that, yes).
There are two dire guardians in this one (which are two of the most nasty ones), and then there are four big honkin’ Zenith golems. This includes the Dyson Sphere, the Zenith Trader… and yeah, the Devourer. 🙂 Ho-lee smokes.
Bear in mind that these are the last of the ships until things are playing really well and the interface and whatnot have matured substantially. Sometime during the Early Access period when things are running well, Keith will work on those interplanetary weapons (a stretch goal), the spire stuff (another stretch goal), the Nemesis (yep: stretch goal), and whatever other minor stuff might be left that I’ve overlooked. I think basically everything else is in the game now, though.
Anyhow, so this is a very big milestone for us, because that means that Keith’s focus can stop being on content, and can shift instead to refinement, usability, and all that sort of thing.
I’m finally done with all my performance-chasing stuff as of a little while ago, and as of last release the sound system is in place (though not with all sound effects yet, of course), so cumulatively this makes for quite a satisfactory 0.500, I think.
Post-Processing Visual Stack AGAIN!?
I just finished redoing that, right!? Well, it’s been redone yet again thanks to some issues that are detailed in the release notes. The overall look is pretty similar to what it was before, except things are a little crisper and better antialiased, and there’s a very slight vignette effect.
The big difference is in the bloom effect, which is generally more subtle now, but also more diffuse and thus a bit more dramatic in how it blends things around. Previously things were super intense in their bloom in a short range, but now they’re intense in their immediate area, then fade out more gradually. Gives a more natural look.
Additionally, in order to deal with the flickering glimmering lights that could happen in some cases previously, the game now uses a much longer (about 3/4 of one second) temporal filter on the bloom, which can cause some really pleasing light trails that are purely a screen-space (and thus “free” in terms of performance) effect.
You can see that with:
The first shot in this post, which has the camera stationary and then the Ark moving away from it, leaving a bit of a ghosting trail from its engines. That’s completely a screens-space effect.
The second shot in this post, which has the camera panning super fast to the right while the ships are stationary, and so you can see the glows being pulled to the left. This looks less good, but is also a lot less common of a case and generally happens so fast you can’t see it unless you screenshot it while you’re in motion. It does give a bit better sense of your own speed of movement, though, I’d say.
The third shot in this post (below) shows a stationary camera and both ships and shots that are moving, and how the glow trails help a bit with those. This is more subtle since the shots themselves are trail renderers in a lot of the cases there. It’s noticeable in a still shot, but during gameplay I wasn’t sure it was actually even happening.
If the temporal effect feels too strong to some folks, then I can easily make that a slider that folks can adjust in the settings, and we can debate what the best default setting would be if this is not it. For the moment — and I’m too close to this at the moment to speak with any real confidence on the matter — I like how this is looking, though.
Over the next half-week or so, Keith and I are going to be pretty quiet/absent, because of some other-life things that we need to take care of, respectively. But then after that he’ll be working on the user experience and GUI and so forth, and I’m sure a bunch of mantis reports. I’ll be working on mantis reports and more sound effects work, and getting the first voice acting in place, etc.
New version! Release notes here. They are long, and in parts technical if you’re interested in the innards of our new sound mixing system.
If you’d like a quicker look at the results of the sound mixing system, as well as a brief video-based overview of it, then here you go:
I had, naturally, hoped to get ALL of the shot graphics into the game today, and have their sounds linked up to them, and get the existing voice work integrated into the game… and of course that didn’t happen. I was super tempted to delay the release because I didn’t have every last thing in it, but already there’s so much goodness in here that there was no point in waiting.
One of my favorite things was actually coded by community-member and top-bughunter BadgerBadger: the ability to name your savegames. We hadn’t had time to get to it yet, so he said “heck, I’ll do it myself.” 🙂 That was a side benefit to open sourcing those parts of our code that I hadn’t really anticipated!
Just some visuals for ships, not all of which are in the game. The ships that are in the game and the ships that have visuals are two different sets for a variety of reasons, although there’s 80%+ overlap I’d say.
First up, there’s a new video where I do a bit of show and tell relating mostly to performance and some of the visual things:
Regarding the sprite compound-batching thing, I wrote about that in the last release post, and now you can see it here actually in action.
There are 14 new ship types in this version, including the first of the golems. There’s only one more batch before we have the original “target ship list for Early Access” done. That isn’t all of the ships for 1.0, just to warn you — the spire ships, the interplanetary cannons, and the Nemesis stuff is all for during the early access period, not prior to it.
There may be a few other odds and ends for after EA starts, I’m not sure. But basically the list of ships for implementation during-EA are ones that came from stretch goals on the kickstarter, plus a few that will require particular refinement for whatever reason.
What’s Up With The Wiki??
Well… okay, so we’ve had a bit of a saga going on since late last week. Basically we had some admin human error on our end — it happens to the best of us — and we managed to corrupt our forum database. That should have been no problem, because we have 10 days of rolling backups with hostwinds, our web host. We’ve been using them for a few years, and have been happier with them than we had been with rackspace, hostgator, A2, and whoever else we hosted with in that time. Gets hard to keep track over 8 years, sheesh.
Anyway, the short version of the story is that Quinn has been on the phone and on chat and email with them constantly, and they’ve had a really hard time actually restoring things properly. It’s been quite unpleasant, and a real surprise after our previous excellent support interations with them. We’ve had to do restores before with other web hosts, and possibly even with hostwinds, but this time things just haven’t been great. It’s been a comedy of errors and other issues all around.
Anyway, the wiki is down as a casualty of that, at the moment. So far as I know there was no data loss with the wiki, but I certainly wouldn’t swear to it.
Hey… The Forums??
Yeah, as part of the forums backup restore, we lost about seven days of data from there. We definitely did not lose any data from mantis or the wordpress sites. And obviously anything on Steam or kickstarter or backerkit is all unaffected.
Our code and game hosting stuff is on Amazon, repositoryhosting.com, and elsewhere. Our code, for instance, is backed up by our hosting provider for that (repositoryhosting.com), as well as being on at least 3 computers and also backed up by another service on at least my machine.
TLDR: We’re super-duper-extra careful with the data that really truly matters — anything to do with customer data, code, tools, or whatnot. We thought we were being careful with the website stuff as well, but we were relying on a single point of potential failure (one service and their own backups) rather than having a second tier of backups or a secondary service for the backups.
That was… clearly a mistake, we now see. In the past we’ve used a secondary service to back up our website, but now we’re clearly going to need to be in the market for a service like that again. If anyone knows of one they trust, please drop us a line. :/
Anyway: The Game
We’ll get the wiki updated with the new stuff when the database issues get sorted out there, but the good news is that since Quinn has been handling all of this (hugely frustrating) stuff, Keith and I have not been interrupted in our coding at all. I like keeping our productivity tools spread around a bit partly because there’s then not one single point of failure, to be honest. It’s come in handy at least once in most years we’ve been in business. 😉