Spring RTS Engine

Messing around with chili in BAR on a map I'm working on, with a snow/rain widget that actually works well - or at all - on both my A6 and A8 AMD APUs; all in one screen for no particular reason.

It still has some stuff im personally not happy in a "clean" gui (it hate those smallish icons that hide important stuff...) but its better. Way better. Now if we could have text on every Icon

Funkencool wrote:Messing around with chili in BAR on a map I'm working on, with a snow/rain widget that actually works well - or at all - on both my A6 and A8 AMD APUs; all in one screen for no particular reason.

So you fix the bug introduced where the rain/snow particles move with the camera instead of staying where they are?

If you're going to be making this for BA:R I'd suggest cutting the categories down. Zero-K seperates the categories the way it does because everything can build everything and these are the exact number of categories we need to fit everything in one panel: If you're only taking up half the page you can double the number of things per category. You might be able to combine Special/Factories (the Rarely Built Stuff) and Defense/Eco (often built stuff), so down to only two tabs.

Sweet stuff funken, I like the layout.

PicassoCT wrote:It still has some stuff im personally not happy in a "clean" gui (it hate those smallish icons that hide important stuff...) but its better. Way better. Now if we could have text on every Icon

and for now, I'm plenty happy with better

smoth wrote:

Funkencool wrote:Messing around with chili in BAR on a map I'm working on, with a snow/rain widget that actually works well - or at all - on both my A6 and A8 AMD APUs; all in one screen for no particular reason.

So you fix the bug introduced where the rain/snow particles move with the camera instead of staying where they are?

I'm using a different widget than the one in the blueprint, which never worked for me. I figured out it was because it wouldn't render any images with transparency (and square boxes don't make for very appealing snow). So I found a different one and got it working, but yes the particles move independently from the camera.

Saktoth wrote:If you're going to be making this for BA:R I'd suggest cutting the categories down. Zero-K seperates the categories the way it does because everything can build everything and these are the exact number of categories we need to fit everything in one panel: If you're only taking up half the page you can double the number of things per category. You might be able to combine Special/Factories (the Rarely Built Stuff) and Defense/Eco (often built stuff), so down to only two tabs.

I had the same thought but I'm having trouble coming up with labels for the groups.
Here's a screen of some progress on both my map and the UI


I just grouped all tactical structures (factories, defense, radar, sonar) under one roof with econ seperate. Although I've more or less just been working on getting the unit names into the config and haven't put a lot of thought into the grouping.
I think econ and def together might be too much, especially when you get to tech 2 and especially if you have both a tech 2 and tech 1 constructor selected.
Maybe "enter label here" {factories, defense} and "enter other label here" {specialty, econ} would work out better

I don't know if I said this before or if your are unable or haven't got to it yet but it bears reiterating. Ditch transparency.

why? I think the makes the ui less invasive

obviously each one has its own ideals of "perfect GUI", for the transparency maybe a configurable one would be a... intermediate solution

I personally like it, especially since you can select units behind it.
but yes to VVV

Cubex wrote:obviously each one has its own ideals of "perfect GUI", for the transparency maybe a configurable one would be a... intermediate solution

The transparency comes from my skin, which can be easily changed to an opaque one.

it isn't hard to give people skin options with chili. personally my gripe is how the tabs are on the left of the build menu creating empty space beneath them

smoth wrote:it isn't hard to give people skin options with chili. personally my gripe is how the tabs are on the left of the build menu creating empty space beneath them

Well originally they didn't leave empty space; but now they do, so I've been thinking of throwing them on the right side.

if you think of it, you could have 3 sections

[minimap]
[squarebuttons]
[commandicons]

and it would be a nice rectangle

can chili gif?

imagine the possiblities... animated porn in dithered 16 colors in a video game like its 1993!!!!!

im hard as a pixels contrast to its neighbour right now

I've been doing a unit model all in blender, all in lua. This works by being imported via assimp from .blend directly, no intermediate formats, no config lua, no nothing. All hierarchy and piece positions are in blender, etc

Also i kinda intend this to replace ZK's current buoy model, which, for shame, is just another Core Can.

(also yes, it's a mutant jellyfish octopus photon cannon pacman ghost robot with opening top and six tentacles and a DDM on top, that propels itself in water by spinning with tentacles as fins. AWSUM, right?)

The fun part: remember that "don't turn piece across multiple axes at once" caveat? I kinda had to do that in order to translate between each leg's local rotation axes and the global ones, because the way i've been doing this, all pieces start aligned to global axes. Maybe i should <apply scale, but not rotation> in blender >.>

looking good, couldnt see the tentacles.

couldnt see the tentacles.

Obviously, the feet! But i guess i'll have to make them longer and more slimy if i get tempted to make more amph models for zk.

Top notch work, Anarchid!
I see you are using the gritty industrial atlas! YAY FOR ATLASSING!