|
litefire by Lungcancer Entertainment [web]
[nfo]
|
||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|||||||||||||
|
popularity : 50% |
|||||||||||||
alltime top: #67176 |
|
|||||||||||||
|
||||||||||||||
added on the 2010-09-12 14:45:25 by diver  |
||||||||||||||
popularity helper
comments
slow for me
added on the 2010-09-12 14:53:36 by bfx 
ok
not the first fire intro and there have been better/smaller ones for over 10 years
fire effect
red/black
red/black
fire effect
old/boring
old/boring
fire effect
old/slow
old/slow
real code.
fire!! fiiirrrreeeee!!!!
great fire
way too slow.
I realized it is slow under WinXP, not a problem of the intro because in dosbox and probably real DOS it runs smoothly.
So, I thought to check running 256b intros in WinXP and I didn't know they could run. I thought about trying a 256b remote entry for the incoming Function, show the rules that said they will run from windows. I am wondering if some intros suffered from this, but anyway if I am going to make on and test it, I will know when it's slow and possibly find the bottleneck that happens in XP (because I won't like it running so slowly in the compo)
So, I thought to check running 256b intros in WinXP and I didn't know they could run. I thought about trying a 256b remote entry for the incoming Function, show the rules that said they will run from windows. I am wondering if some intros suffered from this, but anyway if I am going to make on and test it, I will know when it's slow and possibly find the bottleneck that happens in XP (because I won't like it running so slowly in the compo)
It probably read from video ram directly (usual mistake to do with fire effects), same mistake I did right now and wondered if it's because of running dos intro from winxp. Makes sense. Didn't knew though that even in todays computer it's so slow to read from vga even in a dos intro. This needs a buffer :)
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !