@sleve_mcdichael said in Does Each Core Handle Scanline Filters Different?:

Right, it is only "integer scaling" at those exact scale factors which may not work well if your overlays aren't similarly-sized.

Makes sense, thanks for confirming. I thought it might be an extra thing I can do to improve things overall, but the overlays are a must for my setup. But I'm very satisfied with the results already, so no harm no foul!

@dankcushions said in Does Each Core Handle Scanline Filters Different?:

@AlphaBetaPie your psx logo example is interesting and shows what i was saying nicely. the psx boot sequence goes through some interesting resolutions - that psx logo is actually 480i interlaced output. since it is an (i)nterlaced output, it would not generate scanlines on a real CRT, but the shader doesn't know this and applies anyway. by applying to a high(er) vertical resolution the scanlines appear all blurred and weird.

once you get in game, most psx games are more standard progressive resolutions (320p, etc), but not always. some games switched temporarily to interlaced higher resolution modes in menus, etc. so shaders aren't always going to be appropriate, but there's nothing you can do, other than remove them completely (or turn the boot logo off in core options)

integer scaling is not the issue here. and yeah it can change the aspect ratio from 4:3 (massively in some cases) and will not fit into your overlays (without additional borders). if it was good it would be the default :)

Again, thanks for confirming. I suspected as much, but it's also nice to see that it's just the nature of the emulator beast and not necessarily my setup. And as you mentioned, if it's giving me fairly accurate (and overall good) results, I can overlook little inconsistency here and there, like the bootup screens. I think the overall benefit (for my setup anyway) is worth the few little hiccups. Maybe they'll figure out things a bit better as the cores advance. Thanks!

@TimZett said in General questions on applying shaders (video filters):

The vertical shader I just took for testing purpose, because it shows something significant ;-)
Currently I'm using the bilinear (blur) shader since I find the Atari games in all emulators way too blocky.

I use CRT + smoother for everything. Then again, the only stuff I really play on RetroPie is SNES and PS1.

@TimZett I think @dankcushions posted a link (maybe in another topic) to the Shader docs in Retropie's documentation - https://retropie.org.uk/docs/Shaders-and-Smoothing/.

Thanks for the reply that makes sense. :)

Dwarfboysim

Bumping this, might help clarify matters for several other GPGX users!

ekeeke replied to me about this, explaining the following regarding the new MAME sound engines:

*ASIC version corresponds to the chip model used in later Model 1 consoles and most Model 2 consoles. It features the better (not distorded and less noisy) DAC output and full address decoding of status register (which causes slower music in Hellfire since it was developed for the discrete chip version) compared to discrete chip version.

Enhanced version has same "enhanced" features as ASIC version + full resolution DAC (14-bit instead of 9-bit in real hardware versions) + zero busy flag time (busy flag in FM status is only emulated for real hardware chip versions). It corresponds to an "idealized" version of the chip, like it is emulated in other Genesis emulators.

The low pass filter is unrelated to the chip DAC and exists in all console models (it is implemented by analog circuitry outside of the chip). It should be enabled for accurate emulation of analog sound output (and disabled if you prefer the clear sound of pure digital emulation). Filtering ratio is configurable because it varies for each console models (also between model 1 consoles or between model 2 ones) so it's up to you to find a value that matches your own memory of accurate sound. Default value should correspond to Model 1 VA4 console.*

@battlecat One way to do this would be to do the following:

Scrape all of your roms to make sure all are listed in the gamelist.xml file. Manually edit the gamelist.xml file (usually located in ~/.emulationstation/gamelists/<system>) to remove the unwanted roms. From the main emulationstation screen, push start, then find the option in the menu that says "Parse gamelist.xml file only" or something like that. Reboot your system, then enjoy!

This is how I hide the various bios files as well. Of note, if you add a new system or rom, you'll have to disable the "Parse gamelist.xml" option to see the new roms, unless you've scraped them already.

Good luck!

Followed steps as described (running on Windows on VirtualBox on an MacOS system). Worked brilliantly.

@jdrassa The way I see it, from my limited knowledge point of view, is that it should be easier to align the icon with the corresponding text entry in the gamelist if it's a font (you can just render it inline) rather than a separate icon element that you need to explicitly render at a different location trying to guess which gamelist entry is selected at a time.

Then again, I don't know enough of the components in question to confirm that'd be the case. And, certainly, it's not that it can't be done, but just something to bear in mind.

@mattrixk fantastic post. Thank you for taking the time! I'll comment further if I have anything to add when I'm on my laptop later today.

Re. speed gains :
What about running games at low resolutions, but then using shaders to make it look acceptable? Or do the shaders always run at the emulated resolution?

@publicENEMY There was a test build that let you select multiple entries with Ctrl-A, Ctrl-Click, and Shift-Click, but alas, the download link doesn't work anymore.

@markwkidd Maybe you could put it up again somewhere? I'm still using it and I find its selection controls very convenient. Alternatively, I could host it in my own Github repo with your permission. At the moment, only my local storage and its backups prevent this version from vanishing into oblivion …

(Oh, I just noticed that I already asked you this nine months ago. I don't want to bug you, just tell me to shut up about it and I will. 🤐 )

edit: According to his profile, markwkidds last login happened in May, 2019. So maybe we lost him entirely. 😟