BlenderWiki - Recent changes [en]

Doc:CA/Manual/Introduction/Installing Blender

85.58.85.21 — Fri, 20 Nov 2009 21:53:39 GMT

Baixant-vos i instal·lant la distribució binària:

← Older revision		Revision as of 21:53, 20 November 2009
(One intermediate revision not shown)
Line 19:		Line 19:

	Els sistemes operatius Linux disposen de binaris per a dues arquitectures de maquinari x86 diferents (processadors Intel i AMD) i per a PowerPC, i la possibilitat d'escollir entre biblioteques enllaçades estàticament o biblioteques carregades dinàmicament.		Els sistemes operatius Linux disposen de binaris per a dues arquitectures de maquinari x86 diferents (processadors Intel i AMD) i per a PowerPC, i la possibilitat d'escollir entre biblioteques enllaçades estàticament o biblioteques carregades dinàmicament.
-	~~<!--~~
-	The difference between the dynamic and the static binaries is important. The static binarie has the OpenGL libraries compiled in. This makes Blender run on your system without using hardware accelerated graphics. Use the static version if the dynamic version fails! OpenGL is used in Blender for all drawing, including menus and buttons. For this, you will need OpenGL installed on your system. This dependency makes a proper and compliant OpenGL installation at your system a requirement. Generally speaking integrated graphics chips and older low end graphics cards will perform poorly or not at all with Blender due to their poor support for OpenGL. (It is ofter possible to work around the poor OpenGL support of such cards by using software based OpenGL solutions such as by turning down or off hardware accelleration on Windows, or using software MESA OpenGL on Linux).

		+	La diferència entre biblioteques estàtiques i dinàmiques és important. El binari estàtic conté les biblioteques OpenGL compilades. Això permet que pugueu fer córrer el Blender al vostre sistema sense usar gràfics accelerats per maquinari. Useu la versió estàtica si la versió dinàmica falla! L'OpenGL s'usa al Blender per a totes les funcions de dibuix, incloent-hi els menús i els botons. Per això necessitareu que l'OpenGL estigui instal·lat al vostre sistema. Aquesta dependència fa que sigui un requeriment una instal·lació apropiada i compatible amb l'OpenGL. En general els xips gràfics integrats i les targes gràfiques antigues de gama baixa funcionaran de manera pobre o no funcionaran amb el Blender degut al seu pobre suport per a l'OpenGL. (Sovint és possible esquivar el pobre suport OpenGL d'aquestes targes usant solucions OpenGL basades en programari, com desconnectar l'acceleració de maquinari en Windows, o usar el programari MESA OpenGL en Linux).
		+	<!--
	Rendering is done by the Blender rendering engine in core memory and by the main CPU of your machine, so a unsupported graphics card will not have an impact if you use the machine only for rendering (as would be the case for a rendering farm).		Rendering is done by the Blender rendering engine in core memory and by the main CPU of your machine, so a unsupported graphics card will not have an impact if you use the machine only for rendering (as would be the case for a rendering farm).

Doc:Manual/Game Engine/Logic/Object type

Mindrones — Fri, 20 Nov 2009 21:46:42 GMT

← Older revision		Revision as of 21:46, 20 November 2009
Line 1:		Line 1:
-	{{Page/Header\|?\|Doc:Manual/Game Engine/Logic\|Doc:Manual/Game Engine/Logic/~~Properties~~}}	+	{{Page/Header\|2.49\|Doc:Manual/Game Engine/Logic\|Doc:Manual/Game Engine/Logic/Object type/Occluder}}

-	~~{{Note\|1~~=~~Warning\|2~~=~~This description is a bit outdated, especially because the GUI has changed in the last releases… But the general meaning of the controls remains the same, so it’s still useful!}}~~	+	= Object types =

-	~~[[Image:GM_Actors_Menu~~.~~png~~\|~~frame\|right\|The Actors controls~~.]]	+	You can have several object types. The {{Literal\|Object type}} menu is where you define all properties associated with active objects. Active objects are evaluated by the physics engine and treated as more than simple world objects.

-	The Actors Menu is where you define all properties associated with active objects. Active objects are evaluated by the physics engine and treated as more than simple world objects. We will look at each button individually and what it means.	+	You can choose these object types:
-	~~{{clr}}~~	+	* [[Doc:Manual/Game Engine/Logic/Object type/Occluder\|Occluder]]
		+	* [[Doc:Manual/Game Engine/Logic/Object type/No collision\|No collision]]
		+	* [[Doc:Manual/Game Engine/Logic/Object type/Sensor\|Sensor]]
		+	* [[Doc:Manual/Game Engine/Logic/Object type/Static\|Static]]
		+	* [[Doc:Manual/Game Engine/Logic/Object type/Dynamic\|Dynamic]]
		+	* [[Doc:Manual/Game Engine/Logic/Object type/Rigid body\|Rigid body]]
		+	* [[Doc:Manual/Game Engine/Logic/Object type/Soft body\|Soft body]]

-	~~==Actor==~~	+	{{Page/Footer\|Doc:Manual/Game Engine/Logic\|Doc:Manual/Game Engine/Logic/Object type/Occluder}}
-	By default this button occurs switched off and alone ([[Image:GM_Actors_Undepressed_Button.png]]). Once pressed it gives you the option of {{Literal\|Ghost}} or {{Literal\|Dynamic}} ([[Image:GM_Actors_Active_Button.png]]). This causes the physics engine to evaluate your object, causing your object to be seen as more than part of the world (a simple wall or floor). This object can now be seen by other active objects.	+
-		+
-	At this point your object is not affected by normal physics (e.g. gravity) but is seen as more than just a background object. This is useful for interaction between objects that need not have physics properties, such as gravity, e.g. a button on a wall.	+
-	~~{{clr}}~~	+
-		+
-	~~==Ghost==~~	+
-	{{Literal\|Ghost}} gives the object the ability to pass through other objects. This helps save processing time while calculating objects’ physics (e.g. bouncing, friction, etc.). A collision with another object is still detected and reported to your game logic.	+
-	~~{{clr}}~~	+
-		+
-	~~==Dynamic==~~	+
-	Once activated, this gives your object real physics properties. Your object will now be pulled by gravity, bounce off other objects, have mass and be slowed by friction. You will also now see a much large list of buttons on the menu, each of which aids you in setting up different physics properties for your game.	+
-	~~{{clr}}~~	+
-		+
-	~~==Rigid Body==~~	+
-	This enables rolling physics, giving objects a life-like feel. If a ball drops on a level surface naturally, it would seem strange if it just came to a halt. With rolling physics enabled your ball even dropping on a perfectly level surface and will roll as a natural object would.	+
-	~~{{clr}}~~	+
-		+
-	~~==No Sleeping==~~	+
-	By default if and object that is affected by rolling physics comes to a rest, Rolling Physics is disabled. The physic engine assumes that it no longer needs to calculate the object’s motion. In some case this is true and will save you processing power, in other case such as in a soccer game, the physics needs to be maintained until someone kicks the ball placing it back in motion.	+
-	~~{{clr}}~~	+
-		+
-	~~==Do Fh==~~	+
-	This causes your object to interact with [[Doc:Manual/Game Engine/Dynamic Materials\|Dynamic Materials]]. This is currently not supported by the default bullet physics and is not fully supported in the Sumo engine in the current edition of Blender. It is fully supported by version 2.24 of Blender.	+
-	~~{{clr}}~~	+
-		+
-	~~==Rot Fh==~~	+
-	~~This option causes the Z axis to be pointed away from a [[Doc:Manual/Game Engine/Dynamic Materials\|Dynamic Materials]]. This is activated by {{Literal\|Do Fh}}.~~	+
-	~~{{clr}}~~	+
-		+
-	~~==Mass==~~	+
-	{{Literal\|Mass}} affects the amount of force that is required to move an object. The greater the mass the greater the force that need to be applied to the object in order to move the object. Mass will not cause objects to fall faster or slower. To slow an object down use [[#Damp\|dampening]], if you wish to accelerate the falling rate increase [[Attic:Incomplete/Game Engine/World Settings\|gravity]] (normal gravity is 9.81).	+
-	~~{{clr}}~~	+
-		+
-	~~==Size==~~	+
-	This determines the size of the bounding area. This can be change to a large or smaller size to give your object the look and feel you desire. The shape of the bounding area is determined by the {{Literal\|Bounds}} button, by default it is a {{Literal\|Box}}.	+
-		+
-	When changing the bounding size you can see the effect on the screen, in the shape of a circle. At this point in time all bounding shapes are reflected as a circle in the 3D window, even though they react differently during the game play.	+
-	~~{{clr}}~~	+
-		+
-	~~==Form==~~	+
-	~~The {{Literal\|Form}} factor gives you a degree of control over rigid body objects. The higher the {{Literal\|Form}} factor, the less likely an object is to roll, especially rolling on a flat surface.~~	+
-	~~{{clr}}~~	+
-		+
-	~~==Damp==~~	+
-	~~Dampening affects the freedom of an object to move. In space there should be almost no dampening, while in water the dampening should be set quite high.~~	+
-	~~{{clr}}~~	+
-		+
-	~~==RotDamp==~~	+
-	~~Rotational Dampening is the same as dampening but only affects the object’s rotation. A high Rotational Dampening will not affect the rest of the object’s momentum.~~	+
-	~~{{clr}}~~	+
-		+
-	~~==Anisotropic==~~	+
-	This controls the direction of friction in the X, Y or Z direction. Anisotropic is relative to the amount of friction in a particular direction. For example, take the wheel of a skate board, the forward direction should rotate easily, yet a sideward motion should be difficult and decreased by a higher level of friction.	+
-	~~{{clr}}~~	+
-		+
-	~~==Bounds==~~	+
-	~~[[Image:GM_Actors_Bounding_Menu.png\|right]]~~	+
-		+
-	The Blender Game Engine has a number of ways of dealing with the shapes of objects. The reason that the game engine avoids highly accurate, per face object collisions, is due to the high level of processing power that it would demand. It is often faster, during game play, to uses a simpler system such as a box or a sphere for an object that’s shape is very similar.	+
-		+
-	~~[[Image:GM_Actors_Object_Centre.png\|right]]~~	+
-		+
-	The bounds are calculated from the object’s centre, which is designated by the pink dot normally at the centre of your object. It is not uncommon or useful to move this centre to a more convenient location. This can be done in the {{Literal\|Editing}} context ({{Shortcut\|f9}}) and choosing one of the 3 options that focus around Centre movement (see [[Doc:Reference/Panels/Editing/Mesh\|Mesh]] for more info).	+
-		+
-	~~{{Literal\|Convex Hull}} and static {{Literal\|Triangle Mesh}} are designed for uses with World objects floors, walls, trees, etc.~~	+
-		+
-	~~Blender has no generic way of interacting with hollow objects. An example, which would be difficult to create, would be a cup to shake dice in.~~	+
-	~~{{clr}}~~	+
-		+
-	{{Page/Footer\|Doc:Manual/Game Engine/Logic\|Doc:Manual/Game Engine/Logic/~~Properties~~}}	+

	[[Category:Game engine]]		[[Category:Game engine]]

Doc:Manual/Game Engine/Logic/Object type/Soft body

Mindrones — Fri, 20 Nov 2009 21:45:45 GMT

Created page with '{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Rigid body|Doc:Manual/Game Engine/Logic/Properties}} = Soft body object type = [[File:GameEngine_ObjectType_SoftBody…'

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Rigid body|Doc:Manual/Game Engine/Logic/Properties}}

= Soft body object type =

[[File:GameEngine_ObjectType_SoftBody.png|right|thumb|300px|Soft body]]

Physical object, deforms on collision.
{{clr}}

{{Doc:Manual/Game Engine/Logic/Object type/actor}}
{{Doc:Manual/Game Engine/Logic/Object type/ghost}}
{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}

== Advanced ==

Collision advanced settings.
 
{{Doc:Manual/Game_Engine/Logic/Object_type/mass}}

== Shape match ==

Enables softbody shape matching goal

== Bending Const ==

Enables bending contraints

== LinStiff ==

Linear stiffness of the softbody links

== Friction ==

Dynamic friction

== kMT ==

Shape matching threshold
 
{{Doc:Manual/Game_Engine/Logic/Object_type/bounds}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type/Rigid body|Doc:Manual/Game Engine/Logic/Properties}}

Doc:Manual/Game Engine/Logic/Object type/Rigid body

Mindrones — Fri, 20 Nov 2009 21:44:52 GMT

Created page with '{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Dynamic|Doc:Manual/Game Engine/Logic/Object type/Soft body}} = Rigid body object type = [[File:GameEngine_ObjectType…'

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Dynamic|Doc:Manual/Game Engine/Logic/Object type/Soft body}}

= Rigid body object type =

[[File:GameEngine_ObjectType_RigidBody.png|right|thumb|300px|Rigid body]]

This enables rolling physics, giving objects a life-like feel. If a ball drops on a level surface naturally, it would seem strange if it just came to a halt. With rolling physics enabled your ball even dropping on a perfectly level surface and will roll as a natural object would.
{{clr}}

{{Doc:Manual/Game Engine/Logic/Object type/actor}}
{{Doc:Manual/Game Engine/Logic/Object type/ghost}}
{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}

== Advanced ==

Collision advanced settings.
 
{{Doc:Manual/Game_Engine/Logic/Object_type/mass}}
{{Doc:Manual/Game_Engine/Logic/Object_type/radius}}
{{Doc:Manual/Game Engine/Logic/Object type/no sleeping}}
 
{{Doc:Manual/Game Engine/Logic/Object type/damp}}
{{Doc:Manual/Game Engine/Logic/Object type/rotdamp}}
 
{{Doc:Manual/Game Engine/Logic/Object type/do fh}}
{{Doc:Manual/Game Engine/Logic/Object type/rot fh}}
{{Doc:Manual/Game_Engine/Logic/Object_type/form}}
{{Doc:Manual/Game_Engine/Logic/Object_type/anisotropic}}
 
{{Doc:Manual/Game_Engine/Logic/Object_type/bounds}}
{{clr}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type/Dynamic|Doc:Manual/Game Engine/Logic/Object type/Soft body}}

Doc:Manual/Game Engine/Logic/Object type/Dynamic

Mindrones — Fri, 20 Nov 2009 21:44:06 GMT

Created page with '{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Static|Doc:Manual/Game Engine/Logic/Object type/Rigid body}} = Dynamic object type = [[File:GameEngine_ObjectType_Dy…'

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Static|Doc:Manual/Game Engine/Logic/Object type/Rigid body}}

= Dynamic object type =

[[File:GameEngine_ObjectType_Dynamic.png|right|thumb|300px|Dynamic]]

Once activated, this gives your object real physics properties. Your object will now be pulled by gravity, bounce off other objects, have mass and be slowed by friction.
{{clr}}

{{Doc:Manual/Game Engine/Logic/Object type/actor}}
{{Doc:Manual/Game Engine/Logic/Object type/ghost}}
{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}

== Advanced ==

Collision advanced settings.
 
{{Doc:Manual/Game_Engine/Logic/Object_type/mass}}
{{Doc:Manual/Game_Engine/Logic/Object_type/radius}}
{{Doc:Manual/Game Engine/Logic/Object type/no sleeping}}
 
{{Doc:Manual/Game Engine/Logic/Object type/damp}}
{{Doc:Manual/Game Engine/Logic/Object type/rotdamp}}
 
{{Doc:Manual/Game Engine/Logic/Object type/do fh}}
{{Doc:Manual/Game Engine/Logic/Object type/rot fh}}
{{Doc:Manual/Game_Engine/Logic/Object_type/form}}
{{Doc:Manual/Game_Engine/Logic/Object_type/anisotropic}}
 
{{Doc:Manual/Game_Engine/Logic/Object_type/bounds}}
{{clr}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type/Static|Doc:Manual/Game Engine/Logic/Object type/Rigid body}}

Doc:Manual/Game Engine/Logic/Object type/Static

Mindrones — Fri, 20 Nov 2009 21:43:20 GMT

Created page with '{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Sensor|Doc:Manual/Game Engine/Logic/Object type/Dynamic}} = Static object type = [[File:GameEngine_ObjectType_Static…'

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Sensor|Doc:Manual/Game Engine/Logic/Object type/Dynamic}}

= Static object type =

[[File:GameEngine_ObjectType_Static.png|right|thumb|300px|Static]]

Physical object, but not affected by gravity.
{{clr}}

{{Doc:Manual/Game Engine/Logic/Object type/actor}}
{{Doc:Manual/Game Engine/Logic/Object type/ghost}}
{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}

== Advanced ==

Collision advanced settings.

{{Doc:Manual/Game_Engine/Logic/Object_type/anisotropic}}

{{Doc:Manual/Game_Engine/Logic/Object_type/bounds}}
{{clr}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type/Sensor|Doc:Manual/Game Engine/Logic/Object type/Dynamic}}

Doc:Manual/Game Engine/Logic/Object type/Sensor

Mindrones — Fri, 20 Nov 2009 21:42:06 GMT

Created page with '{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/No collision|Doc:Manual/Game Engine/Logic/Object type/Static}} = Sensor object type = [[File:GameEngine_ObjectType_S…'

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/No collision|Doc:Manual/Game Engine/Logic/Object type/Static}}

= Sensor object type =

[[File:GameEngine_ObjectType_Sensor.png|right|thumb|300px|Sensor]]

The object detects static and dynamic objects but not other collisions sensors objects.
{{clr}}

== Detect actor ==

Sensor should detect only the objects with Actor option enabled. Unset to detect all objects.

{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}

== Advanced ==

Collision advanced settings.

{{Doc:Manual/Game_Engine/Logic/Object_type/bounds}}
{{clr}}

= Technical specifications =

(from Blender 2.49 Release Notes)

{{Template:Release Notes/2.49/Game Engine/Physics/sensor object type}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type/No collision|Doc:Manual/Game Engine/Logic/Object type/Static}}

Doc:Manual/Game Engine/Logic/Object type/No collision

Mindrones — Fri, 20 Nov 2009 21:40:14 GMT

Created page with '{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Occluder|Doc:Manual/Game Engine/Logic/Object type/Sensor}} = No collision object type = [[File:GameEngine_ObjectType…'

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type/Occluder|Doc:Manual/Game Engine/Logic/Object type/Sensor}}

= No collision object type =

[[File:GameEngine_ObjectType_NoCollision.png|right|thumb|300px|No collision]]

This disables object collisions. Use this for objects which can never be touched by any dynamic object to save performance.
{{clr}}

{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}
{{clr}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type/Occluder|Doc:Manual/Game Engine/Logic/Object type/Sensor}}

Doc:Manual/Game Engine/Logic/Object type/Occluder

Mindrones — Fri, 20 Nov 2009 21:38:14 GMT

New page

{{Page/Header|2.49|Doc:Manual/Game Engine/Logic/Object type|Doc:Manual/Game Engine/Logic/Object type/No collision}}

= Occluder object type =

[[File:GameEngine ObjectType Occluder.png|right|thumb|300px|Occluder]]

The object prevents the objects behind itself from being sent to the GPU, to save performance. (see [[Dev:Ref/Release Notes/2.49/Game Engine#Occlusion culling|release notes about Occlusion Culling]])
{{clr}}

{{Doc:Manual/Game Engine/Logic/Object type/invisibile}}
{{clr}}

= Technical specifications =

(from Blender 2.49 Release Notes)

{{Release Notes/2.49/Game Engine/Optimization/Culling}}

{{Page/Footer|Doc:Manual/Game Engine/Logic/Object type|Doc:Manual/Game Engine/Logic/Object type/No collision}}

Doc:CA/Manual/Introduction/Installing Blender

85.58.85.21 — Fri, 20 Nov 2009 21:32:44 GMT

Instal·lant El Blender des dels Executables:

← Older revision		Revision as of 21:32, 20 November 2009
(One intermediate revision not shown)
Line 2:		Line 2:
	{{UM/navigator.ca\|2.41\|Manual.ca/Introduction\|Manual.ca/The_Interface}}		{{UM/navigator.ca\|2.41\|Manual.ca/Introduction\|Manual.ca/The_Interface}}

-	=='''Instal·lant El Blender ~~des~~ dels ~~Executables~~'''==	+	=='''Instal·lant El Blender a partir dels executables'''==
	El Blender està disponible en un format executable preparat per funcionar en la majoria dels sistemes operatius. A més també teniu a la vostra disposició el codi font del programa, ja que aquest es distribueix sota la llicència GPL. Totes les versions del programa estan disponibles al lloc web de la seva Fundació (http://www.blender.org/), en un enllaç a la secció 'Downloads'.		El Blender està disponible en un format executable preparat per funcionar en la majoria dels sistemes operatius. A més també teniu a la vostra disposició el codi font del programa, ja que aquest es distribueix sota la llicència GPL. Totes les versions del programa estan disponibles al lloc web de la seva Fundació (http://www.blender.org/), en un enllaç a la secció 'Downloads'.

	Per al manual en línia hostatjat al wiki, generalment podeu usar la versió més recent del Blender del lloc web de la Blender Foundation (si bé pot ser que totes les característiques de la darrera versió publicada no estiguin completament actualitzades). Si esteu utilitzant una versió publicada d'aquest manual, es recomana que useu la versió del Blender inclosa al CD-ROM de la guia. Al text que hi ha a continuació, quan es parli de "baixada", els que utilitzin el llibre haurien de carregar el Blender del CD-ROM.		Per al manual en línia hostatjat al wiki, generalment podeu usar la versió més recent del Blender del lloc web de la Blender Foundation (si bé pot ser que totes les característiques de la darrera versió publicada no estiguin completament actualitzades). Si esteu utilitzant una versió publicada d'aquest manual, es recomana que useu la versió del Blender inclosa al CD-ROM de la guia. Al text que hi ha a continuació, quan es parli de "baixada", els que utilitzin el llibre haurien de carregar el Blender del CD-ROM.
-	~~<!--~~
-	~~=== Downloading and installing the binary distribution ===~~

-	~~The binary distributions are provided for~~ 6 ~~primary operating system families~~:	+	=== Baixant-vos i instal·lant la distribució binària ===
		+
		+	Hi ha disponibles distribucions binàries per a 6 famílies primàries de sistemes operatius:

	* [[#Windows\|Windows]]		* [[#Windows\|Windows]]
Line 18:		Line 18:
	* [[#Solaris\|Solaris]]		* [[#Solaris\|Solaris]]

-	~~Binaries for the~~ Linux ~~operating systems are provided for two different hardware architectures~~ x86 (Intel ~~and~~ AMD ~~processors~~) ~~and~~ PowerPC, ~~and the choice between statically linked or dynamically loaded libraries~~.	+	Els sistemes operatius Linux disposen de binaris per a dues arquitectures de maquinari x86 diferents (processadors Intel i AMD) i per a PowerPC, i la possibilitat d'escollir entre biblioteques enllaçades estàticament o biblioteques carregades dinàmicament.
-		+	<!--
	The difference between the dynamic and the static binaries is important. The static binarie has the OpenGL libraries compiled in. This makes Blender run on your system without using hardware accelerated graphics. Use the static version if the dynamic version fails! OpenGL is used in Blender for all drawing, including menus and buttons. For this, you will need OpenGL installed on your system. This dependency makes a proper and compliant OpenGL installation at your system a requirement. Generally speaking integrated graphics chips and older low end graphics cards will perform poorly or not at all with Blender due to their poor support for OpenGL. (It is ofter possible to work around the poor OpenGL support of such cards by using software based OpenGL solutions such as by turning down or off hardware accelleration on Windows, or using software MESA OpenGL on Linux).		The difference between the dynamic and the static binaries is important. The static binarie has the OpenGL libraries compiled in. This makes Blender run on your system without using hardware accelerated graphics. Use the static version if the dynamic version fails! OpenGL is used in Blender for all drawing, including menus and buttons. For this, you will need OpenGL installed on your system. This dependency makes a proper and compliant OpenGL installation at your system a requirement. Generally speaking integrated graphics chips and older low end graphics cards will perform poorly or not at all with Blender due to their poor support for OpenGL. (It is ofter possible to work around the poor OpenGL support of such cards by using software based OpenGL solutions such as by turning down or off hardware accelleration on Windows, or using software MESA OpenGL on Linux).

User:Vinux

Vinux — Fri, 20 Nov 2009 21:27:38 GMT

New user account

New page

File:GameEngine ObjectType SoftBody.png

Mindrones — Fri, 20 Nov 2009 21:24:51 GMT

uploaded "[[File:GameEngine ObjectType SoftBody.png]]"

New page

Doc:Manual/Game Engine/Logic/Object type/form

Mindrones — Fri, 20 Nov 2009 21:15:18 GMT

Created page with '== Form == The {{Literal|Form}} factor gives you a degree of control over rigid body objects. The higher the {{Literal|Form}} factor, the less likely an object is to roll, espec…'

New page

== Form ==

The {{Literal|Form}} factor gives you a degree of control over rigid body objects. The higher the {{Literal|Form}} factor, the less likely an object is to roll, especially rolling on a flat surface.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/rot fh

Mindrones — Fri, 20 Nov 2009 21:13:48 GMT

Created page with '==Rot Fh== This option causes the Z axis to be pointed away from a Dynamic Materials. This is activated by {{Literal|Do Fh}}. {{clr}…'

New page

==Rot Fh==

This option causes the Z axis to be pointed away from a [[Doc:Manual/Game Engine/Dynamic Materials|Dynamic Materials]]. This is activated by {{Literal|Do Fh}}.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/do fh

Mindrones — Fri, 20 Nov 2009 21:13:23 GMT

Created page with '==Do Fh== This causes your object to interact with Dynamic Materials. This is currently not supported by the default bullet physics a…'

New page

==Do Fh==
This causes your object to interact with [[Doc:Manual/Game Engine/Dynamic Materials|Dynamic Materials]]. This is currently not supported by the default bullet physics and is not fully supported in the Sumo engine in the current edition of Blender. It is fully supported by version 2.24 of Blender.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/rotdamp

Mindrones — Fri, 20 Nov 2009 21:12:10 GMT

Created page with '==RotDamp== Rotational Dampening is the same as dampening but only affects the object’s rotation. A high Rotational Dampening will not affect the rest of the object’s moment…'

New page

==RotDamp==

Rotational Dampening is the same as dampening but only affects the object’s rotation. A high Rotational Dampening will not affect the rest of the object’s momentum.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/damp

Mindrones — Fri, 20 Nov 2009 21:11:58 GMT

Created page with '==Damp== Dampening affects the freedom of an object to move. In space there should be almost no dampening, while in water the dampening should be set quite high. {{clr}}'

New page

==Damp==

Dampening affects the freedom of an object to move. In space there should be almost no dampening, while in water the dampening should be set quite high.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/no sleeping

Mindrones — Fri, 20 Nov 2009 21:09:28 GMT

← Older revision		Revision as of 21:09, 20 November 2009
Line 1:		Line 1:
	== No Sleeping ==		== No Sleeping ==

-	By default if ~~and~~ object that is affected by rolling physics comes to a rest, Rolling Physics is disabled. The physic engine assumes that it no longer needs to calculate the object’s motion. In some case this is true and will save you processing power, in other case such as in a soccer game, the physics needs to be maintained until someone kicks the ball placing it back in motion.	+	By default if an object that is affected by rolling physics comes to a rest, Rolling Physics is disabled. The physic engine assumes that it no longer needs to calculate the object’s motion. In some case this is true and will save you processing power, in other case such as in a soccer game, the physics needs to be maintained until someone kicks the ball placing it back in motion.
	{{clr}}		{{clr}}

Doc:Manual/Game Engine/Logic/Object type/radius

Mindrones — Fri, 20 Nov 2009 21:07:41 GMT

Created page with '== Radius == This determines the size of the bounding area for sphere bound objects and Fh/FhRot. This can be changed to a large or smaller size to give your object the look and…'

New page

== Radius ==

This determines the size of the bounding area for sphere bound objects and Fh/FhRot. This can be changed to a large or smaller size to give your object the look and feel you desire. The shape of the bounding area is determined by the {{Literal|Bounds}} button, by default it is a {{Literal|Box}}.

When changing the bounding size you can see the effect on the screen, in the shape of a circle. At this point in time all bounding shapes are reflected as a circle in the 3D window, even though they react differently during the game play.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/anisotropic

Mindrones — Fri, 20 Nov 2009 21:01:16 GMT

← Older revision		Revision as of 21:01, 20 November 2009
Line 1:		Line 1:
	== Anisotropic ==		== Anisotropic ==

-	~~Enables anisotropic~~ friction, ~~which means you can set a different friction for each axis~~ of the object.	+	This controls the direction of friction in the X, Y or Z direction of the object. Anisotropic is relative to the amount of friction in a particular direction. For example, take the wheel of a skate board, the forward direction should rotate easily, yet a sideward motion should be difficult and decreased by a higher level of friction.
		+	{{clr}}

Doc:Manual/Game Engine/Logic/Object type/no sleeping

Mindrones — Fri, 20 Nov 2009 20:59:47 GMT

Created page with '== No Sleeping == By default if and object that is affected by rolling physics comes to a rest, Rolling Physics is disabled. The physic engine assumes that it no longer needs to…'

New page

== No Sleeping ==

By default if and object that is affected by rolling physics comes to a rest, Rolling Physics is disabled. The physic engine assumes that it no longer needs to calculate the object’s motion. In some case this is true and will save you processing power, in other case such as in a soccer game, the physics needs to be maintained until someone kicks the ball placing it back in motion.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/mass

Mindrones — Fri, 20 Nov 2009 20:51:00 GMT

Created page with '==Mass== {{Literal|Mass}} affects the amount of force that is required to move an object. The greater the mass the greater the force that need to be applied to the object in ord…'

New page

==Mass==

{{Literal|Mass}} affects the amount of force that is required to move an object. The greater the mass the greater the force that need to be applied to the object in order to move the object. Mass will not cause objects to fall faster or slower. To slow an object down use [[#Damp|dampening]], if you wish to accelerate the falling rate increase [[Doc:Manual/Game_Engine/Physics|gravity]] (normal gravity is 9.81).
{{clr}}

Doc:Manual/Game Engine/Physics

Mindrones — Fri, 20 Nov 2009 20:48:55 GMT

added screenshot

← Older revision		Revision as of 20:48, 20 November 2009
Line 12:		Line 12:
	This part of the World determines the type of physical rules that govern the game engine scene, and the gravity of the situation (sorry, couldn’t resist the pun). Based on the physics engine selected, in physics simulations in the game engine, Blender will automatically move {{Literal\|Actors}} in the downward (-Z) direction. After you arrange the actors and they move as you wish, you can then bake this computed motion into fixed Ipo curves (see [[Doc:Manual/Game Engine/Logic/Actors\|Logic actors]] for more info).		This part of the World determines the type of physical rules that govern the game engine scene, and the gravity of the situation (sorry, couldn’t resist the pun). Based on the physics engine selected, in physics simulations in the game engine, Blender will automatically move {{Literal\|Actors}} in the downward (-Z) direction. After you arrange the actors and they move as you wish, you can then bake this computed motion into fixed Ipo curves (see [[Doc:Manual/Game Engine/Logic/Actors\|Logic actors]] for more info).
	{{clr}}		{{clr}}
		+
		+	[[Image:Dev-GameEngine-occlusion-resolution.png\|center\|640px]]

	==Options==		==Options==

Doc:Manual/Game Engine/Logic/Object type/anisotropic

Mindrones — Fri, 20 Nov 2009 20:37:06 GMT

Created page with '== Anisotropic == Enables anisotropic friction, which means you can set a different friction for each axis of the object.'

New page

== Anisotropic ==

Enables anisotropic friction, which means you can set a different friction for each axis of the object.

File:GameEngine ObjectType Dynamic.png

Mindrones — Fri, 20 Nov 2009 20:29:19 GMT

uploaded "[[File:GameEngine ObjectType Dynamic.png]]"

New page

Doc:Manual/Game Engine/Logic/Object type/actor

Mindrones — Fri, 20 Nov 2009 20:28:12 GMT

← Older revision		Revision as of 20:28, 20 November 2009
Line 1:		Line 1:
	==Actor==		==Actor==

-	By default this button occurs switched off and alone ([[Image:GM_Actors_Undepressed_Button.png]]). Once pressed it gives you the option of {{Literal\|Ghost}} or {{Literal\|Dynamic}} ([[Image:GM_Actors_Active_Button.png]]). This causes the physics engine to evaluate your object, causing your object to be seen as more than part of the world (a simple wall or floor). This object can now be seen by other active objects.	+	This causes the physics engine to evaluate your object, causing your object to be seen as more than part of the world (a simple wall or floor). This object can now be seen by other active objects.

	At this point your object is not affected by normal physics (e.g. gravity) but is seen as more than just a background object. This is useful for interaction between objects that need not have physics properties, such as gravity, e.g. a button on a wall.		At this point your object is not affected by normal physics (e.g. gravity) but is seen as more than just a background object. This is useful for interaction between objects that need not have physics properties, such as gravity, e.g. a button on a wall.
	{{clr}}		{{clr}}

File:GameEngine ObjectType Static.png

Mindrones — Fri, 20 Nov 2009 20:24:57 GMT

uploaded "[[File:GameEngine ObjectType Static.png]]"

New page

Doc:Manual/Game Engine/Logic/Object type/ghost

Mindrones — Fri, 20 Nov 2009 20:23:20 GMT

Created page with '==Ghost== {{Literal|Ghost}} gives the object the ability to pass through other objects. This helps save processing time while calculating objects’ physics (e.g. bouncing, frict…'

New page

==Ghost==
{{Literal|Ghost}} gives the object the ability to pass through other objects. This helps save processing time while calculating objects’ physics (e.g. bouncing, friction, etc.). A collision with another object is still detected and reported to your game logic.
{{clr}}

Doc:Manual/Game Engine/Logic/Object type/actor

Mindrones — Fri, 20 Nov 2009 20:22:29 GMT

Created page with '==Actor== By default this button occurs switched off and alone (Image:GM_Actors_Undepressed_Button.png). Once pressed it gives you the option of {{Literal|Ghost}} or {{Liter…'

New page

==Actor==

By default this button occurs switched off and alone ([[Image:GM_Actors_Undepressed_Button.png]]). Once pressed it gives you the option of {{Literal|Ghost}} or {{Literal|Dynamic}} ([[Image:GM_Actors_Active_Button.png]]). This causes the physics engine to evaluate your object, causing your object to be seen as more than part of the world (a simple wall or floor). This object can now be seen by other active objects.

At this point your object is not affected by normal physics (e.g. gravity) but is seen as more than just a background object. This is useful for interaction between objects that need not have physics properties, such as gravity, e.g. a button on a wall.
{{clr}}

Template:Release Notes/2.49/Game Engine/Physics

Mindrones — Fri, 20 Nov 2009 20:17:24 GMT

← Older revision		Revision as of 20:17, 20 November 2009
Line 14:		Line 14:

	{{clr}}		{{clr}}
-	~~===Sensor Object Type===~~
-	~~New sensor object to generalize Near and Radar sensor, static-static collision capability.~~

-	A new type of "Sensor" physics object is available in the GE for advanced collision management. It's called Sensor for its similarities with the physics objects that underlie the Near and Radar sensors. Like the Near and Radar object it is:	+	{{Template:Release Notes/2.49/Game Engine/Physics/sensor object type}}
-	* static and ghost	+
-	* invisible by default	+
-	* always active to ensure correct collision detection	+
-	* capable of detecting both static and dynamic objects	+
-	* ignoring collision with their parent	+
-	* capable of broadphase filtering based on:	+
-	** Actor option: the collisioning object must have the Actor flag set to be detected	+
-	** property/~~material: as specified in the collision sensors attached to it~~.~~<br>Broadphase filtering is important for performance reason: the collision points will be computed only for the objects that pass the broahphase filter.~~	+
-	* automatically removed from the simulation when no collision sensor ~~is active on it~~	+
-		+
-	~~Unlike the Near and Radar~~ object ~~it can:~~	+
-	* take any shape, including triangle mesh	+
-	* be made visible for debugging (just use the Visible actuator)	+
-	* have multiple collision sensors using it	+
-		+
-	~~Other than that, the sensor objects are ordinary objects. You can move them freely or parent them. When parented to a dynamic object, they can provide advanced collision control to this object.~~	+
-		+
-	~~The~~ type ~~of collision capability depends on the shape:~~	+
-	* box, sphere, cylinder, cone, convex hull provide volume detection.	+
-	* triangle mesh provides surface detection but you can give some volume to the suface by increasing the margin in the Advanced Settings panel. The margin applies on both sides of the surface.	+
-		+
-	~~Performance tip:~~	+
-	* Sensor objects perform better than Near and Radar: they do less synchronizations because of the Scenegraph optimizations and they can have multiple collision sensors on them (with different property filtering for example).	+
-	* Always prefer simple shape (box, sphere) to complex shape whenever possible.	+
-	* Always use broadphase filtering (avoid collision sensor with empty propery/material)	+
-	* Use collision sensor only when you need them. When no collision sensor is active on the sensor object, it is removed from the simulation and consume no CPU.	+
-		+
-	~~Known limitations:~~	+
-	* When running Blender in debug mode, you will see one warning line of the console:<br> "warning btCollisionDispatcher::needsCollision: static-static collision!"<br>In release mode this message is not printed.	+
-	* Collision margin has no effect on sphere, cone and cylinder shape.	+
-		+
-	~~Other performance improvements:~~	+
-	* Remove unnecessary interpolation for Near and Radar objects and by extension sensor objects.	+
-	* Use direct matrix copy instead of quaternion to synchronize orientation.	+

	===Adjustable Frame/Logic/Physics Rate===		===Adjustable Frame/Logic/Physics Rate===

Template:Release Notes/2.49/Game Engine/Physics/sensor object type

Mindrones — Fri, 20 Nov 2009 20:16:52 GMT

Created page with '== Sensor Object Type == New sensor object to generalize Near and Radar sensor, static-static collision capability. A new type of "Sensor" physics object is available in the GE…'

New page

== Sensor Object Type ==

New sensor object to generalize Near and Radar sensor, static-static collision capability.

A new type of "Sensor" physics object is available in the GE for advanced collision management. It's called Sensor for its similarities with the physics objects that underlie the Near and Radar sensors. Like the Near and Radar object it is:
* static and ghost
* invisible by default
* always active to ensure correct collision detection
* capable of detecting both static and dynamic objects
* ignoring collision with their parent
* capable of broadphase filtering based on:
** Actor option: the collisioning object must have the Actor flag set to be detected
** property/material: as specified in the collision sensors attached to it. Broadphase filtering is important for performance reason: the collision points will be computed only for the objects that pass the broahphase filter.
* automatically removed from the simulation when no collision sensor is active on it

Unlike the Near and Radar object it can:
* take any shape, including triangle mesh
* be made visible for debugging (just use the Visible actuator)
* have multiple collision sensors using it

Other than that, the sensor objects are ordinary objects. You can move them freely or parent them. When parented to a dynamic object, they can provide advanced collision control to this object.

The type of collision capability depends on the shape:
* box, sphere, cylinder, cone, convex hull provide volume detection.
* triangle mesh provides surface detection but you can give some volume to the suface by increasing the margin in the Advanced Settings panel. The margin applies on both sides of the surface.

Performance tip:
* Sensor objects perform better than Near and Radar: they do less synchronizations because of the Scenegraph optimizations and they can have multiple collision sensors on them (with different property filtering for example).
* Always prefer simple shape (box, sphere) to complex shape whenever possible.
* Always use broadphase filtering (avoid collision sensor with empty propery/material)
* Use collision sensor only when you need them. When no collision sensor is active on the sensor object, it is removed from the simulation and consume no CPU.

Known limitations:
* When running Blender in debug mode, you will see one warning line of the console: "warning btCollisionDispatcher::needsCollision: static-static collision!" In release mode this message is not printed.
* Collision margin has no effect on sphere, cone and cylinder shape.

Other performance improvements:
* Remove unnecessary interpolation for Near and Radar objects and by extension sensor objects.
* Use direct matrix copy instead of quaternion to synchronize orientation.

Doc:Manual/Game Engine/Logic/Object type/bounds

Mindrones — Fri, 20 Nov 2009 20:11:11 GMT

Created page with '==Bounds== right The Blender Game Engine has a number of ways of dealing with the shapes of objects. The reason that the game engine avoid…'

New page

==Bounds==

[[Image:GM_Actors_Bounding_Menu.png|right]]

The Blender Game Engine has a number of ways of dealing with the shapes of objects. The reason that the game engine avoids highly accurate, per face object collisions, is due to the high level of processing power that it would demand. It is often faster, during game play, to uses a simpler system such as a box or a sphere for an object that’s shape is very similar.

[[Image:GM_Actors_Object_Centre.png|right]]

The bounds are calculated from the object’s centre, which is designated by the pink dot normally at the centre of your object. It is not uncommon or useful to move this centre to a more convenient location. This can be done in the {{Literal|Editing}} context ({{Shortcut|f9}}) and choosing one of the 3 options that focus around Centre movement (see [[Doc:Reference/Panels/Editing/Mesh|Mesh]] for more info).

{{Literal|Convex Hull}} and static {{Literal|Triangle Mesh}} are designed for uses with World objects floors, walls, trees, etc.

Blender has no generic way of interacting with hollow objects. An example, which would be difficult to create, would be a cup to shake dice in.
{{clr}}

Template:Release Notes/2.49/Game Engine/Optimization/Culling

Mindrones — Fri, 20 Nov 2009 20:06:09 GMT

← Older revision		Revision as of 20:06, 20 November 2009
Line 23:		Line 23:
	The resolution of the ZDepth buffer is controllable in the World settings with the "Occlu Res" button:		The resolution of the ZDepth buffer is controllable in the World settings with the "Occlu Res" button:

-	[[Image:Dev-GameEngine-occlusion-resolution.png\|center]]	+	[[Image:Dev-GameEngine-occlusion-resolution.png\|center\|640px]]

	By default the resolution is 128 pixels for the largest dimension of the viewport while the resolution of the other dimension is set proportionally. Although 128 is a very low resolution, it is sufficient for the purpose of culling. The resolution can be increased to maximum 1024 but at great CPU expense.<br>		By default the resolution is 128 pixels for the largest dimension of the viewport while the resolution of the other dimension is set proportionally. Although 128 is a very low resolution, it is sufficient for the purpose of culling. The resolution can be increased to maximum 1024 but at great CPU expense.<br>

Template:Release Notes/2.49/Game Engine/Optimization

Mindrones — Fri, 20 Nov 2009 19:59:37 GMT

← Older revision		Revision as of 19:59, 20 November 2009
Line 21:		Line 21:
	The scenegraph improvement consists in avoiding position update if the object has not moved since last update and the removal of redundant updates and synchronization with the physics engine and the Rasterizer.<br>		The scenegraph improvement consists in avoiding position update if the object has not moved since last update and the removal of redundant updates and synchronization with the physics engine and the Rasterizer.<br>

-	~~== View frustrum culling ==~~	+	{{Template:Release Notes/2.49/Game Engine/Optimization/Culling}}
-		+
-	The Dynamic Bounding Volume Tree (DBVT) broadphase facility of the Bullet Physics Library is used to build a tree of graphical objects in the scene. The elements of the tree are Aabb boxes (Aligned Axis Bounding Boxes) enclosing the objects. This provides good precision in closed and opened scenes. This new culling system is enabled by default but just in case, it can be disabled with a button in the World settings.<br>	+
-		+
-	~~With these improvements, the culling and Scenegraph part of the BGE is as much as 5 times faster than in 2.48. However, the speed up is noticeable only when you have many objects (>100).~~	+
-		+
-	~~== Occlusion culling ==~~	+
-		+
-	Occlusion culling is the ability of certain objects (the occluders) to hide other objects (i.e. not send them to the GPU). Just like the view frustum culling, the implementation is based on Bullet's dynamic bounding volume trees.	+
-		+
-	Occlusion culling is not enabled by default because it is a feature that requires understanding to bring the most benefits. If not used properly, it will just slow down the game. (Not too much, though, as the occlusion processing time is auto regulated.<br>	+
-		+
-	~~==== How it works ====~~	+
-		+
-	~~Occlusion culling is activated when you define at least one occluder in your scene. The Occluder option is in the physics buttons~~:	+
-		+
-	~~[[Image:<!--check-->Dev-GameEngine-occlusion-button.png\|center]]~~	+
-		+
-	<br>The "Occluder" option should only be used on a mesh object. As far as Physics is concerned, it is equivalent to "No collision".  The reason why I chose to make the Occluder mode mutually exclusive with other physics mode is to emphasize on the fact that occluders should be specifically designed for that purpose and not every mesh should be an occluder. However, you can enable the Occlusion capability on physics objects using Python and Logic bricks. We'll come to that.	+
-		+
-	When an occluder object enters the view frustrum, the BGE builds a ZDepth buffer from the faces of that object. Whether the faces are one-side or two-side is important: only the front faces and two-side faces are used to build the ZDepth buffer. If multiple occluders are in the view frustrum, the BGE combines them and keeps the most foreground faces.<br>	+
-		+
-	~~The resolution of the ZDepth buffer is controllable in the World settings with the "Occlu Res" button:~~	+
-		+
-	~~[[Image:Dev-GameEngine-occlusion-resolution.png\|center]]~~	+
-		+
-	By default the resolution is 128 pixels for the largest dimension of the viewport while the resolution of the other dimension is set proportionally. Although 128 is a very low resolution, it is sufficient for the purpose of culling. The resolution can be increased to maximum 1024 but at great CPU expense.<br>	+
-		+
-	~~The BGE traverses the DBVT tree and for each node checks if it is entirely hidden by the occluders and if so, culls the node (and all the objects it contains).<br>~~	+
-		+
-	To further optimize the feature, the BGE builds and uses the ZDepth buffer only when at least one occluder is in the view frustrum. Until then, there is no performance decrease compared to regular view frustrum culling.	+
-		+
-	~~==== How to use it ====~~	+
-		+
-	~~There are situations where occlusion culling will not bring any benefit:~~	+
-		+
-	*If the occluders are small and don't hide many objects. <br>In that case, occlusion culling is just dragging your CPU down.	+
-	*If the occluders are large but hides simple objects.<br>In that case you're better off sending the objects to the GPU.	+
-	*If the occluders are large and hides many complex objects but in a very predictable way.<br>Example: a house full of complex objects. Although occlusion culling will perform well in this case, you will get better performance by implementing a specific logic that hides/~~unhides the objects; for instance making the objects visible only when the camera enters the house~~.~~<br>~~	+
-		+
-	Occlusion culling makes most sense when the occluders are large objects (buildings, mountains, ...) that hide many complex objects in an unpredictable way. However, don't be too concerned about performance: even if you use it inappropriately, the performance decrease will be limited due to the structure of the algorithm.<br>	+
-		+
-	Occluders can be visible graphic objects but beware that too many faces will make the ZDepth buffer creation slow. For example, a terrain is not a good candidate for occlusion: too many faces and too many overlap. Occluder can be invisible objects placed inside more complex objects (ex: "in the walls" of a building with complex architecture). Occluders can have "holes" through which you will see objects.<br>	+
-		+
-	~~Here is a possible workflow to create occluders from a complex terrain:~~	+
-		+
-	*duplicate the terrain and make it low poly	+
-	*remove all horizontal parts and keep only the high elevation parts	+
-	*make all the face invisible and set the Occluder mode.	+
-		+
-	To optimize further, you may split the occluder into several objects (make an occluder from each mountain, each wall, etc.) and do the same for the terrain: this way, parts of the terrain that are behind occluders will not be rendered.	+
-		+
-	~~You can verify how the occlusion is working by running the game in wireframe mode.~~	+
-		+
-	~~==== In-game control ====~~	+
-		+
-	~~You can turn on~~/~~off the occlusion capability of an object with Python:~~	+
-	~~<pre>obj.occlusion = True~~	+
-	~~obj.setOcclusion(True, False) #param1=occlusion, param2=recurse in children~~	+
-	</~~pre>~~	+
-	~~The object doesn't need to be defined as an occluder in the GUI: you can enable occlusion capability on any mesh object, including static and dynamic objects during the game.~~	+
-		+
-	~~You can also use the Visibility Actuator:<br> [[Image:<!--check-->Dev-GameEngine-occlusion-brick.png\|center]]~~	+
-		+
-	~~<br>~~	+
-		+
-	~~Note that the layout of the actuator has changed: The Visible~~/Invisible mutually exclusive buttons have been replaced by two independent buttons: push the button to activate the feature (Visible/Occluding), unpush the button to activate the opposite feature (Invisible/Non-occluding).	+
-		+
-	~~Note that the actuator sets the Visibility and Occlusion mode at the same time. If you need to set them separately, use Python.<br>~~	+
-		+
-	~~==== Known limitation ====~~	+
-		+
-	*If you want to use occlusion culling, you must at least have one occluder at the start of the game. The occluder doesn't need to be in an active layer. After that, you can enable and disable occlusion capability on every mesh objects during the game using on the In-game control.	+

Template:Release Notes/2.49/Game Engine/Optimization/Culling

Mindrones — Fri, 20 Nov 2009 19:59:08 GMT

Created page with '== View frustrum culling == The Dynamic Bounding Volume Tree (DBVT) broadphase facility of the Bullet Physics Library is used to build a tree of graphical objects in the scene. …'

New page

== View frustrum culling ==

The Dynamic Bounding Volume Tree (DBVT) broadphase facility of the Bullet Physics Library is used to build a tree of graphical objects in the scene. The elements of the tree are Aabb boxes (Aligned Axis Bounding Boxes) enclosing the objects. This provides good precision in closed and opened scenes. This new culling system is enabled by default but just in case, it can be disabled with a button in the World settings. 

With these improvements, the culling and Scenegraph part of the BGE is as much as 5 times faster than in 2.48. However, the speed up is noticeable only when you have many objects (>100).

== Occlusion culling ==

Occlusion culling is the ability of certain objects (the occluders) to hide other objects (i.e. not send them to the GPU). Just like the view frustum culling, the implementation is based on Bullet's dynamic bounding volume trees.

Occlusion culling is not enabled by default because it is a feature that requires understanding to bring the most benefits. If not used properly, it will just slow down the game. (Not too much, though, as the occlusion processing time is auto regulated. 

==== How it works ====

Occlusion culling is activated when you define at least one occluder in your scene. The Occluder option is in the physics buttons:

[[Image:Dev-GameEngine-occlusion-button.png|center]]

 The "Occluder" option should only be used on a mesh object. As far as Physics is concerned, it is equivalent to "No collision".  The reason why I chose to make the Occluder mode mutually exclusive with other physics mode is to emphasize on the fact that occluders should be specifically designed for that purpose and not every mesh should be an occluder. However, you can enable the Occlusion capability on physics objects using Python and Logic bricks. We'll come to that.

When an occluder object enters the view frustrum, the BGE builds a ZDepth buffer from the faces of that object. Whether the faces are one-side or two-side is important: only the front faces and two-side faces are used to build the ZDepth buffer. If multiple occluders are in the view frustrum, the BGE combines them and keeps the most foreground faces. 

The resolution of the ZDepth buffer is controllable in the World settings with the "Occlu Res" button:

[[Image:Dev-GameEngine-occlusion-resolution.png|center]]

By default the resolution is 128 pixels for the largest dimension of the viewport while the resolution of the other dimension is set proportionally. Although 128 is a very low resolution, it is sufficient for the purpose of culling. The resolution can be increased to maximum 1024 but at great CPU expense. 

The BGE traverses the DBVT tree and for each node checks if it is entirely hidden by the occluders and if so, culls the node (and all the objects it contains). 

To further optimize the feature, the BGE builds and uses the ZDepth buffer only when at least one occluder is in the view frustrum. Until then, there is no performance decrease compared to regular view frustrum culling.

==== How to use it ====

There are situations where occlusion culling will not bring any benefit:

*If the occluders are small and don't hide many objects. In that case, occlusion culling is just dragging your CPU down.
*If the occluders are large but hides simple objects. In that case you're better off sending the objects to the GPU.
*If the occluders are large and hides many complex objects but in a very predictable way. Example: a house full of complex objects. Although occlusion culling will perform well in this case, you will get better performance by implementing a specific logic that hides/unhides the objects; for instance making the objects visible only when the camera enters the house. 

Occlusion culling makes most sense when the occluders are large objects (buildings, mountains, ...) that hide many complex objects in an unpredictable way. However, don't be too concerned about performance: even if you use it inappropriately, the performance decrease will be limited due to the structure of the algorithm. 

Occluders can be visible graphic objects but beware that too many faces will make the ZDepth buffer creation slow. For example, a terrain is not a good candidate for occlusion: too many faces and too many overlap. Occluder can be invisible objects placed inside more complex objects (ex: "in the walls" of a building with complex architecture). Occluders can have "holes" through which you will see objects. 

Here is a possible workflow to create occluders from a complex terrain:

*duplicate the terrain and make it low poly
*remove all horizontal parts and keep only the high elevation parts
*make all the face invisible and set the Occluder mode.

To optimize further, you may split the occluder into several objects (make an occluder from each mountain, each wall, etc.) and do the same for the terrain: this way, parts of the terrain that are behind occluders will not be rendered.

You can verify how the occlusion is working by running the game in wireframe mode.

==== In-game control ====

You can turn on/off the occlusion capability of an object with Python:
<pre>obj.occlusion = True
obj.setOcclusion(True, False) #param1=occlusion, param2=recurse in children
</pre>
The object doesn't need to be defined as an occluder in the GUI: you can enable occlusion capability on any mesh object, including static and dynamic objects during the game.

You can also use the Visibility Actuator: [[Image:Dev-GameEngine-occlusion-brick.png|center]]

 

Note that the layout of the actuator has changed: The Visible/Invisible mutually exclusive buttons have been replaced by two independent buttons: push the button to activate the feature (Visible/Occluding), unpush the button to activate the opposite feature (Invisible/Non-occluding).

Note that the actuator sets the Visibility and Occlusion mode at the same time. If you need to set them separately, use Python. 

==== Known limitation ====

*If you want to use occlusion culling, you must at least have one occluder at the start of the game. The occluder doesn't need to be in an active layer. After that, you can enable and disable occlusion capability on every mesh objects during the game using on the In-game control.

File:OMD.16.png

J.Alcántara — Fri, 20 Nov 2009 19:30:05 GMT

uploaded "[[File:OMD.16.png]]"

New page

Doc:CA/Manual/Introduction/Installing Blender

85.58.85.21 — Fri, 20 Nov 2009 19:28:42 GMT

Instal·lant des dels Executables:

← Older revision		Revision as of 19:28, 20 November 2009
Line 2:		Line 2:
	{{UM/navigator.ca\|2.41\|Manual.ca/Introduction\|Manual.ca/The_Interface}}		{{UM/navigator.ca\|2.41\|Manual.ca/Introduction\|Manual.ca/The_Interface}}

-	=='''Instal·lant des dels Executables'''==	+	=='''Instal·lant El Blender des dels Executables'''==
	El Blender està disponible en un format executable preparat per funcionar en la majoria dels sistemes operatius. A més també teniu a la vostra disposició el codi font del programa, ja que aquest es distribueix sota la llicència GPL. Totes les versions del programa estan disponibles al lloc web de la seva Fundació (http://www.blender.org/), en un enllaç a la secció 'Downloads'.		El Blender està disponible en un format executable preparat per funcionar en la majoria dels sistemes operatius. A més també teniu a la vostra disposició el codi font del programa, ja que aquest es distribueix sota la llicència GPL. Totes les versions del programa estan disponibles al lloc web de la seva Fundació (http://www.blender.org/), en un enllaç a la secció 'Downloads'.