Расширенная настройка ИИ - История изменений

DCamer в 21:38, 15 июня 2012

2012-06-15T21:38:26Z

← Предыдущая		Версия 21:38, 15 июня 2012
Строка 1:		Строка 1:
-	~~{{В процессе перевода\|дата=11 января 2012}}~~	+	= Введение =
-		+
-	= Введение~~<br/>~~ =	+

	Несмотря на широкие графические возможности CryENGINE 2, его красивая графика ещё не делает каждый уровень интересным и правильным с точки зрения дизайна уровней. Crysis не только был технической демонстрацией движка, но также преподносил линейный, в то же время ориантированный на выбор игрока геймплей. Это пособие направлено на повышение знаний дизайнеров об игровой настройке ИИ, и создания расширенных возможностей по управлению единицами ИИ в игре, чтобы приспособить их к любым вариантам дизайна уровней. Это руководство предполагает, что вы владеете эементарными техниками дизайна уровней, такими как '''''триггеры'' '''и '''''сценарии flowgraph'''''.		Несмотря на широкие графические возможности CryENGINE 2, его красивая графика ещё не делает каждый уровень интересным и правильным с точки зрения дизайна уровней. Crysis не только был технической демонстрацией движка, но также преподносил линейный, в то же время ориантированный на выбор игрока геймплей. Это пособие направлено на повышение знаний дизайнеров об игровой настройке ИИ, и создания расширенных возможностей по управлению единицами ИИ в игре, чтобы приспособить их к любым вариантам дизайна уровней. Это руководство предполагает, что вы владеете эементарными техниками дизайна уровней, такими как '''''триггеры'' '''и '''''сценарии flowgraph'''''.

-	= Использование нода Entity:BroadcastEvent в своих целях~~<br/> =~~	+	= Использование нода Entity:BroadcastEvent в своих целях =
-		+
-	'''Entity:BroadcastEvent''' is an iterative flowgraph node that is capable of selecting a multitude of entities (on the basis of their names containing a certain string) and then performing an entity event. How does this aid in level design? Instead of manually adding all entities to a given flowgraph for whatever purpose, you can simply set up all your entities with certain names (which you should be doing anyway for organisation's sake!) and then execute one flowgraph node. This means that if you decide to, say, change the amount of enemies in the future, you can simply add them with certain names and not worry about rescripting them. Let’s look at an example of this now in a real level design scenario.	+
-		+
-	~~== Появление ИИ<br/> ==~~	+
-		+
-	~~For the purposes of this tutorial we are only going to apply the effect to two alien troopers, but this will work on much larger groups of AI if necessary.~~	+
-		+
-	~~=== Правила наименования<br/> ==~~=	+

-	Firstly, we need to set our AI up with names that are guaranteed to be unique. I personally use a fairly long string that corresponds to the event in the level. For this particular occasion I have used '''~~CrashSiteAI~~''' ~~as the prefix to the entity names~~ (~~''the actual troopers are CrashSiteAI1 and CrashSiteAI2 respectively''~~).	+	'''Entity:BroadcastEvent''' - итеративный нод, который может выбрать множество сущносте (на основе их имен, содержащих определенную строку), а затем выполняет событие сущности. Как это может помощь в дизайне уровней? Вместо того, чтобы вручную добавлять все сущности к потоковому графу в любых целях, вы можете просто назвать все ваши сущности по определенному (что надо делать в любом случае ради порядка!), а затем выполнять всё в одном ноде. Это означает, что если вы решите, например, изменить количество врагов в будущем, вы можете просто добавить их с определенными именами и не беспокоиться о их рескриптинге. Теперь давайте посмотрим на пример этого в реальном дизайне уровней.

-	==~~= Отключение единиц~~ ИИ ~~при старте<br/> =~~==	+	== Появление ИИ ==
		+	В целях этого руководства мы всего лишь применим эффект к двум труперам, но он будет работать на значительно большем количестве групп ИИ, если необходимо.

-	~~What will happen with these AI? Well~~, ~~I want to disable them until the point where the player triggers a certain event which in this instance is entering a proximity trigger~~. ~~Firstly~~, ~~let's take a look at the necessary setup to disable the AI on game start~~. ~~The flowgraph looks like this:~~	+	=== Правила наименования ===
-	~~<center>[[File:EAIS DisableFG.jpg\|RTENOTITLE]]</center>~~	+	Сначала нам необходимо назвать нашего ИИ таким именем, которые гарантированно будет уникальным. Лично я использую довольно длинную строку, которая соответствует событию на уровне. В данном конкретном случае я использовал '''CrashSiteAI''' в качестве префикса для имени сущностей (''фактически труперы имеют название CrashSiteAI1 и CrashSiteAI2 соответственно.'').
-	~~We want to call the~~ '''~~Disable~~''' ~~event for the troopers~~. You can view a full list of entity events by either viewing the Input/Output section of the entity in the rollup bar, or by adding the entity to a flowgraph and looking at the different options available.	+

-	=== ~~Включение по входу~~ в ~~триггер~~<br/> ~~===~~	+	=== Отключение единиц ИИ при старте ===
		+	Что произойдет с этими ИИ? Ну, я хочу, отключить их до того момента, пока игрок не вызовет определенное событие, которое в данном случае — вход в ProximityTrigger. Сначала давайте взглянем на необходимые настройки для отключения ИИ при начале игры. Потоковый граф выглядит следующим образом:
		+	<center>[[File:EAIS DisableFG.jpg]]</center>
		+	Мы хотим вызвать событие '''Disable''' для труперов. Вы можете просмотреть полный список событий сущности взглянув в разделе «Input/Output» сворачивающейся панели, либо путем добавления сущности в потоковый граф и, просмотром доступных параметров.

-	~~Now we need to call the~~ '''Enable''' ~~event when the player enters the trigger~~. ~~The flowgraph is made in a very similar fashion~~.	+	=== Включение по входу в триггер ===
-	<center>[[File:EAIS EnableFG.jpg~~\|RTENOTITLE~~]]</center>	+	Теперь нам необходимо вызвать событие '''Enable''' когда игрок войдёт в триггер. Потоковый граф делается очень похожим образом.
-	~~More to come in the future on extensible AI setup~~, ~~I hope this has helped some people understand flexible design more and that your projects benefit at least slightly~~. :)	+	<center>[[File:EAIS EnableFG.jpg]]</center>
-	<center>[[File:EAIS cover.jpg~~\|RTENOTITLE~~]]</center>	+	Подробные детали по расширенной настройки ИИ будут в будущем, а пока надеюсь, что это помогло некоторым людям чуть больше понять гибкий дизайн и что это хоть чуть-чуть помогло вашим проектам. :)
-	~~<br/><br/~~>	+	<center>[[File:EAIS cover.jpg]]</center>

-	[[Category:Синглплеер]] ~~<br/>~~	+	[[Category:Синглплеер]]

Alex626 в 13:51, 11 января 2012

2012-01-11T13:51:15Z

← Предыдущая		Версия 13:51, 11 января 2012
Строка 1:		Строка 1:
		+	{{В процессе перевода\|дата=11 января 2012}}
		+
	= Введение<br/> =		= Введение<br/> =

Строка 27:		Строка 29:
	More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :)		More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :)
	<center>[[File:EAIS cover.jpg\|RTENOTITLE]]</center>		<center>[[File:EAIS cover.jpg\|RTENOTITLE]]</center>
-	<br/>[[Category:Синглплеер]] ~~<br/>~~<br/>	+	<br/><br/>
		+
		+	[[Category:Синглплеер]] <br/>

Alex626 в 13:49, 11 января 2012

2012-01-11T13:49:18Z

← Предыдущая		Версия 13:49, 11 января 2012
Строка 1:		Строка 1:
-	=~~Intro~~=	+	= Введение<br/> =

-	~~Despite~~ CryENGINE 2~~'s overwhelming graphics capabilities~~, ~~eye candy does not a level make; as much as~~ Crysis ~~was about being a graphical technical demonstration~~, ~~it is still remembered for its linear yet strongly choice-orientated gameplay~~. ~~This tutorial~~, ~~targeted at any level designers using Sandbox 2~~, aims to provide more information on the set up of the AI included in the game; specifically, making sure your AI setup is extensible and will survive the many design iterations that your level will inevitably undergo. ~~This tutorial assumes you have rudimentary knowledge of certain level design principles such as~~ ''~~triggers~~'' ~~and~~ ''flowgraph ~~scripting~~''.	+	Несмотря на широкие графические возможности CryENGINE 2, его красивая графика ещё не делает каждый уровень интересным и правильным с точки зрения дизайна уровней. Crysis не только был технической демонстрацией движка, но также преподносил линейный, в то же время ориантированный на выбор игрока геймплей. Это пособие направлено на повышение знаний дизайнеров об игровой настройке ИИ, и создания расширенных возможностей по управлению единицами ИИ в игре, чтобы приспособить их к любым вариантам дизайна уровней. Это руководство предполагает, что вы владеете эементарными техниками дизайна уровней, такими как '''''триггеры'' '''и '''''сценарии flowgraph'''''.
		+
		+	= Использование нода Entity:BroadcastEvent в своих целях<br/> =

-	~~=Using the Entity:BroadcastEvent node to your advantage=~~
	'''Entity:BroadcastEvent''' is an iterative flowgraph node that is capable of selecting a multitude of entities (on the basis of their names containing a certain string) and then performing an entity event. How does this aid in level design? Instead of manually adding all entities to a given flowgraph for whatever purpose, you can simply set up all your entities with certain names (which you should be doing anyway for organisation's sake!) and then execute one flowgraph node. This means that if you decide to, say, change the amount of enemies in the future, you can simply add them with certain names and not worry about rescripting them. Let’s look at an example of this now in a real level design scenario.		'''Entity:BroadcastEvent''' is an iterative flowgraph node that is capable of selecting a multitude of entities (on the basis of their names containing a certain string) and then performing an entity event. How does this aid in level design? Instead of manually adding all entities to a given flowgraph for whatever purpose, you can simply set up all your entities with certain names (which you should be doing anyway for organisation's sake!) and then execute one flowgraph node. This means that if you decide to, say, change the amount of enemies in the future, you can simply add them with certain names and not worry about rescripting them. Let’s look at an example of this now in a real level design scenario.

-	==~~Spawning AI~~==	+	== Появление ИИ<br/> ==

	For the purposes of this tutorial we are only going to apply the effect to two alien troopers, but this will work on much larger groups of AI if necessary.		For the purposes of this tutorial we are only going to apply the effect to two alien troopers, but this will work on much larger groups of AI if necessary.

-	===~~Naming Conventions~~===	+	=== Правила наименования<br/> ===

	Firstly, we need to set our AI up with names that are guaranteed to be unique. I personally use a fairly long string that corresponds to the event in the level. For this particular occasion I have used '''CrashSiteAI''' as the prefix to the entity names (''the actual troopers are CrashSiteAI1 and CrashSiteAI2 respectively'').		Firstly, we need to set our AI up with names that are guaranteed to be unique. I personally use a fairly long string that corresponds to the event in the level. For this particular occasion I have used '''CrashSiteAI''' as the prefix to the entity names (''the actual troopers are CrashSiteAI1 and CrashSiteAI2 respectively'').

-	===~~Disabling on Game Start~~===	+	=== Отключение единиц ИИ при старте<br/> ===

	What will happen with these AI? Well, I want to disable them until the point where the player triggers a certain event which in this instance is entering a proximity trigger. Firstly, let's take a look at the necessary setup to disable the AI on game start. The flowgraph looks like this:		What will happen with these AI? Well, I want to disable them until the point where the player triggers a certain event which in this instance is entering a proximity trigger. Firstly, let's take a look at the necessary setup to disable the AI on game start. The flowgraph looks like this:
-		+	<center>[[File:EAIS DisableFG.jpg\|RTENOTITLE]]</center>
-	<center>[[~~Image~~:~~EAIS_DisableFG~~.jpg]]</center>	+
-		+
	We want to call the '''Disable''' event for the troopers. You can view a full list of entity events by either viewing the Input/Output section of the entity in the rollup bar, or by adding the entity to a flowgraph and looking at the different options available.		We want to call the '''Disable''' event for the troopers. You can view a full list of entity events by either viewing the Input/Output section of the entity in the rollup bar, or by adding the entity to a flowgraph and looking at the different options available.

-	===~~Enabling on Trigger Entry~~===	+	=== Включение по входу в триггер<br/> ===

	Now we need to call the '''Enable''' event when the player enters the trigger. The flowgraph is made in a very similar fashion.		Now we need to call the '''Enable''' event when the player enters the trigger. The flowgraph is made in a very similar fashion.
-		+	<center>[[File:EAIS EnableFG.jpg\|RTENOTITLE]]</center>
-	<center>[[~~Image~~:~~EAIS_EnableFG~~.jpg]]</center>	+	More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :)
-		+	<center>[[File:EAIS cover.jpg\|RTENOTITLE]]</center>
-	More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :)	+	<br/>[[Category:Синглплеер]] <br/><br/>
-		+
-	<center>[[~~Image~~:~~EAIS_cover~~.jpg]]</center>	+
-		+
-		+
-	[[~~Категория~~:Синглплеер]]	+

Alex626 в 13:31, 11 января 2012

2012-01-11T13:31:26Z

← Предыдущая		Версия 13:31, 11 января 2012
Строка 1:		Строка 1:
-	=Intro=<br/><br/>Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical demonstration, it is still remembered for its linear yet strongly choice-orientated gameplay. This tutorial, targeted at any level designers using Sandbox 2, aims to provide more information on the set up of the AI included in the game; specifically, making sure your AI setup is extensible and will survive the many design iterations that your level will inevitably undergo. This tutorial assumes you have rudimentary knowledge of certain level design principles such as ''triggers'' and ''flowgraph scripting''.<br/><br/>=Using the Entity:BroadcastEvent node to your advantage=<br/>'''Entity:BroadcastEvent''' is an iterative flowgraph node that is capable of selecting a multitude of entities (on the basis of their names containing a certain string) and then performing an entity event. How does this aid in level design? Instead of manually adding all entities to a given flowgraph for whatever purpose, you can simply set up all your entities with certain names (which you should be doing anyway for organisation's sake!) and then execute one flowgraph node. This means that if you decide to, say, change the amount of enemies in the future, you can simply add them with certain names and not worry about rescripting them. Let’s look at an example of this now in a real level design scenario.<br/><br/>==Spawning AI==<br/><br/>For the purposes of this tutorial we are only going to apply the effect to two alien troopers, but this will work on much larger groups of AI if necessary.<br/><br/>===Naming Conventions===<br/><br/>Firstly, we need to set our AI up with names that are guaranteed to be unique. I personally use a fairly long string that corresponds to the event in the level. For this particular occasion I have used '''CrashSiteAI''' as the prefix to the entity names (''the actual troopers are CrashSiteAI1 and CrashSiteAI2 respectively'').<br/><br/>===Disabling on Game Start===<br/><br/>What will happen with these AI? Well, I want to disable them until the point where the player triggers a certain event which in this instance is entering a proximity trigger. Firstly, let's take a look at the necessary setup to disable the AI on game start. The flowgraph looks like this:<br/><br/><center>[[File:EAIS DisableFG.jpg\|RTENOTITLE]]</center><br/><br/>We want to call the '''Disable''' event for the troopers. You can view a full list of entity events by either viewing the Input/Output section of the entity in the rollup bar, or by adding the entity to a flowgraph and looking at the different options available.<br/><br/>===Enabling on Trigger Entry===<br/><br/>Now we need to call the '''Enable''' event when the player enters the trigger. The flowgraph is made in a very similar fashion.<br/><br/><center>[[File:EAIS EnableFG.jpg\|RTENOTITLE]]</center><br/><br/>More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :)<br/><br/><center>[[File:EAIS cover.jpg\|RTENOTITLE]]</center><br/>	+	=Intro=

-	[[~~Category~~:~~Синглплеер\|Singleplayer~~]]<br/><br/>	+	Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical demonstration, it is still remembered for its linear yet strongly choice-orientated gameplay. This tutorial, targeted at any level designers using Sandbox 2, aims to provide more information on the set up of the AI included in the game; specifically, making sure your AI setup is extensible and will survive the many design iterations that your level will inevitably undergo. This tutorial assumes you have rudimentary knowledge of certain level design principles such as ''triggers'' and ''flowgraph scripting''.
		+
		+	=Using the Entity:BroadcastEvent node to your advantage=
		+	'''Entity:BroadcastEvent''' is an iterative flowgraph node that is capable of selecting a multitude of entities (on the basis of their names containing a certain string) and then performing an entity event. How does this aid in level design? Instead of manually adding all entities to a given flowgraph for whatever purpose, you can simply set up all your entities with certain names (which you should be doing anyway for organisation's sake!) and then execute one flowgraph node. This means that if you decide to, say, change the amount of enemies in the future, you can simply add them with certain names and not worry about rescripting them. Let’s look at an example of this now in a real level design scenario.
		+
		+	==Spawning AI==
		+
		+	For the purposes of this tutorial we are only going to apply the effect to two alien troopers, but this will work on much larger groups of AI if necessary.
		+
		+	===Naming Conventions===
		+
		+	Firstly, we need to set our AI up with names that are guaranteed to be unique. I personally use a fairly long string that corresponds to the event in the level. For this particular occasion I have used '''CrashSiteAI''' as the prefix to the entity names (''the actual troopers are CrashSiteAI1 and CrashSiteAI2 respectively'').
		+
		+	===Disabling on Game Start===
		+
		+	What will happen with these AI? Well, I want to disable them until the point where the player triggers a certain event which in this instance is entering a proximity trigger. Firstly, let's take a look at the necessary setup to disable the AI on game start. The flowgraph looks like this:
		+
		+	<center>[[Image:EAIS_DisableFG.jpg]]</center>
		+
		+	We want to call the '''Disable''' event for the troopers. You can view a full list of entity events by either viewing the Input/Output section of the entity in the rollup bar, or by adding the entity to a flowgraph and looking at the different options available.
		+
		+	===Enabling on Trigger Entry===
		+
		+	Now we need to call the '''Enable''' event when the player enters the trigger. The flowgraph is made in a very similar fashion.
		+
		+	<center>[[Image:EAIS_EnableFG.jpg]]</center>
		+
		+	More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :)
		+
		+	<center>[[Image:EAIS_cover.jpg]]</center>
		+
		+
		+	[[Категория:Синглплеер]]

Alex626: Новая страница: «=Intro=

Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical d...»

2012-01-11T13:30:27Z

Новая страница: «=Intro= Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical d...»

Новая страница

=Intro= Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical demonstration, it is still remembered for its linear yet strongly choice-orientated gameplay. This tutorial, targeted at any level designers using Sandbox 2, aims to provide more information on the set up of the AI included in the game; specifically, making sure your AI setup is extensible and will survive the many design iterations that your level will inevitably undergo. This tutorial assumes you have rudimentary knowledge of certain level design principles such as ''triggers'' and ''flowgraph scripting''. =Using the Entity:BroadcastEvent node to your advantage= '''Entity:BroadcastEvent''' is an iterative flowgraph node that is capable of selecting a multitude of entities (on the basis of their names containing a certain string) and then performing an entity event. How does this aid in level design? Instead of manually adding all entities to a given flowgraph for whatever purpose, you can simply set up all your entities with certain names (which you should be doing anyway for organisation's sake!) and then execute one flowgraph node. This means that if you decide to, say, change the amount of enemies in the future, you can simply add them with certain names and not worry about rescripting them. Let’s look at an example of this now in a real level design scenario. ==Spawning AI== For the purposes of this tutorial we are only going to apply the effect to two alien troopers, but this will work on much larger groups of AI if necessary. ===Naming Conventions=== Firstly, we need to set our AI up with names that are guaranteed to be unique. I personally use a fairly long string that corresponds to the event in the level. For this particular occasion I have used '''CrashSiteAI''' as the prefix to the entity names (''the actual troopers are CrashSiteAI1 and CrashSiteAI2 respectively''). ===Disabling on Game Start=== What will happen with these AI? Well, I want to disable them until the point where the player triggers a certain event which in this instance is entering a proximity trigger. Firstly, let's take a look at the necessary setup to disable the AI on game start. The flowgraph looks like this: <center>[[File:EAIS DisableFG.jpg|RTENOTITLE]]</center> We want to call the '''Disable''' event for the troopers. You can view a full list of entity events by either viewing the Input/Output section of the entity in the rollup bar, or by adding the entity to a flowgraph and looking at the different options available. ===Enabling on Trigger Entry=== Now we need to call the '''Enable''' event when the player enters the trigger. The flowgraph is made in a very similar fashion. <center>[[File:EAIS EnableFG.jpg|RTENOTITLE]]</center> More to come in the future on extensible AI setup, I hope this has helped some people understand flexible design more and that your projects benefit at least slightly. :) <center>[[File:EAIS cover.jpg|RTENOTITLE]]</center> 

[[Category:Синглплеер|Singleplayer]]

Расширенная настройка ИИ - История изменений

DCamer в 21:38, 15 июня 2012

Alex626 в 13:51, 11 января 2012

Alex626 в 13:49, 11 января 2012

Alex626 в 13:31, 11 января 2012

Alex626: Новая страница: «=Intro=Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical d...»

Alex626: Новая страница: «=Intro=

Despite CryENGINE 2's overwhelming graphics capabilities, eye candy does not a level make; as much as Crysis was about being a graphical technical d...»