URCHN Arkipelago - User contributions [en]

Stopmotion

2022-02-01T23:47:22Z

Bassam: Documentation for Blender Stop Motion Addon

Stop Motion Page

Scripts

2022-02-01T23:46:49Z

Bassam: /* Pipeline Scripts */

== General instructions ==
*[[How to install Addons]]

== SFX Scripts ==
* [[Mushroomer]]
* Current [[Roach Walk Sim]]
* Old [[Roach Crowd Sim]]
* [[Particle Baker]]
* [[Animation To Path]]
* [[Timelapse toolbox]]
*[[Meshcacher]]

== Pipeline Scripts ==
* [[Reference_desk]]
* [[Geppetto]]
* [[Layer_names]]
* [[blendflakes]]
* [[zippo]]
* [[meshcacher]]
* [[stopmotion]]

== Shading Scripts ==
* [[Multi_dirty_verts]]

Blender 2.9 Migration

2020-07-15T20:21:09Z

Bassam:

'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo.
'''Solution:''' We'll (sorta) follow Subversion's migration strategy:
# the two main folders to migrate are lib/ and scenes/ in the main project folder.
# create branches/blender29/ in main tube/ folder
# create lib/ and scenes/ in the blender29/ folder
# commit these to Subversion
# '''copy or move (windows) or symlink (linux) lib/maps and lib/maps_low if needed/'''
# replicate the rest of the folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
# Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
# Manually check, copying/ changing if needed
# Commit new files

Much later:
* SVN delete the old lib/ and scenes/ file
* SVN rename the folders to switch branches/blender29/ to main/

Blender 2.9 Migration

2020-07-15T16:17:54Z

Bassam:

'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo.
'''Solution:''' We'll (sorta) follow Subversion's migration strategy:
* the two main folders to migrate are lib/ and scenes/ in the main project folder.
* create branches/blender29/ in main tube/ folder
* create lib/ and scenes/ in the blender29/ folder
* commit these to Subversion
* '''copy or move (windows) or symlink (linux) lib/maps and lib/maps_low if needed/'''
* replicate the rest of the folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
* Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
* Manually check, copying/ changing if needed
* Commit new files

Much later:
* SVN delete the old lib/ and scenes/ file
* SVN rename the folders to switch branches/blender29/ to main/

Blender 2.9 Migration

2020-07-13T14:46:17Z

Bassam:

'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo.
'''Solution:''' We'll (sorta) follow Subversion's migration strategy:
* the two main folders to migrate are lib/ and scenes/ in the main project folder.
* create branches/blender29/ in main tube/ folder
* create lib/ and scenes/ in the blender29/ folder
* commit these to Subversion
* '''copy or move (windows) or symlink (linux) lib/textures/'''
* replicate the rest of the folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
* Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
* Manually check, copying/ changing if needed
* Commit new files

Much later:
* SVN delete the old lib/ and scenes/ file
* SVN rename the folders to switch branches/blender29/ to main/

Main Page

2020-07-13T14:45:13Z

Bassam:

== Documentation ==
=== Story ===
* [[Story]]

=== Style and Guidelines ===
* [[Propaganda]]
* [[Advertisement]]
* [[Text]]
* [[Timelapse]]
* [[Color|Color and lighting]]

=== Assets ===
* [[Scripts]]
* [[Rigs]]
* [[Models]]
* [[Assets]]
* [[Software]]

=== Project Management/Communication ===
* [[Blender 2.9 Migration]]
* [[SVN and Helga access]]
* [[Sparkleshare]]
* [[IRC]]
* [[Funding]]
* 'live' video and voice: [[skype/google hangouts]]

=== Workflow ===
* [[Creating a linkable asset]]
* [[Shot pipeline]]
* [[Layout]]
* [[Animation Notes]]
* [[Hair Sim workflow]]
* [[Lighting and rendering workflow]]
* [[Timelapse Assets]]

=== General ===
* [[Maya to Blender]]
* [[Object and Material ID table]]

Blender 2.9 Migration

2020-07-13T14:44:11Z

Bassam:

'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo.
'''Solution:''' We'll (sorta) follow Subversion's migration strategy:
* the two main folders to migrate are lib/ and scenes/ in the main project folder.
* create branches/blender29/ in main tube/ folder
* create lib/ and scenes/ in the blender29/ folder
* commit these to Subversion
* replicate folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
* Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
* Manually check, copying/ changing if needed
* Commit new files

Much later:
* SVN delete the old lib/ and scenes/ file
* SVN rename the folders to switch branches/blender29/ to main/

Blender 2.9 Migration

2020-07-13T14:39:15Z

Bassam: Created page with "'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo. '''Solut..."

2017-07-23T23:12:25Z

Bassam:

== When ==
We'll see advertisements mainly in the transition to act_2, and in act_3. The advertisements can and should be varied, but here are some basic guidelines and ideas
== Fonts ==
Use the font [https://urchn.org/post/type-in-wires-for-empathy Soomerian Modern], available in the SVN repo, or downloadable [http://urchn.org/tube/Soomerian.zip here]
This font can be modified in font editing programs such as [http://birdfont.org/ birdfont] in combination with vector editors such as [https://inkscape.org/en/ inkscape], or simply in your image editor, to achieve desired effects such as decorations, styles, kerning, or special effects such as stencil or strike through.
== Inspiration/Reference ==
=== Travel and or Movie Posters ===
Invisible Cities by Italo Calvino is an excellent starting point for inspiring travelog style advertisements, like those put out by travel agencies to advertise a location. The cities are conceptual and on a theme, and could inspire a conceptual (or literal response). I prefer using travel images with simple colour pallets and small or no human figures in the image - focus on location/concept/or mood rather than on a personal image.
Some randomish links for travel images:
[https://misslovelight.files.wordpress.com/2008/03/sta011.jpg]
Illustrations for Calvino cities (much cooler reference):
[https://4.bp.blogspot.com/_0uxiDUIwkXw/TIE14A7g2QI/AAAAAAAAACU/RD2pKG1hgcc/s1600/DSCN4182.JPG]
[https://mir-s3-cdn-cf.behance.net/project_modules/disp/10587d8262069.560ba047936e0.jpg]
So what's being asked is to blend the Calvino concepts with text/layout used in advertising. The result can be either a travel image or a film poster (theater play also possible). The basic idea is that most of the advertisments is portraying possible worlds.
<gallery>
FreeBassel-by-Ahmad-Ali.png
</gallery>

2017-07-23T23:00:30Z

Bassam: /* Fonts */

2017-07-23T22:54:58Z

Bassam: /* When */

== When ==
We'll see advertisements mainly in the transition to act_2, and in act_3. The advertisements can and should be varied, but here are some basic guidelines and ideas
== Fonts ==
Use the font Soomerian Modern, available in the SVN repo, or downloadable here
This font can be modified in font editing programs such as birdfont, or simply in your image editor, to achieve desired effects such as decorations, styles, kerning, or special effects such as stencil or strike through.
<gallery>
FreeBassel-by-Ahmad-Ali.png
</gallery>

SVN and Helga access

2016-06-03T23:14:26Z

Bassam: /* SVN (Subbversion) */

Access to Helga and SVN.

== Helga ==

=== Signing In ===

Access Helga here [http://anim.hampshire.edu Hampshire Animation]

You will need a username and password

If you just received a username your password is blank. Go ''immediately'' to the 'MyHelga' tab, and create a password for yourself you can remember.

=== What it is ===

Helga is a project management/Asset management tool. On the front end, it looks like a webpage with lists of shots and models in the project. Each shot/model has a preview image, and a short 'blog' where you can put in comments.

Helga also knows who is working on a project, here you can be assigned to work on the shot/model. As you work, post comments in the Shot or Model, with a preview image or movie as an attachment. This makes it easy for the directors to reply with corrections/comments, and let you know when the work is final.

Helga sends email to you on assignments, and lets you know in general how things are going.

=== In short ===

For most of us, it acts like a blog or flickr, with each shot having it's own page where you can comment/upload preview images or videos. When you are working on your assigned task and need feedback, upload a comment with a preview, and the feedback will come in the same thread.

==SVN (Subversion)==

=== Repository and Working Copy ===
SVN is what is known as a Version Control System; it can take a collection of files and save them on a server (this is called the ''repository'').
Multiple people can '''Check out''' the files on their own machines (these are called ''working copies'').

=== Updating and Committing ===

Let's say Liz modifies the file 'train.blend' in the working copy. In order for Henri to work with her changes, she has to make them available to everybody - so she does what is called a '''commit''' . After the commit, the file is now on the '''repository''' but not on everybody's '''working copy'''.

Henri now has to run an '''update''' on his working copy. This will get the version of the file that Liz changed, and he can now use her changes.

=== Clients ===

To work with SVN you need a special program installed on your computer. There are many of them, and they are all called '''svn clients'''. Some common ones are:

* '''svn''' command line client (From a terminal in any OS) [http://subversion.apache.org/packages.html packages]
* '''rapidsvn''' (linux)
* '''tortoise svn''' (windows) [http://tortoisesvn.net/downloads.html Downloads]
* '''svnX''' [http://www.lachoseinteractive.net/en/community/subversion/svnx/download/ Download](Mac)

==== Instructions for the SVN terminal client ====

To do the initial checkout , run:

''svn checkout PROJECTURL''

To update a file:

''svn update FILEPATH''

To update a directory:
''
svn update''

(if you are in the top directory of the project it will update all the files in the project)

To commit a file:

''svn commit FILEPATH''

If you type:

''svn commit''

It will commit all things in the current directory.

=== Adding New Files ===

If a file does not exist and you create it, you need to do an extra step before you can type svn commit. This is '''svn add''' which tells svn you are adding the new file:
''
svn add FILEPATH''

followed by:
''
svn commit''

== file structure ==

Once you have checked out SVN, you have a bunch of files! a quick overview of directory structure follows:

===scenes===
Contains all the shots of the movie!
====act_1====
Shots for act_1, typically one blend file per shot, a1sxx.blend (where xx is the shot number)
====act_2====
Same as act_1, but with a2sxx.blend files.
====act_3====
Same, but here a3sxx.blend
====edits====
Contains reel.blend, a live edit that links all the shots.
===lib===
Contains files that get linked into the scenes (usually as groups), also contains Python scripts, textures, etc. etc.
====models====
Here's the meat! All our assets live here, except some really specific things that can just live in their own shots. We categorize so that the number of files in each folder is not so big...
=====chars=====
rigged characters such as gilgamesh and the roaches, crowd characters, etc.
=====vehicles=====
Trains live here

Timelapse Assets

2016-05-13T17:17:08Z

Bassam: /* Shaders */

== Creating The Asset ==
Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though in some cases we will only need a subsection of the total lifetime of an object.
For example, a security camera may be installed, operate for a while, age and rust, and finally cease function and be removed. The rig for the camera, in addition to controlling (for example) the swivel of the camera head, must have a property that can control the age of the camera in those stages. It's easiest to break up this workflow into steps.
=== Modeling ===
This should resemble normal assets but there are some differences.
* Only use mesh objects for render-able parts of the asset; this is for the meshcacher later. This means if you need to use a curve with bevel, instead use a curve modifier on a mesh.
* You may need to make multiple 'stages' of the meshes, if there are changes that other methods would be difficult to control. It's easier to start from a main stage - something that is either undamaged, or lasts longest in the shot, and modify it to make other stages.
* If meshes will only be visible for a short period of time during the timelapse, don't give them a lot of detail - and they probably don't need an animated material.
=== Animation ===

Next step is to animate the model/s. Don't worry too much about rigging/linking, here are some helpful hints:
* shapekeys are nice for either specific changes, or for general dishevelment
* lattice modifiers are nice because they can apply to multiple objects, you can then use a shapekey or other modifiers to affect the lattice
* the modifier stack is your friend!
* you can use mask modifiers to hide/unhide bits of your model, or booleans with animated cutters (but be careful, they're finicky)
* direct animation (loc rot scale) should be rigged first - you can use armatures, hooks, any kind of modifiers.
* have fun, be creative!

=== Shaders ===
[[file:AgingShadersLib.png]]

Shaders might be the trickiest bit , the thing to remember is to think about how the material changes over time, not just fade it from 'old' to 'new' – the result will be either too subtle to see or somewhat fake looking if sped up. There's a growing library of timelapse nodes that should help with this – also if you end up creating something particularly cool, we can add it to the library. The library shaders also have a built in 'time' input, so you don't have worry about the aging as much. You can access them from reference desk by searching on 'Aging' and then shift-a adding the node group into your material.
* Animating the contrast of a brightness contrast node can give the appearance of a texture 'growing' or shrinking over time
* The same can be done (with more control) with a ramp node, but ramp nodes don't allow inputs - [[Timelapse toolbox]] can fix this.
* Think of 'plugging in boxes' layering groups on top of each other - dust, dirt, cracking paint, rust, cracks, etc layering on top of each other.

[[file:modularmaterial.png]]

'''Note:''' You don't have to make your materials modular: you can just animate them any old which way, and then, when you use timelapse toolbox to drive your animation in the 3D view, but it will non trivial to reuse bits from them later. This might become important if you are building variations on one material for the same asset/assets, or if you are making shaders for a library of node groups.

=== Rigging (timelapse) ===

Create an armature object (this should be the same one you use to control any non – timelapse animation of the group) and pick a bone that will be the driver for all the timelapse, and add a custom property to it – the name 'time' is quite appropriate. Then on to timelapse toolbox!

=== Timelapse Toolbox ===

[[Timelapse toolbox]] contains all the tools you need to convert your local 'in asset' animation, into driven animation, where all time based animation is set to a property on a single bone.

== Asset-izing ==
Once Rigging / modelling/ shading is complete, refer to the [[Creating a linkable asset]], [[blendflakes]], [[Reference_desk]], etc. to make this easy and controlled to use.
== Use and Caching ==
The use of these assets in anim files is identical to most, with one exception. Start by adding the asset via reference desk or direct linking. I'll encourage and disseminate a proxy creation script for the assets, to avoid having to manually press ctrl-alt-p and make the proxy.
After proxying, time / aging is achievable via the rig, as well as any additional animation required.
If you need more than one copy of an object (with different animation) you'll need to use the [[meshcacher]] addon, which allows creating chaches of your animation, in order to create new ones.

File:Modularmaterial.png

2016-05-13T17:12:52Z

Bassam:

Timelapse Assets

2016-05-13T17:12:23Z

Bassam: /* Shaders */

== Creating The Asset ==
Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though in some cases we will only need a subsection of the total lifetime of an object.
For example, a security camera may be installed, operate for a while, age and rust, and finally cease function and be removed. The rig for the camera, in addition to controlling (for example) the swivel of the camera head, must have a property that can control the age of the camera in those stages. It's easiest to break up this workflow into steps.
=== Modeling ===
This should resemble normal assets but there are some differences.
* Only use mesh objects for render-able parts of the asset; this is for the meshcacher later. This means if you need to use a curve with bevel, instead use a curve modifier on a mesh.
* You may need to make multiple 'stages' of the meshes, if there are changes that other methods would be difficult to control. It's easier to start from a main stage - something that is either undamaged, or lasts longest in the shot, and modify it to make other stages.
* If meshes will only be visible for a short period of time during the timelapse, don't give them a lot of detail - and they probably don't need an animated material.
=== Animation ===

Next step is to animate the model/s. Don't worry too much about rigging/linking, here are some helpful hints:
* shapekeys are nice for either specific changes, or for general dishevelment
* lattice modifiers are nice because they can apply to multiple objects, you can then use a shapekey or other modifiers to affect the lattice
* the modifier stack is your friend!
* you can use mask modifiers to hide/unhide bits of your model, or booleans with animated cutters (but be careful, they're finicky)
* direct animation (loc rot scale) should be rigged first - you can use armatures, hooks, any kind of modifiers.
* have fun, be creative!

=== Shaders ===
[[file:AgingShadersLib.png]]

Shaders might be the trickiest bit , the thing to remember is to think about how the material changes over time, not just fade it from 'old' to 'new' – the result will be either too subtle to see or somewhat fake looking if sped up. There's a growing library of timelapse nodes that should help with this – also if you end up creating something particularly cool, we can add it to the library. The library shaders also have a built in 'time' input, so you don't have worry about the aging as much. You can access them from reference desk by searching on 'Aging' and then shift-a adding the node group into your material.
* Animating the contrast of a brightness contrast node can give the appearance of a texture 'growing' or shrinking over time
* The same can be done (with more control) with a ramp node, but ramp nodes don't allow inputs - [[Timelapse toolbox]] can fix this.
* Think of 'plugging in boxes' layering groups on top of each other - dust, dirt, cracking paint, rust, cracks, etc layering on top of each other.

[[file:modularmaterial.png]]

=== Rigging (timelapse) ===

Create an armature object (this should be the same one you use to control any non – timelapse animation of the group) and pick a bone that will be the driver for all the timelapse, and add a custom property to it – the name 'time' is quite appropriate. Then on to timelapse toolbox!

=== Timelapse Toolbox ===

[[Timelapse toolbox]] contains all the tools you need to convert your local 'in asset' animation, into driven animation, where all time based animation is set to a property on a single bone.

== Asset-izing ==
Once Rigging / modelling/ shading is complete, refer to the [[Creating a linkable asset]], [[blendflakes]], [[Reference_desk]], etc. to make this easy and controlled to use.
== Use and Caching ==
The use of these assets in anim files is identical to most, with one exception. Start by adding the asset via reference desk or direct linking. I'll encourage and disseminate a proxy creation script for the assets, to avoid having to manually press ctrl-alt-p and make the proxy.
After proxying, time / aging is achievable via the rig, as well as any additional animation required.
If you need more than one copy of an object (with different animation) you'll need to use the [[meshcacher]] addon, which allows creating chaches of your animation, in order to create new ones.

Timelapse Assets

2016-05-13T16:56:37Z

Bassam: /* Use and Caching */

== Creating The Asset ==
Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though in some cases we will only need a subsection of the total lifetime of an object.
For example, a security camera may be installed, operate for a while, age and rust, and finally cease function and be removed. The rig for the camera, in addition to controlling (for example) the swivel of the camera head, must have a property that can control the age of the camera in those stages. It's easiest to break up this workflow into steps.
=== Modeling ===
This should resemble normal assets but there are some differences.
* Only use mesh objects for render-able parts of the asset; this is for the meshcacher later. This means if you need to use a curve with bevel, instead use a curve modifier on a mesh.
* You may need to make multiple 'stages' of the meshes, if there are changes that other methods would be difficult to control. It's easier to start from a main stage - something that is either undamaged, or lasts longest in the shot, and modify it to make other stages.
* If meshes will only be visible for a short period of time during the timelapse, don't give them a lot of detail - and they probably don't need an animated material.
=== Animation ===

Next step is to animate the model/s. Don't worry too much about rigging/linking, here are some helpful hints:
* shapekeys are nice for either specific changes, or for general dishevelment
* lattice modifiers are nice because they can apply to multiple objects, you can then use a shapekey or other modifiers to affect the lattice
* the modifier stack is your friend!
* you can use mask modifiers to hide/unhide bits of your model, or booleans with animated cutters (but be careful, they're finicky)
* direct animation (loc rot scale) should be rigged first - you can use armatures, hooks, any kind of modifiers.
* have fun, be creative!

=== Shaders ===
[[file:AgingShadersLib.png]]

Shaders might be the trickiest bit , the thing to remember is to think about how the material changes over time, not just fade it from 'old' to 'new' – the result will be either too subtle to see or somewhat fake looking if sped up. There's a growing library of timelapse nodes that should help with this – also if you end up creating something particularly cool, we can add it to the library. The library shaders also have a built in 'time' input, so you don't have worry about the aging as much. You can access them from reference desk by searching on 'Aging' and then shift-a adding the node group into your material.
* Animating the contrast of a brightness contrast node can give the appearance of a texture 'growing' or shrinking over time
* The same can be done (with more control) with a ramp node, but ramp nodes don't allow inputs - [[Timelapse toolbox]] can fix this.
* Think of 'plugging in boxes' layering groups on top of each other - dust, dirt, cracking paint, rust, cracks, etc layering on top of each other.

=== Rigging (timelapse) ===

Create an armature object (this should be the same one you use to control any non – timelapse animation of the group) and pick a bone that will be the driver for all the timelapse, and add a custom property to it – the name 'time' is quite appropriate. Then on to timelapse toolbox!

=== Timelapse Toolbox ===

[[Timelapse toolbox]] contains all the tools you need to convert your local 'in asset' animation, into driven animation, where all time based animation is set to a property on a single bone.

== Asset-izing ==
Once Rigging / modelling/ shading is complete, refer to the [[Creating a linkable asset]], [[blendflakes]], [[Reference_desk]], etc. to make this easy and controlled to use.
== Use and Caching ==
The use of these assets in anim files is identical to most, with one exception. Start by adding the asset via reference desk or direct linking. I'll encourage and disseminate a proxy creation script for the assets, to avoid having to manually press ctrl-alt-p and make the proxy.
After proxying, time / aging is achievable via the rig, as well as any additional animation required.
If you need more than one copy of an object (with different animation) you'll need to use the [[meshcacher]] addon, which allows creating chaches of your animation, in order to create new ones.

Scripts

2016-05-13T16:55:03Z

Bassam: /* Pipeline Scripts */

Timelapse Assets

2016-05-13T16:34:07Z

Bassam: /* Shaders */

== Creating The Asset ==
Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though in some cases we will only need a subsection of the total lifetime of an object.
For example, a security camera may be installed, operate for a while, age and rust, and finally cease function and be removed. The rig for the camera, in addition to controlling (for example) the swivel of the camera head, must have a property that can control the age of the camera in those stages. It's easiest to break up this workflow into steps.
=== Modeling ===
This should resemble normal assets but there are some differences.
* Only use mesh objects for render-able parts of the asset; this is for the meshcacher later. This means if you need to use a curve with bevel, instead use a curve modifier on a mesh.
* You may need to make multiple 'stages' of the meshes, if there are changes that other methods would be difficult to control. It's easier to start from a main stage - something that is either undamaged, or lasts longest in the shot, and modify it to make other stages.
* If meshes will only be visible for a short period of time during the timelapse, don't give them a lot of detail - and they probably don't need an animated material.
=== Animation ===

Next step is to animate the model/s. Don't worry too much about rigging/linking, here are some helpful hints:
* shapekeys are nice for either specific changes, or for general dishevelment
* lattice modifiers are nice because they can apply to multiple objects, you can then use a shapekey or other modifiers to affect the lattice
* the modifier stack is your friend!
* you can use mask modifiers to hide/unhide bits of your model, or booleans with animated cutters (but be careful, they're finicky)
* direct animation (loc rot scale) should be rigged first - you can use armatures, hooks, any kind of modifiers.
* have fun, be creative!

=== Shaders ===
[[file:AgingShadersLib.png]]

Shaders might be the trickiest bit , the thing to remember is to think about how the material changes over time, not just fade it from 'old' to 'new' – the result will be either too subtle to see or somewhat fake looking if sped up. There's a growing library of timelapse nodes that should help with this – also if you end up creating something particularly cool, we can add it to the library. The library shaders also have a built in 'time' input, so you don't have worry about the aging as much. You can access them from reference desk by searching on 'Aging' and then shift-a adding the node group into your material.
* Animating the contrast of a brightness contrast node can give the appearance of a texture 'growing' or shrinking over time
* The same can be done (with more control) with a ramp node, but ramp nodes don't allow inputs - [[Timelapse toolbox]] can fix this.
* Think of 'plugging in boxes' layering groups on top of each other - dust, dirt, cracking paint, rust, cracks, etc layering on top of each other.

=== Rigging (timelapse) ===

Create an armature object (this should be the same one you use to control any non – timelapse animation of the group) and pick a bone that will be the driver for all the timelapse, and add a custom property to it – the name 'time' is quite appropriate. Then on to timelapse toolbox!

=== Timelapse Toolbox ===

[[Timelapse toolbox]] contains all the tools you need to convert your local 'in asset' animation, into driven animation, where all time based animation is set to a property on a single bone.

== Use and Caching ==

File:AgingShadersLib.png

2016-05-13T16:32:37Z

Bassam:

Timelapse Assets

2016-05-13T16:32:20Z

Bassam: /* Shaders */

== Creating The Asset ==
Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though in some cases we will only need a subsection of the total lifetime of an object.
For example, a security camera may be installed, operate for a while, age and rust, and finally cease function and be removed. The rig for the camera, in addition to controlling (for example) the swivel of the camera head, must have a property that can control the age of the camera in those stages. It's easiest to break up this workflow into steps.
=== Modeling ===
This should resemble normal assets but there are some differences.
* Only use mesh objects for render-able parts of the asset; this is for the meshcacher later. This means if you need to use a curve with bevel, instead use a curve modifier on a mesh.
* You may need to make multiple 'stages' of the meshes, if there are changes that other methods would be difficult to control. It's easier to start from a main stage - something that is either undamaged, or lasts longest in the shot, and modify it to make other stages.
* If meshes will only be visible for a short period of time during the timelapse, don't give them a lot of detail - and they probably don't need an animated material.
=== Animation ===

Next step is to animate the model/s. Don't worry too much about rigging/linking, here are some helpful hints:
* shapekeys are nice for either specific changes, or for general dishevelment
* lattice modifiers are nice because they can apply to multiple objects, you can then use a shapekey or other modifiers to affect the lattice
* the modifier stack is your friend!
* you can use mask modifiers to hide/unhide bits of your model, or booleans with animated cutters (but be careful, they're finicky)
* direct animation (loc rot scale) should be rigged first - you can use armatures, hooks, any kind of modifiers.
* have fun, be creative!

=== Shaders ===
[[file:AgingShadersLib.png]]
Shaders might be the trickiest bit , the thing to remember is to think about how the material changes over time, not just fade it from 'old' to 'new' – the result will be either too subtle to see or somewhat fake looking if sped up. There's a growing library of timelapse nodes that should help with this – also if you end up creating something particularly cool, we can add it to the library. The library also has a built in 'time' input, so you don't have worry about the aging as much.
* Animating the contrast of a brightness contrast node can give the appearance of a texture 'growing' or shrinking over time
* The same can be done (with more control) with a ramp node, but ramp nodes don't allow inputs - [[Timelapse toolbox]] can fix this.
* Think of 'plugging in boxes' layering groups on top of each other - dust, dirt, cracking paint, rust, cracks, etc layering on top of each other.

=== Rigging (timelapse) ===

Create an armature object (this should be the same one you use to control any non – timelapse animation of the group) and pick a bone that will be the driver for all the timelapse, and add a custom property to it – the name 'time' is quite appropriate. Then on to timelapse toolbox!

=== Timelapse Toolbox ===

[[Timelapse toolbox]] contains all the tools you need to convert your local 'in asset' animation, into driven animation, where all time based animation is set to a property on a single bone.

== Use and Caching ==

Timelapse Assets

2016-05-13T16:24:52Z

Bassam: /* Timelapse Toolbox */

== Creating The Asset ==
Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though in some cases we will only need a subsection of the total lifetime of an object.
For example, a security camera may be installed, operate for a while, age and rust, and finally cease function and be removed. The rig for the camera, in addition to controlling (for example) the swivel of the camera head, must have a property that can control the age of the camera in those stages. It's easiest to break up this workflow into steps.
=== Modeling ===
This should resemble normal assets but there are some differences.
* Only use mesh objects for render-able parts of the asset; this is for the meshcacher later. This means if you need to use a curve with bevel, instead use a curve modifier on a mesh.
* You may need to make multiple 'stages' of the meshes, if there are changes that other methods would be difficult to control. It's easier to start from a main stage - something that is either undamaged, or lasts longest in the shot, and modify it to make other stages.
* If meshes will only be visible for a short period of time during the timelapse, don't give them a lot of detail - and they probably don't need an animated material.
=== Animation ===

Next step is to animate the model/s. Don't worry too much about rigging/linking, here are some helpful hints:
* shapekeys are nice for either specific changes, or for general dishevelment
* lattice modifiers are nice because they can apply to multiple objects, you can then use a shapekey or other modifiers to affect the lattice
* the modifier stack is your friend!
* you can use mask modifiers to hide/unhide bits of your model, or booleans with animated cutters (but be careful, they're finicky)
* direct animation (loc rot scale) should be rigged first - you can use armatures, hooks, any kind of modifiers.
* have fun, be creative!

=== Shaders ===

Shaders might be the trickiest bit , the thing to remember is to think about how the material changes over time, not just fade it from 'old' to 'new' – the result will be either too subtle to see or somewhat fake looking if sped up. There's a growing library of timelapse nodes that should help with this – also if you end up creating something particularly cool, we can add it to the library. The library also has a built in 'time' input, so you don't have worry about the aging as much.
* Animating the contrast of a brightness contrast node can give the appearance of a texture 'growing' or shrinking over time
* The same can be done (with more control) with a ramp node, but ramp nodes don't allow inputs - [[Timelapse toolbox]] can fix this.
* Think of 'plugging in boxes' layering groups on top of each other - dust, dirt, cracking paint, rust, cracks, etc layering on top of each other.

=== Rigging (timelapse) ===

Create an armature object (this should be the same one you use to control any non – timelapse animation of the group) and pick a bone that will be the driver for all the timelapse, and add a custom property to it – the name 'time' is quite appropriate. Then on to timelapse toolbox!

=== Timelapse Toolbox ===

[[Timelapse toolbox]] contains all the tools you need to convert your local 'in asset' animation, into driven animation, where all time based animation is set to a property on a single bone.

== Use and Caching ==

Timelapse toolbox

2016-05-12T23:42:29Z

Bassam: /* Add a new Channel to Ramp Group */

== Tools for Timelapse Makers in the 3D Editor ==
[[File:timelapsetools.png]]
Currently split into 7 tools, they will affect animation on the object, object-data, modifiers, shapekeys, materials and nodegroups level.
Activate via pie menu with hotkey ctrl F1

=== Curves To Drivers ===
[[File:fcurvestodrivers.png]]
Transforms animation curves mapped to the Frame Start / Frame End of the current scene into drivers based on a property of the active pose bone.
Workflow:
** Select animated objects
** Shift Select a bone with at least one driver you need to use
** Press Ctrl F1 and pick Curves to Drivers from the menu
** If you have more than one property, you will be presented with a popup to select which one to drive from, and then press OK
** Drivers are mapped to the min and max of the property (it should be a float) from frame start and frame end
** The original Actions are not deleted.

=== Drivers To Curves ===
[[File:driverstofcurves.png]]
The Inverse of the previous option, it will copy the drivers mapped from the min/max of the property of the active pose bone into animation curves mapped to frame start/ frame end of the current scene. Workflow:
** select driven objects
** Shift Select a bone with the property you are driving with
** Press Ctrl F1 and pick Drivers to Curves from the menu
** If the bone has more than one property, you will be presented with a menu to select the desired one
** Curves will be created/ mapped to frame start/frame end from the min and max of that property
** The original drivers will '''not''' be deleted, so you will need to do this if you want to see the animation.

=== Display to Render ===
It is often desirable that renderability curves/drivers for the objects or their modifiers match exactly with visibility curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Display to Render from the menu
=== Render to Display ===
It is often desirable that visibility curves/drivers for the objects or their modifiers match exactly with renderability curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Render to Display from the menu
=== Un Drive ===
Once you have drivers on an object it will ignore the animation in actions: In order to see it once again, you will need to remove those drivers. This utility does just that:
** Select driven objects
** Press Ctrl F1 and select Un Drive from the menu
=== Un Curve ===
Once you've finished creating your driven setup you may not want those extra actions hanging around, doing nothing. Use UnCurve to unlink them:
** Select animated objects
** Press Ctrl F1 and select Un Curve to unlink all actions from your objects
=== Show Bools ===
Coming soonish!
== Tools for Timelapse in the node editor (shaders) ==
[[File:TimelapseShaders.png]]
=== Create a Time Driven Group ===
while timelapse toolbox can directly convert material animation into drivers, this is only really good for 'one-offs': such materials will work just fine, but will be only usable for specific cases, not easily generalizable to reusable nodegroups. There is another way however: use timelapse toolbox within the node editor, to convert animated node trees into a node group with a 'time' input. This will keep your animation curves, converting them into curve nodes with the time input as Fac, preserving delicate timing you've created.
Animated Color ramps can be used, Timelapse toolbox will simply convert them into nodegroups inside the main group.

=== Turn Ramp Node into a Group ===
Color ramp nodes are super useful in timelapse sequences, video to help explain:
<HTML5video width="720" height="420">rembrand</HTML5video>
As you can see, the color-ramp, with animation, can change a grey scale texture into a progression over time. This can be done with any of the interpolation types, so you can use a constant interpolation to make the effect of 'flakes' falling off - this can be done with an image texture or with voronoi cells texture.
The following interpolation types are supported by timelapse tools:
* Linear
* Constant
* Ease
bezier and cardinal are '''not''' supported, as the math is a bit more complex. However, there is no limit to how many stops you can use, or how you want to animate them (color or position)
However, each timelapse element is not available as an input, which means the only way to 'access' them is through direct driving or animation. This is inconvenient for modularisation, so timelapse toolbox can convert the ramp into a nodegroup with explicit inputs for each element (position, color, or both):
[[file:Ramptogroup.png]]

=== Add a new Channel to Ramp Group ===
Color ramp outputs are quite useful, each element will give us Color and Alpha. The latter can be used to drive (for example) a bump intensity, spec or a mix between multiple shaders. On occasion we'd like more channels per element, to use, for example, for glossiness, bump and roughness. We can't do this to a regular color ramp, but if you've already converted one to a nodegroup, you can simply click on it, hit ctrl-F1 and add a new channel from the menu.

Timelapse toolbox

2016-05-12T23:39:08Z

Bassam: /* Create a Time Driven Group */

File:Ramptogroup.png

2016-05-12T23:32:27Z

Bassam:

Timelapse toolbox

2016-05-12T23:32:12Z

Bassam: /* Turn Ramp Node into a Group */

== Tools for Timelapse Makers in the 3D Editor ==
[[File:timelapsetools.png]]
Currently split into 7 tools, they will affect animation on the object, object-data, modifiers, shapekeys, materials and nodegroups level.
Activate via pie menu with hotkey ctrl F1

=== Curves To Drivers ===
[[File:fcurvestodrivers.png]]
Transforms animation curves mapped to the Frame Start / Frame End of the current scene into drivers based on a property of the active pose bone.
Workflow:
** Select animated objects
** Shift Select a bone with at least one driver you need to use
** Press Ctrl F1 and pick Curves to Drivers from the menu
** If you have more than one property, you will be presented with a popup to select which one to drive from, and then press OK
** Drivers are mapped to the min and max of the property (it should be a float) from frame start and frame end
** The original Actions are not deleted.

=== Drivers To Curves ===
[[File:driverstofcurves.png]]
The Inverse of the previous option, it will copy the drivers mapped from the min/max of the property of the active pose bone into animation curves mapped to frame start/ frame end of the current scene. Workflow:
** select driven objects
** Shift Select a bone with the property you are driving with
** Press Ctrl F1 and pick Drivers to Curves from the menu
** If the bone has more than one property, you will be presented with a menu to select the desired one
** Curves will be created/ mapped to frame start/frame end from the min and max of that property
** The original drivers will '''not''' be deleted, so you will need to do this if you want to see the animation.

=== Display to Render ===
It is often desirable that renderability curves/drivers for the objects or their modifiers match exactly with visibility curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Display to Render from the menu
=== Render to Display ===
It is often desirable that visibility curves/drivers for the objects or their modifiers match exactly with renderability curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Render to Display from the menu
=== Un Drive ===
Once you have drivers on an object it will ignore the animation in actions: In order to see it once again, you will need to remove those drivers. This utility does just that:
** Select driven objects
** Press Ctrl F1 and select Un Drive from the menu
=== Un Curve ===
Once you've finished creating your driven setup you may not want those extra actions hanging around, doing nothing. Use UnCurve to unlink them:
** Select animated objects
** Press Ctrl F1 and select Un Curve to unlink all actions from your objects
=== Show Bools ===
Coming soonish!
== Tools for Timelapse in the node editor (shaders) ==
[[File:TimelapseShaders.png]]
=== Create a Time Driven Group ===
=== Turn Ramp Node into a Group ===
Color ramp nodes are super useful in timelapse sequences, video to help explain:
<HTML5video width="720" height="420">rembrand</HTML5video>
As you can see, the color-ramp, with animation, can change a grey scale texture into a progression over time. This can be done with any of the interpolation types, so you can use a constant interpolation to make the effect of 'flakes' falling off - this can be done with an image texture or with voronoi cells texture.
The following interpolation types are supported by timelapse tools:
* Linear
* Constant
* Ease
bezier and cardinal are '''not''' supported, as the math is a bit more complex. However, there is no limit to how many stops you can use, or how you want to animate them (color or position)
However, each timelapse element is not available as an input, which means the only way to 'access' them is through direct driving or animation. This is inconvenient for modularisation, so timelapse toolbox can convert the ramp into a nodegroup with explicit inputs for each element (position, color, or both):
[[file:Ramptogroup.png]]

=== Add a new Channel to Ramp Group ===

Timelapse toolbox

2016-05-12T23:31:43Z

Bassam: /* Turn Ramp Node into a Group */

== Tools for Timelapse Makers in the 3D Editor ==
[[File:timelapsetools.png]]
Currently split into 7 tools, they will affect animation on the object, object-data, modifiers, shapekeys, materials and nodegroups level.
Activate via pie menu with hotkey ctrl F1

=== Curves To Drivers ===
[[File:fcurvestodrivers.png]]
Transforms animation curves mapped to the Frame Start / Frame End of the current scene into drivers based on a property of the active pose bone.
Workflow:
** Select animated objects
** Shift Select a bone with at least one driver you need to use
** Press Ctrl F1 and pick Curves to Drivers from the menu
** If you have more than one property, you will be presented with a popup to select which one to drive from, and then press OK
** Drivers are mapped to the min and max of the property (it should be a float) from frame start and frame end
** The original Actions are not deleted.

=== Drivers To Curves ===
[[File:driverstofcurves.png]]
The Inverse of the previous option, it will copy the drivers mapped from the min/max of the property of the active pose bone into animation curves mapped to frame start/ frame end of the current scene. Workflow:
** select driven objects
** Shift Select a bone with the property you are driving with
** Press Ctrl F1 and pick Drivers to Curves from the menu
** If the bone has more than one property, you will be presented with a menu to select the desired one
** Curves will be created/ mapped to frame start/frame end from the min and max of that property
** The original drivers will '''not''' be deleted, so you will need to do this if you want to see the animation.

=== Display to Render ===
It is often desirable that renderability curves/drivers for the objects or their modifiers match exactly with visibility curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Display to Render from the menu
=== Render to Display ===
It is often desirable that visibility curves/drivers for the objects or their modifiers match exactly with renderability curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Render to Display from the menu
=== Un Drive ===
Once you have drivers on an object it will ignore the animation in actions: In order to see it once again, you will need to remove those drivers. This utility does just that:
** Select driven objects
** Press Ctrl F1 and select Un Drive from the menu
=== Un Curve ===
Once you've finished creating your driven setup you may not want those extra actions hanging around, doing nothing. Use UnCurve to unlink them:
** Select animated objects
** Press Ctrl F1 and select Un Curve to unlink all actions from your objects
=== Show Bools ===
Coming soonish!
== Tools for Timelapse in the node editor (shaders) ==
[[File:TimelapseShaders.png]]
=== Create a Time Driven Group ===
=== Turn Ramp Node into a Group ===
Color ramp nodes are super useful in timelapse sequences, video to help explain:
<HTML5video width="720" height="420">rembrand</HTML5video>
As you can see, the color-ramp, with animation, can change a grey scale texture into a progression over time. This can be done with any of the interpolation types, so you can use a constant interpolation to make the effect of 'flakes' falling off - this can be done with an image texture or with voronoi cells texture.
The following interpolation types are supported by timelapse tools:
* Linear
* Constant
* Ease
bezier and cardinal are '''not''' supported, as the math is a bit more complex. However, there is no limit to how many stops you can use, or how you want to animate them (color or position)
However, each timelapse element is not available as an input, which means the only way to 'access' them is through direct driving or animation. This is inconvenient for modularisation, so timelapse toolbox can convert the ramp into a nodegroup with explicit inputs for each element (position, color, or both):
[[Ramptogroup.png]]

=== Add a new Channel to Ramp Group ===

Timelapse toolbox

2016-05-12T23:16:32Z

Bassam: /* Turn Ramp Node into a Group */

Timelapse toolbox

2016-05-12T23:03:32Z

Bassam: /* Turn a Ramp Node into a Group */

Timelapse toolbox

2016-05-12T22:24:07Z

Bassam: /* Tools for Timelapse in the node editor (shaders) */

File:TimelapseShaders.png

2016-05-12T22:22:12Z

Bassam:

Timelapse toolbox

2016-05-12T22:21:52Z

Bassam:

Timelapse Assets

2016-05-12T22:16:10Z

Bassam: /* Shaders */

Timelapse Assets

2016-05-12T20:49:33Z

Bassam: /* Animation */

Timelapse Assets

2016-05-12T20:38:23Z

Bassam: /* Creating The Asset */

Timelapse Assets

2016-05-12T20:25:59Z

Bassam: Created page with "== Creating The Asset == Since the asset must show the effect of time, we need to make an animatable group with a time driver that will take from 'creation' to 'death' though..."

Main Page

2016-05-12T20:20:57Z

Bassam: /* Workflow */

== Documentation ==
=== Story ===
* [[Story]]

=== Style and Guidelines ===
* [[Propaganda]]
* [[Advertisement]]
* [[Text]]
* [[Timelapse]]
* [[Color|Color and lighting]]

=== Assets ===
* [[Scripts]]
* [[Rigs]]
* [[Models]]
* [[Assets]]
* [[Software]]

=== Project Management/Communication ===
* [[SVN and Helga access]]
* [[Sparkleshare]]
* [[IRC]]
* 'live' video and voice: [[skype/google hangouts]]

=== Workflow ===
* [[Creating a linkable asset]]
* [[Shot pipeline]]
* [[Layout]]
* [[Animation Notes]]
* [[Hair Sim workflow]]
* [[Lighting and rendering workflow]]
* [[Timelapse Assets]]

=== General ===
* [[Maya to Blender]]
* [[Object and Material ID table]]

Timelapse toolbox

2016-05-12T20:15:51Z

Bassam:

Scripts

2016-05-12T20:10:15Z

Bassam: /* SFX Scripts */

File:Driverstofcurves.png

2016-05-12T20:09:00Z

Bassam:

Timelapse toolbox

2016-05-12T20:08:41Z

Bassam: /* Drivers To Curves */

Timelapse toolbox

2016-05-12T20:05:21Z

Bassam: /* Curves To Drivers */

File:Fcurvestodrivers.png

2016-05-12T20:04:55Z

Bassam:

Timelapse toolbox

2016-05-12T20:03:41Z

Bassam: /* Curves To Drivers */

Timelapse toolbox

2016-05-12T19:37:22Z

Bassam: /* Tools for Timelapse Makers */

File:Timelapsetools.png

2016-05-12T19:27:15Z

Bassam: Bassam uploaded a new version of File:Timelapsetools.png

toolkit for making timelapses

Timelapse tools

2016-05-12T19:13:46Z

Bassam: Bassam moved page Timelapse tools to Timelapse toolbox

#REDIRECT [[Timelapse toolbox]]

Timelapse toolbox

2016-05-12T19:13:45Z

Bassam: Bassam moved page Timelapse tools to Timelapse toolbox

== Tools for Timelapse Makers ==
[[File:timelapsetools.png]]
Currently split into 6 tools, they will affect animation on the object, object-data, modifiers, shapekeys, materials and nodegroups level.
Activate via pie menu with hotkey ctrl F1

=== Curves To Drivers ===
Transforms animation curves mapped to the Frame Start / Frame End of the current scene into drivers based on a property of the active pose bone.
Workflow:
** Select animated objects
** Shift Select a bone with at least one driver you need to use
** Press Ctrl F1 and pick Curves to Drivers from the menu
** If you have more than one property, you will be presented with a popup to select which one to drive from, and then press OK
** Drivers are mapped to the min and max of the property (it should be a float) from frame start and frame end
** The original Actions are not deleted.
=== Drivers To Curves ===
The Inverse of the previous option, it will copy the drivers mapped from the min/max of the property of the active pose bone into animation curves mapped to frame start/ frame end of the current scene. Workflow:
** select driven objects
** Shift Select a bone with the property you are driving with
** Press Ctrl F1 and pick Drivers to Curves from the menu
** If the bone has more than one property, you will be presented with a menu to select the desired one
** Curves will be created/ mapped to frame start/frame end from the min and max of that property
** The original drivers will '''not''' be deleted, so you will need to do this if you want to see the animation.
=== Display to Render ===
It is often desirable that renderability curves/drivers for the objects or their modifiers match exactly with visibility curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Display to Render from the menu
=== Render to Display ===
It is often desirable that visibility curves/drivers for the objects or their modifiers match exactly with renderability curves. This utility simply copies them over:
** Select driven and/ or animated objects
** Press Ctrl F1 and select Render to Display from the menu
=== Un Drive ===
Once you have drivers on an object it will ignore the animation in actions: In order to see it once again, you will need to remove those drivers. This utility does just that:
** Select driven objects
** Press Ctrl F1 and select Un Drive from the menu
=== Un Curve ===
Once you've finished creating your driven setup you may not want those extra actions hanging around, doing nothing. Use UnCurve to unlink them:
** Select animated objects
** Press Ctrl F1 and select Un Curve to unlink all actions from your objects

Text

2016-01-26T00:31:51Z

Bassam: /* English/Roman */

== Mystery Font ==
In the station, we have a variety of text- signs for depos, etc.
Lets call the language 'Sumerian' - not the ancient cuneiform glyphs but a modern language for a utopian current civilization.
With two exceptions we will '''not''' use English / Roman characters for this

Most of the text is not important to read; reading it will distract from the visuals, we mainly need it as a visual element, not a literal one. Thus we can make up fonts!

Style ideas:
<gallery>
File:Text_example.png|example text!
File:Fontexploring.png|exploring fonts
File:Letters2.jpg|another example
File:Letters2.png|more letters
File:Letters!!!.jpg|moar
File:Slightlymorerefinedletters.png|slight refinement
File:Vectorletters.png|vector letters
</gallery>

However, choice of the general shapes of the letters is complicated by usage, I think we can identify 3 general types of lettering:
#signage and print : this should probably be a truetype font that is believable as type (or more than one for simple vs ornate)
#stencil-ish type signage: this should be similar to e.g. [http://www.dafont.com/boston-traffic.font]
#graphiti: we should probably hand draw this in paint programs as needed (not a font file)
#handwritten: could be handdrawn but we could have a 'handwriting' style font. Comic sans Sumerian anybody ?

== English/Roman ==

There are a couple of exceptions to this - We need to read gilgamesh's name in two places:
* Her Dogtags need to have her name in human readable form (maybe both!)
* The book title needs gilgamesh in human readable form. This will likely be a one-word parenthetical in a Sumerian language page

== Numbers ==
Numbers should be Arabic numerals i.e.: 1,2,3,4,5,6,7,8,9

== Add your own language ==
It is encouraged to add words in the artists' own language as occasional elements ( a word here or there, graphitti, other...)

Text

2016-01-26T00:30:57Z

Bassam: /* Mystery Font */

== Mystery Font ==
In the station, we have a variety of text- signs for depos, etc.
Lets call the language 'Sumerian' - not the ancient cuneiform glyphs but a modern language for a utopian current civilization.
With two exceptions we will '''not''' use English / Roman characters for this

Most of the text is not important to read; reading it will distract from the visuals, we mainly need it as a visual element, not a literal one. Thus we can make up fonts!

Style ideas:
<gallery>
File:Text_example.png|example text!
File:Fontexploring.png|exploring fonts
File:Letters2.jpg|another example
File:Letters2.png|more letters
File:Letters!!!.jpg|moar
File:Slightlymorerefinedletters.png|slight refinement
File:Vectorletters.png|vector letters
</gallery>

However, choice of the general shapes of the letters is complicated by usage, I think we can identify 3 general types of lettering:
#signage and print : this should probably be a truetype font that is believable as type (or more than one for simple vs ornate)
#stencil-ish type signage: this should be similar to e.g. [http://www.dafont.com/boston-traffic.font]
#graphiti: we should probably hand draw this in paint programs as needed (not a font file)
#handwritten: could be handdrawn but we could have a 'handwriting' style font. Comic sans Sumerian anybody ?

== English/Roman ==
There are a couple of exceptions to this - We need to read gilgamesh's name in two places:
* Her Dogtags need to have her name in human readable form (maybe both!)
* The book title needs gilgamesh in human readable form.

== Numbers ==
Numbers should be Arabic numerals i.e.: 1,2,3,4,5,6,7,8,9

== Add your own language ==
It is encouraged to add words in the artists' own language as occasional elements ( a word here or there, graphitti, other...)

File:Letters!!!.jpg

2016-01-26T00:23:42Z

Bassam: Bassam uploaded a new version of File:Letters!!!.jpg