AI War 2 v0.508 Released! "The Adornment Of The Buttons"

[keith.lamothe]

Release notes here!

More work on the build menu, which we are trying to nail down to a 1.0-ready state. Some significant improvements to the tech menu as well. Here's an example of the current state of the build menu:



And the tech menu:



Enjoy :)

Keith

[BadgerBadger]

Can we make those build numbers larger? They're actually pretty hard to read on some screens.

[keith.lamothe]

Can we make those build numbers larger? They're actually pretty hard to read on some screens.

Yea, they just run into the icons then, which didn't work with white text and white bomber icons. But I'll look into making them contrast.

[BadgerBadger]

What if we reduced the size of the icons for the fighter/bomber/missile corvette a bit? They seem a bit large right now anyway. The bonus ships don't have this issue because those icons are smaller for the flairs anyway.

[keith.lamothe]

What if we reduced the size of the icons for the fighter/bomber/missile corvette a bit? They seem a bit large right now anyway. The bonus ships don't have this issue because those icons are smaller for the flairs anyway.

Ah, I see, always use the smaller version that goes with flairs. I'll give it a try.

[BadgerBadger]

Sure, try that. For me when I look very carefully at the buttons for the fighter/bomber/missile corvette, the icons actually stick past the edge of the buttons. I'd be happy with "halfway between their current size and the size of the bonus ships", or just the size of the bonus ships. Then you can use that extra space for the build numbers.

Other comments: It would be nice to have a build progress bar. Maybe not critical for fleetships, but for larger starships (and eventually the Spire) we're gonna want it. Proposal; make the build queue items a bit taller, then have another thing just over the Looping/Running buttons to show build progress. (Could be a percentage number, could be filling that bar from left to right with color).

While I'm critiqueing things, the for the  Fuel Synthesizer/Aux reactor etc, the flairs are weird. Fuel is blue there but a kinda a light pinkish in the resource bar. The "power" icon looks really fuzzy and sometimes the lightning bolt is going to the left and sometimes the right. And metal is purple instead of pink.

Also it would be nice to have the mark levels in the sidebar made larger. Also, is there any rhyme or reason to the ordering of ships in the sidebar? In one of my modded games the icons golike this.
First row:      Laser Gatling Mk 1, Autocannon Mk 1, Laser Gatling Mk 2, Laser Gatling Mk 3, Spider Mk 1, Autocannon Mk 2, Fighter Mk 1

[BadgerBadger]

Could I also entice you to include mantis 0019219?

[BadgerBadger]

There isn't a .509 release post yet, but I've found .509 to be 100% broken. I immediately hit crashes whenever I try to open any build menus on linux. See mantis 0019222. I would advise against installing it if you haven't done so already.

[keith.lamothe]

Sorry about the problems with the build. I confirmed them last night (game works fine in my svn working copy, and dies horribly in my steam copy) and let Chris know. Looks like something didn't rebuild properly on the Unity side.

[keith.lamothe]

Chris put a hotfix out earlier today; my steam build works again. Does yours?

[BadgerBadger]

The immediate crash has been fixed. I managed to tag 0019223 after just a few minutes though. (Edit): this crash is caused by holding CTL and hovering over a wormhole. So another nasty bug.

Also I can no longer compile the external code

   src/UIs/CustomControls/ShipLabelButton.cs(19,41): error CS7036: There is no argument given that corresponds to the required formal parameter 'Parent' of 'ArcenUI_Image.SubImageGroup.SubImageGroup(ArcenUI_Element)'
   src/UIs/CustomControls/ShipLabelButton.cs(20,41): error CS1501: No overload for method 'Init' takes 2 arguments

I haven't touched any of that code in my sandbox.

[BadgerBadger]

Any chance of getting those issues (the wormhole crash and the inability to compile the external code)  fixed for the weekend?

[keith.lamothe]

Any chance of getting those issues (the wormhole crash and the inability to compile the external code)  fixed for the weekend?

Chris fixed the external code thing just now and did a release, along with updating the unity version because of a recently discovered security vulnerability. So my development environment is down for a few hours while I update the editor and reimport all the projects. If I can get the wormhole thing after that in time for another release today I'll do so.

[BadgerBadger]

Sounds good.

Incidentally, I played a quick Maze the other day on .510 and wanted to share my experience. I took the 5 planets nearest to me so I could get enough fuel to build a good fleet, which put me at about 110 AIP. Once I had those planets though the next planets on either side of my chunk of the Maze were Mark IV. I sent in a multi-flagship fleet with my ark that used all my fuel (so lots of starships and fleetships with tech upgrades) and got annihilated. Not even close. Also in this game I was unable to capture an ARS and a Golem on one of my planets (see Mantis 19209 for some save games to reproduce the issue).

Also planetary cloakers are really hard to deal with. I felt like I needed o send in my ark and let the AI ships shoot at my fleet until I eventually wore down their cloaks. Maybe I was just doing it wrong?

Aside from the mentioned mantis bug and the fact that I couldn't beat a Mark IV planet to save my life, the game was actually feeling pretty solid. That's awesome!

[BadgerBadger]

Hey Keith, as a heads up, my crash is in Window_InGameEntityTooltyiPanel.cs, in UpdateContent when we run
                    markLevel = typeData.Balance_MarkLevel.Ordinal;

a wormhole has no Balance_MarkLevel so we're dereferencing a null.

For anyone else who wants to mess with things pre-5.12, replace the mentioned line with the following to stop the crashing. The result does not look pretty but it fails to crash:

Code: [Select]

                  int markLevel;
                  if(typeData.Balance_MarkLevel == null)
                      markLevel = 0;
                  else
                    markLevel = typeData.Balance_MarkLevel.Ordinal;