May 25th update: turns out that not only were comments disabled while MSDN blogs were being upgraded, but the three posts I made during the upgrade got deleted, too! So I shall repost them now. Looks like I have some CSS work to make things look right...

May 25th update: turns out that not only were comments disabled while MSDN blogs were being upgraded, but the three posts I made during the upgrade got deleted, too! So I shall repost them now. Looks like I have some CSS work to make things look right...

May 25th update: turns out that not only were comments disabled while MSDN blogs were being upgraded, but the three posts I made during the upgrade got deleted, too! So I shall repost them now. Looks like I have some CSS work to make things look right...

Quick history lesson: Once upon a time, we were designing XNA 1.0, and decided that instead of just exposing managed wrappers around the old D3DX functions for loading textures and models, it would be better to create a new thing called the Content Pipeline...

Previous XNA versions included an Effect.CompileEffectFromSource method. We do not support runtime shader compilation on Xbox, so this was only available in the Windows framework, which could compile shaders targeting either Windows or Xbox. This factoring...

This article is prerecorded. Shawn is away (on honeymoon). Replies to comments will be delayed. Typical XNA model drawing code goes something like: Matrix[] transforms = new Matrix[model.Bones.Count]; model.CopyAbsoluteBoneTransformsTo(transforms...

This article is prerecorded. Shawn is away (on honeymoon). Replies to comments will be delayed. In previous XNA versions, the Content Pipeline imported materials like so: If an FBX or X model directly references a .fx effect, the importer creates an EffectMaterialContent...