New pages

11:39, 15 July 2023 ‎Movie Player (hist | edit) ‎[1,140 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ right|thumb|800px|'''Figure 1.''' The Movie Player window. The '''Movie Player''' is part of the '''Movie Tool''' plugin that ships with the C4 Engine, and it is used to preview movie files in the engine's proprietary <code>.mvi</code> format. == Opening a Movie == The Movie Player is opened by selecting '''Open Movie''' from the C4 Menu, or by typing <code>movie [''name'']</code> in the Command Console. If the '''Open Movie''...")
11:38, 15 July 2023 ‎Movie Importer (hist | edit) ‎[3,392 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ right|frame|'''Figure 1.''' The Movie Importer dialog. The '''Movie Importer''' tool is used to generate movies in the proprietary C4 Engine <code>.mvi</code> format. This functionality is part of the '''Movie Tool''' plugin. To generate a movie, either choose '''Import Movie''' from the C4 Menu or type the <code>imovie</code> command in the Command Console. This causes this Import Movie dialog, shown in Figure 1, to be displ...")
11:37, 15 July 2023 ‎OpenGEX (hist | edit) ‎[39 bytes] ‎Eric Lengyel (talk | contribs) (Redirected page to Open Game Engine Exchange) Tag: New redirect
11:37, 15 July 2023 ‎Open Data Description Language (hist | edit) ‎[329 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "right|thumb|640px|'''Figure 1.''' [http://openddl.org/ The Open Data Description Language.] The Open Data Description Language (OpenDDL) is a generic text-based data language used for a variety of purposes by the C4 Engine. == See Also == * [http://openddl.org/ openddl.org] * Open Game Engine Exchange")
11:35, 15 July 2023 ‎Open Game Engine Exchange (hist | edit) ‎[430 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "The '''Open Game Engine Exchange (OpenGEX)''' format is a text-based file format designed to facilitate the transfer of complex scene data between applications such as modeling tools and game engines. The C4 Engine World Editor can import files in the OpenGEX format after they have been exported from programs such as 3ds max and Maya. == See Also == * [http://opengex.org/ opengex.org] * Open Data Description Language")
11:35, 15 July 2023 ‎OpenDDL (hist | edit) ‎[44 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "right|thumb|640px|'''Figure 1.''' [http://openddl.org/ The Open Data Description Language.] The Open Data Description Language (OpenDDL) is a generic text-based data language used for a variety of purposes by the C4 Engine. == See Also == * [http://openddl.org/ openddl.org] * Open Game Engine Exchange")
11:33, 15 July 2023 ‎String Importer (hist | edit) ‎[1,626 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "The '''String Importer''' is a plugin that ships with the C4 Engine, and it generates string table resources in the engine's proprietary <code>.str</code> file format. The String Importer can be run by choosing '''Import String Table''' from the C4 Menu or by typing <code>istring [''name'']</code> in the Command Console. If the '''Import String Table''' menu item is selected (or name is omitted from the console command), then a dialog appears to let you select a...")
11:32, 15 July 2023 ‎Resource Packer (hist | edit) ‎[973 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Resource Packer''' is a plugin that ships with the C4 Engine, and it is used to create pack files in the engine's proprietary <code>.pak</code> format. For information about how pack files work, see Pack Files and Virtual Directories. == Creating a Pack File == The console command <code>pack ''name''</code> is used to create a pack file, where ''name'' is the name of a top-level subfolder inside the <code>Data</code> folder. Once a pack file has b...")
11:25, 15 July 2023 ‎Simple Games (hist | edit) ‎[3,017 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The C4 Engine ships with two basic game projects called <code>SimpleBall</code> and <code>SimpleChar</code>. Both are made up of two files that are heavily commented and represent nearly the minimum amount of code that needs to be written to have a working game module. You can tell the engine to load one of these game module by editing the file <code>Data/Engine/game.cfg</code> and changing the value of the variable <code>gameModuleName</code> to either <code>...")
11:23, 15 July 2023 ‎Teleport Tutorial (hist | edit) ‎[9,824 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "This tutorial describes the method used to create an indirect portal that can see another part of a level, apply a material with animated waves to the portal, and make the destination image float up and down. This tutorial doesn't have you modify a world, but instead examines what has been done in a fully functional example. To follow this tutorial, you need the <code>Data/Tutorial/world/Teleport.wld</code> file that is included in the C4 Engine distribution. To enlarg...")
11:21, 15 July 2023 ‎Water Tutorial (hist | edit) ‎[6,923 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "This tutorial guides you through the creation of a new water surface with reflection and refraction effects applied. To follow this tutorial, you need the <code>Data/Tutorial/world/Water.wld</code> file that is included in the C4 Engine distribution. To enlarge any of the screenshots below, click on the thumbnail icon below the image. == Step A: Open Water.wld == Open <code>Data/Tutorial/world/Water.wld</code> in the World Editor by typing Ctrl-O or by entering <...")
11:17, 15 July 2023 ‎Terrain Tutorial (hist | edit) ‎[6,074 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "This tutorial guides you through the creation of a new terrain block and some basic terrain editing operations. For more general information about the terrain tools, see the Terrain article. To follow this tutorial, you need the <code>Data/Tutorial/world/Terrain.wld</code> file that is included in the C4 Engine distribution. To enlarge any of the screenshots below, click on the thumbnail icon below the image. == Step A: Open Terrain.wld == Open <code>Data/Tutoria...")
11:09, 15 July 2023 ‎Oscillation Tutorial (hist | edit) ‎[6,364 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "This tutorial teaches you how to assign an Oscillation Controller to a node in a level. The Oscillation Controller is a specific type of controller that's built into the C4 Engine, and it causes a node to oscillate back and forth between two points with a velocity based on a sine wave. To follow this tutorial, you need the <code>Data/Tutorial/world/Oscillation.wld</code> file that is included in the <code>C4-xxx-Data.zip</code> distribution. To enlarge any of the s...")
11:05, 15 July 2023 ‎Portal Tutorial (hist | edit) ‎[7,692 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "In order to allow for arbitrarily large and complex environments, every sizable world built in the C4 Engine World Editor should be organized into multiple zones. The root node of a world is an infinitely large zone, and all other zones are contained within the root zone. When new zones are added to a world, they need to be connected by portals so that it's possible to see from one zone into another. This tutorial describes a simple example in which two rooms are con...")
11:02, 15 July 2023 ‎New World Tutorial (hist | edit) ‎[18,594 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "This tutorial teaches you how to create a new world from scratch in the C4 Engine and add all of the essential pieces for a typical game level. To enlarge any of the screenshots below, click on the thumbnail icon below the image. == Step A: Open the World Editor == To open the World Editor with a new empty world, select '''New World''' from the C4 Menu or type Ctrl-N when any user interface window is open. If you're running the demo game, you may want to hit E...")
10:57, 15 July 2023 ‎Fog Spaces (hist | edit) ‎[4,926 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "In the C4 Engine, a '''fog space''' is a node that causes fog to be rendered in a scene. It's actually a half-space because all space is divided in half by a single boundary plane, and fog is rendered on one side of the plane. == Creating a Fog Space == right A fog space is placed in a world using the Fog Space tool in the Atmosphere Page (shown to the right) in the World Editor under the Object tab. This tool draws a rectangular...")
10:55, 15 July 2023 ‎Motion Blur (hist | edit) ‎[2,490 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "right|frame|'''Figure 1.''' Motion blur is visible due to the movement of the camera and the falling debris. The C4 Engine is capable of rendering full-scene motion blur as a post-processing effect. Motion blur in C4 is based on the concept of a velocity buffer, and it employs a sophisticated algorithm that uses information in both the velocity buffer and the structure buffer to apply the correct blur after the entire scene has been rendered. The...")
10:54, 15 July 2023 ‎Cascaded Shadow Mapping (hist | edit) ‎[3,167 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ Cascaded shadow mapping is the method used by the C4 Engine to cast real-time dynamic shadows over very large areas for an infinite light source. This article describes the settings that control the sizes of the cascades and the transition areas between them, which affect the resolution of the shadows and the smoothness involved in changing from one cascade to another. == Shadow Settings == The infinite light generates up to four separate shadows maps during...")
10:53, 15 July 2023 ‎Models and Instanced Worlds (hist | edit) ‎[5,423 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ There are two file formats in which scene data can be saved for use in the C4 Engine: # A world file having the <code>.wld</code> extension. # A model file having the <code>.mdl</code> extension. Both of these types of resources can contain just about any kind of scene data, and they can both be loaded into a larger world as instances of the data they contain. This article describes the differences between models and instanced worlds and discusses when one ty...")
10:51, 15 July 2023 ‎The C4 Rendering Pipeline (hist | edit) ‎[5,804 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "right|frame|'''Figure 1.''' The major stages of the C4 Engine rendering pipeline. The C4 Engine executes a complex sequence of rendering operations during each frame of gameplay. This article gives a high-level overview of the various components of the C4 Engine rendering pipeline so that users of the engine, having some knowledge of its internal processes, can achieve more efficient results. The following sections describe the rendering stages exec...")
10:49, 15 July 2023 ‎Defining a Custom Method (hist | edit) ‎[11,633 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "In the C4 Engine, a ''method'' refers to an individual action that can appear in a script. There are many types of methods built into the engine, and an application can define its own custom methods by implementing new subclasses of the [http://c4engine.com/docs/Controller/Method.html Method] class. == Defining a Method Subclass == In this article, we will use the example of a method called <code>ChangeLightColorMethod</code> that simply changes the color of a light so...")
10:48, 15 July 2023 ‎Defining a Custom Controller (hist | edit) ‎[13,036 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "In the C4 Engine, a ''controller'' is attached to a node to give it some kind of dynamic behavior. A controller is represented by a subclass of the [http://c4engine.com/docs/Controller/Controller.html <code>Controller</code>] class and contains all of the information needed to move or change an object in some way. It is often the case that a controller is assigned to a node and configured in the World Editor under the Controller tab in the Node Info window. == Defining...")
10:46, 15 July 2023 ‎Distribution Controller (hist | edit) ‎[2,057 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Distribution Controller''' is a special type of controller that forwards the messages it receives to other controllers. This can be useful for performing the same action on multiple nodes in the world using only a single script method. If the target of a script method has a Distribution Controller attached to it, then it's as if the same script method were applied to all of the nodes to which the distribution controller forwards its messages. As an exam...")
10:46, 15 July 2023 ‎Animation Controller (hist | edit) ‎[1,728 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Animation Controller''' is a type of controller that can be used to play animations for a generic model. == Settings == The following settings are available for Animation Controllers. {| {{Table}} {{Tablehead|Setting|Description}} |- {{Setting|'''Initial animation name'''|The name of the animation resource that is initially applied to the model.}} |- {{Setting|'''Animation is initially playing'''|If checked, then the animation is initially playing whe...")
10:45, 15 July 2023 ‎Physics Controller (hist | edit) ‎[1,426 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Physics Controller''' is a type of controller that represents the global physics simulation. The Physics Controller is built into the core engine, and automatically assigned to the Physics Node when it is placed in the scene. A single Physics Node should be placed in any world that uses the built-in physics simulation by using the tool in the Physics Page. == Settings == The following settings are available for Physics Controllers. {| {{Table}} {{...")
10:45, 15 July 2023 ‎Rigid Body Controller (hist | edit) ‎[2,971 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Rigid Body Controller''' is a type of controller that represents a rigid body in a physics simulation. The Rigid Body Controller is built into the core engine, and it's used for all solid objects that move under the control of the built-in physics system. == Settings == The following settings are available for Rigid Body Controllers. {| {{Table}} {{Tablehead|Setting|Description}} |- {{HeadingSetting|'''Rigid Body Flags'''|}} |- {{Setting|'''...")
10:44, 15 July 2023 ‎Cloth Controller (hist | edit) ‎[5,491 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Cloth Controller''' is the type of controller assigned to a dynamic cloth geometry. The Cloth Controller is built into the core engine, and it is part of the Physics Manager. == Settings == The following settings are available for Cloth Controllers. {| {{Table}} {{Tablehead|Setting|Description}} |- {{HeadingSetting|'''Deformable Body Flags'''|}} |- {{Setting|'''Ignore force fields'''|If checked, then force fields do not affect this...")
10:43, 15 July 2023 ‎Rope Controller (hist | edit) ‎[5,041 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Rope Controller''' is the type of controller assigned to a dynamic rope geometry. The Rope Controller is built into the core engine, and it is part of the Physics Manager. == Settings == The following settings are available for Rope Controllers. {| {{Table}} {{Tablehead|Setting|Description}} |- {{HeadingSetting|'''Deformable Body Flags'''|}} |- {{Setting|'''Ignore force fields'''|If checked, then force fields do not affect this rop...")
10:43, 15 July 2023 ‎Spin Controller (hist | edit) ‎[2,788 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Spin Controller''' is a type of controller that causes a node to continuously spin about a particular axis. The Spin Controller is built into the core engine, and it is one of four ''kinematic'' controllers that cause an object to follow an exact motion. Rigid bodies controlled by the Physics Manager are able to interact with kinematic objects, but they cannot stop kinematic objects or alter their motions. A kinematic object pushes rigid bodies out of it...")
10:42, 15 July 2023 ‎Rotation Controller (hist | edit) ‎[3,388 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Rotation Controller''' is a type of controller that causes a node to rotate forward or backward through a given angle. The Rotation Controller is built into the core engine, and it is one of four ''kinematic'' controllers that cause an object to follow an exact motion. Rigid bodies controlled by the Physics Manager are able to interact with kinematic objects, but they cannot stop kinematic objects or alter their motions. A kinematic object pushes rigid b...")
10:42, 15 July 2023 ‎Oscillation Controller (hist | edit) ‎[2,960 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Oscillation Controller''' is a type of controller that causes a node to oscillate between two positions on a sine wave. The Oscillation Controller is built into the core engine, and it is one of four ''kinematic'' controllers that cause an object to follow an exact motion. Rigid bodies controlled by the Physics Manager are able to interact with kinematic objects, but they cannot stop kinematic objects or alter their motions. A kinematic object pushes rig...")
10:40, 15 July 2023 ‎Movement Controller (hist | edit) ‎[3,273 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ The '''Movement Controller''' is a type of controller that causes a node to move forward and backward between two positions. The Movement Controller is built into the core engine, and it is one of four ''kinematic'' controllers that cause an object to follow an exact motion. Rigid bodies controlled by the Physics Manager are able to interact with kinematic objects, but they cannot stop kinematic objects or alter their motions. A kinematic object pushes rigid bo...")
10:39, 15 July 2023 ‎String Tables (hist | edit) ‎[1,512 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "'''String tables''' are used by the C4 Engine to store human-readable text strings in resources that are external to the engine code and game code. The use of string tables is not required, but they can be convenient for storing strings separately in order to make localization easy and allow text to be changed without the need to recompile your game. == String Table Resources == String table resources have the <code>.str</code> file extension and reside inside subfolde...")
10:38, 15 July 2023 ‎File Locations (hist | edit) ‎[1,325 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "The following table lists the locations where certain types of files created by the C4 Engine are stored under Windows. {| {{Table}} {{Tablehead|File Type|File Location}} |- {{Tablerow|Log file|<code>C:\Users\''<username>''\AppData\Local\C4 Engine\</code>}} |- {{Tablerow|Configuration files|<code>C:\Users\<username>\AppData\Roaming\C4 Engine\</code>}} |- {{Tablerow|Screenshots and saved games|<code>C:\Users\<username>\Documents\C4 Engine\</code>}}...")
10:36, 15 July 2023 ‎Pack Files and Virtual Directories (hist | edit) ‎[3,269 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "The Resource Manager supports pack files and a virtual directory hierarchy. All resources are stored inside the <code>Data</code> folder, where resources can be organized in an arbitrary manner. However, the top-level contents of the <code>Data</code> folder have special meanings. All of the top-level sub-folders of the <code>Data</code> folder behave as if their contents belonged to a single virtual folder at the root of the resource name space. These top-level subfold...")
10:35, 15 July 2023 ‎Command Console (hist | edit) ‎[11,243 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "480px|right The '''Command Console''' window can be opened at any time by pressing the tilde/grave key. (On some non-English keyboards, the key directly below the Escape key should be used.) The window displays a command line and an output buffer as shown in the image to the right. If the C4 Engine was built using the debug settings, the window displays "(Debug)" to the right of the build number. The console stores a small command history that can b...")
10:30, 15 July 2023 ‎C4 Menu (hist | edit) ‎[4,160 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "The '''C4 Menu''' is opened by clicking on the skull logo in the bottom-left corner of the screen. It contains several commands that are built into the core engine as well as commands that access the plugin tools. Most of these menu commands also have equivalent console commands that can be typed into the Command Console. {| {{Table}} {{Tablehead|Command|Description}} |- {{Tablerow|'''New World'''|Opens the World Editor with a new blank world. You can type...")
10:26, 15 July 2023 ‎Release Notes for Version 7.1 (hist | edit) ‎[1,511 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' April 24, 2023 == Core Engine == * Luminance and chromaticity have been separated for most things that emit light. This applies to light sources, emission attributes, and several special effects. This essentially allows color to be chosen independently of brightness, which can be much higher than 1.0. Brightness is now measured in physical quantities appropriate for the type of object. Infinite lights have illuminance measured in kilolux (...")
10:25, 15 July 2023 ‎Release Notes for Version 7.0 (hist | edit) ‎[5,282 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' March 22, 2023 == Core Engine == * The <code>Color4C</code> class has been renamed to [http://c4engine.com/docs/Math/Color4U.html <code>Color4U</code>] to reflect the fact that it has unsigned components. There are also new classes called [http://c4engine.com/docs/Math/Color2U.html <code>Color2U</code>], [http://c4engine.com/docs/Math/Color2S.html <code>Color2S</code>], and [http://c4engine.com/docs/Math/Color4S.html <code>Color4S</code>],...")
10:24, 15 July 2023 ‎Release Notes for Version 6.9 (hist | edit) ‎[4,179 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' November 2, 2018 (C4 version 6.9 corresponds to Tombstone version 2.9.) * The file formats have been updated a little bit in this version. While it's not a requirement, you ''may'' upgrade your resources to the newer formats by typing <code>updateworlds</code> in the Command Console. '''Always backup your entire Data folder before doing this just in case something goes wrong.''' == Core Engine == * All of the unsigned integer types t...")
10:23, 15 July 2023 ‎Release Notes for Version 6.5 (hist | edit) ‎[2,931 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' September 30, 2017 (C4 version 6.5 corresponds to Tombstone version 2.5.) == Core Engine == === Math Library === * The vector and matrix classes have been redesigned and now have new capabilities that promote higher performance and more legible code. * Vector components can now be accessed using the swizzle syntax that's available in shading languages. For example, a 3D vector <code>v</code> can be treated as another 3D vector with its...")
10:22, 15 July 2023 ‎Release Notes for Version 6.2 (hist | edit) ‎[757 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' May 11, 2017 (C4 version 6.2 corresponds to Tombstone version 2.2.) == Core Engine == === Graphics Manager === * When the <code>GL_NV_alpha_to_coverage_dither_control</code> extension is available, the engine now disables dithering for alpha to coverage rendering. This gets rid of the unsightly dot pattern sometimes visible in dense alpha-tested vegetation. == Tools == === Model Viewer === * Added a scale factor to the animation impor...")
10:22, 15 July 2023 ‎Release Notes for Version 6.1 (hist | edit) ‎[4,579 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' April 29, 2017 (C4 version 6.1 corresponds to Tombstone version 2.1.) == Core Engine == * The project files for Visual Studio have been updated to 2017. == Graphics Manager == * The engine no longer attempts to figure out how fast the GPU is in order to set defaults for all the rendering options. A single set of default options is now used for all GPUs. * By default, the engine now tries to create a 1920×1080 full-screen renderin...")
10:21, 15 July 2023 ‎Release Notes for Version 6.0 (hist | edit) ‎[3,230 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' January 27, 2017 (C4 version 6.0 corresponds to Tombstone version 2.0.) == Core Engine == * Support for the Open Data Description Language has been updated to version 2.0. === Graphics Manager === * A few new workarounds have been implemented to deal with subtle bugs in the AMD graphics driver. === Interface Manager === * All text drawing, both in the user interface and in panel effects, now uses our new technology to render glyphs on...")
10:20, 15 July 2023 ‎Release Notes for Version 5.5.1 (hist | edit) ‎[1,219 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' December 6, 2016 (C4 version 5.5.1 corresponds to Tombstone version 1.5.1.) == Core Engine == * The API documentation has been corrected in many places to update function names in cross references. === World Manager === * New settings have been added to the Interaction property that let you specify object-space axis and angle constraints that have to be satisfied for an object to appear interactive. The direction that the camera is look...")
10:20, 15 July 2023 ‎Release Notes for Version 5.5 (hist | edit) ‎[1,554 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' November 16, 2016 (C4 version 5.5 corresponds to Tombstone version 1.5.) == Core Engine == === Graphics Manager === * This version of the engine contains a workaround that avoids a bug in the current AMD graphics drivers. This has to do with the code that resolves the multisample frame buffer. === Interface Manager === * The appearance of the set of GUI widgets has been updated to be more crisp and to be ready for high DPI displays. Th...")
10:19, 15 July 2023 ‎Release Notes for Version 5.0 (hist | edit) ‎[5,188 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' September 20, 2016 (C4 version 5.0 corresponds to Tombstone version 1.0.) == Core Engine == * All C-style casts have been changed to constructor syntax. * The <code>*</code> and <code>%</code> operators for dot product and cross product have been removed from the engine. The <code>Dot()</code> and <code>Cross()</code> functions should always be used instead. * The container modification and iteration functions have been made more verbos...")
10:19, 15 July 2023 ‎Release Notes for Version 4.5 (hist | edit) ‎[3,327 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' March 28, 2015 == Core Engine == * The C4 Engine now runs on iOS devices. Separate Xcode project files are included with the engine for those who have a license for mobile development. The C4 Engine currently runs on iOS devices containing an A7 or A8 processor, listed below. ** iPad Air and iPad Air 2 ** iPad Mini with Retina display and iPad Mini 3 ** iPhone 5s and iPhone 6 * Custom properties, controllers, properties, forces, modifiers...")
10:18, 15 July 2023 ‎Release Notes for Version 4.2 (hist | edit) ‎[2,683 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' January 11, 2015 == Core Engine == === Graphics Manager === * Screen-space depth derivatives are now stored in the structure buffer along with the existing high-precision linear depth value. This allows for higher quality rendering along depth discontinuities, making effects such as SSAO look better. When motion blur is enabled, screen-space velocities are now stored in a separate render buffer. * Support for the Nvidia driver API has be...")
10:17, 15 July 2023 ‎Release Notes for Version 4.1 (hist | edit) ‎[4,467 bytes] ‎Eric Lengyel (talk | contribs) (Created page with "__NOTOC__ '''Release date:''' December 25, 2014 == Core Engine == * The format of animation resources has changed in this release in order to accommodate morph weight animation. Existing animation resources need to be updated before they can be used in version 4.1. A conversion utility has been included, and it can be run by typing "updateanims" in the command console. This utility will update all <code>.anm</code> files in the <code>Data</code> directory hierarchy. ''...")

New pages

Navigation menu