Jump to content
Visual Boy Advance-M
spacy51

Removing pixel filters

Recommended Posts

Doing my anti-bloat campaign, I am considering removing some rarely used pixel filters (CPU only).

 

Here's what I would remove:

  • Pixelate
  • TV mode OR Scanlines
  • Bilinear
  • Bilinear Plus
  • LQ2x (not sure, comment!)
  • 2x SaI (not sure, comment!)

 

Here's what should stay:

  • Simple 2x/3x/4x (nearest neighbor) [useful for debugging pruposes]
  • Super 2xSaI
  • Super Eagle
  • AdvanceMAME Scale2x
  • HQ 2x/3x/4x

Share this post


Link to post
Share on other sites

I personally appreciate the TV-like filtering. Is removal indispensable? Feature loss would encourage forks of vba-m (the official version turning into a 'lite' one with smaller featureset might not be the best course of action)

 

2xsai and tv-like filters are appreciated by many, and available by default for many 2d emus.

 

Such a question would benefit from feedback from a wider audience. Posted here: http://forums.ngemu.com/vba-m-discussion/113301-removing-pixel-filters.html

Share this post


Link to post
Share on other sites

I'm interested what Linux users think.....

 

For Windows, we already have filter plugins so......

Share this post


Link to post
Share on other sites

NOOOOOOO not Bilenear/Bilenear Plus !!!!!!

 

Ehm.. you know that OpenGL/Direct3D can do this in hardware? SDL does it as well if I'm not mistaken.

And Bilinear plus looks like it has a bug.

Share this post


Link to post
Share on other sites

Agreed, there are too much similar filters. I don't care which filters are removed.

Share this post


Link to post
Share on other sites

I use Super Eagle mostly, and occasionally Super 2xSAI. As long as those stay, I'm good. But I wonder why it would be necessary to remove any as an anti-bloat step? To me, bloat is code that weighs down performance. These are mutually exclusive options, and the only encumbrance on performance should come from the one the user selects. No?

Share this post


Link to post
Share on other sites

Doing my anti-bloat campaign, I am considering removing some rarely used pixel filters (CPU only).

 

Here's what I would remove:

  • Pixelate
  • TV mode OR Scanlines
  • Bilinear
  • Bilinear Plus
  • LQ2x (not sure, comment!)
  • 2x SaI (not sure, comment!)

 

Here's what should stay:

  • Simple 2x/3x/4x (nearest neighbor) [useful for debugging pruposes]
  • Super 2xSaI
  • Super Eagle
  • AdvanceMAME Scale2x
  • HQ 2x/3x/4x

 

I use both LQ2X and 2xSaI, 2xSaI looks better on 4:3 resolutions, while LQ2X is better on 16:9 and 16:10 resolutions.

 

LQ2X is 3/4 the qualty of HQ2X, while only requiring half the cpu processing.

 

on an AthlonXP 3000, i can use LQ2x on firered, during the opening with the fire, while HQ2x requires frameskipping to run at 100%

Share this post


Link to post
Share on other sites

Well, as long as you leave Scanlines (2x...) and Super 2xSaI the rest can go, and maybe keep Pixelate to still keep a GBA style lcd look. That's three useful and common pixel filters. I've explained my interest and reasons for keeping them and have given examples as to why they should be left:

 

Scanlines - - - Simulates playing VBA on a TV using the GC Gameboy player

Super 2xSaI - Looks quite nice and smooth for cartoon style gba games (Pitfall...)

Pixelate - - - Appears to give nearly the same result as a regular GBA screen

 

There are quite a few plugin renderers for use with Kega Fusion, and all in all most of them are the same. BUT, anyway, I'd like to have VBA-M keep these three. Scanlines would be my personal favorite to keep however if any others were to go.

 

PS: This is my first post, and just glad to join now since i just recently found out about a version of VBA finally seeing another new version after a long while. :-)

Share this post


Link to post
Share on other sites

I mostly prefer 2xSai or HQ2X and hate scanlines but, given the very different preferences shown by everyone here I would not support this. Encouraging forks of a comprehensive emulator and for such a small feature is not ok in my book. Considering this will probably turn into the ultimate emulator for GBA, I'd prefer everything to stay. Especially since, as Cobra951 put it, these are mutually exclusive options and I would have a hard time considering them as encumbering bloat.

Share this post


Link to post
Share on other sites

Hmmm, a interesting thought.

 

Though, bloat is one thing I do heavily despise in any app, though, what does bloat mean really?

 

Like for me, I rather have the whole GUI redone in the Win32 API instead of MFC to remove the dependancy on MFC DLLs. Plus loads other things rewritten and reworked for size and speed, even accuracy even.

 

So for "bloat" I do honestly think this emulator is bloated. The file size doesn't feel right, the code is definately a eyesore and in need of a pure deep clean & potential rewrite all together, but I suppose then that doesnt make it VBA based then at all.....

 

And plus, VBA itself has its own quirky charm.

Share this post


Link to post
Share on other sites

I think bloat would simply be inefficient code as I personally like my apps bursting with features even if I may end up never using them all and some being entirely useless to me.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×