There haven't been a lot of RTS's released in recent years. But there have been some.

In this thread, let's talk about what you think they did right and what they did wrong and what Ashes can learn from them.

 Examples:

Game #1: Planetary Annihilation

Game #2: Grey Goo

Game #3: Acts of Aggression

Please discuss below.

Thanks!

Screenshots are hard.   What looks good in motion doesn’t necessarily look good standing still.

So what is the hype about Ashes of the Singularity about? These are just giant land ships right?

What the big deal isn’t the detail you can have on a single unit.  Homeworld was doing that years ago.  What DirectX 12 makes really practical is that you can have thousands of these units in this detail.

Let’s take a look at these two screenshots:

This is the Hyperion zoomed in.  I could zoom in further but you will get pixilation at some point since DirectX 12 doesn’t make texture size disappear.

The point of this screenshot (click on the thumbnail to see a bigger version) is to look at how the light is affecting the unit and its parts. This unit has a series of guns, each with its own firing solution, it has its own personal line of sight. But let’s focus on the lighting of it.  This image hasn’t been photoshopped. It’s just a print screen.  You get the detail without the noise and you can have thousands of these.

Now, let’s zoom out:

You’ll want to click on this to see more what I mean. But notice how clean the unit remains zoomed out. It’s not noisy. It’s still crisp, distinct.   There’s no such thing as full-screen antialiasing in this game because it’s not doing deferred rendering. It’s rendered much the same way a movie CGI scene would be. 

Not to be confused with the art style or art quality

Now, someone might say they don’t think these shots look good.  That’s an artistic call.  The rendering system won’t save a game from bad art or just bad taste.  It has nothing to do with realism. What it does mean is that your objects are rendered like physical objects and not like scenes in a video game.

Ashes of the Singularity’s Alpha will be going onto Steam early access next week for those who are really really brave and have high end hardware.

Screenshot from the map editor. I expect within a year we’ll have randomized map generation.

Early Access is near

We are getting close to making Ashes available on early access. 

Personally, I’d have preferred to wait until January for doing that but there is a very small number of Steam keys we can use for our Founder’s Program and we’re are basically out.  If you want to join the Founder’s Program, time is just about out.  You can do that here: https://www.ashesofthesingularity.com/store?utm_source=website&utm_medium=home&utm_content=BECOMEAFOUNDER&utm_campaign=Ashes%2BFounders%2BBenchmark

We will be handing out additional Steam keys to the Founders shortly. It’s just a question of when we can get more Steam keys to give out.  Expect them before the end of the month.

Yes, we need your help. BIG TIME.

It’s a shame that marketing types throw around “revolutionary” so often. I’ve gotten pretty cynical when I hear that phrase.  But Ashes is pretty revolutionary and as a practical matter, it can’t succeed without the help of technically sophisticated early adopters.  So let’s take a look at what we’re doing:

• This is the first native 64-bit RTS.   Ashes requires a few gigabytes of memory to run.   And this has a lot of interesting implications.  When I was young, we worried about algorithms (we called it the big O).  But you know what slows games down now? Memory allocations.  The CPUs are now so fast that the performance bottleneck is the relatively slow speed of memory.    How bad? We got a 10% boost by making sure our memory SIMMS (or whatever they’re called now) are not in contiguous banks on the motherboard. (i.e. if you have 4 memory slots and 2 SIMMS, don’t put them next to each other).   So we’ll need a lot of help on the ramifications of 64-bit RTS gaming.
  
  tl;dr: There are unknown ramifications of dealing with so much memory in real-time.
  
• DirectX 12.  This is the first native DirectX 12 game.  What does native mean? It means that the engine makes asynchronous calls to the GPU. That’s my definition anyway.  There will be lots of “DirectX 12” games in the future where they use some minor feature of it.  As a gamer, if I’m not getting a big perf boost from DirectX 12 then it’s not really a native DirectX 12 game.  But DirectX 12 is brand new and the drivers are still very rough.   To be clear: DirectX 11 is just fine on this game, particularly if you have NVIDIA (AMD is absolutely amazing on DirectX 12, I think their Mantle work has really paid off).
  
  tl;dr: This is the first DirectX 12 game. The drivers are new. We need technically sophisticated players to work with us and, NVIDIA, AMD, Microsoft and Intel to optimize this stuff.

The AMD Nano is the most awesomeness video card ever. It’s as fast as a Fury, faster than the NVIDIA 980. Look how small it is! Mark my words: This size is the future of video cards. In a year, they’ll all be this size using HBM type memory.

• Epic, World-Wide Battle Scale.  Those of you in the Founder’s Alpha have got a glimpse of this.  On a small map, you really can finish the game in like half an hour.  But the really big maps? The map in the screenshot above is only medium sized.  For 1.0, we’ll support up to “large” but we have “huge” and “epic” planned for the future.  But when we say we want to have thousands of units, we mean it.  And we mean thousands of units, on screen, each with its own series of guns with their own firing solutions all running on your 5K monitor at 60FPS with the fidelity you’d see in a movie.  That’s a big promise to make.  We want you to feel like you’re righting a world-wide war.  But consider the bugs: (1) Pathfinding (2) units getting stuck (3) When should a unit attack another unit versus hold its ground? (4) What level of micromanagement is fun?
  
  tl;dr: We need your help to identify bad pathing and dumb unit behaviors.
  
• First Multi-Core RTS AI.  I am writing this from the Stardock East building in Towson Maryland.  Possibly never again will a game come together with the concentration of veteran strategy game talent in the same building.   The architect of the new AI is Brian Wade who was the lead developer of Civilization V.  But also here in the building to share AI strategies and architecture help include me (Galactic Civilizations I/II), Soren Johnson  (Civilization IV), Jon Shafer (Civilization V), Andrew Zoboki (Grey Goo), Tim Kipp (Systems lead of Civilization V), Dan Baker (led the HLSL work on DirectX 10 at Microsoft, graphics lead of Civilization V).   That’s just a few of the people you’ll find in this 6,500 square foot space.  
  
  The result is that we have a lot of experience in writing computer AI and have longed for the day of being able to have an AI in an RTS that can seamlessly send out jobs to multiple cores (I’ve done that in 4X turn based games mind you but doing it in real time is a very different beast).   You know how this game is still in alpha right? As the Founders have discovered, the AI is already quite lethal. It also doesn’t cheat (at higher levels it gets handicaps but it is actually playing the same game you are).  
  
  tl;dr: We will need you guys to help us on STRATEGIES.  We may have the most experienced AI development team in the industry but we’re not necessarily going to actually good at the game compared to you guys.
  
• Multiplayer. Multiplayer. Multiplayer. We’ll have custom games and ranked games, etc.  But this will be a challenge in a game that will probably have a small MP player base during early access.  So we’ll need you guys to help us set up dates and times to play multiplayer, find bugs, add new options, etc.

Missing Game Mechanics

We are painfully aware that not all the game mechanics and features will be available for early access. This is another reason we would have preferred to wait until January.  The Steam early access page will contain a plea for people NOT to join early access so that only those who really know what they’re getting into are part of it. 

Here are some basic stuff the early access game is missing:

1. Orbitals.  In Starcraft, various units have special abilities that the player is expected to be pretty decent at microing.  That’s fine in a game with limited units.  In Ashes, units do have special abilities but the player isn’t expected to handle them.  Instead, the player has GLOBAL ABILITIES.  You build a particular building and you get access to a cool ability that costs radioactives (one of the resources) to use.  You want to put up a force field on a particular army? You don’t have to hunt for the right unit, instead you, the player, have that ability.   This won’t be in the first early access build. This would be like Starcraft having a beta without special abilities on its units. 
2. The Substrate.  The other race won’t be in the game until next year.   We have the assets (as some of you noticed) but there’s no point putting them in the game until we have a good balance of the PHC (humans).
3. Veterancy.  Not sure if that’s a real word. Anyway, your T3s will get experience and gain levels which allows you to give them new passive abilities and make them generally better. We want you to care about the T3s as these dreadnoughts are the heart of your military.
4. Other Worlds. We will only have Terran and Barren worlds in for early access. We will be adding Ice worlds later but they’re not ready yet.
5. Stability. I’m not going to kid you. It’s buggy. Very buggy. I have yet to get through a game without it crashing.  Autosave works pretty well so I just load it up and continue from there. But it’ll be a good month before it’s relatively stable IMO.

How you can help?

1. If you can record your games and upload them to YouTube as UNLISTED and point us to them, we’ll check them out.  These can be bugs or suggestions or game ideas too.  Generally, we’d prefer reports be in text, on the forum, but if you feel something can only be shown then go ahead.
2. Mockups of what you’d like.  We’re serious about having you guys as part of the team. This is a game we’re truly looking to make together with you.  So don’t just say “I don’t like X” or “I want Y”.  Show it if you can. Even if it’s primitive.  For example, someone says “I want Strategic Zoom like Supreme Commander”.  That’s not going to happen. Not because we don’t love SupCom.  But because such a system won’t work on a game of the scale we’re going for (quantity of units and eventual size of the map). We have to come up with other ways to abstractly show an entire world at war. We want to hear your ideas. We have our own of course but we are excited to listen to other points of view.
3. BUGS BUGS BUGS.   When the game crashes, we get a crash dump sent automatically.  So you don’t have to worry about that.  But compatibility is a different beast.   Tell us your specs. Run dxdiag and post the text to the forum.  Alternatively, get JING (www.jingproject.com) to take screenshots of stuff and share it.

A note about the future

For those of you not familiar with Stardock, let me give you a little background.  We’re privately held. In fact, we might be the longest running independent game studio in the industry of decent size (>100 employees, 23 years).  I founded it while in college long long ago. I still own it today.  I still write code.  All my old colleagues of my generation sold their studios, typically to the generation before me whose companies have long since gone public. 

The reason the above is important is because we’re in this for the long-haul.  That’s why this game is so cutting edge – because we want to keep expanding on it for many years into the future.  It’s why so many wonderful and talented people have joined us these past few years.

We’re free to make the games we want. The games YOU want. That’s what we want to do here.   When you give us feedback and talk to us, you’re talking to US. Directly.  There’s no one in between.  Mind you, I can be a rude, cranky jerk sometimes but if you make a good point, I’ll do my best to make sure we do something about it.

I hope you guys are as excited as we are.  Things are about to start getting very interesting…

WHERE TO POST: https://forums.ashesofthesingularity.com/forum/1140

We’ve been working like crazy to improve stability while at the same time adding in lots of new features and UI improvements.  The next build, 0.55, is due out next week.

If you haven’t joined the Founder’s Program, it is going to be ending in the next couple weeks.  At that point, Founders will start to receive additional keys to give to friends to help build up a proto-multiplayer community.

To join the Founder's program go here: https://www.ashesofthesingularity.com/store

- by Brad Wardell

Galactic Civilizations III is one of the first of the “new generation” of natively 64-bit, DirectX 11 games.  More importantly, it is both critically acclaimed and a best seller meaning that the hardware requirements of this game, while non-trivial, are not so high as to prevent it from being commercially successful.

We got the Steam hardware results on tens of thousands of Galactic Civilizations III players. Let’s take a look.

So what do they have?

Operating System

1. Windows 7 (42%)
2. Windows 8.1 (28%)
3. Windows 10 (25%)
4. Other (trivial)

Number of cores

1. 4 cores (76%)
2. 2 cores (15%)
3. 6 cores (7%)
4. Other (trivial)

CPU vendor

1. Intel (84%)
2. AMD (16%)

GPU vendor

1. Nvidia (68%)
2. AMD (23%)
3. Intel (8%)

System RAM

1. >12 GB (53%)
2. 8 GB (35%)
3. 4 GB (5%)
4. other (trivial)

Video memory

1. 2GB (30%)
2. 4GB (23%)
3. 1GB (21%)
4. other (trivial)

Display Resolution

1. 1920x1080  or 1920 x 1200 (63%)
2. 1600x900 or 1680 x 1050 (9%)
3. 1366x768 (6%)
4. 2560x1440 (6%)
5. other (trivial)

Multi-Monitors

1. 25% of players have multiple monitors

So the AI is getting a massive overhaul for v1.4.  And I have to say, it's making a much bigger difference than we had originally expected.  

To be honest, I was pretty skeptical that it was worthwhile to have engineering time spent on improving the way the AI manages its planets. Not to be a a lazy bum too much but I figured it a lot smarter to just let expert players play against the AI with bonuses.  But as others have pointed out, the compounding nature of planetary improvements makes the bonuses we give too trivial.

Now, the AI is really quite good (better than most humans) at placing improvements in 1.4.  It will never be as good as the best humans (traveling salesman AI problem) but it's close to an order of magnitutde better.

They're also working on improving the way the AI designs ships.  Now this matters in a lot more ways than simply warfare.  In GalCiv II, the AI took into account the ranges of various things to decide how much range techs it needed and how much life support it should have on ships.  This is a non-trivial coding effort but needs to be done in order for the game to more challenging on larger map sizes.

Combined with the 1.31 AI update (the AI should be very noticeably better in 1.31 versus 1.3) I think that by the end of 1.4 the complains about GalCiv III's AI should be largely put to rest for most people.  We shall see. The opt-in for it should be available in a few weeks.

I love my Surface Pro 3.  Windows 10 has transformed it from something I occasionally fiddled with to my primary mobile device (replacing my iPad and MacBook Pro combo for trips).

But it is, by no means, perfect.

The weaknesses of the Surface Pro 3 include:

1. It is almost 1.8 pounds.  That's really too heavy to use as a tablet for an extended period of time.
2. While Windows 10 has greatly improved the issue of it getting hot and the fan blariung, the fact it has a fan means extra weight and noise.
3. No LTE.  I always found that astounding.  I keep my iPhone with me at all times anyway but it's kludgy to have to connect to it from my Surface while traveling.
4. The power connector is obnoxious and expensive. 

So what would my dream Surface 4 be like?

1. Less than 1.4 pounds
2. 13 inch screen
3. No fan
4. LTE integration
5. USB-C based power.

Note I made no mention of the CPU speed.  That's because the Surface Pro 3, with its 3 year old Core I5 in it, is fast enough for all my computing needs.

Does your laptop or tablet run out of battery while it’s supposed to be asleep?

You can find out why thanks to a fairly obscure but relatively new feature in Windows.

Step 1: Open a command prompt in adminstrative mode

Step 2: Go to a temp directory (like cd\temp)

Step 3: Type powercfig /SleepStudy

This will create a file in the current directory.  Open that file in your web browser and you will find out why.

Common causes:

1. Notifications. Even while sleeping, the Windows notification system (WNS) does stuff.  Turn off as many unnecessary notifications as possible.
2. Your type cover can wake the machine inadvertently.
3. Your network card. Make sure you have the latest firmware and network drivers.

Good luck!

Ever wondered what Sins of the Solar Empire might be like on the surface of a planet?

Would you be interested in help shape the world's first 64-bit, DirectX 12 RTS?

Head over to https://www.ashesgame.com and check out what we're doing in Ashes of the Singularity.

Greetings!

Here are some questions on game modes for ya:

1. Do you prefer to play 1 on 1 vs computer?
2. 1 on 1 vs a human
3. 2 humans vs. 2 computer
4. 2 humans vs. 2 humans?
5. Free for all (3 players or more)
6. 3 humans vs. 3 computers
7. 3 humans vs. 3 humans?

Thanks!