16 hours ago, Oberon_Command said:

Attach the debugger and put a breakpoint at the line with the memset. What are the contents of sRect?

The debugger says: (Directly Quoted)

sRect = {Pitch=128 pBits=0x05bc7000 }

The Pitch is equal to 128, and the value pBits is located at 0x05bc7000

What is the actual size of the texture? How many bits per pixel? And how do you know?

44 minutes ago, L. Spiro said:

Why is everyone guessing whether you still have pitch*pitch?  Did you lock the texture yet (this is not optional)

...

 Why aren't you helping us help you?
 

Ok... I will divide this answer into 3 answers.

(1) I am still using pitch * pitch in the code because it is essential in the usage of memset for the drawing of the texture which is saved in memory (the minimap texture). This texture is checked every frame to make sure that the player's troops and their view radii are visible on the minimap, allowing for easy viewing, such as games like Age of Empires, Civilization, and Total War do.

(2) I am sorry that I have provided too little information for your, and some other peoples' liking... Just tell me what other information you would need, and I will provide it... After all, this whole project was just based on random techniques (mostly old ones from the late '90s) that seemed to do exactly what I wanted them to.

(3)I do know, actually, that the texture HAS to be locked in order for everything to work correctly, and I just forgot to uncomment it in the main question.  

Here is a few more lines of code: (I am extremely sorry that I forgot to post them in the starting code!)

//Sight texture
	m_pDevice->CreateTexture(64, 64, 1, D3DUSAGE_DYNAMIC, D3DFMT_L8, D3DPOOL_DEFAULT, &sightTexture, NULL);

I did uncomment the locking texture code... I changed that in the first question...

1 hour ago, L. Spiro said:

Essential not to do, you mean?  It's pitch * height, not pitch * pitch.

No, I mean essential... the image height is 64, and the pitch is 128... 

It may be essential not to do, but that is how it supposed to work. Anyway, it worked in older Windows Versions that could run DX 9.0c.

10 minutes ago, L. Spiro said:

What are you misunderstanding about this math?

Why are you looking at your error repeatedly and calling it good?
 

(1) The pitch multiplied by the height give a lesser value than the pitch squared... thus giving an image that is not complete.

For some reason, as I have seen, the member values for the 3rd variable in the function are not supposed to be greater than the width or height...

Why would I settle for half an image?

-rjhwinner03

12 minutes ago, rjhwinner03 said:

 

Why would I settle for half an image?

Because it probably isn't. The pitch is not the width in pixels! It might be, if the hardware surface is one byte per pixel and there's no extra padding added to the end of each row of pixels. But that seems unlikely to me, given that you're getting this crash.

What is the width of the texture, in pixels? Is it 64, or 128?