DirectX Tool Kit

Commented Unassigned: Implement polyhedron as geometric primitive [931]

walbourn — Wed, 22 May 2013 22:42:29 GMT

DirectXTK implements a number of GeometricPrimitives, but it is missing a number of shapes supported by OpenGL's glut library.

* glut*Dodecahedron
* glut*Octahedron
* glut*Tetrahedron
* glut*Icosahedron

This combined with the existing Cube implementation make up the '[platonic solids](http://en.wikipedia.org/wiki/Platonic_solid)'

PS: It's also missing glut*Cone, but that's covered by [921](https://directxtk.codeplex.com/workitem/921)
Comments: ** Comment from web user: walbourn **

Note that one difference between DirectXTK and OpenGL's glUT is that DirectXTK supports texture coordinates as well as normal on all GeometricPrimitive shapes. glut supports normals but not texture coordinates except on the Utah teapot.

Updated Wiki: GeometricPrimitive

walbourn — Wed, 22 May 2013 22:32:33 GMT

This is a helper for drawing simple geometric shapes including texture coordinates and surface normals.

Cube
Sphere
Geodesic Sphere
Cylinder
Torus
Teapot

Initialization

The GeometryPrimitive class must be created from a factory method which takes the Direct3D 11 device context.

std::unique_ptr<GeometricPrimitive> shape(
GeometricPrimitive::CreateTeapot(deviceContext) );

For exception safety, it is recommended you make use of the C++ RAII pattern and use a std::unique_ptr or std::shared_ptr

CreateCube( deviceContext, float size = 1)
CreateSphere( deviceContext, float diameter = 1, size_t tessellation = 16)
CreateGeoSphere( deviceContext, float diameter = 1, size_t tessellation = 3)
CreateCylinder( deviceContext, float height = 1, float diameter = 1, size_t tessellation = 32)
CreateTorus( deviceContext, float diameter = 1, float thickness = 0.333f, size_t tessellation = 32)
CreateTeapot( deviceContext, float size = 1, size_t tessellation = 8)

Simple drawing

shape->Draw(world, view, projection, Colors::CornflowerBlue);

The draw method accepts an optional texture parameter, wireframe flag, and a callback function which can be used to override the default rendering state:

shape->Draw(world, view, projection, Colors::White, catTexture, false, [=]
{
    deviceContext->OMSetBlendState(...);
});

This makes use of a BasicEffect shared by all geometric primitives drawn on that device context.

Advanced drawing

This form of drawing makes use of a custom Effects instance. The caller is responsible for using an input layout that matches the effect.

IEffect* myeffect = ...

Microsoft::WRL::ComPtr<ID3D11InputLayout> inputLayout;
shape->CreateInputLayout( myeffect, &inputLayout );

shape->Draw( myeffect, inputLayout.Get() );

This takes an optional parameter for enabling alpha-blending, wireframe, and a callback function which can be used to override the default rendering state.

Coordinate systems

These geometric primitives (based on the XNA Game Studio conventions) use right-handed coordinates. They can be used with left-handed coordinates by setting the rhcoords parameter on the factory methods to 'false' to reverse the winding ordering (the parameter defaults to 'true').

std::unique_ptr<GeometricPrimitive> shape(
GeometricPrimitive::CreateTeapot( deviceContext, 1.f, 8, false ) );

Alpha blending

Alpha blending defaults to using premultiplied alpha. To make use of 'straight' alpha textures, override the blending mode via the optional callback:

CommonStates states(deviceContext);

shape->Draw(world, view, projection, Colors::White, catTexture, false, [=]
{
    deviceContext->OMSetBlendState( states.NonPremultiplied(), nullptr, 0xFFFFFFFF);
});

Feature Level Notes

In order to support all feature levels, the GeometricPrimitive implementation make use of 16-bit indices (DXGI_FORMAT_R16_UINT) which limits to a maximum of 65535 vertices. Feature Level 9.1 is limited to a maximum of 65535 primitives in a single draw.

Threading model

Each GeometricPrimitive instance only supports drawing from one thread at a time, but you can simultaneously submit primitives on multiple threads if you create a separate GeometricPrimitive instance per Direct3D 11 deferred context.
http://msdn.microsoft.com/en-us/library/windows/desktop/ff476892.aspx

Updated Wiki: GeometricPrimitive

walbourn — Wed, 22 May 2013 22:29:11 GMT

This is a helper for drawing simple geometric shapes including texture coordinates and surface normals.

Cube
Sphere
Geodesic Sphere
Cylinder
Torus
Teapot

Initialization

The GeometryPrimitive class must be created from a factory method which takes the Direct3D 11 device context.

std::unique_ptr<GeometricPrimitive> shape(
GeometricPrimitive::CreateTeapot(deviceContext) );

For exception safety, it is recommended you make use of the C++ RAII pattern and use a std::unique_ptr or std::shared_ptr

CreateCube( deviceContext, float size = 1)
CreateSphere( deviceContext, float diameter = 1, size_t tessellation = 16)
CreateGeoSphere( deviceContext, float diameter = 1, size_t tessellation = 3)
CreateCylinder( deviceContext, float height = 1, float diameter = 1, size_t tessellation = 32)
CreateTorus( deviceContext, float diameter = 1, float thickness = 0.333f, size_t tessellation = 32)
CreateTeapot( deviceContext, float size = 1, size_t tessellation = 8)

Simple drawing

shape->Draw(world, view, projection, Colors::CornflowerBlue);

The draw method accepts an optional texture parameter, wireframe flag, and a callback function which can be used to override the default rendering state:

shape->Draw(world, view, projection, Colors::White, catTexture, false, [=]
{
    deviceContext->OMSetBlendState(...);
});

This makes use of a BasicEffect shared by all geometric primitives drawn on that device context.

Advanced drawing

This form of drawing makes use of a custom Effects instance. The caller is responsible for using an input layout that matches the effect.

IEffect* myeffect = ...

Microsoft::WRL::ComPtr<ID3D11InputLayout> inputLayout;
shape->CreateInputLayout( myeffect, &inputLayout );

shape->Draw( myeffect, inputLayout.Get() );

This takes an optional parameter for enabling alpha-blending, wireframe, and a callback function which can be used to override the default rendering state.

Coordinate systems

std::unique_ptr<GeometricPrimitive> shape(
GeometricPrimitive::CreateTeapot( deviceContext, 1.f, 8, false ) );

Alpha blending

Alpha blending defaults to using premultiplied alpha. To make use of 'straight' alpha textures, override the blending mode via the optional callback:

CommonStates states(deviceContext);

shape->Draw(world, view, projection, Colors::White, catTexture, false, [=]
{
    deviceContext->OMSetBlendState( states.NonPremultiplied(), nullptr, 0xFFFFFFFF);
});

Feature Level Notes

Threading model

Commented Unassigned: Implement polyhedron as geometric primitive [931]

walbourn — Wed, 22 May 2013 22:22:25 GMT

DirectXTK implements a number of GeometricPrimitives, but it is missing a number of shapes supported by OpenGL's glut library.

* glut*Dodecahedron
* glut*Octahedron
* glut*Tetrahedron
* glut*Icosahedron

PS: It's also missing glut*Cone, but that's covered by [921](https://directxtk.codeplex.com/workitem/921)
Comments: ** Comment from web user: walbourn **

[Dodecahedron](http://en.wikipedia.org/wiki/Dodecahedron)
[Octahedron](http://en.wikipedia.org/wiki/Octahedron)
[Tetrahedron](http://en.wikipedia.org/wiki/Tetrahedron)
[Icosahedron](http://en.wikipedia.org/wiki/Icosahedron)

Commented Feature: Implement cone as geometry primitive [921]

walbourn — Wed, 22 May 2013 22:22:12 GMT

Hello,

I'm sorry if this is not the right place to request, is there a chance to implement a cone as a geometry primitive in DirectxTK?

the reason is, cones are very useful in implementing spot lights, especially in deferred or pre-pass lightning renderers.

thanks in advance.
Comments: ** Comment from web user: walbourn **

Related to workitem [931](https://directxtk.codeplex.com/workitem/931)

Created Unassigned: Implement polyhedron as geometric primitive [931]

walbourn — Wed, 22 May 2013 22:20:51 GMT

DirectXTK implements a number of GeometricPrimitives, but it is missing a number of shapes supported by OpenGL's glut library.

* glut*Dodecahedron
* glut*Octahedron
* glut*Tetrahedron
* glut*Icosahedron

PS: It's also missing glut*Cone, but that's covered by [921](https://directxtk.codeplex.com/workitem/921)

Commented Feature: Implement cone as geometry primitive [921]

walbourn — Wed, 22 May 2013 22:17:32 GMT

Thanks for the suggestion. Note that the choice of GeometricPrimitives we already implemented was based on historical precedent.

XNA Game Studio same "Primitives3D"
http://xbox.create.msdn.com/en-US/education/catalog/sample/primitives_3d

DXUT 'shapes' (cube, sphere, cylinder, torus, teapot)

OpenGL's glut implements glut*Cone, so this seems like a reasonable request.

New Post: AccessViolationException while creating SpriteBatch

progs — Fri, 17 May 2013 06:12:07 GMT

Hello,

that's it. Works all fine now. Thanks!

New Post: AccessViolationException while creating SpriteBatch

dajyareo — Thu, 16 May 2013 20:26:55 GMT

I imagine that's because the interop hasn't completed initializing yet. Put it in CubeRenderer::CreateWindowSizeDependentResources() instead, or somewhere else.

New Post: AccessViolationException while creating SpriteBatch

progs — Wed, 15 May 2013 18:03:50 GMT

Hello,

I don't get an StackTrace. The Problem i think is here the mixed C++ and C# Code. The WP8 Project is written in C# and includes the C++ Library. I only get the ArgumentViolationException. I also do not think the m_d3dContext is bad, because if I remove the SpriteBatch initialization, all other code (including Context Methods) work fine.

I use the Standard Default Template of Visual Studio and only added the DirectX Tool Kit.

New Post: AccessViolationException while creating SpriteBatch

dajyareo — Wed, 15 May 2013 17:07:33 GMT

Usually I've found this will happen when you've got a bad pointer (perhaps you deleted it somewhere or it was never initialized?). I'd need more information (a stack trace would be handy here) to help you figure out what the cause was. If it's happening when you create your SpriteBatch object, I'd bet your m_d3dContext pointer is bad.

New Post: AccessViolationException while creating SpriteBatch

progs — Wed, 15 May 2013 08:42:54 GMT

Hello,

if I try to create a new SpriteBatch, I get an AccessViolationException on (MainPage.xaml)

DrawingSurfaceBackground.SetBackgroundContentProvider(m_d3dBackground.CreateContentProvider());

Code to init SpriteBatch (CubeRenderer.cpp in CreateDeviceResources()):

m_spriteBatch = unique_ptr<SpriteBatch>(new SpriteBatch(m_d3dContext.Get()));

As Project Template I use the default Windows Phone Direct3D with XAML Tempalte of the Windows Phone 8 SDK and I modify the CubeRenderer basic class. Does anyone know this issue?

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

dajyareo — Wed, 15 May 2013 05:55:35 GMT

That article was perfect! It really helped me understand what was actually going on and how to draw my billboards correctly. My rendering looks great now and is batched together.

Thanks again Shawn! Also, it seems like your blog has a wealth of free information. I'll be studying up on it a lot in the future :)

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

ShawnHargreaves — Wed, 15 May 2013 03:22:40 GMT

This article might help with your question about depth sorting:

http://blogs.msdn.com/b/shawnhar/archive/2009/02/18/depth-sorting-alpha-blended-objects.aspx

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

dajyareo — Tue, 14 May 2013 20:14:53 GMT

Thanks Shawn, this is very helpful. I'll take your advice and do a XMVector3Transform() to transform my positions on the CPU using the billboard's world matrix before rendering, keeping each billboard using the same state for the batch.

The 2nd concern I had was the ordering of the billboards when they were drawn. Giving each billboard its own separate batch had them clipping each other. Do I have to sort manually via Z order before drawing or is there a way to have PrimitiveBatch do the right thing?

Thanks again for your help!

Jared

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

ShawnHargreaves — Tue, 14 May 2013 19:48:26 GMT

You cannot change state settings in between individual draw calls within a single batch. The whole point of a batch is to 'batch' up many draw calls, then submit them to the GPU all in one go. So by definition, it's impossible to have a different state for each draw, because there is really only one single combined draw taking place.

The simplest solution is to use a separate batch (begin/end block) for each object that you want to draw using a different state. First set the state, then begin the batch, then draw, then end the batch.

A more efficient approach is to draw everything in a single batch, and change your rendering algorithms so that all the objects within the batch can use the same state. This means no longer applying a different world matrix to the effect per draw. One way to do that would be to leave the effect world matrix set to identity, and instead apply that same transform to your source vertex positions on the CPU, before passing them to PrimitiveBatch.

An even more efficient but complex way to draw very large numbers of billboards is to do the billboarding computation inside the vertex shader. I don't know of a good D3D sample showing this technique, but the XNA Particle 3D sample uses this idea.

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

dajyareo — Tue, 14 May 2013 17:35:31 GMT

I've been struggling a bit to get this working the right way.. figured I'd give this forum a try.

I'd like to batch a textured billboard quad draw using BasicEffect and PrimitiveBatch.. but I'm not sure how to go about doing this.

What I'm trying to do looks something like this:


// Setup during initialization
BasicEffect* be = new BasicEffect(dc);
be->SetTextureEnabled(true);
be->EnableDefaultLighting(true);

// Load shader blob using BasicEffect and Create input layout using
// VertexPositionNormalColorTexture in DirectXTK
// Create PrimitiveBatch<VertexPositionNormalColorTexture> 

// Every Update Call 
be->SetProjection(camera->GetProjection);
be->SetView(camera->GetView);

// Every draw call
be->SetTexture(myTexture);
be->Apply(dc);
dc->IASetInputLayout(myLayout);
primitiveBatch->Begin();

for(auto it = billboards.begin(); it != billboards.end(); it++)
{
    be->SetWorld(it->GetWorld());
    be->Apply(dc);
    primitiveBatch->DrawQuad(/* draw quad vertices untransformed */);
}

primitiveBatch->End();

In case it's not clear from my code, I'm trying to save to the perframe const buffer the final world translation of each billboard in the effect before calling primitiveBatch draw. The only way I can get this to work properly is do a PrimitiveBatch::Begin() and ::End() call per billboard with each having the basic effect's world translation set each time before the call to ::Begin().

Also, even with my non-batch like calls to PrimitiveBatch, my billboards do not draw in the correct order... Although they do show up as transparent, when placed next to each other, they seem to clip each other. Do I have to manually order each one before drawing in the batch based on its z value?

Thanks!

Jared

New Post: Where to start

walbourn — Tue, 14 May 2013 06:55:56 GMT

There's a ton of material on MSDN for Windows Store and Windows phone 8 which is your best place to start for overviews...

As for DirectXTK, there are a few basic samples to get you started:

New Post: Where to start

Strikerx87 — Sat, 11 May 2013 22:53:23 GMT

I'm a total beginner and I'm wondering if there is any good and free tutorials that go into detail to help me get started making games foe windows store and windows phone 8.

Updated Wiki: Model

walbourn — Sat, 04 May 2013 03:26:19 GMT

This is a class hierarchy for drawing simple meshes with support for loading rigid models from Visual Studio 3D Starter Kit .CMO files and legacy DirectX SDK .SDKMESH files. It is an implementation of a mesh renderer similar to the XNA Game Studio Model, ModelMesh, ModelMeshPart design.

NOTE: Currently Model only supports rigid models. Support for animation, skinning, and frame hierarchy is not yet implemented.

A Model consists of one or more ModelMesh instances. The ModelMesh instances can be shared by multiple instances of Model. A ModelMesh instance consists of one or more ModelMeshPart instances.

Each ModelMeshPart references an index buffer, a vertex buffer, an input layout, an Effects instance, and includes various metadata for drawing the geometry. Each ModelMeshPart represents a single material to be drawn at the same time (i.e. a submesh).

Initialization

Model instances can be loaded from either .CMO files or .SDKMESH files, or from custom file formats. The Model loaders take an EffectFactory instance to facilitate the sharing of Effects and textures between models. For simplicity, provided Model loaders always return built-in Effect instances. Any references to specific shaders in the runtime mesh files are ignored.

Visual Studio 2012 includes a built-in content pipeline that can generate .CMO files from an Autodesk FBX, as well as DDS texture files from various bitmap image formats, as part of the build process. See the Visual Studio 3D Starter Kit for details. http://code.msdn.microsoft.com/windowsapps/Visual-Studio-3D-Starter-455a15f1

EffectFactory fx( device );

auto teapot = Model::CreateFromCMO( device, L"teapot.cmo", fx );

The legacy DirectX SDK has an exporter that will generate .SDKMESH files from an Autodesk FBX. The latest version of this exporter tool can be obtained from http://go.microsoft.com/fwlink/?LinkId=226208

auto tiny = Model::CreateFromSDKMESH( device, L"tiny.sdkmesh", fx );

A Model instance also contains a name (a wide-character string) for tracking and application logic. Model can be copied to create a new Model instance which will have shared references to the same set of ModelMesh instances (i.e. a 'shallow' copy).

Simple drawing

The Model::Draw functions provides a high-level, easy to use method for drawing models.

CommonStates states(device);

XMMATRIX local = XMMatrixTranslation( 1.f, 1.f, 1.f );
local = XMMatrixMultiply( world, local );
tiny->Draw( context, states, local, view, projection );

There are optional parameters for rendering in wireframe and to provide a custom state override callback.

Advanced drawing

Rather than using the standard Model::Draw, the ModelMesh::Draw method can be used on each mesh in turn listed in the Model::meshes collection. ModelMesh::Draw can be used to draw all the opaque parts or the alpha parts individually. The ModelMesh::PrepareForRendering method can be used as a helper to setup common render state, or the developer can set up the state directly before calling ModelMesh::Draw. See ModelMesh for an example.

More detailed control over rendering can be had by skipping the use of Model::Draw and ModelMesh::Draw in favor of the ModelMeshPart::Draw method. Each Model::meshes collection can be scanned for each ModelMesh::meshParts collection to enumerate all ModelMeshPart instances. For this version of draw, the ModelMeshPart::effect and ModelMeshPart::inputLayout can be used, or a custom effect override can be used instead (be sure to create the appropriate matching input layout for the custom effect beforehand using ModelMeshPart::CreateInputLayout). See ModelMeshPart for an example.

Effects control

The Model loaders create an appropriate Effects instance for each ModelMeshPart in a mesh. Generally all effects in a mesh should use the same lighting and fog settings, which is facilitated by the Model::UpdateEffects method. This calls back for each unique effect in the ModelMesh once.

tiny->UpdateEffects([&](IEffect* effect)
{
    auto lights = dynamic_cast<IEffectLights*>(effect);
    if ( lights )
    {
        XMVECTOR dir = XMVector3Rotate( g_XMOne, quat );
        lights->SetLightDirection( 0, dir );
    }
    auto fog = dynamic_cast<IEffectFog*>(effect);
    if ( fog )
    {
        fog->SetFogEnabled(true);
        fog->SetFogStart(6); // assuming RH coordiantes
        fog->SetFogEnd(8);
        fog->SetFogColor(Colors::CornflowerBlue);
    }
});

It is also possible to change the Effects instance used by a given part (such as when overriding the default effect put in place from a Model loader) by calling ModelMeshPart::ModifyEffect. This will regenerate the ModelMeshPart::inputLayout appropriately.

Be sure to call Model::Modified on all Model instances that reference the impacted ModelMesh instance to ensure the cache used by UpdateEffects is correctly updated. Model::Modified should also be called whenever a Model::meshes or ModelMesh::meshParts collection is modified.

As noted above, it is also possible to render part or all of a model using a custom effect as an override, rather than changing the effect referenced by the ModelMeshPart::effect directly. See ModelMeshPart for an example.

Alpha blending

Proper drawing of alpha-blended models can be a complicated procedure. Each ModelMeshPart has a bool value to indicate if the associated part is fully opaque (isAlpha is false), or has some level of alpha transparency (isAlpha is true). The Model::Draw routine handles some basic logic for the rendering, first rendering the opaque parts, then rendering the alpha parts. More detailed control is provided by the ModelMesh::Draw method which can be used to draw all opaque parts of all meshes first, then go back and draw all alpha parts of all meshes second. See ModelMesh for an example.

To indicate the use of ‘straight’ alpha vs. ‘premultiplied’ alpha blending modes, ModelMesh::pmalpha is set by the various loaders functions controlled by a default parameter (which defaults false to indicate the texture files are using 'straight' alpha). If you make use of DirectXTex's texconv tool with the -pmalpha switch, you should use pmalpha=true instead.

Custom render states

All the various Draw method provide a setCustomState callback which can be used to change the state just before the geometry is drawn.

tiny->Draw( context, states, local, view, projection, false, [&]()
{
    ID3D11ShaderResourceView* srv = nullptr;
    context->PSSetShaderResources( 0, 1, &srv );
});

Coordinate systems

Meshes are authored in a specific winding order, typically using the standard counter-clockwise winding common in graphics. The choice of viewing handedness (right-handed vs. left-handed coordinates) is largely a matter of preference and convenience, but it impacts how the models are built and/or exported.

The Visual Studio 3D Starter Kit’s .CMO files assume the developer is using right-handed coordinates. DirectXTK’s default parameters assume you are using right-handed coordinates as well, so the ‘ccw’ parameter defaults to true. If using a .CMO with left-handed coordinates, you should pass false for the ‘ccw’ parameter which will use clockwise winding instead. This makes the geometry visible, but could make textures on the model appear ‘flipped’ in U.

// When using LH coordinates
auto teapot = Model::CreateFromCMO( device, L"teapot.cmo", fx, false );

The legacy DirectX SDK’s .SDKMESH files assume the developer is using left-handed coordinates. DirectXTK’s default parameters assume you are using right-handed coordinates, so the ‘ccw’ parameter defaults to false which will use clockwise winding and potentially have the ‘flipped in U’ texture problem. If using a .SDKMESH with left-handed coordinates, you should pass true for the ‘ccw’ parameter.

// When using LH coordinates
auto tiny = Model::CreateFromSDKMESH( device, L"tiny.sdkmesh", fx, true );

Feature Level Notes

If any ModelMeshPart makes use of 32-bit indices (i.e. ModelMeshPart:: indexFormat equals DXGI_FORMAT_R32_UINT) rather than 16-bit indices (DXGI_FORMAT_R16_UINT), then that model requires Feature Level 9.2 or greater.

If any ModelMeshPart uses adjacency (i.e. ModelMeshPart::primitiveType equals D3D_PRIMITIVE_TOPOLOGY_*_ADJ), then that model requires Feature Level 10.0 or greater. If using tessellation (i.e. D3D_PRIMITIVE_TOPOLOGY_?_CONTROL_POINT_PATCHLIST), then that model requires Feature Level 11.0 or greater.

Keep in mind that there are maximum primitive count limits per ModelMeshPart based on feature level as well (65535 for Feature Level 9.1, 1048575 or Feature Level 9.2 and 9.3, and 4294967295 for Feature Level 10.0 or greater).

Content Notes

The SDKMESH exporter http://go.microsoft.com/fwlink/?LinkId=226208 uses Autodesk FBX 2011.3.1.

VS 2012's CMO exporter uses Autodesk FBX 2013.1. Recommended settings for exporting an FBX as a CMO include:

Geometry: Smoothing Groups, TurboSmooth, Convert Deforming Dummies to Bones, Preserve edge orientation
Animation: Bake Animation (Start=0, End=100, Step=1), Deformations, Skins, Morphs
Units: Automatic
Axis conversion: Y-up
FBX File Format: Binary, FBX 2013

Threading model

The ModelMeshPart is tied to a device, but not a device context. This means that Model creation/loading is ‘free threaded’. Drawing can be done on the immediate context or by a deferred context, but keep in mind device contexts are not ‘free threaded’. See EffectFactory for some additional notes.

DirectX Tool Kit

Commented Unassigned: Implement polyhedron as geometric primitive [931]

Updated Wiki: GeometricPrimitive

Initialization

Simple drawing

Advanced drawing

Coordinate systems

Alpha blending

Feature Level Notes

Threading model

Further Reading

Updated Wiki: GeometricPrimitive

Initialization

Simple drawing

Advanced drawing

Coordinate systems

Alpha blending

Feature Level Notes

Threading model

Further Reading

Commented Unassigned: Implement polyhedron as geometric primitive [931]

Commented Feature: Implement cone as geometry primitive [921]

Created Unassigned: Implement polyhedron as geometric primitive [931]

Commented Feature: Implement cone as geometry primitive [921]

New Post: AccessViolationException while creating SpriteBatch

New Post: AccessViolationException while creating SpriteBatch

New Post: AccessViolationException while creating SpriteBatch

New Post: AccessViolationException while creating SpriteBatch

New Post: AccessViolationException while creating SpriteBatch

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

New Post: Batching textured quads using BasicEffect and PrimitiveBatch

New Post: Where to start

New Post: Where to start

Updated Wiki: Model

Initialization

Simple drawing

Advanced drawing

Effects control

Alpha blending

Custom render states

Coordinate systems

Feature Level Notes

Content Notes

Threading model

Further reading