Index Librorum's Maps, assorted projects, and Gaea tutorials

[IndexLibrorum]

I'm Index Librorum (aka Prohibitorum), and this is a showroom for my maps and other projects.

For most of these maps, the terrain, map-wide assets, and stratum masks are made using Quadspinner's Gaea. For questions related to my workflow, contact me on discord or here on the forums. (though discord will get you a reply significantly faster)

Gaea tutorials

All tutorials may also be found on the FAF wiki.

• Basic introduction to Gaea and how to use the program to create a heightmap for FAF maps
• Producing terrain masks in Gaea
• Texturing in Gaea

All projects:

Project Mesa, Project Situs Impactae, Project Praetensus, (Adaptive) Project Dust, Project Tabula, and Project Luminary, Adaptive project Luminary Maxima, Project Albus, Project Vortex, Project Fluxus, Project Mesa HD, Project Tumulus.

Unless otherwise mentioned, all maps shown here are in the vault.

Latest Project:

This newly discovered garden world would be a great place to start a new farming colony, commander. Secure it for us! // Licensed under CC BY-NC-SA 4.0. This map is AI compatible.

Click here for more information on Project Tumulus.

[IndexLibrorum]

Where once a gigantic river flowed, now only a parched canyon remains. A research facility, studying the geology of the area, accidentally gave away its location after the signal of a crashed dropship rescue beacon was intercepted. The enemy is on his way commander, do not let them get a foothold!

Project Mesa is a 10x10km map fit for two teams of four. Two crevices split the map in two halves connected by a small plateau, on which a small base of hostile AI is built. Because of this base, commanders and units can not easily reinforce the other side of the map in the first few minutes of the game once committed to a lane. This regularly results in a 2 vs 1 matchup in both lanes.

The air players, while spawned on top of a plateau, are able to walk their commanders to the middle as well to add additional firepower. Several mesas can be dropped for mexes, extra hydros, and reclaim, as well as offer good locations for radar, AA, TML, and static arty installations. Due to the close proximity of the commanders throughout the game, naked T3 air rush builds are not advised.

Project Mesa was my first map, and heavily relies on map-wide assets generated in Gaea. At some point in the future, I would like to rework the map to match the quality of later maps such as Project Dust and Project Tabula.

[IndexLibrorum]

A shower of meteors impacted this location, creating deep craters and exposing a layer of mineral that HQ believes is critical for the war effort. Commander, secure those resources!

Project Situs Impactae (Site of impact) is a 20x20km map fit for two teams of four. The playable area is limited to the large crater containing several smaller craters. All craters that are deep enough to expose the yellow 'mineral layer' require transport ships to access. Consequently, the two commanders that are spawned inside the largest crater can not walk out, and require T2 transports to participate on the frontline. However, given how aggressive engineer drops to the various craters will be rewarded by mexes and extra reclaim, this slot does not need to be boring to play.

This map is rather large: although broken up by smaller craters, the map is mostly flat and offers many routes to slip a raiding army past your enemy's defences. Expect to play zoomed out a lot, as there is a lot of ground to cover. Several clusters of reclaim can be found in the middle, and clumps of yellow and black crystals as well as large forests of dead, burned trees will provide enough materials to scale quickly.

As of version 5, this map is compatible with AI.

[IndexLibrorum]

<Reserved for Project Praetensus>

[IndexLibrorum]

Do not breathe in the dust.

Adaptive Project Dust is a 10x10km map supporting two to eight players. A non-adaptive legacy version named Project Dust supports up to four players.

Two main lanes are divided by a significant height difference: the rocky top lane, streaked with accents of a green mineral, overlooks the bottom lane, which is contained within a large sandy canyon. The two lanes are connected by a deep channel shaped by a long-since evaporated river. The top lane is further split in a primary and secondary lane, while the bottom lane has two minor lanes that hold some extra reclaim and a small plateau.

As of June 2023, this map is in the 4v4 TMM map pool.

Special thanks to @Fichom for insisting this was clearly the right idea for a map.

[IndexLibrorum]

Well this is embarrassing. We were supposed to drop on the other side of this plateau... Looks like the enemy is already setting up bases there too. Kindly remove them so we can pretend this mistake never happened.

Project Tabula is a 20x20km map, although the main playing area is closer to 15x15km. Eight commanders may be spawned on top of a large plateau, which has a partial collapse in the middle effectively creating three main lanes. Access to the terrain beyond the plateau is blocked; although planes may use the airspace, units can not be dropped outside the plateau.

This is the first of my maps that uses clouds. Feedback on this feature in particular is highly appreciated.

The map is licensed under CC. BY-NC-SA 4.0 and is compatible with AI.

[IndexLibrorum]

Update: Project Situs Impactae (v6) now supports AI and has some more decals to bring detail to the crater rims.

[DerpFAF]

Tabula is a top tier 4v4 map IMO.

Had some fun games on it so far.

[snoog]

Big fan of Tabula so far. Hosted it a few times and will continue to.

[IndexLibrorum]

@snagglefox Glad you guy's liked Project Tabula.
I certainly consider it my best map to date. A lot of the techniques I learnt and practise I got from my other maps were important to make this map look as good as it does. The people in the FAF-discord's mapping channel deserve a shout out for the help with some of the issues I ran into while making the maps!

[Stellar_Property]

congrats for featured in map sporlight

[IndexLibrorum]

Updated info on Adaptive Project Dust.

As of June 2023, Project Situs Impactae and Project Dust are part of the 4v4 TMM map pool! If you found this thread because you recently played any of these maps and want to share your feedback, leave a comment.

--

@stellar_property said in Index Librorum's Maps and assorted projects:

congrats for featured in map sporlight

Thanks! Is very cool to see it up there!

[IndexLibrorum]

As part of Jip's 'Princess Burke' Mapping tournament, here is me documenting my process of trial and error while designing my entry for the tournament.

The Goal

For this tournament, the requirements are a 10x10km, 6 player, aeon-themed map. All of my previous maps are very focussed on arid environments: lots of sand and dust. When thinking about the Aeon, I felt like a more nature-loving space-techno-elf vibe was a better fit. This makes me think of greens and blues; grass and water. That's a challenge, because I haven't much played with texturing those kind of terrains before. Aeon is also all about symmetry, order, and circles, so some elements should reflect this.

The first design

I also thought something with blue/green crystals might be interesting. Few maps on FAF use large clusters of crystals, and I figured that that might be an interesting approach. I doodled out some ideas on paper, and started creating a quick draft in Gaea. A moon-like crescent shaped island with a 'spine' of large crystals was the thing I settled on.

The technology behind FAF's terrain comes with certain limitations. Because the terrain is shaped by heightmaps, where the greyscale value of each pixel corresponds to that pixel's height in the editor, it is not possible to create overhangs. This means no caves, no overhanging cliffs, and no crystal spikes jutting out from walls or hanging over other terrain. This is quite a shame, because that limits the shape of the crystals I can make. Nonetheless, a first draft was created, and a very preliminary attempt at texturing made. Oceans would be added later, in the FAF editor.

The idea is kind of interesting, but I didn't like the shape of the crystals I managed to create. While these might be improved, I didn't really feel enthusiastic enough about this design to keep working on it. I moved on to a different idea, and this project was tossed on the heap of other half-worked out doodles that has been steadily accumulating over the past months. (Including at least four different attempts at creating a decent looking volcano/lava style map. I really want to create one, but lava is just very difficult to get right.)

The second design

Remaining with the ocean and island theme, the next concept was the result of some random experimenting in Gaea. Gaea has a lot of different nodes, and I've found that the best way to understand how each of those behave is to play around with them. Fiddling with the an interesting combination of Voronoi noise, swirl displacements, and polar displacements got me an interesting island cluster.

I figured an Aeon map themed an 'eye of Rhianne' wouldn't be a bad idea, but I ran into some problems with finetuning the shores: The island had rather steep geometries, and while flattening them isn't difficult, the map started to look boring quickly. At the same time, I saw some cool ideas on the Gaea discord, and decided to take that 'Eye of Rhianne' concept in a different direction.

This concept will likely be finished some point into the future, though, because I still think the layout is kind of cool.

The third design

... will be shared once I've got it fully textured and in the editor, because I like it enough that I want to work it out for the tournament entry. I've taken some inspiration from my previous map Project Tabula, but made it a bit more interesting and fit for an Aeon-style map.

More info to be posted soon.

[IndexLibrorum]

As part of Jip's 'Princess Burke' Mapping tournament, here is me documenting my process of trial and error while designing my entry for the tournament. Continuation from the previous post.

Designing Project Luminary

The third design was inspired in many ways by design two: I wanted the map to somewhat resemble an eye—to stick with the 'Eye of Rhianne' theme—and to be clearly aeon. This meant that the main colours would be shades of green and blue, that circles should feature heavily, and that in general the place should feel somewhat orderly and vibrant.

Version 1

Taking some inspiration from Project Tabula, I designed a round plateau surrounded by water with a raised cutout in the center.

This center was designed with two thoughts in mind: on the one hand the raised round platform evoked the idea of an iris, reinforcing the 'eye' motive, while on the other it split the main plateau into two lanes, forcing players to work around the obstruction. Some more obstructions were added to break up the lanes and make it all a bit more interesting.

The water around the platform would allow another big aspect of the Aeon faction to shine: hover. The T1 hovertanks would be able to raid the enemy backlines by moving over the water, being able to bypass any point defences that might be raised to block the land paths.

Unlike Project Tabula, however, this map is relatively small for a 3v3: 10Km really isn't all that much to work with. The way the map was designed now, three players would fight on a relatively boring platform, with the only difficulty being having to—maybe—work with naval and deal with some flanking aurora's. More small islands were scattered around the rim of the map—some raised, requiring airdrops, others flat, to allow easy raiding—and one of the three spawns moved off of the main island.

The terrain was weathered by erosion to add a lot of details and add some realism, and a first draft for the textures was created. A quick version got slapped together in the editor for playtesting, as I wanted to get the first round of feedback from my clan before doing all the detail work. Consequently, several things I had planned were not yet implemented in this test version: there were almost no decals, there was no tree or rock reclaim, and there certainly weren't any unit wrecks or structures on the map. At this point I already had some ideas for all of these, but it was critical to receive a first round of feedback first, as adding all those elements takes a lot of time.

First Feedback round

I cannot overstate how important it is to check your ideas and drafts with others. Creating something over several days leaves you blind to some—in hindsight—obvious mistakes, and feedback forces you to reevaluate choices that you've made.

Feedback included several important things:

• The middle island is too small
• The middle island is too simple and boring to play on. (Or as @Xayo put it: "wait where's the terrain?)
• Several areas of the map are too bumpy to build on
• A few mexes were unbuildable because of terrain issues
• It was unclear if and where players could enter the water: ramp communication was poor. @BananaSmoothie came up with the great suggestion to include beaches to improve on this.
• There's a lot of water, but no water mexes, which is boring

We spend a good hour talking about how we experienced playing the different slots, brainstormed a bit about possible changes, and then I got back to editing the map.

[IndexLibrorum]

Version 2

The feedback was processed over the next day: the middle island was increased by 15% and reshaped, and beaches were added across the map. The heightmap was then adjusted by hand using the tools in the FAF editor. I normally prefer to do as much as possible within Gaea, as that makes it a bit easier to create the masks later and I positively suck at hand painting masks and terrain. However, Gaea is really not great at small adjustments in particular places, so hand painting was the way to go. Cliffs were clearly distinguished from slopes, and the original boulders were removed and improved boulders added. Lastly, needlessly bumpy terrain was flattened, which took care of the boring and badly communicated terrain.

Water mexes were placed and another spawn was moved off the main island. During playtesting we noticed that walking the commander from the side island to the main island took no time at all, and having three commanders on the island on the first minute meant it rapidly devolved in a close-combat knife fight, which no one enjoyed. Placing one commander on a side island theoretically solved this very well.

After spending way too long on adjusting some of the textures, a new version for playtesting was slapped together. At this point, a large part of the decal work was completed, trees and other props were added, and the centerpiece was created.
The centerpiece with the heavily fortified Aeon research base was designed with a few purposes in mind. First and foremost, the damn thing just looks really cool and clearly marks the map as an Aeon planet. Lore-wise, the map is designed as the location for the secret research location for the 'Eye of Rhianne', and as such one Eye is placed in the middle of the base. Notice also how precisely the trees are placed: more detail to reinforce the order and symmetry aspects of the map.

Secondly, the heavy defenses of the base ensure that no player can quickly claim the middle of the map. With small maps such as these, controlling a center position has a lot of tactical benefits: AA will block a significant and the most direct paths for planes, T2 arty and T2 TML's will reach most of the map, and T2 radars see mostly everything. Meanwhile, it was important that the reclaim (about 3K) would not immediately be dropped. Although the map had plenty of reclaim scattered throughout (about 22K), having a difficult to contest clump of high value reclaim is not general beneficial for gameplay. The defences are purposefully made somewhat overkill: I want the base to barely be worth the effort to clear.

Thirdly, the hostile Aeon base includes two aeon TMD's. Because of the size of the main island, without these TMD's it would be very attractive to rush out T2 TML's and take out the enemy's base. This is still possible with these TMD's, but is made a bit more difficult as missles can now not be shot through the middle of the map.

In style with the Aeon orderliness, a lot of props and decals were very precisely placed. To say that this was tedious work is an overstatement, but at least it looks good. More sexy pictures will be posted in the post discussing the final version.

Second feedback round

The second round for feedback was blessedly much shorter: the changes made to the map were well received and solved many of the previously identified issues.
The way the slots were laid out meant that every slot has a lot to do: both back slots had to go into navy as well as air, and also had to walk their commanders to the middle. Meanwhile, the center player had a bit more time in the beginning where they would be on their own, and would have to focus on aggressively spamming T1.

Small changes were made based on the feedback: the defences for the centerpiece were slightly reduced, a few mexes were adjusted, and a small pathing issue with the terrain resolved. The main point raised was that the islands in the top left/bottom right corner were too difficult to get for the navy player, and were generally too high. These issues were addressed in the final version.

Version 3

The final touches to textures, decals, and terrain were made. The corner island were lowered, the map-wide shadow, normal, and texture decals finalised, and some extra tree-props added. Some subtle waves were added to the water as well. Pretty!

AI markers were placed to support AI players, and a T1 AA was placed on the top left/bottom right islands added in a place that mostly makes it more difficult for the air player to reach the island before the navy player does.

An issue with flickering map-wide decals was found and solved: in maps with large differences in terrain, map-wide decals might sometimes produce weird visual artifacts and flicker. Solving this took some debugging and more time than I am willing to admit. To save anyone else the time and effort: placing the two map-wide assets at the bottom of the decal stack solved this issue. One remaining issue where some decals pop into view, rather than gradually fade into view, remains, but this issue will be fixed by the upcoming FAF update.

With that, the map was finished. Details, pretty pictures, and highlights will be showcased in the next post.

[IndexLibrorum]

Gaea tutorial: Producing terrain masks

The various map projects I've made have all been made possible by Quadspinner's Gaea, a terrain design application for VFX and games. Gaea is an industry standard and a great tool to significantly speed up creating or increasing the complexity of masks, heightmaps, and decals. Because of FAF's peculiarities and the fact that the game is more than a decade old, the process of producing masks using Gaea is a bit involved. Being the shiny beacon of enlightenment that I am, I will here share my workflow for making these masks.

This tutorial assumes you've got a basic understanding of image editing and FAF mapping. Additionally, it is suggested you familiarize yourself with the concept of visual node based programming. A very rudimentary understanding of Gaea is also required: while I will discuss the relevant nodes and how they work, I will leave familiarizing yourself with the software for self study. Watch a few youtube tutorials on the basics, or read the general introduction to Gaea here.

Required for this tutorial is a copy of Gaea (the indie version is free to use and more than sufficient for maps up to 20km), which can be downloaded here. Additionally, an image editor such as Photoshop or Gimp is required, though the free to use online photoshop-clone Photopea works fine too, as is the FAF map editor.

Footnotes marked as '[0]' where needed. Notes are added to the bottom of the tutorial.

When specific nodes are referenced, they are highlighted like this: Node. Specific parameters for these nodes are written like this: Slope, 30, 90, 0, to specify a Slope node with Parameters 30 (min), 90 (Max), and 0 (Falloff).

Terrain, masks, and stratum layers

A quick recap of the basics:
Once the terrain of the map has been created, usually the next step is applying textures. To apply the textures to specific spots, masks are drawn. At most, eight masks can be used per map. Masks are greyscale images, where the intensity of the pixel relates to the opacity of the texture. These masks can be imported and exported to and from the FAF editor.

The mask files usually have nearly the same resolution as the heightmap, with one small caveat: while heightmaps have resolutions of 2^n+1, masks have resolutions of 2n. Consequently, a square 10km map has a heightmap of 513 x 513px, but masks of 512x512px.[1]

Furthermore, masks have several strict requirements:

• Masks are 8-bit RGB, non-interleaved .raw files
• Only greyvalues of 128 to 256 (50% white to 100% white) are used to assign textures. Values below 128 are ignored. (See figure 1)
• Due to a bug in the shader code, the normals of a layer are applied using the greyscale values of 0 to 256. Consequently, you may see the normals of a layer applied in sections where you do not see the albedo of a texture applied.[2]

Figure 1: Showing how greyscale values below 128 (50% white, or grey) are ignored.

The workflow summarized

In short, the workflow to create these masks is as follows:

1. The terrain is created in or loaded into Gaea
2. Several masks are defined using the various relevant nodes
3. The masks are exported as .png8 files
4. The greyscale value of the masks is adjusted
5. The masks are exported as .raw files
6. The masks are imported into the editor

For my map Project Dust, the masks when exported at step 3 (before the greyvalues are adjusted) look like this:

Figure 2: An overview of the exported masks for my map Project Dust. Notice how each masks highlights different features.

After adjusting the greyscale value, the final mask looks like this (example of mask #5):

Figure 3: Grey-scale adjusted copy of mask 5.

Loading the terrain in Gaea

To export terrain from a map made in the editor, open the map in the FAF editor and navigate to the Terrain tab. Under the Heightmap subtab, you will find a button labelled "Export heightmap". This will export the heightmap as a 16-bit RGB, non-interleaved, IBM-PC (34-12) .raw file.

This file can be loaded into Gaea using the File node. Add a File node to your workspace, and load in the exported heightmap. Due to differences in how Gaea and FAF interpret heightmaps, it may be required that you manually rescale the terrain vertically. The easiest way to do this is by using the Raise adjustments, which you can find by selecting the node and clicking the corresponding button at the bottom of the node's side-panel. Increasing the Multiplier value to scales the terrain up vertically. It is my understanding that for the subject of masking this scaling is optional, though I personally have found it easier to work at a scale as similar as possible to the FAF editor.

Figure 4: A file node is added, and the heightmap of Project Dust loaded. The Raise adjustment is selected, but in this instance the multiplier is set to 1.000, so the terrain is not scaled.

Defining masks

As shown above in Figure 2, your aim should be to create distinct layers with specific textures in mind. The masks will allow you to distinguish specific features from the total terrain and to add extra detail to large areas that would otherwise be very homogenous. Using these masks, you can prototype a set of colours and textures within Gaea, and later use the masks for texturing your map. (Setting up this system within Gaea will be the topic of another tutorial).

Figure 5: A mockup of the textures using the generated masks in Gaea

When designing a set of masks, I aim to have at least the following:

• One mask for each of the types of terrain
• A mask to distinguish the cliffs and unpathable terrain
• A mask for dirt, dust, and soil
• A mask for highlights

More masks may be added to add complexity to large sections of one type of terrain.

To create these masks, most commonly the nodes in the Data section are used. These nodes allow you to select certain parts of the heightmap, and include Height, Slope, Soil, Curvature, Flow, and Texture. Where necessary, the outputs of these are blended and combined using the Combine node.

To select all the cliffs on Project Dust, for example, I used the following setup:

Figure 6: Setting up the cliff mask

First, I chained a Slope node to the File node. The Slope node has three main parameters: Min, Max, and Falloff. By adjusting the Min and Max values, you select all terrain that is sloped with an angle in degrees between those two values. The falloff value specifies the feathering of this selection; a falloff value of 0 results in a sharp delineation of the two selected and unselected regions, while the border gets progressively blurred as the value increased.

Figure 7: The effect of increasing the falloff value

Similarly, the Height node allows you to select terrain at certain relative heights.

Figure 8: The bottom 50% of the terrain is selected, and the selection fades out over the next 25%.

These and others may be blended together to make selections of selections, or to add different selections together. If you want, for example, to only highlight all the slopes at the top of the terrain, you could select all the slopes (Slope: 30, 90, 0), selecting the bottom 50% of the terrain (Height, 0, 50, 10, Normalized), and subtracting the Height from the Slopes (Combine, Subtract, 100%).

Alternatively, you may select the top 50% of the terrain (Height, 60, 100, 10, Normalized) and chain this node as a mask into a slope node (Slope, 30, 90, 0).

Figure 9: Two approaches to combining height and slope selection nodes to select only the slopes in the top 50% of the terrain.

The process of combining the various nodes will take some time and effort, and involves a lot of finetuning of values to get the masks exactly as you need them to. To keep all the masks organized, you may choose to rename the nodes corresponding to what terrain they select. For Project Dust, the final node tree to select all masks looked like this:

Figure 10: Overview of the node tree generating the masks for Project Dust

This somewhat complex graph might look a bit daunting at first, but it is important to realise that these structures are built one node at the time, logically following from and combining with the previous nodes.

For the curious reader: the little tags on some of the nodes are called portals, and allow for connection between nodes that do not share the same worksheet. For an introduction on portals, check the Gaea documentation.

Exporting masks

To export the masks, select the relevant nodes and press F3, or right click and select Mark for export. The marked nodes will now show up under the Build tab in the top right. Adjust the relevant settings:

• Change the filetype of all masks to .png8
• Method should be left on Normal Build
• Resolution should be set to the size corresponding to your map's heightmap. (See note about resolution above)
• Colorspace should be left on sRGB
• Range should be left on Raw, although alternatively this may be set to Remapped, 0.5, 1 to skip the step of adjusting the greyscale values of masks.[3]
• Baked Cache may be left on Use

After selecting where Gaea should dump the generated files, you can render the files by pressing Start Build.

Adjusting masks

Two steps remain before the masks can be imported to the FAF editor. First, if the masks were exported with the Range setting left on Raw, the greyscale values have to be adjusted so that only values of 128 and up are used. Masks that were exported using the Remapped setting may skip this step.

Adjusting the greyscale values is as simple as adjusting the levels using your preferred image editing software.

Figure 11: Adjusting the mask using the levels adjustment layer in photoshop

Similarly, encoding these files as .raw can be done in Photoshop or alternative image editing software. A great free and online alternative is Photopea, for those who do not own Photoshop.

To save the masks as .raw filetype, make sure of the following:

• The files are 8-bit RGB (should be fine as long as you export as .png8 in Gaea)
• The file is saved as .raw., 8-bit , 1-channel, non-interleaved, at IBM PC or 34-12 byte order.
• Double check that the resolution of your mask is correct

Importing masks

Your masks are now ready to import into the FAF editor. Navigate to the textures tab, select a stratum, navigate to the Settings subtab, and click the Import selected stratum mask button. After loading the mask, the texture for that stratum should now appear where the mask exposes them.

Common mistakes

"Hey", you say, "I see weird lines in my masks. What gives?"

If you see something like the above, verify if you followed the instruction on the strict requirements above. Likely, you saved the .raw file as either an interleaved rather than a non-interleaved .raw or you exported the image as an 16-bit .raw.

A very common issue is a mismatch between the resolution of your mask and the resolution the map requires you to provide. This may be caused by [1] and should be debugged by creating a mask in the FAF editor, exporting the mask, and verifying the resolution in an image editor.

Remaining questions

If you are left with questions or need help, your best bet is to check with people in the FAF discord Mapping-General channel. Alternatively, you may send me a PM on discord, or leave a message on this forum.

Footnotes

[1]: The GPG editor is known mess with these values. Any map that has touched the GPG editor at any point is suspect and the resolution of the masks should be verified by exporting the mask file and opening the image in an image editor.

[2]: There is a semi-functional workaround to prevent the normal maps from showing where they shouldn't. Finding this workaround has been left as an exercise for the reader.

[3]: If you are planning on using some of these masks in photoshop for manual adjustments or the like, it is best to export using raw range setting. This setting should also be used if you are attempting workarounds for the issue mentioned at [2]. The quickest and easiest method is to export as Remapped, though.

[IndexLibrorum]

On this classified planet claimed by the Aeon Illuminate, researchers worked years on developing novel surveillance technology. The research, codenamed Project Luminary, resulted in a working prototype, the creation of the Eye of Rhianne, and later on even a minitiurized version which can be installed on the commander. Ever since, the surveillance abilities of the Aeon are without peer. // Licensed under CC BY-NC-SA 4.0. Contact the map author on FAF discord for feedback. This map is compatible with AI.

Project Luminary is a 10x10km map, and is my entry for @Jip 's 'Princess Burke' Mapping tournament. This section of the secret and classified Aeon planet is designed for six people and is best played using the Aeon race, as the terrain allows hover tanks to shine.

Expect aggressive gameplay: players are likely to have to multitask navy, air, and land at the same time, as many mexes are easily raidable by all three options.

The map is licensed under CC. BY-NC-SA 4.0 and is compatible with AI.

Design

As the tournament for which this map is my submission requires an Aeon-themed map, several aspects of the design—both major and minor—are themed to reflect this.

I decided to imagine a map that would serve as the location for the research station that developed the Eye of Rhianne. The map design somewhat resembles an eye, with a pupil-like platform in the middle and an 'iris' as the main island. The name is similarly derived from this concept. A luminary is someone who enlightens others, or refers to 'that which lights up the surroundings'. Given that an Eye of Rianne literally lights up the darkness, the name is a great fit.

Key recurring features are circles, geometric shapes, and precisely placed props. (I spent an inappropriate amount of time carefully shifting the decals, buildings, and props until they lined up exactly. Please someone notice T.T)

Frigates will be having a fun time contesting mexes on the shores, but will have to keep in mind that the shore will never be far away, and Aeon hover tanks might want to use the same space to flank around any PD installations.

Other fun facts:

• This map uses just over 2000 decals, two of which are a map-wide normal map and a map-wide Albedo/Shadow decal
• The map-wide albedo is mostly transparant, but helps a lot with color correction and cliff details
• The map-wide assets took 2 hours to render at the required 8k resolution, during which my PC froze and could not be used for other stuff. This had to be done four times. (My PC is ten years old and desperately needs a replacement. If you're reading this and you're rich, please buy me a new pc. Help.)
• There are only 4 circle-type Aeon-ish decals. To create the various patterns, I stacked and combined these in different combinations to keep everthing interesting. Getting everything lined up was super fiddly and a massive pain and please don't make me do this again.
• The centerpiece features 3 small transport ships (because naturally, the people living in that base have to get off their little platform somehow.) These transports have their own little designated landing zone, though at the start of the game they decide to relocate for some reason. (Compare the third and last picture). I suspect either some roughness in the terrain or too close proximity to other structures, but I haven't figured that one out yet.
• I added very subtle waves and clouds because they look beautiful. The clouds are only visible if you zoom all the way out, because it's deeply annoying to not be able to properly see the things you're trying to focus on.
• Not including whatever mass you get from the structures (about 5k, estimated), the map contains 23K mass reclaim and 65K energy reclaim. Most of the mass is stuck in little tiny rocks, so while a steady stream of reclaim is available, we shouldn't see too large of spikes in income.

Images

[IndexLibrorum]

Gaea tutorial: A basic introduction to mapping with Gaea

The various map projects I've made have all been made possible by Quadspinner's Gaea, a terrain design application for VFX and games. Gaea is an industry standard and a great tool to significantly speed up creating or increasing the complexity of masks, heightmaps, and decals. Because of FAF's peculiarities and the fact that the game is more than a decade old, the process of producing these assets using Gaea is a bit involved. Being the shiny beacon of enlightenment that I am, in this tutorial series I will explain my process for creating all the relevant map assets in gaea (see figure 1). This specific tutorial will discuss the basics of Gaea and how it can be used to create the main heightmap for your terrain.

Figure 1: a breakdown of the map Project Luminary to show all the assets generated in Gaea. Note: some of the stratum textures are stock-FAF textures and were not created in Gaea, but are here included to illustrate the different components of the map.

Prerequisites

This tutorial assumes you've got a basic understanding of image editing and FAF mapping. Additionally, while this specific tutorial will explain some of the basics of visual node based programming, the technique Gaea uses to create the assets, it is recommended that you take some time to familiarize yourself with the concept and Gaea in particular. This 6-minute video is highly recommended, as is giving the general documentation for gaea a read. Using this node system may look daunting at first, but is very intuitive and easy to learn.

Required tools

Required for this tutorial is a copy of Gaea (the indie version is free to use and more than sufficient for maps up to 20km), which can be downloaded here. Additionally, an image editor such as Photoshop or Gimp is required, though the free to use online photoshop-clone Photopea works fine too. Finally, you need to have installed the FAF map editor.

Footnotes marked as '[0]' where needed. Notes are added to the bottom of the tutorial.

When specific nodes are referenced, they are highlighted like this: Node. Specific parameters for these nodes are written like this: Slope, 30, 90, 0, to specify a Slope node with Parameters 30 (min), 90 (Max), and 0 (Falloff).

Introducing Gaea

Gaea is a graph-based application for creating terrain and focussed on providing techniques to simulate realistic erosion. To create these terrains, different nodes are linked to eachother. Nodes affect or combine with other nodes to create complex shapes and structures. While working in Gaea, you will navigate between several panels.

The workspace

As of June 2023, a typical workspace in Gaea might look like Figure 2. The workspace can be configured to your preferences, with different panels moved or scaled. The largest part of the screen is taken up by the viewports and the graph surface. The viewport shows you the terrain and masks, the view of which can be rotated, scaled, and panned. Optionally, you can press the 2D button in the viewport toolbar to show the second, top-down, viewport. Below the viewports, you will see the graph surface, where your nodes and their connections are displayed. Clicking on a node will show the contents of that node in the viewports.

! Tip: you can lock the viewport to show one specific node by selecting the node and pressing F on the keyboard. The node will be marked with a small green circle on the bottom right of the node to indicate the viewport is locked on that node. This is very useful when you are adjusting parameters of nodes earlier in the chain, but want to see the result on a specific node later in the chain. Press F again while selecting the node to unlock the viewport.

Figure 2: Typical workspace of Gaea. Colored accents added to highlight the different panels. Red: Main toolbar. Orange: Toolkit containing various nodes. Yellow: Viewport, 2D viewport, and viewport toolbar. Green: Graph surface. Blue: Properties panel.

The toolbox contains all the nodes you can put onto the graph surface. Nodes are grouped by type, and have a specific colour to signify which group they belong to.
Clicking on a node will also reveal the properties panel for that node. Here, you can adjust the effect or contents of the specific node.

Above all the other panels is the main toolbar, which contains a few important things to discuss. First, the viewport resolution can be selected in this panel. It is generally recommended to select the resolution that you will be exporting your heightmap in. Gaea recalculates the terrain and parameters of the nodes every time you switch resolution, and the resolution can drastically affect how the terrain is shaped. Aside from the obvious increase in fine details, you might find that elements have changed shapes or moved when comparing different resolutions.

! As the terrain changes based on the resolution it is rendered in, creating high-resolution map-wide decals might result in some mismatch between the heightmap and the decals. A method to prevent this will be discussed in the tutorial on map-wide assets.

Figure 3: Showing the differences between the viewport at 0.5k, 1k, and 2k resolution. Note the increase in fine details.

Another important section of the main toolbar is the save button. Attached to the save button is a smaller button labeled with (+). This button will create a version-copy of your project: if a project is named 'Project Luminary V1', clicking this button will create a new savefile labelled "Project Luminary V1001". The next time you click the button, the new savefile will be labelled "Project Luminary V1002". I cannot stress enough how important it is to regularly create a new version. Since before I started using Gaea, the undo and redo buttons have been rather dysfunctional. Maintaining a recent version of your project will ensure you do not lose large sections of your work when you inevitably have to undo changes that the undo-button refuses to process. Note that the save-files Gaea creates are very small: do not hesitate to create new savefiles.

Nodes and graphs

As mentioned, nodes are sorted by type and colored accordingly. Generally, basic nodes that create a type of terrain are green. Nodes that transform or adjust other nodes are generally light blue or teal. Nodes that apply erosion or aggressively 'damage' terrain are light or dark orange. A different, darker shade of orange is reserved for Data nodes, which are nodes that can be used to mask or select parts of the terrain based on certain parameters. When creating textures, the purple nodes will allow you to work with colour.

Nodes often have one or more inputs, and one or more outputs. A Combine node, for example has three inputs and two outputs. Hovering over the little dot marking the node's in- or output will show the name of the port and indicate whether or not a connection is required for the node to function. Ports that need a connection have the same colour as the node-type, while optional ports are grey. Additionally, many ports have a designated input for masks. Adding a node (A) to the mask-input of another node (B) allows you to restrict the effect of node (B) to the specific area determined by node (A). Connections to a mask-input are always coloured purple, to indicate the type of connection.

Nodes that are improperly connected will have a red-dotted border and display the text "error". A node that has not been rendered yet will show as a blue-dotted bordered node. Clicking on this node (and, if required, un-locking any previously locked nodes from the viewport) will prompt Gaea to calculate the effect of the node and display its contents. Nodes that are selected will be marked with a blue glow. The node will then turn into a solid-bordered node, or if failed, be marked with an error.

! Sometimes, Gaea runs into an error that it refuses to get unstuck from. In most cases, it suffices to select the whole graph and press the 'Force a Refresh' button at the right bottom corner of the graph surface. If this does not resolve the issue, double check your connections (a common mistake is to connect to a secondary input rather than a primary input) or restart Gaea.

Figure 4: A properly connected and selected node, an unrendered node, and a node that was rendered but produced an error. Note how the first node has three inputs, one of which is a mask, and one output.

Node parameters

Each node has a particular set of parameters that can be adjusted to change the result of the node. Some of these have obvious effects: the Height parameter for the Constant node affects the height of the flat plane that the node generates. Common parameters include Scale and Seed. Seed in particular is a very powerful parameter common to nearly all nodes: changing the seed value randomizes the noise used to generate the effect of the node, which changes the outcome significantly (see figure 5). Other parameters are less intuitive, and require some experimenting to understand how the node is affected.

Figure 5: Four copies of a mountain node with identical settings but different seeds.

Creating a heightmap for FAF

Creating your first terrain

Primitives

Whether you have a design in mind or are hoping to combine nodes until something presentable falls out, you're going to want to start out with one of the primitives. This category of node is coloured green and serves as the basic building blocks for your terrain. Half of this category consists of 'plain' primitives: the Constant node produces a flat plane, the Gradient node produces a ramp or a cone. Different types of noise generators are included as well, such as Gabor, LineNoise, Voronoi, and Multifractal.

Figure 6: A selection of primitive nodes: Constant, Gradient, Gabor, and MultiFractal.

Geo primitives

The other half of this categories includes more complex presets of common terrain features. Among these Geo Primitives you will find nodes such as Badlands, Crater, Mountain, Canyon, Dunes, and Island (figure 7). Many of these advanced nodes can be recreated by combining 'plain' primitives, but as they are rather complex it is often easier to use the Geo primitives.

Figure 7: A selection of geoprimitive nodes: Badlands, Dunes, Crater, and Canyon.

Adjustments Nodes

To start adding things together, you'll need some nodes from the next main category: the adjustments nodes. The Combine node does what it says on the tin: you can combine two different nodes into one using different blending modes and strengths. Figure 8 shows the result of blending the Badlands node and Crater node from figure 7 together using four different blendmodes.

Figure 8: Blending Crater and Badlands using the blending modes Embed, Subtract, Divide, and Insert.

The other be scaled, rotated, and repositioned using the Transform command, while the Clamp node gives you good control over the global height of the terrain.
In my map Project Mesa, for example, I created the basis for the various pillars using a Gradient, Radial node, which I then repositioned and rescaled using the Transform node, and merged with the main terrain using a Combine, Embed node.

Erosion Nodes

Once the basic design of your map has been established, you might want to take a look at the various Erosion nodes. These nodes create rugged looking terrain, simulating decay over time from exposure to the elements. They can be applied to separate elements if you are combining multiple elements into one whole, be limited to specific areas using masks, or can be applied to the whole terrain at once. The Wizard node is a powerful erosion node with many presets that will be adequate in most situations (figure 9).

I want to caution against using Erosion excessively; units in FAF do not like rough terrain: it messes with pathing and blocks shots. While erosion adds lots of detail to a map, consider that the main areas that units fight on should be smooth and relatively flat whenever possible. Naturally, this is of no concern in areas that are limited to air or navy only.

Figure 9: A mountain and three variants with progressively stronger and more aggressive erosion (Wizard) applied. Note the formation of fine details, debris, and lots of sediment.

Modifier parameters

The properties panel of all nodes contains a set of buttons at the bottom right that allow for common modifications to nodes. Several of these modifications have their own nodes with the same effect: the Clmp and Clip buttons imitate the Clamp node, and the Blur button functions as the Blur node.

Aside from these modifications, there are two more settings that are very useful. Be pressing the '>' button, two further options appear. The Influence parameter allows you to reduce the overal effect of the node. The Drop to Floor checkbox lowers the contents of the node to the lowest possible limit, which can be very useful after combining several layers together.

Figure 10: This panel containing modifier parameters is present on all nodes and allows for adjustments without having to add more nodes. The Drop to Floor checkbox is not visible by default and will only show up when pressing the chevron to the left of the buttons.

Using nodes as masks

Using greyscale values to create terrain

So far, we've discussed how nodes can be used to create the terrain for your map. To understand how nodes can also be used to create masks to select specific parts of the terrain, we need to quickly discuss what it is these nodes are creating.

In games such as FAF, a greyscale image creates the terrain. Every pixel of the image has a greyscale value, which ranges from 0, complete black, to 256, complete white. The value of each pixel corresponds to the height of that pixel when it is used to render the terrain. A full white pixel is at maximum height, while a black pixel is at the minimum height. Any values between 0 and 256 correspond to a height somewhere in between the minimum and the maximum.

Gaea similarly translates greyscale pixels to terrain. By default, the viewport renders the resulting 3D terrain for you, but by changing the display mode we can visualize the flat greyscale image. Right clicking on any node and select Show as, Mask, or by selecting a node and pressing T, will change how the viewport renders that node. You will now see the greyscale pixels for your heightmap.

It might be that the greyscale value is still overlaid on the 3D model, rather than shown as a flat plane. This is because Gaea always shows two layers: the node and the underlay. The underlay is the geometry that Gaea projects the contents of a node on top of. This is generally selected automatically, but similarly to how you can freeze a node into the viewport by pressing F, a node can be chosen to serve as underlay frozen by pressing G. To visualize the greyscale image as on a flat plane, you can create a Constant, 0% height node and select that as underlay.

If the image is dark and you would like more contrast to see the different structures, you may press the Show raw data button and the Enhanced view button on the right side of the view port (figure 11).

Since the greyscale value of each pixel is a number, we can easily make selections based on these values. The Data category of nodes contains a lot of nodes that we need to do such selections. The Height node lets you make selections based on the height of the terrain, which corresponds to the higher greyscale value. Similarly, Slope allows you to make selections of pixels that are at a certain angle, by calculating the relationship of a pixel with its neighbours.

For a more extensive introduction to Data nodes to create masks, please see the Gaea tutorial on Masking.

Figure 11: The 3D image, and the corresponding greyscale representation of the raw data for the heightmap. The three greyscale images show the heightmap projected on the 3D model, on a flat plane, and on a flat plane with Enhanced view enabled.

Using greyscale values to select

The greyscale values can also serve to create selections: effects of nodes can be limited to only areas that are white, and not be applied to areas that are black. Greyscale values between white and black correspond to a percentage of the effect being applied. As all nodes contain essentially nothing more than a greyscale image, the outputs of nearly all nodes can be used to make such selections.

By using masks, you get infinitely more control over how nodes are applied. One example might be limiting where erosion is applied. In the fourth panel of figure 10, the erosion is applied to the whole mountain. As an example, we will now limit the erosion to only half of the mountain.

To do this, we first set up our mountain and apply the Wizard erosion node. Then, we create our mask. The mask that we need to limit the erosion to only half of the mountain is a mask that is half white, and half black. Only in the white regions will the erosion effect be applied. To create a full white heightmap, we could take the Constant node and set it to 100% height. Using a Transform node, we could then move the Constant node halfway off of the workspace. As there is no information on the now empty half of the heightmap, these pixels will be black. The results is a heightmap that is white in one half of the image, and black on the other half. When we then use the output of this Transform node and chain it as the mask-input of the Wizard node, we get the result we intend (figure 12).

Figure 12: The erosion effect is applied to half of the mountain using a mask. Panel 2 and 3 both show the same node, but the display mode differs. The bottom panel shows the Graph to create this effect. The Fold node shown was used to slightly alter the result of Mountain node, and does not affect the process of making a mask.

Naturally, this specific effect is not something that would work well for a FAF map, but clearly illustrates the principle of using masks.

Other nodes

There are several other useful nodes that you might use to create more advanced materials for your map. These include the Normal Map node, which can be used to create map-wide normal map decals, or the Light node, which can be used to create map-wide shadow decals. As these nodes are more complex, they will be discussed in detail in another tutorial.

Creating symmetry

As Gaea is designed to create realistic and natural terrain, it does not create symmetric terrain by default. In contrast, competitive FAF maps require symmetry to ensure no team has an advantage over the other. Luckily, by combining a few nodes we can create seamless symmetry for all kinds of terrain.

Symmetry of basic terrain

The most simple way to create a symmetric heightmap is done by using the Flip and Combine nodes. The Flip node allows for three different types of mirroring: Horizontal, Vertical, and Both. By combining the flipped copy with the original, you get symmetry.

Figure 13: An example of how the Flip node can be used to create three different kinds of symmetry: Horizontal, Vertical, and Both. Combine, Add, 100% was used in these examples.

Rendering your height mask

When you've completed your terrain, you can export it for importing into the FAF editor. To do this, take the last node in your graph and mark that node for export by selecting the node and pressing F3, or by right clicking it and selecting Mark for Export. The marked nodes will now show up under the Build tab in the top right. Adjust the relevant settings:

• Change the filetype of all masks to .raw
• Method should be left on Normal Build
• Resolution should be set to the size corresponding to your map's heightmap (257px for a 5km map, 513px for a 10km map, 1025px for a 20km map).
• Colorspace should be left on sRGB
• Range should be left on Raw, although alternatively this may be set to Remapped to rescale the whole terrain if it proves to be too tall for the FAF editor, see below.
• Baked Cache may be left on Use

After selecting where Gaea should dump the generated files, you can render the files by pressing Start Build.

Rescaling height

If, upon importing the heightmap into the FAF map editor, you realize that there is an issue with the vertical scale, you may want to adjust your heightmap. There are a few easy ways of achieving this. The Clamp node lets you scale the whole heightmap proportionally. Connect this node to the last node of your graph and adjust as necessary. Similarly, under the modifier parameters (those little buttons at the bottom right of a node's parameter panel) you will find the Raise modifier, a circle containing an X. This parameter behaves nearly identical to the Clamp node. Lastly, by setting the Range setting under the build menu to Remapped, and setting the maximum value to some fraction of 1, you can rescale the terrain.

Some trial and error is likely required to find the right scale.

Common errors and checklist

If you are running into problems with importing your heightmap to the FAF editor, please check the following:

• Verify you are using the correct resolution
• Verify you exported the heightmap in the .raw file format.
• Try changing the Baked Cache setting to None and re-render.

If Gaea is producing errors and you cannot get it to work, please check the following:

• Verify that the offending node is properly connected. Remove connections and try again. Nine times out of ten you accidently connected a non-primary output to the next node that cannot use that particular type of data, or connected one node to the a secondary input of the second node.
• Force refresh the complete graph.
• Replace the bugged node.
• Restart Gaea.

If Gaea refuses to render your heightmap, attempt the following:

• Add a Transform node to the end of the graph, and mark that node for export. Some nodes are known not to produce an output, but the Transform node is known to behave as expected.

Remaining questions

If you are left with questions or need help, your best bet is to check with people in the FAF discord Mapping-General channel. Alternatively, you may send me a PM on discord, or leave a message on this forum.

[IndexLibrorum]

On this classified planet claimed by the Aeon Illuminate, researchers worked years on developing novel surveillance technology. The research, codenamed Project Luminary, resulted in a working prototype, the creation of the Eye of Rhianne, and later on even a minitiurized version which can be installed on the commander. Ever since, the surveillance abilities of the Aeon are without peer. // Licensed under CC BY-NC-SA 4.0. Contact the map author on FAF discord for feedback. This map is compatible with AI and is adaptive.

To celebrate Project Luminary winning first place in Jip's 'Princess Burke' Mapping tournament, I have released a 20km version of the map. A maximum of 12 players can play on this map, and several options are configurable: underwater mexes can be turned off, and extra hydros, core mexes, and middle mexes may be spawned in.

Due to the increased size of the map, Project Luminary Maxima is expected to be less hectic than the original, where players are likely to have to multitask navy, air, and land at the same time. Nonetheless, all three unit types will be relevant, and floating units will find lots of opportunities too.

In this 20km version, the islands that were at the edge of the map in Project Luminary have been expanded and more sea has been added. Due to the many mexes under or near water, you may expect T1 navy to be very relevant. Consider sending your commanders to the main island, to ensure that your team does not quickly lose control of the middle. Although this is a 20km map, all but one commanders spawn close enough to the center island that they will certainly be relevant by the time they arrive there.

T2 air is similarly expected to be strong on this map. It is advised not to blindly rush into T3, but rather see if there are opportunities for snipes, drops, or for supporting your navy players with torps.

The map is licensed under CC BY-NC-SA 4.0 and is compatible with AI.

[IndexLibrorum]

"Under pale moon,
Across the snow
...
Did we not lose, a hundred times?
Did we not win, a hundred times?"

Hello. It has been a while.

Project Albus is my first snow-type map, featuring large ice and snow covered flats. This 15x15 km map supports up to 8 players and consists of 5 lanes. The center lane is rather wide, while the lanes in the corners have several areas that serve as chokes. While the two large mountains serve as a barrier separating the main and the side lanes, the mountains can be crossed by small groups of units, albeit with some difficulty; You'll have to remain vigilant against enterprising enemies trying to raid through them.

This map was a real pleasure to create, and uses several new techniques and tricks. First and foremost is the use of asymmetry: you'll notice that the ice floe in the corner ponds are different between the two map halves. To ensure that this difference in terrain does not affect gameplay, the two ponds have been made inaccessible using terrain types. Units will not be able to access this part of the map, air units excepted.

Experiments with asymmetric texturing have worked out rather well, and textures have been applied in a more organic manner. While the main playable area has identical terrain, textures are not applied symmetrically, creating a sense of natural distribution of the snow and ice. Additionally, some experiments with creating texture masks in Gaea have led to some improvements, and I believe the quality of the masks has increased significantly compared to my previous maps.

Future iterations of Adaptive Project Albus are pending on feedback, and might lead to an adjustment of mexes and reclaim. As per usual, any feedback is welcome either in this thread, or via discord directed to Prohibitorum.

The map is licensed under CC BY-NC-SA 4.0 and is compatible with AI.