I'm trying to load skinned animations into my game.  I've been able to successfully load them in on the windows/x86 version but the momment I try to create a copy for the xbox I get the errors listed here:

  http://forums.xna.com/forums/p/17118/92767.aspx#92767

 So, I started a new xbox 360 project with the intent of copying what the working xbox verion of skinned model has accomplished:

With the new xbox project with the default game1.cs: everything compiles

I then add the SkinnedModelXbox project to my solution: everything compiles

I then add the SkinnedModelWindows project to my solution: everything compiles

I then add the SkinnedModelPipeline project to my solution (by default, it has SkinnedModelWindows as a reference): errors

First error:The type 'Microsoft.Xna.Framework.Matrix' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Xna.Framework, Version=2.0.0.0, Culture=neutral, PublicKeyToken=51c3bfb2db46012c'. C:\~\SkinnedModelPipeline\TypeWriters.cs 27 13 SkinnedModelPipeline

It's then followed by a bunch of matrix function errors.

I haven't even included a reference to it in my game project and yet I'm getting errors in the pipeline project. I was wondering if this is happening to anyone else who is trying to get animations to work on the xbox and if there's any advice on how to handle these errors.

Dan

Good news is that importing fbx animations on your skinned models is doable and so far I haven't had too many problems...

What exactly did you do?

I have the same problem and cannot fix it.

I have tried making a new solution and copying my classes across by hand, but all of a sudden it just goes bang, completly randomly, what the hell is going on.

Had a brainwave and it worked.

Load up the sample and change the assembly name of the xbox version of SkinnedModelXbox to SkinnedModelXbox but leave the default namespace alone.

Build this to create SkinnedModelXbox.dll

Reference this in your xbox version and all is well.

Spoke too soon, doing the above compiles, but does not run.

You need to leave the name alone, but use that version of the dll.

This dll seems to create a hell of a lot of problems.

I wrote a whole game for the PC, got it signed off and ready for release, then tried to create the XBOX version.

Having SkinnedModel in the project seems to create massive problems for the conversion wizard. The symptoms I had are...

1) Content handling system bust.

      All the assets had an importer and handler as blank fields. If you attempt to manually change them, visual studio crashes.

2) Project type incorrect

     The created project was set as a windows application instead of a console application

3) Files copied

    All the source files were copied, so in the solution directory I had Game1.cs and Game1(2).cs, and the same for all files (including content assets)

In the end I created a new solution with the same name as my original but in a new directory, saved it and closed visual studio. 

Then I copied all the files over by hand, including the content.contentproj and game1.cs but not program.cs, replaced the dangerous dll with the xbox version, then reopened the solution in visual studio.

I used "Add existing resource" to add all the source code files.

This worked perfectly.

  I'd have to agree with the dll's giving me problems.  I recently added more files and folders to my windows version and erased my xbox version and created another copy since I was too lazy to create the same folders on the xbox version.  And what happened?  More of these damn reference errors.  I went back and did the following:

 -created a copy of my project for the xbox.

-added "SkinnedModelXbox" in my Xbox Copy reference folder.

-"SkinnedModelPipleline" should already be inside the Xbox Copy Content/reference folder.

 Before, this was all I needed to do.  But then I started getting the same errors again.  I even did everything from scratch and I kept on getting errors.  However, make sure to also do a "rebuild solution" to rebuild the .dll's and everything else.

I also didn't mess with any of the assembly namespaces.  I just tried to match the dependencies and clean everything.  Anywho, thanks for the advice and I'm glad I'm not the only one running into this problem.  Cool name btw ;P

Wipeless:

 Just remember to delete previous copies of your project (to prevent the duplicate existing files). 

There shouldn't be any, it SHOULD use the same source code files as the PC version.

Cool name btw ;P

It's been my handle for a lot of years, given to me by some old school hackers in the late 80's.