Horde3D Wiki - User contributions [en]

Community Roadmap

2021-02-15T18:27:00Z

Irdis:

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 2.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.1.0 ===

* Emscripten support
* Directional light support
* FBX and gltf 2.0 support in collada (asset) converter
* Extension for debug geometry shapes drawing
* Initial PBR support
* PBR sample

=== Horde3D 2.2.0 ===

* New sample that show how to work with different light types, cameras, pipelines and render to texture
* OpenGL 4 AZDO (Achieving zero driver overhead) improvements
* Unification of OpenGL backends common functionality
* Multithreaded culling and scene graph updates (partial)
* Basic instancing support
* Reflection probes

=== Horde3D 2.3.0 ===

* Multithreaded rendering
* Binary shader (preparation for Vulkan shaders)
* Multithreaded culling and scene graph updates
* Instancing support

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* Support for double precision variables.
* Full PBR support, rewrite shader system

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2020-12-22T20:19:40Z

Irdis: Fix roadmap, add 2.3 version

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 2.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.1.0 ===

* Emscripten support
* Directional light support
* FBX and gltf 2.0 support in collada (asset) converter
* Extension for debug geometry shapes drawing
* New sample that show how to work with different light types, cameras, pipelines and render to texture

=== Horde3D 2.2.0 ===

* Partial PBR support
* OpenGL 4 AZDO (Achieving zero driver overhead) improvements
* Unification of OpenGL backends common functionality
* Multithreaded culling and scene graph updates
* Basic instancing support
* Initial PBR support
* Reflection probes

=== Horde3D 2.3.0 ===

* Multithreaded rendering
* Binary shader (preparation for Vulkan shaders)
* Multithreaded culling and scene graph updates
* Instancing support
* Support for double precision variables.

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* Full PBR support, rewrite shader system

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Regenerating documentation

2020-11-07T18:17:21Z

Irdis:

Horde3D uses NaturalDocs as documentation generator. This instruction is written for the version 1 of NaturalDocs. Version 2 is not tested and may or may not work with the instruction below.

In order to regenerate documentation you'll have to:
#[https://www.naturaldocs.org/download/#Legacy Install NaturalDocs].
#Copy horde's css file (api.css) from <Horde's SDK folder>/Horde3D/Docs/html/css to <NaturalDocs folder>/Styles. On Windows it is likely in C:\Program Files (x86)\NaturalDocs. On Linux it is likely in /usr/share/perl5/naturaldocs.
#Use the following command to generate docs:
<code>naturaldocs -i <full path to Horde SDK folder>\Horde3D\Bindings\C++ -o FramedHTML <OutputPath> -p <ProjectPath> -s api</code>.

OutputPath and ProjectPath should also be full paths, like <code>C:/GeneratedDocs</code>.

NaturalDocs cannot change the name of the css file that is included with generated documentation, so it is always named main.css and resides in <ProjectPath>/styles.
Therefore, the reference to the css file should be changed in the generated docs from <code>../styles/main.css</code> to <code>css/api.css</code>.
After that generated doc file should be renamed to _api.html and copied to <Horde's SDK folder>/Horde3D/Docs/html.

Automated script for Windows is available. Powershell 2.0 is required.
In order to run the script open (first time only) powershell with administrator rights and type <code>Set-ExecutionPolicy RemoteSigned</code> or <code>Set-ExecutionPolicy Unrestricted</code>.
Open the script with your favorite text editor and change the paths at the top. Run the script.

Automated script for Linux is also available.
Do not forget to make script executable with <code>chmod +x Horde_generate_docs_linux.sh</code>

Check this forum thread to download scripts: [http://www.horde3d.org/forums/viewtopic.php?f=6&t=2305 link]

Community Roadmap

2020-03-01T19:12:59Z

Irdis: /* Release milestones */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.0.0 ===

* Move Overlays to an extension - done.
* Directional light support
* Material class performance improvements - done
* OpenGL ES3 backend - done
* Support for Android & iOS platforms - android support is done, ios is planned
* Multithreaded culling and scene graph updates - partially done

=== Horde3D 2.1.0 ===

* Emscripten support
* Instancing support
* FBX and gltf 2.0 support in collada (asset) converter
* Extension for debug geometry shapes drawing.
* New sample that show how to work with different light types, cameras, pipelines and render to texture.

=== Horde3D 2.2.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.
* Initial PBR support
* Reflection probes

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* Full PBR support, rewrite shader system

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2020-03-01T19:11:51Z

Irdis: /* Release milestones */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.0.0 ===

* Move Overlays to an extension - done.
* Directional light support
* Material class performance improvements - done
* OpenGL ES3 backend - done
* Support for Android & iOS platforms - android support is done, ios is planned
* Multithreaded culling and scene graph updates - partially done

=== Horde3D 2.1.0 ===

* Emscripten support
* Instancing support
* FBX and gltf 2.0 support in collada (asset) converter
* Extension for debug geometry shapes drawing.
* New sample that show how to work with different light types, cameras, pipelines and render to texture.

=== Horde3D 2.2.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.
* PBR support
* Reflection probes

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* PBR support

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2020-03-01T19:08:46Z

Irdis: /* Release milestones */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.0.0 ===

* Move Overlays to an extension - done.
* Directional light support
* Material class performance improvements - done
* OpenGL ES3 backend - done
* Support for Android & iOS platforms - android support is done, ios is planned
* Multithreaded culling and scene graph updates

=== Horde3D 2.1.0 ===

* Emscripten support
* Instancing support
* FBX and gltf 2.0 support in collada (asset) converter
* Extension for debug geometry shapes drawing.
* New sample that show how to work with different light types, cameras, pipelines and render to texture.

=== Horde3D 2.2.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* PBR support

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2019-02-01T20:00:09Z

Irdis: /* Horde3D 2.1.0 */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.0.0 ===

* Move Overlays to an extension.
* Support for geometry shapes drawing.
* Directional light support
* Material class performance improvements
* OpenGL ES3 backend.
* Support for Android & iOS platforms.
* New sample that show how to work with different light types, cameras, pipelines and render to texture.

=== Horde3D 2.1.0 ===
* Multithreaded culling and scene graph updates
* Instancing support
* FBX support in collada (asset) converter

=== Horde3D 2.2.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* PBR support

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2019-02-01T19:58:06Z

Irdis:

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 2.0.0 ===

* Move Overlays to an extension.
* Support for geometry shapes drawing.
* Directional light support
* Material class performance improvements
* OpenGL ES3 backend.
* Support for Android & iOS platforms.
* New sample that show how to work with different light types, cameras, pipelines and render to texture.

=== Horde3D 2.1.0 ===
* Multithreaded culling and scene graph updates
* Instancing support

=== Horde3D 2.2.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.

=== Horde3D 3.0.0 ===

* Moving scene graph to utility library.
* Clustered forward (deferred) lighting support.
* Model resources.
* Vulkan support
* Custom memory allocation
* PBR support

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2017-10-01T11:52:17Z

Irdis: /* Horde3D 2.0.0 */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 1.1.0 ===

* Move Overlays to an extension.
* Support for geometry shapes drawing.
* Directional light support
* Material class performance improvements
* Multithreaded culling and scene graph updates

=== Horde3D 1.2.0 ===

* OpenGL ES3 backend.
* Support for Android & iOS platforms.
* Instancing support

=== Horde3D 1.3.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.

=== Horde3D 2.0.0 ===

* Moving scene graph to utility library.
* Model resources.
* Vulkan support
* Custom memory allocation
* PBR support

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2017-10-01T11:50:13Z

Irdis: /* Horde3D 2.0.0 */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 1.1.0 ===

* Move Overlays to an extension.
* Support for geometry shapes drawing.
* Directional light support
* Material class performance improvements
* Multithreaded culling and scene graph updates

=== Horde3D 1.2.0 ===

* OpenGL ES3 backend.
* Support for Android & iOS platforms.
* Instancing support

=== Horde3D 1.3.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.

=== Horde3D 2.0.0 ===

* Moving scene graph to utility library.
* Model resources.
* Vulkan support
* Custom memory allocation
* PBR support

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues/milestones

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Community Roadmap

2017-10-01T11:48:46Z

Irdis: /* Release milestones */

As a way to keep the community in touch with the development of '''Horde3D''' project, this page will keep an up to date log of the official '''Roadmap''' for next releases.

= Release milestones =

Our policy is to release often, with atomic changes between two following releases.

The current release version is: '''Horde3D 1.0.0'''

For the future, we planned the following releases:

=== Horde3D 1.1.0 ===

* Move Overlays to an extension.
* Support for geometry shapes drawing.
* Directional light support
* Material class performance improvements
* Multithreaded culling and scene graph updates

=== Horde3D 1.2.0 ===

* OpenGL ES3 backend.
* Support for Android & iOS platforms.
* Instancing support

=== Horde3D 1.3.0 ===

* OpenGL 4 AZDO (Achieving zero driver overhead) improvements.
* Support for double precision variables.

=== Horde3D 2.0.0 ===

* Moving scene graph to utility library.
* Model resources.
* Vulkan support
* Custom memory allocation

You can follow the progress on this '''GitHub''' page:

https://github.com/horde3d/Horde3D/issues/milestones

= Versioning system =

The '''Horde3D''' project is following [http://semver.org/ SemVer 2.0] definition.

Basically it means that, given a version number '''MAJOR.MINOR.PATCH''', we increment the:

<blockquote>
MAJOR version when we make incompatible API changes,
 
MINOR version when we add functionality in a backwards-compatible manner, and
 
PATCH version when we make backwards-compatible bug fixes.
</blockquote>

Additional labels for pre-release and build metadata are used when necessary ('''i.e.:''' ''Alpha'', ''Beta'', ''Release Candidate'', etc.)

{{ContentBlock | width=100% | thickness=1 | color=#eeee88 | content-color=#ffffcc | content=
A '''deprecated''' version of this '''Roadmap''' is available at: [[Community Roadmap deprecated]].}}

Regenerating documentation

2017-07-06T10:23:15Z

Irdis:

Horde3D uses NaturalDocs as documentation generator.

In order to regenerate documentation you'll have to:
#[http://www.naturaldocs.org/download.html Install NaturalDocs]
#Copy horde's css file (api.css) from <Horde's SDK folder>/Horde3D/Docs/html/css to <NaturalDocs folder>/Styles. On Windows it is likely in C:\Program Files (x86)\NaturalDocs. On Linux it is likely in /usr/share/perl5/naturaldocs.
#Use the following command to generate docs:
<code>naturaldocs -i <full path to Horde SDK folder>\Horde3D\Bindings\C++ -o FramedHTML <OutputPath> -p <ProjectPath> -s api</code>.

OutputPath and ProjectPath should also be full paths, like <code>C:/GeneratedDocs</code>.

NaturalDocs cannot change the name of the css file that is included with generated documentation, so it is always named main.css and resides in <ProjectPath>/styles.
Therefore, the reference to the css file should be changed in the generated docs from <code>../styles/main.css</code> to <code>css/api.css</code>.
After that generated doc file should be renamed to _api.html and copied to <Horde's SDK folder>/Horde3D/Docs/html.

Automated script for Windows is available. Powershell 2.0 is required.
In order to run the script open (first time only) powershell with administrator rights and type <code>Set-ExecutionPolicy RemoteSigned</code> or <code>Set-ExecutionPolicy Unrestricted</code>.
Open the script with your favorite text editor and change the paths at the top. Run the script.

Automated script for Linux is also available.
Do not forget to make script executable with <code>chmod +x Horde_generate_docs_linux.sh</code>

Check this forum thread to download scripts: [http://www.horde3d.org/forums/viewtopic.php?f=6&t=2305 link]

Regenerating documentation

2017-06-14T21:17:14Z

Irdis:

Horde3D uses NaturalDocs as documentation generator.

In order to regenerate documentation you'll have to:
#[http://www.naturaldocs.org/download.html Install NaturalDocs]
#Copy horde's css file (api.css) from <Horde's SDK folder>/Horde3D/Docs/html/css to <NaturalDocs folder>/Styles
#Use the following command to generate docs:
<code>naturaldocs -i <full path to Horde SDK folder>\Horde3D\Bindings\C++ -o FramedHTML <OutputPath> -p <ProjectPath> -s api</code>.

OutputPath and ProjectPath should also be full paths, like <code>C:/GeneratedDocs</code>.

NaturalDocs cannot change the name of the css file that is included with generated documentation, so it is always named main.css and resides in <ProjectPath>/styles.
Therefore, the reference to the css file should be changed in the generated docs from <code>../styles/main.css</code> to <code>css/api.css</code>.
After that generated doc file should be renamed to _api.html and copied to <Horde's SDK folder>/Horde3D/Docs/html.

Automated script for Linux is in the works.

Automated script for Windows is available. Powershell 2.0 is required.
In order to run the script open (first time only) powershell with administrator rights and type <code>Set-ExecutionPolicy RemoteSigned</code> or <code>Set-ExecutionPolicy Unrestricted</code>.
Open the script with your favorite text editor and change the paths at the top. Run the script.
[[File:Horde3D_generate_docs.ps1]]

Regenerating documentation

2017-06-13T20:37:35Z

Irdis: Documentation generator how-to

Horde3D Wiki:Community portal

2017-06-13T19:45:17Z

Irdis:

__NOEDITSECTION__ __NOTOC__{{ContentBlock|color=orange
|content= '''The community portal section of the Horde3D wiki contains community contributed articles that are not part of the official documentation. Feel free to add articles to our wiki or links to external tutorials.'''}}
{{SpacerBlock}}
{{ContentBlock|
|header=Information, instructions and tips on using Horde3D
|content={{!!}}
==Programming Guide==
=== Build Instructions ===
#[[Building Horde3D]] - Instructions for obtaining the code and building Horde on all supported platforms
#[[Regenerating documentation]] - Instructions for updating documentation

[[Category: Tutorials]]

===Beginner Tutorials===
#[[Tutorial - Hello World]] - In this section we will create a simple application that loads a character and animates it using a walk cycle.
#[[Tutorial - Picking]] - In this section we will demonstrate picking the node under the mouse cursor
#[[Tutorial - Simple HUD]] - How to use showOverlay to create a simple HUD.
#[[Tutorial - Setup Horde with SDL]] - How to Setup Horde with SDL.
#[[Tutorial - Setup Horde with Qt4]] - How to Setup Horde with Qt4.
#[[Tutorial - Setup Horde with Qt5 & QtQuick 2.1]] - How to Setup Horde with Qt5 & QtQuick 2.1.
#[[Tutorial - Setup Horde with Gtkmm]] - How to Setup Horde with Gtkmm
#[[Tutorial - Setup Horde with SFML]] - How to Setup Horde with SFML
#[[Tutorial - Stereo rendering]] - Basic outline for quad-buffered stereo rendering

===Advanced Tutorials===
#[[Basic Pipeline Tutorial]] - Create your first custom pipeline.
#[[Procedurally generated geometry tutorial]] - How to create Horde3D compatible procedural geometry (Horde3D 1.0.0 '''Beta 3''' only!).

==Shader Development==
[[Category: Techniques]]
===General===
#A syntax highlighting schemes for editors like Notepad++ and Kate that work with Horde3D shader files can be found [http://www.horde3d.org/forums/viewtopic.php?f=5&t=2303 here] and [http://www.horde3d.org/forums/viewtopic.php?f=5&t=697 here (old)].

===Debugging and Profiling===
#[[Using GPU PerfStudio]] - Quick steps to get started with GPU PerfStudio

===Render System Basics===
#[[The Flexible Rendering Pipeline]] - Introduction to Horde's data-driven rendering pipelines

===Rendering Quality===
#[[Gamma Correction]] - Overview of gamma correction and how to apply it with Horde

===Shading===
#[[Shading Technique - Dot Product Detail Texturing]] - Using the dot product of vectors and signed textures for high frequency detail
#[[Shading Technique - Palette Coloring]] - Quick and dirty palette recoloration of objects
#[[Shading Technique - Gloss Mapping]] - Mask which areas of an object have specular highlights
#[[Shading Technique - Glow Mapping]] - Allow areas on an object to emit a strong glowing highlight
#[[Shading Technique - Fresnel]] - Using reflection and refraction
#[[Shading Technique - Linear Depth Buffer]] - Create a custom linear depth buffer using vertex
#[[Shading Technique - Terrain Shading]] - Height and slope based shading with triplanar texturing

===Preprocessing===
#[[Preprocessing Technique - Distance Field Vector Textures]] - Using Adobe Photoshop to generate textures suitable for efficient vector art rendering

==Asset Creation==

[[Category: Content Import]]
#[[DCC Tool Support]] - List of supported Digital Content Creation Tools
#[[AssetTroubleshooting|Troubleshooting]] - ''"Help, my model is not showing up!"''
#[[Tips and Techniques]] - Asset creation suggestions & ideas for Horde3d, exporting and program quirks..
#[[Extending ColladaConv]] - Add support for exporting cameras
}}

Horde3D Wiki:Community portal

2017-04-25T19:58:58Z

Irdis:

__NOEDITSECTION__ __NOTOC__{{ContentBlock|color=orange
|content= '''The community portal section of the Horde3D wiki contains community contributed articles that are not part of the official documentation. Feel free to add articles to our wiki or links to external tutorials.'''}}
{{SpacerBlock}}
{{ContentBlock|
|header=Information, instructions and tips on using Horde3D
|content={{!!}}
==Programming Guide==
=== Build Instructions ===
#[[Building Horde3D]] - Instructions for obtaining the code and building Horde on all supported platforms

[[Category: Tutorials]]

===Beginner Tutorials===
#[[Tutorial - Hello World]] - In this section we will create a simple application that loads a character and animates it using a walk cycle.
#[[Tutorial - Picking]] - In this section we will demonstrate picking the node under the mouse cursor
#[[Tutorial - Simple HUD]] - How to use showOverlay to create a simple HUD.
#[[Tutorial - Setup Horde with SDL]] - How to Setup Horde with SDL.
#[[Tutorial - Setup Horde with Qt4]] - How to Setup Horde with Qt4.
#[[Tutorial - Setup Horde with Qt5 & QtQuick 2.1]] - How to Setup Horde with Qt5 & QtQuick 2.1.
#[[Tutorial - Setup Horde with Gtkmm]] - How to Setup Horde with Gtkmm
#[[Tutorial - Setup Horde with SFML]] - How to Setup Horde with SFML
#[[Tutorial - Stereo rendering]] - Basic outline for quad-buffered stereo rendering

===Advanced Tutorials===
#[[Basic Pipeline Tutorial]] - Create your first custom pipeline.
#[[Procedurally generated geometry tutorial]] - How to create Horde3D compatible procedural geometry (Horde3D 1.0.0 '''Beta 3''' only!).

==Shader Development==
[[Category: Techniques]]
===General===
#A syntax highlighting schemes for editors like Notepad++ and Kate that work with Horde3D shader files can be found [http://www.horde3d.org/forums/viewtopic.php?f=5&t=2303 here] and [http://www.horde3d.org/forums/viewtopic.php?f=5&t=697 here (old)].

===Debugging and Profiling===
#[[Using GPU PerfStudio]] - Quick steps to get started with GPU PerfStudio

===Render System Basics===
#[[The Flexible Rendering Pipeline]] - Introduction to Horde's data-driven rendering pipelines

===Rendering Quality===
#[[Gamma Correction]] - Overview of gamma correction and how to apply it with Horde

===Shading===
#[[Shading Technique - Dot Product Detail Texturing]] - Using the dot product of vectors and signed textures for high frequency detail
#[[Shading Technique - Palette Coloring]] - Quick and dirty palette recoloration of objects
#[[Shading Technique - Gloss Mapping]] - Mask which areas of an object have specular highlights
#[[Shading Technique - Glow Mapping]] - Allow areas on an object to emit a strong glowing highlight
#[[Shading Technique - Fresnel]] - Using reflection and refraction
#[[Shading Technique - Linear Depth Buffer]] - Create a custom linear depth buffer using vertex
#[[Shading Technique - Terrain Shading]] - Height and slope based shading with triplanar texturing

===Preprocessing===
#[[Preprocessing Technique - Distance Field Vector Textures]] - Using Adobe Photoshop to generate textures suitable for efficient vector art rendering

==Asset Creation==

[[Category: Content Import]]
#[[DCC Tool Support]] - List of supported Digital Content Creation Tools
#[[AssetTroubleshooting|Troubleshooting]] - ''"Help, my model is not showing up!"''
#[[Tips and Techniques]] - Asset creation suggestions & ideas for Horde3d, exporting and program quirks..
#[[Extending ColladaConv]] - Add support for exporting cameras
}}