From BlenderWiki

Jump to: navigation, search
Blender3D FreeTip.gif
IMPORTANT! Do not update this page!
We have moved the Blender User Manual to a new location. Please do not update this page, as it will be locked soon.


Page status (reviewing guidelines)

Text we need command line options for this page, explained and some examples for rendering, opening Blender with debug flag, and how to open Blender for screencasts/screenshots
Proposed fixes: none

The Console Window

The Console Window is an operating system text window that displays messages about Blender operations, status, and internal errors. If Blender crashes on you, the Console Window may be able to indicate the cause or error.

Windows XP/Vista/7

The Blender Console Window on Windows XP and subsequent messages.

When Blender is started on a Windows operating system, the Console Window is first created as a separate window on the desktop. Assuming that the right start-up conditions are met, the main Blender window should also appear and the Console Window will then be toggled off. To display the console again, go to Window » Toggle System Console.

The screenshot on the right shows the Blender Console Window on Windows XP directly after starting Blender and then a short while later after opening a file along with the relevant messages.


Blender3D FreeTip.gif
Closing the Blender Console Window
The Blender Console Window must remain open while Blender is running. Closing the Console Window will also close Blender, and unsaved work would be lost. To turn off the console without closing Blender, toggle the console state to off via re-selecting Toggle System Console option from the drop-down menu Window » Toggle System Console. Note the Blender Console Window can look very similar to MS-DOS, so make sure that you are closing the correct window if an instance of MS-DOS is open.




Linux

Starting Blender from a Linux console window and subsequent messages.

The Blender Console Window in Linux will generally only be visible on the Desktop if Blender is started from a Linux Terminal/Console Window as Blender uses the Console Window it is started from to display Console output.

Depending on your Desktop Environment setup, a Blender icon may appear on your desktop or an entry for Blender added to your menu after you install Blender. When you start Blender using a Desktop icon or menu entry rather than a Terminal window, the Blender Console Window text will most likely be hidden on the Terminal that your XWindows server was started from.

This screenshot shows Blender started from a Linux Terminal/Console Window and the resulting console text being printed to it. This example shows that when Blender was started it was unable to access a library related to the Pulseaudio sound server. When Blender closed, it saved the recovery file to /tmp/quit.blend.

MacOS

Starting Blender from a Mac OS X console window and subsequent messages.

The process in MacOS is very similar to the one described for Linux. MacOS uses "files" with the .app extension called applications. These files are actually folders that appear as files in Finder. In order to run Blender you will have specify that path to the Blender executable inside this folder, to get all output printed to the terminal. You can start a terminal from Applications -> Utilities. The path to the executable in the .app folder is ./blender.app/Contents/MacOS/blender.

If you have Blender installed in the Applications folder, the following command could be used, adapted to the particular Blender version: /Applications/blender-2.64/blender.app/Contents/MacOS/blender

Console Window Status and Error Messages

The Blender Console Window can display many different types of Status and Error Messages. Some messages simply inform the user what Blender is doing, but have no real impact on Blender's ability to function. Other messages can indicate serious errors that will most likely prevent Blender carrying out a particular task and may even make Blender non-responsive or shut down completely. The Blender Console Window messages can also originate internally from within the Blender code or from external sources such as Python scripts.

Common messages

  • found bundled python: (FOLDER)
This message indicates that Blender was able to find the Python library for the Python interpreter embedded within Blender. If this folder is missing or unable to be found, it is likely that an error will occur, and this message will not appear.
  • malloc returns nil()
When Blender carries out operations that require extra memory (RAM), it calls a function called malloc (short for memory allocate) which tries to allocate a requested amount of memory for Blender. If this cannot be satisfied, malloc will return nil/null/0 to indicate that it failed to carry out the request. If this happens Blender will not be able to carry out the operation requested by the user. This will most likely result in Blender operating very slowly or shutting down. If you want to avoid running out of memory you can install more memory in your system, reduce the amount of detail in your Blender models, or shut down other programs and services which may be taking up memory that Blender could use.



Blender3D FreeTip.gif
This is the old manual!
For the current 2.7x manual see http://www.blender.org/manual/


User Manual

World and Ambient Effects

World

Introduction
World Background

Ambient Effects

Mist
Stars (2.69)


Game Engine

Introduction

Introduction to the Game Engine
Game Logic Screen Layout

Logic

Logic Properties and States
The Logic Editor

Sensors

Introduction to Sensors
Sensor Editing
Common Options
-Actuator Sensor
-Always Sensor
-Collision Sensor
-Delay Sensor
-Joystick Sensor
-Keyboard Sensor
-Message Sensor
-Mouse Sensor
-Near Sensor
-Property Sensor
-Radar Sensor
-Random Sensor
-Ray Sensor
-Touch Sensor

Controllers

Introduction
Controller Editing
-AND Controller
-OR Controller
-NAND Controller
-NOR Controller
-XOR Controller
-XNOR Controller
-Expression Controller
-Python Controller

Actuators

Introduction
Actuator Editing
Common Options
-2D Filters Actuator
-Action Actuator
-Camera Actuator
-Constraint Actuator
-Edit Object Actuator
-Game Actuator
-Message Actuator
-Motion Actuator
-Parent Actuator
-Property Actuator
-Random Actuator
-Scene Actuator
-Sound Actuator
-State Actuator
-Steering Actuator
-Visibility Actuator

Game Properties

Introduction
Property Editing

Game States

Introduction

Camera

Introduction
Camera Editing
Stereo Camera
Dome Camera

World

Introduction

Physics

Introduction
Material Physics
No Collision Object
Static Object
Dynamic Object
Rigid Body Object
Soft Body Object
Vehicle Controller
Sensor Object
Occluder Object

Path Finding

Navigation Mesh Modifier

Game Performance

Introduction
System
Display
Framerate and Profile
Level of Detail

Python API

Introduction
Bullet physics
VideoTexture

Deploying

Standalone Player
Licensing of Blender Game

Android Support

Android Game development