[Question] D3DXSprite quality?

[Kosaki]

Hello,

I have stumbled upon another problem when writing my gfx toolkit.
It seems like the quality D3DXSprite renders with is too bad.

My fonts are basically 256x256 textures containing all the ASCII characters.
As you can see in the picture below it is not precise enough.



As you can see the quality is not usable for drawing text at this time.
Does anyone have any ideas on how to improve the quality?

The original texture:


If you guys want my rather simple drawing function for the text:

HRESULT TextRenderer::DrawStrokedText( char *text, int x, int y, DWORD color )
{
	FVEC2 currentPos = {(float)x, (float)y};
	for(int i = 0; text[i]; i++)
	{
		RECT bounds;
		bounds.left = (text[i] % 16)*16; // 16 characters per row
		bounds.top = text[i] & 0xF0; // 16 rows
		bounds.right = bounds.left + 16;
		bounds.bottom = bounds.top + 16;
		m_pGFXToolkit->DrawSprite(IDB_CONSALAS_STROKED, &currentPos, &bounds, color);
		currentPos.x += m_fontWidths[text[i]]+3;
	}
	return S_OK;
}

It is only a prototype of the TextRenderer class I am making so some stuff is hardcoded. (Like resolution of texture, and character spacing)

Would using primitves and textures directly have any effect on the quality?

I dont know of your rendering class, but using direct3d's I get



@ 512 x 512 image size

[Kosaki]

Here is a small dump of whats relevant.

HRESULT GFXToolkit9::LoadTexture(WORD textureID, HMODULE hSrcModule, LPCTSTR pSrcResource)
{
	if(m_textures[textureID])
	{
		m_textures[textureID]->Release();
	}
	LPDIRECT3DTEXTURE9 pTexture = NULL;
	HRESULT hRes = D3DXCreateTextureFromResource(m_pDevice, hSrcModule, pSrcResource, &pTexture);
	if(SUCCEEDED(hRes))
	{
		m_textures[textureID] = pTexture;
	}
	return hRes;
}

HRESULT GFXToolkit9::DrawSprite( WORD textureID, FVEC2 *pos, RECT *imageBounds, DWORD colorMask)
{	
	LPDIRECT3DTEXTURE9 pTexture = m_textures[textureID];
	if(!pTexture)
	{
		return E_FAIL;
	}
	D3DXVECTOR3 vec;
	vec.x = pos->x;
	vec.y = pos->y;
	vec.z = 0;
	return m_pSprite->Draw(pTexture, imageBounds, NULL, &vec, colorMask);
}

The D3DXSprite is started like this:
m_pSprite->Begin(D3DXSPRITE_ALPHABLEND);

I just can't find any reason for why it is acting like that.

o: you could try my QTS texture from resource function and see if that fixes the difference.
Also resizing to the 8x8 based 512 x 512 size.

[Kosaki]

Alright, I will be trying that out tomorrow.

Hopefully it will be something that simple

Thanks

[kolbybrooks]

Originally Posted by segnosis

o: You could try my qts texture from resource function and see if that fixes the difference.
Also resizing to the 8x8 based 512 x 512 size.

8
16
32
64
128
256
512


Think you meant the Higher quality 512x512 (?)

Ofc, im not basic math impaired >: o

[silverfish]

Sorry for the off topic but QTS of how to draw text using textures would be a nice addition, no?

Originally Posted by silverfish

Sorry for the off topic but QTS of how to draw text using textures would be a nice addition, no?

Added, didn't go to much into it since toymaker explains it better

[Kosaki]

Changing the method how I load the textures did not affect anything. =(

However I decided to go with the work around. Using a 512x512 texture now which contains 20p characters stroked 1 pixel.

The text drawing is now done with some scaling. It causes a bit blurred character at small fonts but I believe it should be good enough.



Pros:
It works

Cons:
Uses more memory 512x512 with 4 channels uses quite a bit more memory than 256x256.

Thanks for the help

np, glad to help :]