@basil_
Protip: use GL_R11F_G11F_B10F as texture format for bloom. The precision is almost the same, you just lose the sign bit and a small amount of precision while halving the bandwidth cost and memory usage. GL_RGB16F is padded to GL_RGBA16F, i.e. 64 bits while GL_R11F_G11F_B10F is 32 bits.

EDIT: I see no horizontal streak in the video you posted. I'm also not entirely sure how the "ring" works from the video...

interesting.

as you suggested, using seems to be a good idea. saves about 0.5 - 1.0 ms frametime on a texture heavy scene (NV GTX 970).

tho' the banding is too noticeable. even worse than 8 bit . here's a example boosted by 200% :

8 bit


16 bit packed


16 bit


32 bit


*edit* but it's good enough for the bloom mask and flare output. thanks D

Some work on constraints:
(Ignore shadow issues, for now)

So for the last couple of weeks I've been working on a project based around the idea of "Impossible Spaces". I've made a video showing off the first type of impossible space here:

<a href="http://www.youtube.com/v/ciLv2gGRb10?version=3&amp;hl=en_US&amp;start=" target="_blank">http://www.youtube.com/v/ciLv2gGRb10?version=3&amp;hl=en_US&amp;start=</a>

Due to my poor texture choice, its kinda hard to see in the video, however the idea is that the wall you see when you look through the pillars at the beginning is the same wall as the one you see when you're not looking through the pillars, so when you're looking through the pillars, the space between the camera and the wall is lesser than it otherwise would be.

EDIT: I also turned 18 today.

EDIT2: Riven baked me a birthday cake.

Longarmx, I achieved this specific effect through the use of 'portals'.
Consider the following the screenshot:



From above, it has the following layout:



Where represents a wall, represents the blue cube, is the camera and represents a portal.

So even though there is only one blue cube on the map, it would appear as though there are two. The interesting  thing is here is that I could walk between the two pillars, go through the portal and despite only walking a straight line, I'd have rotated 90°.

EDIT: LiquidNitrogen suggested a version with moving cubes.

Thus, here is the gfy

The Internet in a nutshell:

* Disbelieving Sonic

No.Over 90% of the text in your attempted post consisted of quotes.
Please either remove (nested) quotes or write something interesting.

I started adding Hunters and Beggars to Vangard.

I finished the save-game functionality to the "good enough" level - I can save a record of the game in readable form at any point in the game so I can debug more easily but I have made no attempt to load the game from the file - that would just be a waste of time at this early stage.

Save files are not compressed yet and are 75MB big! With compression they go down to a nicer 5.8MB.

This is the third project in a row to lose inspiration in. I keep doing this because I have no real goal to achieve. I wish I could find a better project to have fun on.

All I got done was some backend collision and rendering. I also decided to (finally) animate a robot I used as my main player sprite ever since I started with LibGDX just over a year ago.

gif

Managed to get openJDK to build on windows 10 and removed array bounds checks from generating to see what'll happen.
There's a lot of LUT math going on server side and if I can end up with a annotation to skip bounds checks on specific arrays that can't otherwise be eliminated then I'll be pretty happy.

Got my random room generator finished. Paths all connect to eachother. It can be expanded infinitely in all directions with no errors.

The dimensions of the rectangles are determined by taking a chunk of the world, and splitting it up with a binary space partition with randomized widths and heights.

I am using 5 different factors of width/height size. I pick a minimum size, then force the splitting of rectangles in the BSP to make child rectangles using those factors.

Then I path the rectangles, add them into a world, and put the walls in. The walls are so complex, took me 2 days just to set up the walls or something.

Anyway, that's about it

here's some code:


Whole method: http://pastebin.com/AwuUcYuW

Ignorance is bliss

Today I managed to finally get the actual finished world atlas data for my extraordinarily long-in-the-development game Battledroid onto the screen, in 3D, for the first time.

The world atlas is a fiddly thing to create, and is based on actual real data. I've got a water/land projection that shows what's water and what's not; a basic terrain projection, that I hand painted in GIMP with reference to a colourful and cloud-free globe and with a bit of knowledge about latitude and a little bit of creative license (so it's like, arctic, tundra, scrubland, temperate, forest, jungle, swamp, arid, or full desert); a map of the current (2013 anyway) population density of the whole globe; and a map of the average slope gradients for the whole globe less Antarctica for which I seem to be unable to get data. The gradient data is then applied to the terrain data to determine where the terrain is mountainous and impassable. The population data is combined with a generated cellular texture to produce a pattern of urbanisation.

The normals and water map are turned into cubemaps for a geodesic sphere renderer coded by @theagentd. The combined map turned into a cubemap and from there is munged into a rectangular image that happens to match the geodesic sphere's memory layout. The globe has approx 1 million hexes (and 20 pentagons ), of which about 2/3rds are water, and most of the rest is conquerable territory. So players will have about 300,000 territories to fight over.

Here are the source textures:







Here's a view of the world, showing a heatmap of the value of resources at each hex:



And zoomed in a bit:



Just got to get it into the game UI now and make all the different data views (resource map, attack heat map, ownership map, etc)

Cas

There should only be 12 pentagons. 2 at the poles and 5 around each tropical line. =P