OK, largish program, probably uses too much vidmem (but I have 128MB and I definately havn't used that much yet;) - three very large (3000x800+) pictures being blitted to the screen, amongst other smaller, much more normal images.
Runs fine in B2D, crawls to a halt in B+. Two of those pictures are loaded from a png - one created using CreateImage(). If either of the two pngs are blitted anywhere on the visible screen area, massive slowdown. If pngs are blitted offscreen everything runs smoothly.
This is not true for the CreateImage()'d pic - it doesn't slow anything down whether it's in view or not.
---
Forgetting the defualt response of 'don't blit images larger than the screen', can we discuss reasons why this behaviour exists and perhaps also why it doesn't exist in B2D/B3D at all?
I should probably mention that the behaviour doesn't exist in a small testbed comprising the offending images only (B+ is faster then)... but it's 2.30am here and instead of creating a bigger, more elaborate, comprehensive testbed, I'm gunna go sleep ;] I don't drink coffee. =]
Runs fine in B2D, crawls to a halt in B+. Two of those pictures are loaded from a png - one created using CreateImage(). If either of the two pngs are blitted anywhere on the visible screen area, massive slowdown. If pngs are blitted offscreen everything runs smoothly.
This is not true for the CreateImage()'d pic - it doesn't slow anything down whether it's in view or not.
---
Forgetting the defualt response of 'don't blit images larger than the screen', can we discuss reasons why this behaviour exists and perhaps also why it doesn't exist in B2D/B3D at all?
I should probably mention that the behaviour doesn't exist in a small testbed comprising the offending images only (B+ is faster then)... but it's 2.30am here and instead of creating a bigger, more elaborate, comprehensive testbed, I'm gunna go sleep ;] I don't drink coffee. =]