Printable View
You could do it that way, but you would still have to loop trough all pixels, which means that if you don't use 8-bit surfaces but just use a 16-bit surface and loop trough every pixel it would be just as fast...
Well, I don't want to loop trough every #*(^$@)( pixel :mad:, my game will run #(*)&@# slow!! :mad::mad::mad:
Sorry, just had to let it out :rolleyes:
I guess I don't have much choice but to learn C a little bit more...
that's probably the only way to handle the problem. Most of the slowness is due to vb array bound checks (which can be removed before compilation), but DMA in vb is still several times slower than in C++Quote:
Originally posted by PsychoMark
Well, I don't want to loop trough every #*(^$@)( pixel :mad:, my game will run #(*)&@# slow!! :mad::mad::mad:
...Or you can try finding someone to make the C++ DLL for you!
If you can't, I don't think you'll notice a big difference if you use 16-bits images ;)
BTW, Kedaman: nice signature, how did you make it? ;)
(We should make a signature contest poll! :p )
thanks jotaf, it was generated
btw, i think array slowness is even worse with the lower bound feature. Even if the lowerbound was 0, the aritmetics for getting the address would be arraypointer+20+lowerbound+index*fixedlength
with pointers in c++ you could do a single aritmetic operation with +=
I should've guessed, it looked like an eye and it would be kinda hard to do it by hand :)
Hey, what happened to it? Why did you remove it?
BTW, I still think the best way is to use 16-bits images ;)
Learning C++ now, so there might be a small chance I'm able to create a DLL for it, but that's not really what I had in mind. So I'm still searching for a fast way to do it in VB preferably with 16-bit images. After all, it's the challenge of making VB perform fast what makes it so interesting ;)
Btw, Jotaf98, you've been talking about 16-bit and your special effects a little, can you tell a bit more, I'm getting interested now! :D
Oh, and to kedaman: thank you for removing the huge signature, you have no idea how much my slow internet connection likes it this way ;)
I knew I had seen your name before (your nickname at least), I already had that submission on my hd ;)
I'm not sure what you're trying to do with the lookup tables, I know the array part and the fact that you can calculate all values before actually running the program so it speeds up, but the rest is just a big mystery to me...
Lookup tables in vb are extreemly slow, especially when they're twodimensional. The amount of aritmetical operations may be more than 8 times than in c++ further array access is slowed down by the lower and upperbound checks (in case you don't switch them off) no good top secret if it's no use.
Remember, you can't do anything fast enough in Vb, if you at least want any speed at all don't use getpixel/setpixel
Kedaman is right, but it's not THAT slow! The demo I made runs at 100 FPS on my PIII 833Mhtz ;)
Still, I had to preload the images to arrays, because using GetPixel all the time was slooooow... and I had to use look-up tables because of the slow Sin/Sqr functions used in some nifty effects... as well as all the calculations for translucency...
Oh, almost forgot: you can check it out here (the new version):
http://forums.vb-world.net/showthrea...threadid=71234
I know! But look at it this way: it was made in pure VB, and it uses slow Get/SetPixel. Also, I saw an alpha blending lib made in C++, with lots of optimizations, and it gave me 150 FPS!