next »

[Sik]

I think the game is just being lazy.

[Photon]

I was sent here from my DevLog thread to post this:



As you can see, the player's vehicle transitions smoothly and safely from the game map to the platform on the build screen.

For some reason I find this especially humorous. I suppose its because the game seems to just so nonchalantly drop it in... upside down. 

[Zogthor]

Shared our first version of our alpha with a friend and they made a comment that one of the enemies was doing a ninja pose. Our designer double checked what he was talking about and found this.

[Armageddon]

[Zarkonnen]

Forgot to tell my air marines that they should stop moving when injured. Result: near-dead marines climbing ladders.

[Whiteclaws]

Forgot to tell my air marines that they should stop moving when injured. Result: near-dead marines climbing ladders.

no you dont get it, he's going to a better place

[Zogthor]

Forgot to tell my air marines that they should stop moving when injured. Result: near-dead marines climbing ladders.

He must go, his planet needs him!

[Pol]

Oh, forgot to post this here : experimenting with some procedurally generated highways, when I tried putting two roads at the same time a shared static variable caused them to generate symmetrically in a rorschach-esque fashion.



(pics from the actual, unbugged result)

[Guv]

What happens when you accidentally tell A* to find the longest route not the shortest.

[Sik]

On the upside, at least now you know it has absolutely no problem dealing with extremely complex paths (makes for a good stress test I guess).

[ThemsAllTook]

What happens when you accidentally tell A* to find the longest route not the shortest.

Interesting... I did that once and got a very different result. Instead of covering every space on the map, it just found a path that touched the farthest-away point before reaching the destination. Looks like you might have something more complex going on though (different costs for different types of terrain?).

[Guv]

Looks like you might have something more complex going on though (different costs for different types of terrain?).

Maybe I worded the bug wrong so to be exact, I had built a heap and accidentally ordered it from Biggest Cost to Lowest, essentially forcing the path finder to travel across every node before being forced to expand the goal.

Or maybe it's because I'm pathing on Quad Trees, not just a fixed grid. This is the correct result on a much smaller example, before smoothing:

[kamac]

[ndke]

http://dl.dropboxusercontent.com/s/gxq1lkhrlg1gkdk/glitch.gif

Mipmapping related?

[kamac]

Custom mipmapping in shader (I scale the texture instead of using normal mipmaps because the latter gave me gaps between textures) & triplanar texturing problems.

[Keen]

I have no idea where these blobby shapes are coming from...

[marquet]

It's supose to be a Firetrower

[conghal]

Hair physics:

[failrate]

He seems rather surprised at his current situation.

[Snail_Man]

When attempting to generate a number of stars, and some civilizations to occupy them, I accidentally put the max number of stars to 600 instead of 60.