Do you mean like how the Process(input, context) function has parameters?
There is an option in the MGCB console to set parameters, but I’ve no idea what to pass into them. My apologies for all the questions, I just really don’t know the slightest thing about how processors work (I didn’t think I’d need to know for Monogame). Thank you so much for all your help thus far though!
The easiest way to see what a proper MGCB file looks like is to create a small content project in the Pipeline tool. Otherwise, run MGCB.exe /? to see a list of parameters it takes.
As for your specific issue, the ‘processor’ parameter specifies the name of the class to instantiate to process the imported asset. You tell MGCB to load a custom DLL with a separate parameter (‘reference’ I think). Run MGCB.exe /? to be sure.
Assembly is either corrupt or built using a different target platform than this process. Reference another target architecture (x86, x64, AnyCPU, etc.) of this assembly. ‘C:/…/SkinnedModelPipeline.dll’: Could not load file or assembly ‘file:///C:…SkinnedModelPipeline.dll’ or one of its dependencies.
An attempt was made to load a program with an incorrect format. C:/…mod_lizard_skinned.fbx C:/…mod_lizard_skinned.fbx: error: Failed to create processor ‘SkinnedModelPipeline’
Build 0 succeeded, 1 failed.
Time elapsed 00:00:00.27.
Out of curiosity, I edited the SkinnedModelPipeline.cs to see if it’s show me anything by doing this:
I don’t know much (or pretty much anything) about processors, but I thought this would at least show me the string I wrote. I compiled it and copied the .dll to the same folder as MGCB, but it was the same result as above.
You can’t use the console to debug it.
Either you need to get the Monogame’s sources, set the “debug” to true in the pipeline tool and choose an instance of visualstudio to debug (and even like this i haven’t found how to debug the processor’s dll like this, it will only show what MGCB is doing)
or you make your processor write strings into a textfile
The options don’t seem to be there (and I’ve tried clicking <New…>). That, and the MGCB also complains about not finding the default importer I’m really sorry for all these questions, it’s embarrassing.
And it looks like you’re still using the XNA csproj for the pipeline extension (by the presence of the Xbox 360 platform). If the x64 platform is not available to be added, it may be because of that. If so, create a new class library project.
That is because it is a XNA Content Pipeline Extension project, and XNA only supported x86, Xbox 360 and Windows Phone 7. Create a new C# class library project to replace the existing SkinnedModelPipeline project, and add the existing source files to it.
Ok, I’m back. I made a new processor project, and added my files to it like so:
I set the Framework to 4.5, the compile to x64, built the project, got the .dll, ran it through MGCB.exe and…
MGCB /processor:SkinnedModelProcessor /reference:MGSkinnedModelPipeline.dll /build:mod_lizard_skinned.fbx
Build started 4/29/2016 9:30:24 PM
Failed to load assembly 'C:/.../MGSkinnedModelPipeline.dll': Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
C:/.../mod_lizard_skinned.fbx C:/.../mod_lizard_skinned.fbx: error: Failed to create processor 'SkinnedModelProcessor'
Build 0 succeeded, 1 failed.
Visual Studio let me build the project just fine, and I added references as is in the image. I also tried throwing a new TypeLoadException() in the Process function, but that didn’t do anything.
All I knew how to do was copy the XNA example. I tried the whole error catching thing suggested in the link, but nothing seems to output anything to the console whatsoever. I think I may be in over my head. I guess I’ll just hope MonoGame implements skinned meshes as a default thing. As it stands, I just don’t think I’m qualified to be doing this.
Thanks for all your help though, KonajuGames. Sorry about all this.
I mean one you have added, like “skinningdata.dll” referencing the things passed to the mesh.tag field.
If you have a bad understanding of C# coding or visualstudio use at least, it will be difficult to port a code from a “technology” to another one (XNA > MG).