crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come)

[GreenHawk84]

I tested out a couple games with the newer shader, both a vertical and horizontal game, and the games were "fatter" than the regular shader I used before (with the vertical fix for banding). I don't like how that looks, was that a part of the fix to make the shader fit right?

[dankcushions]

@Nataq said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@dankcushions

In some games the fatter version is OK and i some other it bugs me more. Both options are viable I guess. I don't want to take more of your time but would it be feasible to genarate configs with my shader path ? What works for me is this :

video_shader = "~/.config/retroarch/shaders/crt-pi-vertical.glslp"

i'm not generating configs for your busted install :P the scripts are all public if you want to edit them.

And like if its not enough, how about a little windows GUI instead of a python script where you could input your shaders path, screen resolution and hit "Generate" to start the magic ? ;) You could always chose to include the scaling parameter or not or just generate cfgs for vertical games only. Why not add a blank space too so to add any other custom command lines... That would be fantastic ! And probably not so hard to code. You may already have the code for that actually.

"not so hard" :) someone else can code that haha.

[dankcushions]

@GreenHawk84 said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

I tested out a couple games with the newer shader, both a vertical and horizontal game, and the games were "fatter" than the regular shader I used before (with the vertical fix for banding). I don't like how that looks, was that a part of the fix to make the shader fit right?

i haven't created a new shader. these are just configs. and yeah, the aspect ratio change is intentional. you can't remove the scaling artifacts AND not have top/bottom borders without changing the aspect ratio. on a 1080p setup it should be hardly noticeable though.

[GreenHawk84]

@dankcushions, I understand now. Well yes I noticed it right away. But if it must be this way then I'll have to get use to it. I prefer as much screen fill as possible while maintaining as much of the proper X and Y as possible, which I think you've done here.

[KillerContusion]

Can these config files be used for the Arcade folder using a rom set that is a mix of Mame2003, FBA, and Mame2010? Or, would it be possible to build a config for the Arcade folder? I currently have the config file working great using Mame2003 outside of the Arcade folder and would love to get this working for the new rom set I will be using out of the Arcade folder. Any help would be much appreciated.

Also, thank you for the hard work on the shaders and config files.

[dankcushions]

@KillerContusion said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

Can these config files be used for the Arcade folder using a rom set that is a mix of Mame2003, FBA, and Mame2010? Or, would it be possible to build a config for the Arcade folder? I currently have the config file working great using Mame2003 outside of the Arcade folder and would love to get this working for the new rom set I will be using out of the Arcade folder. Any help would be much appreciated.

they only work for the lr-fbalpha, lr-mame2003 and lr-nestopia emulators, but it doesn't matter where you launch games from (arcade, mame-libretro, etc). these configs will apply to the emulators regardless.

no plans to make a mame2010 set as yet.

[KillerContusion]

@dankcushions great thanks for the info! Just so I am clear I should just be able to create a folder for FBA the same as I did for Mame2003, as you instructed?
/opt/retropie/configs/all/retroarch/config/MAME 2003/
/opt/retropie/configs/all/retroarch/config/FB Alpha/
Load your config files in there, then put my rom set into the Arcade folder, and when they launch using those emulators should look to your config files in the above directories?

I am not too much worried about Mame2010. If needed I can create rom specific config files for anything out of there that might be needed.
Thanks!

[dankcushions]

@KillerContusion said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@dankcushions great thanks for the info! Just so I am clear I should just be able to create a folder for FBA the same as I did for Mame2003, as you instructed?
/opt/retropie/configs/all/retroarch/config/MAME 2003/
/opt/retropie/configs/all/retroarch/config/FB Alpha/
Load your config files in there, then put my rom set into the Arcade folder, and when they launch using those emulators should look to your config files in the above directories?

yes :)

[Nataq]

@dankcushions said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@Nataq said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@dankcushions

In some games the fatter version is OK and i some other it bugs me more. Both options are viable I guess. I don't want to take more of your time but would it be feasible to genarate configs with my shader path ? What works for me is this :

video_shader = "~/.config/retroarch/shaders/crt-pi-vertical.glslp"

i'm not generating configs for your busted install :P the scripts are all public if you want to edit them.

And like if its not enough, how about a little windows GUI instead of a python script where you could input your shaders path, screen resolution and hit "Generate" to start the magic ? ;) You could always chose to include the scaling parameter or not or just generate cfgs for vertical games only. Why not add a blank space too so to add any other custom command lines... That would be fantastic ! And probably not so hard to code. You may already have the code for that actually.

"not so hard" :) someone else can code that haha.

Well, I totally understand. Turns out, I was wrong and even the alternate path isn't working. Enough of that problem here though. Thank you for trying to help anyway.

[pirossi]

i thank you for your work
have: 1920x1200 16:10
i use the script but It leaves the screen off-center

# Place in /opt/retropie/configs/all/retroarch/config/FB Alpha/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the height
aspect_ratio_index = "22"
custom_viewport_width = "1920"
custom_viewport_height = "1792"
custom_viewport_x = "0"
custom_viewport_y = "-296"

Manually changing this by this looks good, but would have to change it in thousands of cfg's ..

# Place in /opt/retropie/configs/all/retroarch/config/FB Alpha/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the height
aspect_ratio_index = "22"
custom_viewport_width = "1920"
custom_viewport_height = "1200"
custom_viewport_x = "0"
custom_viewport_y = "0"

Other friends have happened the same with the script and other resolutions.

If you have any solutions, thank you, your work is good

[garion]

@pirossi you beat me for it :-)

I'm sure @dankcushions can help us.
It's strange because DB should be ok because 1920x1080 works so it should be the script.

[dankcushions]

@pirossi what game is this cfg for? i just rang the script locally:

crt-pi-configs>python crt_pi_configs.py fbalpha 1920 1200

and it seemed to generate file with the custom_viewport_height as 1200. eg, sf2.cfg:

# Auto-generated crt-pi.glslp .cfg
# Place in /opt/retropie/configs/all/retroarch/config/FB Alpha/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1920"
custom_viewport_height = "1200"
custom_viewport_x = "0"
custom_viewport_y = "0"

if you're running the script please give full details of your os, the command you ran, and the game your .cfg is for.

[pirossi]

@dankcushions said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@pirossi what game is this cfg for? i just rang the script locally:

crt-pi-configs>python crt_pi_configs.py fbalpha 1920 1200

and it seemed to generate file with the custom_viewport_height as 1200. eg, sf2.cfg:

# Auto-generated crt-pi.glslp .cfg
# Place in /opt/retropie/configs/all/retroarch/config/FB Alpha/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1920"
custom_viewport_height = "1200"
custom_viewport_x = "0"
custom_viewport_y = "0"

if you're running the script please give full details of your os, the command you ran, and the game your .cfg is for.
i am using windos7pro
Button windows start -> I type cmd and the ms-dos window opens
You go to the directory I created

thanks for your reply!
I'm using windows 7pro

Button windows start -> I type cmd and the ms-dos window opens
You go to the directory I created

Cd \ retropie

And then I run the script for mame and then for fba:

Python crt_pi_configs.py mame2003 1920 1200
Python crt_pi_configs.py fbalpha 1920 1200

Will create two files each with 4000.. cfg files
I put the .cfg files in: / opt / retropie / configs / all / retroarch / config / FB Alpha
and in:
/opt/retropie/configs/all/retroarch/config/MAME 2003

But the games are off the screen, they are expanded, I guess it's because the cfg generator.

Example when opening cfg generated with your script game:3countb

video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the height
aspect_ratio_index = "22"
custom_viewport_width = "1920"
custom_viewport_height = "1792"
custom_viewport_x = "0"
custom_viewport_y = "-296"

[dankcushions]

@pirossi is that a fbalpha or mame2003 cfg for 3countb? you only pasted a bit of the cfg.

for fbalpha, mine is generated via windows 7 as

# Auto-generated crt-pi.glslp .cfg
# Place in /opt/retropie/configs/all/retroarch/config/FB Alpha/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1600"
custom_viewport_height = "1200"
custom_viewport_x = "160"
custom_viewport_y = "0"

for mame2003 i get:

# Place in /opt/retropie/configs/all/retroarch/config/MAME 2003/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1600"
custom_viewport_height = "1200"
custom_viewport_x = "160"
custom_viewport_y = "0"

(the same, as expected)

i don't know what else to suggest. you definitely have the latest version of the script from git? you need the whole repo in a directory: https://github.com/dankcushions/crt-pi-configs

[pirossi]

@dankcushions said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@pirossi is that a fbalpha or mame2003 cfg for 3countb? you only pasted a bit of the cfg.

for fbalpha, mine is generated via windows 7 as

# Auto-generated crt-pi.glslp .cfg
# Place in /opt/retropie/configs/all/retroarch/config/FB Alpha/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1600"
custom_viewport_height = "1200"
custom_viewport_x = "160"
custom_viewport_y = "0"

for mame2003 i get:

# Place in /opt/retropie/configs/all/retroarch/config/MAME 2003/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1600"
custom_viewport_height = "1200"
custom_viewport_x = "160"
custom_viewport_y = "0"

(the same, as expected)

i don't know what else to suggest. you definitely have the latest version of the script from git? you need the whole repo in a directory: https://github.com/dankcushions/crt-pi-configs

yes i have lastest version, i dont know why generates Other results than yours. It's very weird

You u can upload for could generate them and put them on the front page? 1290x1200 16:10
I am desperate and it seems to me an excellent job.

By the way my operating system is windows 7 pro 32 bits, maybe it's ready for 64bit?
But same erratic values for mame cfgs.. in all cfgs

EDITED

Another 2 colleague of spanish forum made me the favor of generating cfg's in windows10 64bits, with my resolution and the same result as mine, erratic values.
And another with windows 7 ultimate and it also comes out like me with cfg failure

[Riverstorm]

@pirossi - I just downloaded it from scratch using Python 3.6.1rc1 and it is working fine.

EDITED

Another 2 colleague of spanish forum made me the favor of generating cfg's in windows10 64bits, with my resolution and the same result as mine, erratic values.
And another with windows 7 ultimate and it also comes out like me with cfg failure

I just downloaded it from scratch. Using Windows 10 64-bit & Python 3.6.1rc1 x86-64 embeddable zip @ 1900x1200 and it looks good as far as I can see. That's the config for 3countb.

# Auto-generated crt-pi.glslp .cfg
# Place in /opt/retropie/configs/all/retroarch/config/MAME 2003/
video_shader_enable = "true"
video_shader = "/opt/retropie/configs/all/retroarch/shaders/crt-pi.glslp"
# To avoid horizontal rainbow artefacts, use integer scaling for the width
aspect_ratio_index = "22"
custom_viewport_width = "1600"
custom_viewport_height = "1080"
custom_viewport_x = "160"
custom_viewport_y = "0"

[pirossi]

@Riverstorm
thank you very much!!
I installed python 3.6 and now everything works correctly !!!!

now super! 1920x1200
Thank you very much partner !!
The problem was given by python 2.7 without a doubt!

[Riverstorm]

@pirossi said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

@Riverstorm
thank you very much!!
I installed python 3.6 and now everything works correctly !!!!

now super! 1920x1200
Thank you very much partner !!
The problem was given by python 2.7 without a doubt!

That's great. At a minimum we know 3.6 does work as some syntax or command is processing differently than intended but we know it's somewhere between 2.7 and 3.6.

[dankcushions]

neat, thanks for figuring it out, both! i've added the python version requirement in the readme. i think someone else had a similar issue earlier on in the thread when they were running the script locally and it did weird stuff. here i'm on 3.5.2.

i'd never written a line of python before this script so it's possible i've used a bunch a of 3.x python stuff when i didn't need to. python seems to have a lot of different ways of doing the same things! i'm not sure i really like it, but it seemed like the popular way to do this sort of thing.

[Riverstorm]

@dankcushions said in crt-pi shader users - reduce scaling artifacts with these configs in lr-mame2003, lr-fbalpha, lr-nestopia (and more to come):

i'd never written a line of python before this script so it's possible i've used a bunch a of 3.x python stuff when i didn't need to. python seems to have a lot of different ways of doing the same things! i'm not sure i really like it, but it seemed like the popular way to do this sort of thing.

No complaints here! It's a great script and works perfectly. I'm grateful you did write it regardless as our gaming experience is much improved for it. :)

I never think of it as an exact science but more of an art as there's so many ways to do the same thing in any language, some guys get crazy creative but it seems each programmer almost develops a specific style that becomes recognizable. You can always tweak the script here and there as you see an improvement in code or feature. It's really a nice script for never writing in Python before.