Printable View
This program is the most useless program ever, but I watched it for 5 minutes straight because it was so mesmerizing.
Code:#include <iostream.h>
#include <conio.h>
#include <stdlib.h>
int main()
{
int random;
int x;
do
{
random = rand();
cout<<random;
for(x=0; x!=50000; x++)
{
}
}while(!kbhit());
return 0;
}
wow... its almost like watching a fire burn...
Easily entertained ? :rolleyes:
I wish i could run it but its not portable enough :)
No this is like watching a fire burn.
Code:#define RGBTODWORD (r,g,b) ((r<<16)+(g<<8)+(b))
RGB fire[30][100];
void AddHeat(int heatvalue)
{
int x=rand() % 30;
int y=rand()%100;
fire[x][y]+=heatvalue;
fire[x][y]&=0xFF;
}
void DrawFire(int x,int y)
{
int row=0,col=0;
for (int i=x;i<x+30,i++)
{
for (int j=y;j<y+100;j++)
{
int heat=fire[col][row];
if (heat>30)
{
float coef=heat/255.0;
DWORD firecolor=RGBTODWORD(coef*255,0,0);
PlotPixel32(i,j,firecolor);
}
row++
}
col++;
row=0;
}
}
void UpdateFire(int cooldownfactor)
{
for (int i=0;i<30;i++)
{
for (int j=98;j>0;j--)
{
int heat=fire[i][j+1];
heat-=cooldownfactor;
if (heat<0) heat=0;
fire[i][j]=heat;
}
}
}
Just add main and a loop for your fire and watch to see what happens....that is, if I didn't make any mistakes.
I almost fell asleep :o
After i read that post I went back and watched it, and it really does look like a fire burning if you just unfocus your eyes! (Like with those 3-D picture books...) :eek:Quote:
Originally Posted by Vicious
I don't know what <.h> files to include. Which ones!
do you need to include any headers beside cstdlib? what do you need for type RBG?Quote:
Originally Posted by Bubba
edit: sorry for repeating child, started this yesterday and finished it today
We're wondering what headers to include. ({(<Waiting.>)})
C++child no need to be rude. By the looks of it probably windows.h or knowing bubba some direct x header(i have no clue cause i never even touched direct x) or it could even be openGL?
I believe that would be Windows API graphics calls actually
So include <windows.h>
create a window.. and call these functions in your loop.
Judging by the call to PlotPixel32, it came from a DirectX program (Andre LaMothe?)
It is not necessarily DirectX or windows, though...
That code can be DOS, DirectX, OpenGL, or Windows.
Your choice. Sorry I forgot all about this thread and so I didn't know all of you were wondering about the headers.
All you need to do to port it is to write your PlotPixel32 function. Since the algo is not API specific you can use it any way you want.
If you want to know which is faster profile it because I cannot make any guarantees that the assembly version is faster.Code:void PlotPixel32(DWORD *Buffer,int x,int y,DWORD color,int bufwidth)
{
Buffer[(y*bufwidth+x)<<2]=color;
}
void PlotPixel32Ex(DWORD *Buffer,int x,int y,DWORD color,int bufwidth)
{
asm {
push edi
les edi,[Buffer]
mov eax,[y]
mov ebx,[bufwidth]
mul eax,ebx
add eax,[x]
shl eax,2
add edi,eax
mov eax,[color]
stosd
pop edi
}
}
This only works if the color is defined as ARGB or XRGB.
Since y*bufwidth+x will never exceed 32-bits then you don't need to worry about what is in EDX because it will be all zeros. Mul will multiply EAX by r/m 32 and leave the result in EDX:EAX where EDX is the high order 32-bits and EAX is the low-order 32-bits. The CF and OF flags are cleared if EDX is zero (which in this case it will be so no need to check).Code:#define RGBTODWORD(a,r,g,b) (DWORD)((a<<24)+(r<<16)+(g<<8)+(b))
Since most cards support ARGB and XRGB natively you are fairly safe in assuming this snippet will work on all current video hardware.
For DirectX you simply would use SURFACEDESC.MemPitch for the width value instead of the actual width of the screen. This in turn would not need to be shifted left by 2 since the MemPitch takes care of that.
In Windows you simply need to get a pointer to the HDC, then to the client area of the HDC and write a 32-bit value to the client area using the API or by getting a pointer directly to the buffer.