I'm pretty sure that the OP is using Direct3D 9 and the ID3DXSprite and ID3DXFont interfaces for drawing sprites and fonts, respectively. Which would be why these items in particular are not working.
Nope, I'm using Direct3D 11. Sprite and text classes are written by me.
I'll be doing what ya'll said then. Thanks!
Nope, I'm using Direct3D 11. Sprite and text classes are written by me.
Well you've probably got a bug in them then; either the classes themselves or how you're using them. Simple process of elimination: if sprites and text aren't drawing, then somewhere around your sprite and text classes are where you'll most likely find the cause of the problem.
I found a pixel on my screen which is my sprite's. Found that pixel by changing primitive topology to D3D11_primitive_topology_pointlist
My vertexBuffer :
Still don't know why it's only rendering one pixel. I can translate pixel's position with XMMATRIXTRANSLATION, but I can't do anything with XMMATRIXSCALING. Any thoughts?
Still don't know why it's only rendering one pixel. I can translate pixel's position with XMMATRIXTRANSLATION, but I can't do anything with XMMATRIXSCALING. Any thoughts?
A pixel itself will not get scaled, it is just a portion of rasterized object and you seem to only get this one pixel of the object, since translating transformation affects the pixel as you would expect.
I must admit I find it pretty strange combined with fact that it happens on notebook deployment, and not on development deployment. My only suggestion is, that you have not all of the resources and assets deployed on the notebook as well (images etc.)?
If you're doing something undefined, that could also cause differences with different GPUs.
Enable the directx debug layer, and check all return values from your DirectX calls. You said you would do those things... so is everything looking good? All API calls are returning success?
