.spritefont file not loaded

[totallyevil]

ANDROID

ContentManager.Load(@"fonts/" + fontName);

fontName = "Arial"

In Assets/Content/fonts there exists "Arial.spritefont"

MG3D content manager does not load the spritefont.

If I use the XNB file from the WP7 project (Arial.xnb) placed in the exact same location, then MG3D can load the spritefont.

I posted this problem before. The solution then was to use the XNB copy of the asset (happens for some other content types).

The problem is line 290 of ContentManager.cs:

result = ReadRawAsset(assetName, originalAssetName);

This method (ReadRawAsset) throws NotImplementedException for type "SpriteFont". This means you can ONLY use XNB files for your spritefonts.

ContentManager.cs line 359:

        else if ((typeof(T) == typeof(SpriteFont)))
        {
            //result = new SpriteFont(Texture2D.FromFile(graphicsDeviceService.GraphicsDevice,assetName), null, null, null, 0, 0.0f, null, null);
            throw new NotImplementedException();
        }

It is not obvious to me why the XNB path is different than the spritefont path. Why not just use the ContentReader.ReadAsset like the XNB path is using, when processing the ReadRawAsset in ContentManager?

           ContentReader reader = new ContentReader(this, SpriteFontResourceAsAMemoryBuffer, this.graphicsDeviceService.GraphicsDevice,
                                                        mySpriteFontName, 5, null);

Yes, I did try this myself and have had no luck yet.

[dellis1972]

Hi

the loading of "raw" assets is a temporary solution for the content
pipeline not being available for linux and mac. Once the content pipeline
is available the ability to load raw assets will probably be removed.

A runtime .spritefont loader has never been written. the .spritefont format
is an xml format that relys on the true type font being present in the
operating system. The content pipeline would normally load the font and
render a bitmap in memory with the font data and them serialise the
resulting bitmap to the .xnb file.

To implement a runtime raw .spritefont loader it would require the ability
to render true type fonts to memory bitmaps and then generate a Texture2D
from that. I'm not even sure if android (or iOS) supports true type fonts.
Given the current effort to implement the content pipeline I would suggest
it would be better to put our efforts into getting that working on all the
development environments (MonoDevelop / Visual Studio) rather than try to
implement and more raw asset loaders (which will be removed eventually
anyway).

For now I think compiling the font to .xnb via the normal xna development
process is the easiest solution.

Dean

On Aug 24, 2012 6:15 PM, "TotallyEvil Developers" notifications@github.com
wrote:

ANDROID

ContentManager.Load(@"fonts/" + fontName);

fontName = "Arial"

In Assets/Content/fonts there exists "Arial.spritefont"

MG3D content manager does not load the spritefont.

If I use the XNB file from the WP7 project (Arial.xnb) placed in the exact
same location, then MG3D can load the spritefont.

I posted this problem before. The solution then was to use the XNB copy of
the asset (happens for some other content types).

The problem is line 290 of ContentManager.cs:

result = ReadRawAsset(assetName, originalAssetName);

This method (ReadRawAsset) throws NotImplementedException for type
"SpriteFont". This means you can ONLY use XNB files for your spritefonts.

ContentManager.cs line 359:

    else if ((typeof(T) == typeof(SpriteFont)))
    {
        //result = new SpriteFont(Texture2D.FromFile(graphicsDeviceService.GraphicsDevice,assetName), null, null, null, 0, 0.0f, null, null);
        throw new NotImplementedException();
    }

It is not obvious to me why the XNB path is different than the spritefont
path. Why not just use the ContentReader.ReadAsset like the XNB path is
using, when processing the ReadRawAsset in ContentManager?

       ContentReader reader = new ContentReader(this, SpriteFontResourceAsAMemoryBuffer, this.graphicsDeviceService.GraphicsDevice,
                                                    mySpriteFontName, 5, null);

Yes, I did try this myself and have had no luck yet.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/707.

[totallyevil]

And there we are back to where I started - needing the content.pipeline classes for the android build. Having to do the VS build first before I do any other platform build is not cool. That process can't be automated.

Your comment tells me that MG doesn't implement the content pipeline preprocessing for XNA. MG is just the runtime only. Understood.

[dellis1972]

I can suggest this tool

http://xnacontentcompiler.codeplex.com/

You should be able to modify it to run from the command line. if so you can
just put a pre-build script in to the android project.

How you get around adding the output as Assets is a pain, I dont know if
there is any way to automate that bit.

On 24 August 2012 21:03, TotallyEvil Developers notifications@github.comwrote:

And there we are back to where I started - needing the content.pipeline
classes for the android build. Having to do the VS build first before I do
any other platform build is not cool. That process can't be automated.

Your comment tells me that MG doesn't implement the content pipeline
preprocessing for XNA. MG is just the runtime only. Understood.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/707#issuecomment-8013226.