I want to remove "interframe.cpp".
Any objections?

Quote:I want to remove "interframe.cpp"

???
Is there something wrong with it?

Sorry for my strange mood today, here are the reasons:

Motion blur:

• needs CPU processing
• is already implemented for D3D
• issues with 3x/4x filter
  

Smart interframe blending:

• needs CPU processing
• I don't like the algorithm
• issues with 3x/4x filter
  

No clue. I like my applications just about bursting cuz they are packed so full of features, even some I may never use so I have no problem with it staying whereas I might in a few years time have problem with it being removed.

I think interframe blending was the one feature of VBA that I never understood. It just seems unnecessary. I have no objections to removing it.

Actually, it is to kind of reproduce the GBA LCD screen's slow response time. While everyone knows about motion blurring (blend last and current frame together). Some games (like Hardvest Moon or F-Zero) make use of that to save processing time for real transparency and instead just display graphics every second frame (and hide it the other frame). I think the smart interframe blending tries to intelligently only detect those virtually transparent areas and not touch the normal areas, providing a generally less motion-blurred image while still showing virtually transparent areas as transparent. When none of these is activated the virtually transparent image is flickering when the screens response time is too fast. The more I think about it, the less should it be removed, but rather optimized.

Then its decided, make a note of it on the source forge page that we have to optimise it.

VBA-M | NGOHQ | Post Impact Productions | TNHW | XBCD 0.2.7