Game Design Procedural Procworld Grammar Time - Revision history

Shealladh at 08:03, 29 November 2015

2015-11-29T08:03:53Z

Shealladh at 08:01, 29 November 2015

2015-11-29T08:01:44Z

Shealladh at 08:00, 29 November 2015

2015-11-29T08:00:40Z

Shealladh at 07:55, 29 November 2015

2015-11-29T07:55:33Z

Shealladh at 07:54, 29 November 2015

2015-11-29T07:54:48Z

Shealladh: Created page with "Yes, grammars. The last update had a hint of this, but here you can see them in more detail. As you probably know, we are building a repertoire of architectural grammars. The..."

2015-11-29T07:48:30Z

Created page with "Yes, grammars. The last update had a hint of this, but here you can see them in more detail. As you probably know, we are building a repertoire of architectural grammars. The..."

New page

Yes, grammars. The last update had a hint of this, but here you can see them in more detail. As you probably know, we are building a repertoire of architectural grammars. The following video shows a few of them:

https://www.youtube.com/watch?feature=player_embedded&v=scacfkd_Tao

This set is geared towards medieval, fantasy settings, but I suspect most of these grammars would hold for a different theme.

This system becomes very interesting once you consider ending building blocks could be replaced by elements that tie closely to your project's vision. At any time you could replace the arches, columns, ornaments, even bricks, by custom components you may have sculpted earlier. What the grammar gives you is the order and structure of these prefabs, but the final look and feel can be pretty much up to you.

As you can see for the moment we are focusing on smaller grammars. You can think of these as smart brushes that will allow to lay walls, floors, bridges, even towers in the locations you choose.

While grammars are able to express entire buildings (even cities), I believe we need to start small and allow you to place these smaller elements following your imagination. Also there is little point in generating an entire castle if the building elements are not interesting enough. So we are making sure we have a solid repertoire of grammars before we take on larger things. Even something as simple as a basic stair tool can save you a lot of time.

stairs.png

As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.

==[[Game_Design_Procedural_Procworld_Real men don't draw buildings|Real men don't draw buildings]]==
Real men -and women- don't draw buildings, they write them. Why limit yourself to one instance of a building when you could define an entire family?

It turns out writing building '''grammars''' is hard, it feels closer to programming. For procedural architecture to take off, creation tools must appeal to artists. All we have now are maddening languages and graph editors. Only a few artists have the skills to make any sense of them. I would like to find a solution for this, but I got nothing so far.

I have created a timelapse video where you can see me creating a grammar from scratch. It is for a family of simple, rustic houses like this one:

<center>
{|
|+ style="caption-side:bottom; color:#000000;"|This is a rendering of the triangles output by the grammar evaluation. This model has not been altered by hand.
| [[File:demohouse.png|900px|center|link= ]]
|}
</center>

<center>
{|
|+ style="caption-side:top; color:#e76700;"|'''Here is the video'''
| [[File:VoxelStudio - Creating a house.png|500px|center|link=https://www.youtube.com/watch?v=V04dswEIcQU]]
|}
</center>

==Ideas==
* Example of why we want to use Procedural grammars.
** Using this method, [[Game_Concept_ShieldKings|ShieldKings]] could enable [[Hârn_Maps|Hârn style maps]] of a building that the Player wishes to create, either via an architect template/blueprint, or if they have the Skills, design their own.
*** Creating '''grammars''' that include Tiles, Bricks, and other components that are assembled into a '''grammar''' set. '''''See''''' [[Grammar Time]]

=='''Breakdown of Grammars'''==
List here how a grammar works, into a workflow to create the idea.
* [[Link|Link Name]]
** [[Link|Link Name]]
* [[Link|Link Name]]
** [[Link|Link Name]]

=Notes=
* [http://procworld.blogspot.com.au/2012/02/real-men-dont-draw-buildings.html Procedural World Blog]
*

[[Category:Research]] [[Category:Game Design]] [[Category:Articles]] [[Category:Procedural]] [[Category:Procedural World Blog]]

@@ Line 18: / Line 18: @@
 While grammars are able to express entire buildings (even cities), I believe we need to start small and allow you to place these smaller elements following your imagination. Also there is little point in generating an entire castle if the building elements are not interesting enough. So we are making sure we have a solid repertoire of grammars before we take on larger things. Even something as simple as a basic stair tool can save you a lot of time.
-[[File:stairs.png|320|center|link= ]]
+[[File:stairs.png|320px|center|link= ]]
 As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.

@@ Line 18: / Line 18: @@
 While grammars are able to express entire buildings (even cities), I believe we need to start small and allow you to place these smaller elements following your imagination. Also there is little point in generating an entire castle if the building elements are not interesting enough. So we are making sure we have a solid repertoire of grammars before we take on larger things. Even something as simple as a basic stair tool can save you a lot of time.
-[[File:stairs.png|center|320|link= ]]
+[[File:stairs.png|320|center|link= ]]
 As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.

@@ Line 18: / Line 18: @@
 While grammars are able to express entire buildings (even cities), I believe we need to start small and allow you to place these smaller elements following your imagination. Also there is little point in generating an entire castle if the building elements are not interesting enough. So we are making sure we have a solid repertoire of grammars before we take on larger things. Even something as simple as a basic stair tool can save you a lot of time.
-[[File:stairs.png|center|link= ]]
+[[File:stairs.png|center|320|link= ]]
 As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.

← Older revision		Revision as of 07:55, 29 November 2015
Line 21:		Line 21:

	As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.		As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.
−
−
−	~~==[[Game_Design_Procedural_Procworld_Real men don't draw buildings\|Real men don't draw buildings]]==~~
−	~~Real men -and women- don't draw buildings, they write them. Why limit yourself to one instance of a building when you could define an entire family?~~
−
−	It turns out writing building '''<span style="color:#e76700">grammars</span>''' is hard, it feels closer to programming. For procedural architecture to take off, creation tools must appeal to artists. All we have now are maddening languages and graph editors. Only a few artists have the skills to make any sense of them. I would like to find a solution for this, but I got nothing so far.
−
−	~~I have created a timelapse video where you can see me creating a grammar from scratch. It is for a family of simple, rustic houses like this one:~~
−
−	~~<center>~~
−	{\|
−	~~\|+ style="caption-side:top; color:#e76700;"\|'''Here is the video'''~~
−	~~\| [[File:VoxelStudio - Creating a house.png\|500px\|center\|link=https://www.youtube.com/watch?v=V04dswEIcQU]]~~
−	\|}
−	~~</center>~~

@@ Line 1: / Line 1: @@
-Yes, grammars. The last update had a hint of this, but here you can see them in more detail. As you probably know, we are building a repertoire of architectural grammars. The following video shows a few of them:
+==[[Game_Design_Procedural_Procworld_Grammar Time|Grammar Time]]==
-https://www.youtube.com/watch?feature=player_embedded&v=scacfkd_Tao
+Yes, grammars. The last update had a hint of this, but here you can see them in more detail. As you probably know, we are building a repertoire of architectural grammars.
 This set is geared towards medieval, fantasy settings, but I suspect most of these grammars would hold for a different theme.
@@ Line 11: / Line 18: @@
 While grammars are able to express entire buildings (even cities), I believe we need to start small and allow you to place these smaller elements following your imagination. Also there is little point in generating an entire castle if the building elements are not interesting enough. So we are making sure we have a solid repertoire of grammars before we take on larger things. Even something as simple as a basic stair tool can save you a lot of time.
-stairs.png
+[[File:stairs.png|center|link= ]]
 As usual let me know what you think. I'm in particular interested in how many of these do you think we would need for a particular theme, how generic or specific they should be, what kind of parameters would you like to have as inputs.
@@ Line 22: / Line 29: @@
 I have created a timelapse video where you can see me creating a grammar from scratch. It is for a family of simple, rustic houses like this one:
 <center>
@@ Line 39: / Line 39: @@
 ==Ideas==
-* Example of why we want to use Procedural grammars.
+*  Architectural Grammars.
-** Using this method, [[Game_Concept_ShieldKings|ShieldKings]] could enable [[Hârn_Maps|Hârn style maps]] of a building that the Player wishes to create, either via an architect template/blueprint, or if they have the Skills, design their own.
-*** Creating '''<span style="color:#e76700">grammars</span>''' that include Tiles, Bricks, and other components that are assembled into a '''<span style="color:#e76700">grammar</span>''' set. '''''See''''' [[Grammar Time]]
-=='''<span style="color:#e76700">Breakdown of Grammars</span>'''==
+=='''<span style="color:#e76700">Breakdown of Architectural Grammars</span>'''==
 List here how a grammar works, into a workflow to create the idea.
 * [[Link|Link Name]]
@@ Line 53: / Line 51: @@
 =Notes=
-* [http://procworld.blogspot.com.au/2012/02/real-men-dont-draw-buildings.html Procedural World Blog]
+* [http://procworld.blogspot.com.au/2014/05/grammar-time.html Procedural World Blog]
+*
 [[Category:Research]] [[Category:Game Design]] [[Category:Articles]]  [[Category:Procedural]]  [[Category:Procedural World Blog]]