"Are you aware of andreas_blixt's excellent image buffer DLL stuff? Might help speed things up."
It migth speed thngs up in Blitz3D, but it would not speed things up in BlitPlus, and I'm more concerend with BlitzPlus.
Besides, I did a test and I know how much of a speed advantage I'd get by doing that, and it's only in the range of 5-10fps or so. And that's only if you use triple buffering. And that 5-10fps presumes one can find a way to do one poke per pixel rather than 3 when reading/writing 24bit color data... getitng it down to 2 would be easy, but getting it down to 1 would require major effort.
In addition, one would need to support every pixel format.
Given that I have fourteen functions now, if I were to support every pixel format I would need 42 functions. And trying to write each pixel in one poke would double the size of each function because I'd need to write pixels in two seperate loops.
And lastly, as far as I know, that DLL is likely to break in any new update of Blitz... I've been following some imagebank stuff people have been talking about lately, and it relies on the ability to get the data from Blitz' internal structures in an unsupported manner. ONE CHANGE to that structure in Blitz, and the whole thing will blow up.
All in all, it would be a huge headache, and given the lack of interest in these functions so far, completely not worth the headaches. Besides, it would make making changes to it down the road a nightmare.
It migth speed thngs up in Blitz3D, but it would not speed things up in BlitPlus, and I'm more concerend with BlitzPlus.
Besides, I did a test and I know how much of a speed advantage I'd get by doing that, and it's only in the range of 5-10fps or so. And that's only if you use triple buffering. And that 5-10fps presumes one can find a way to do one poke per pixel rather than 3 when reading/writing 24bit color data... getitng it down to 2 would be easy, but getting it down to 1 would require major effort.
In addition, one would need to support every pixel format.
Given that I have fourteen functions now, if I were to support every pixel format I would need 42 functions. And trying to write each pixel in one poke would double the size of each function because I'd need to write pixels in two seperate loops.
And lastly, as far as I know, that DLL is likely to break in any new update of Blitz... I've been following some imagebank stuff people have been talking about lately, and it relies on the ability to get the data from Blitz' internal structures in an unsupported manner. ONE CHANGE to that structure in Blitz, and the whole thing will blow up.
All in all, it would be a huge headache, and given the lack of interest in these functions so far, completely not worth the headaches. Besides, it would make making changes to it down the road a nightmare.