Backdrops in mame2003-plus

Clyde

@Riverstorm said in Backdrops in mame2003-plus:

@Clyde - Damn, you're snaps are sharp! What type of monitor are you using? I can get AdvMAME to look that good but still no dice on Plus.

Maybe it is the shader "VecX" that I don't remember where I got it from? (It was some Retropie/Retroarch shader repo on Github I think.) I can test how it looks without the shader when I get home.

My monitor is an 21" TFT with native 1600x1200. It is connected to the Pi's HDMI port with an HDMI-to-DVI adapter. I can look up the model at home.

I could also show you my retroarch.cfg later.

UDb23

@Clyde this one's for you:

UV without the yellow "top part" ;-)

Available in same folder as previous.

Clyde

@UDb23 You're just too good for this world. 😱 Thanks! Now I have three backdrops to choose from …

@markwkidd Thanks to you, too. I now have white vectors. Interestingly (as logically), the whole picture lost its yellowish tint, which is a new but not bad impression.

@Riverstorm My monitor is a NEC MultiSync LCD2170NX. And I have a theory about my shader. It may be not downloaded, but saved by RetroArch when I tested some Vectrex games. Seems like RA saves its core and game presets in /home/pi/.config/retroarch/shaders/presets, as there is now a /opt/retropie/configs/all/retroarch/shaders/presets/MAME 2003-Plus/omegrace.glslp that I definitely did not put there.

Here's the content of my VecX.glslp, if you want to try it to get "my" picture.

shaders = "1"
shader0 = "/home/pi/.config/retroarch/shaders/stock.glsl"
filter_linear0 = "true"
wrap_mode0 = "clamp_to_border"
mipmap_input0 = "false"
alias0 = ""
float_framebuffer0 = "false"
srgb_framebuffer0 = "false"
textures = "iqLUT;scanLUT"
iqLUT = "/opt/retropie/configs/all/retroarch/shaders/ghogan42/zfast_res/iqLUT.png"
iqLUT_linear = "false"
iqLUT_wrap_mode = "clamp_to_border"
iqLUT_mipmap = "false"
scanLUT = "/opt/retropie/configs/all/retroarch/shaders/ghogan42/zfast_res/scanLUT.png"
scanLUT_linear = "false"
scanLUT_wrap_mode = "clamp_to_border"
scanLUT_mipmap = "false"

So, it uses the normal stock.glsl shader. Why it also uses some of @ghogan42's shader resources, I don't know.

And here's my complete retroarch.cfg if you want to rummage through it for more video options. Why it says video_shader = "~/.config/retroarch/shaders/presets/MAME 2010/MAME 2010.glslp" I don't know either, as I don't use this shader.

Riverstorm

@Clyde - Thanks for all the setup information. I'll see if I can figure what is causing the issue. I have the basics correct I am sure of it as there's just not much there to configure. In fact I went to 1 on beam width as it looks better on the TV. I tried TATE mode too as per Grant's suggestion on Tempest but still a no go but it was cool to see a 65" game board. Anyway It does look fine until I play AdvMAME (or see your screenshots - I'm coming for the NEC Multisync! ;).

@UDb23 - Thanks for the new BD. I spent a good deal of time last night and I lean toward the UV I think, it's very deja-vu. It's great to have options to make it fresh.

Also the BD's seem to work out of the box with no modifications in AdvMAME. I am running 3.8. What type of performance issues are you seeing in 3.9? I see only 3.9 is available for install under the RP setup. That could throw a wrench in the fray if we are forced to use 3.9 as 3.8 has been working great for me with vector games and BD's.

It seems AdvMAME is the same as 2003 in that the "effects" are applied to both the game area and BD. Since AdvMAME is currently being developed maybe he chose to do it that way purposely?

UDb23

@Riverstorm said in Backdrops in mame2003-plus:

work out of the box with no modifications in AdvMAME. I am running 3.8.

I'm (pleasantly) surprised that they work in 3.8. Multiple tests to make it work correctly in the past failed.
Will try 3.8 again and compare vector quality with 2003plus.
Slowdowns are reported for 3.9 w artwork but I haven't tested myself (actually I don't know how to "manually install it).

Riverstorm

@UDb23 - Yes I remember messing with SI to no avail. :) I'll give you the short version here real quick as it took me a while comparing the original with what's on screen.

In 3.8 Omega Race works with all BD's but it crops to the game area and leaves slight black edges on either side but it's fine vertically. I had to look several times to see what it was doing. For contrast if you play it on AdvMAME 1.4 the BD stretches the original BD cropped game area as well as the game itself. Making both game and BD to wide.

In 3.8 SI it's pretty much the same. It crops the left and right to the game area only. In AdvMAME 1.4 it stretches that original game area as well as the game to fill the screen. Way to wide for 3:4 games.

It's not immediately noticeable on 4:3 games and looks great actually. So some improved scaling is happening as the original cockpit resolution is huge but it looks good with the little left/right cropping that is going on. Basically it scales the BD to game area but also does a little cropping. It's hard to explain and weird but looks good. 3:4 games on the other hand are an immediate give away.

So 4:3 look good and 3:4 not so much. You can check it out but I think I would use them for 4:3 games for me as yours are so much nicer but 3:4 just don't look right unless it's SI only, that game.

Here's something weird when I play on a TV I suffer no performance issues (100% on speed--F11) but when I played on the 1920 x 1200 monitor with the speed on screen it dipped down to 75% and lower and performance suffered noticeably several times. I have no idea why as the resolution isn't that much different. Also maybe worth noting is it didn't matter whether it was the 1-2MB star BD or the full size 6MB cockpit BD it ran full speed on the TV.

Riverstorm

@UDb23 - Here's a screenshot as it might be easier than explaining. Click it to zoom full size. It's yellow tint due to AdvMAME. If you start the game and just play it looks good actually. I can't get Plus vectors looking that nice.

I think Clyde has a different monitor and shader that might make a difference but I wonder if @grant2258 or someone with a Pi would post a screenshot of Omega Race for comparison (it doesn't need the background) without a shader to see the vector lines. As of now I only have what I see on my screen for comparison. The shots posted above by Grant have been degraded to much for upload so all the detail is lost.

Clyde

@Riverstorm I tested a bit more with the different settings for beam width (BW) and vector multiplier (VM). Here are the results: https://imgur.com/a/nntJwhJ

It's rather obvious that the VM has a heavy impact on the quality of both the beams as the backdrop. Maybe your VM is too low? But I also noticed that a higher VM puts more strain on the game's speed and jerkiness. On my system (Pi 3B without "+", not overclocked), VM 3 has the best balance between picture quality and performance in my opinion.

That said, modern TVs are infamous for messing with the picture and/or responsiveness of games. Not without reason, there is a section about speed issues with TVs in the Retropie Docs, and some more tips regarding TVs in the FAQ. I can't help you more with that, because I don't have a TV for more than 10 years now.

What I don't understand is why my monitor should have any impact on the quality of my screenshots, since I make them from within RetroArch and not as photos from my monitor screen. Furthermore, I have disabled EDID via a line hdmi_ignore_edid=0xa5000080 in my /boot/config.txt because I had issues with the HDMI splitter that I use to mirror my cabinet's picture on my video projector. So as I understand it, my Pi shouldn't even know what monitor it is connected to.

As for my Omega Race (OR), I now decided to use @UDb23's UV2 backdrop at 0.30 brightness. Even with white vectors, I like it a bit more than the UV version with yellow elements. I also shrunk the game area to 1400x1050 (the next common 4:3 resolution below 1600x1200), because the original OR machines also had a smaller game area than their backdrop, as you can see on the video and the image posted by me and @UDb23.

My beam width remains 2 and my vector multiplier is still 3.

You can see the result here: https://imgur.com/JeE2aqs (A link to Imgur, because I want to reduce my image-spamming here ab bit. 😇 )

edit: typo

grant2258

the screenshots arent degraded they where taken on a laptop 720p with a 1x res. I dont use vector games much what seeting you want the screenshot taken with on the pi?

Riverstorm

@Clyde - Your answers are well written and helpful, thanks. I was referring mainly to the shader altering the frame and not so much the display, except the final output might look nicer on that old NEC Multisync.

I haven't heard that name (NEC) in years. One of my first PC monitors was a company named Packard Bell beyond that the old Tandy line from Radio Shack. Before that the old VIC-20 and 64. Anyway thinking I guess you're using RA so your snaps are "true" to what's generated.

The one area I haven't put time into is my TV and you have given me another avenue to explore. Let me check it's settings for a game mode and other processing but also at the back of my thoughts AdvMAME does look correct but I have hope that something here might be the cause.

I had wondered before about it and glad others do too. Here's my take on it. Beyond a small information exchange (between the TV and Pi--like mode and resolution) the Pi has no idea what "post frame processing" the TV is doing like upscaling, smoothing, color, tint, etc. It also has no information on the pixels dimensions like square or rectangular. If you used h/v sync to stretch or compress an image, etc. A lot of things can happen once it hits the display that the Pi basically has no control over.

So basically screenshots in RA are exactly how the Pi processes them before they even get sent to the TV and then the TV further processes them. I think what we see on screen and how frames are generated are slightly different in appearance.

You could take a RA generated screenshot and actual TV/monitor photo to see the differences.

AdvMAME is that way. It takes the screenshot before any filter effects are applied. Step 1 - generate frame, Step 2 - apply filter effects, Step 3 - send frame to tv.

AdvMAME takes the screenshot between steps 1 and 2 whereas RA between 2 and 3.

I duplicated your all your settings except I made my beam width 1 vs 2. Two looks to wide on my HD TV. The comparison shot above was with a BW of 1.

Since you removed that "feature" do you specify every games resolution manually?

You have given me some good information to work with thank you.

Wow, no TV for 10 years, that's impressive. The TV was like a surrogate parent for me growing up. Even when I don't watch it I have it on for the background noise. I think better with it on or as my wife says; I'm wasting electricity.

grant2258

retroarch has two ways of taking a screen shot go to video->settings

gpu enable screenshot. You really shouldnt limit yourself to retropie when testing install in on windows or linux youll have access to more driver choices

markwkidd

One of the other downsides of not having backdrop artwork support in RetroArch yet is that there is another layer of scaling introduced. Because vector rendering also happens within the core and depends on resolution upscaling to look good on a digital that is another layer of scaling.

That means you have scaling potentially happening four times:

vector rendering in the core
artwork rendering in the core
video rendering in the frontend (retroarch in this case)
television rendering the signal

People on the same emulator platform should be able to synchronize their settings for the first three and produce identical screenshots. However to get good results across a variety of connection types and displays might require trial and error changes to settings for the first three layers -- if that makes any sense.

grant2258

I dont think the artwork is anything to do with it in this case. Does your rendering improve when you disable the artwork if not is scaling somewhere between the tv or the gpu. Im not sure how retropie deals with overscan ect.

for lg i get my scaling working properly for 90% of things by picking aspect ratio-> just scan form the quick menu

grant2258

not really sure what good it will do posting screenshots from the pi but here you go

alt text

Riverstorm

@grant2258 - Thanks, that answers my question. When I get some extra time I am going approach it from a new image with Plus only. Adding one change at a time and see if I can figure out what's taking precedence over my vector settings as my values match what Clyde posted. Can I ask what is your monitor resolution, basically what's your Core Provided resolution on these screenshots?

grant2258

resolution is 1080 this works fine ons 720p laptop monitor as well. Download the image and click properties it will give you the resolution used in the details tab

1440 x 1080 which is 4:3 aspect in 1080 (core provided)

mame2003-plus-dcs-speedhack = "enabled"
mame2003-plus-samples = "enabled"
mame2003-plus-skip_disclaimer = "enabled"
mame2003-plus_art_resolution = "1"
mame2003-plus_brightness = "1.0"
mame2003-plus_cheat_input ports = "disabled"
mame2003-plus_core_save_subfolder = "enabled"
mame2003-plus_core_sys_subfolder = "enabled"
mame2003-plus_crosshair_enabled = "enabled"
mame2003-plus_dcs_speedhack = "enabled"
mame2003-plus_dialsharexy = "disabled"
mame2003-plus_display_artwork = "enabled"
mame2003-plus_display_setup = "disabled"
mame2003-plus_dual_joysticks = "disabled"
mame2003-plus_enable_backdrop = "enabled"
mame2003-plus_four_way_emulation = "enabled"
mame2003-plus_frameskip = "0"
mame2003-plus_gamma = "1.1"
mame2003-plus_input_interface = "retroarch"
mame2003-plus_machine_timing = "enabled"
mame2003-plus_mame_remapping = "enabled"
mame2003-plus_mouse_device = "mouse"
mame2003-plus_neogeo_bios = "default"
mame2003-plus_nvram_bootstraps = "enabled"
mame2003-plus_rstick_to_btns = "enabled"
mame2003-plus_sample_rate = "48000"
mame2003-plus_skip_disclaimer = "disabled"
mame2003-plus_skip_warnings = "disabled"
mame2003-plus_tate_mode = "disabled"
mame2003-plus_use_alt_sound = "enabled"
mame2003-plus_vector_antialias = "enabled"
mame2003-plus_vector_beam_width = "1"
mame2003-plus_vector_flicker = "20"
mame2003-plus_vector_intensity = "1.5"
mame2003-plus_vector_resolution_multiplier = "3"
mame2003-plus_vector_translucency = "enabled"

Clyde

@Riverstorm said in Backdrops in mame2003-plus:

I duplicated your all your settings except I made my beam width 1 vs 2. Two looks to wide on my HD TV. The comparison shot above was with a BW of 1.

Since you removed that "feature" do you specify every games resolution manually?

I don't know what you mean by removing "that feature". Could you please rephrase that?

No, I am not specify the resolutions manually. As far as I remember, I left all of the settings at their default values. See my video options from my retroarch.cfg:

video_adaptive_vsync = "false"
video_allow_rotate = "true"
video_aspect_ratio = "-1.000000"
video_aspect_ratio_auto = "true"
video_black_frame_insertion = "false"
video_context_driver = ""
video_crop_overscan = "true"
video_disable_composition = "false"
video_driver = "gl"
video_filter = ""
video_filter_dir = "default"
video_font_enable = "true"
video_font_path = ""
video_font_size = "12.000000"
video_force_aspect = "true"
video_force_srgb_disable = "false"
video_frame_delay = "0"
video_fullscreen = "false"
video_fullscreen_x = "0"
video_fullscreen_y = "0"
video_gpu_record = "false"
video_gpu_screenshot = "true"
video_hard_sync = "false"
video_hard_sync_frames = "0"
video_max_swapchain_images = "3"
video_message_color = "ffff00"
video_message_pos_x = "0.050000"
video_message_pos_y = "0.050000"
video_monitor_index = "0"
video_msg_bgcolor_blue = "0"
video_msg_bgcolor_enable = "false"
video_msg_bgcolor_green = "0"
video_msg_bgcolor_opacity = "1.000000"
video_msg_bgcolor_red = "0"
video_post_filter_record = "false"
video_record_config = ""
video_record_quality = "4"
video_record_scale_factor = "1"
video_refresh_rate = "59.940060"
video_rotation = "0"
video_scale = "3.000000"
video_scale_integer = "false"
video_shader = "~/.config/retroarch/shaders/presets/MAME 2010/MAME 2010.glslp"
video_shader_dir = "~/.config/retroarch/shaders"
video_shader_enable = "true"
video_shader_watch_files = "false"
video_shared_context = "false"
video_smooth = "false"
video_stream_config = ""
video_stream_port = "56400"
video_stream_quality = "6"
video_stream_scale_factor = "1"
video_stream_url = ""
video_swap_interval = "1"
video_threaded = "true"
video_vsync = "true"
video_window_opacity = "100"
video_window_show_decorations = "true"
video_window_x = "0"
video_window_y = "0"
video_windowed_fullscreen = "true"

@Riverstorm said in Backdrops in mame2003-plus:

Wow, no TV for 10 years, that's impressive. The TV was like a surrogate parent for me growing up. Even when I don't watch it I have it on for the background noise. I think better with it on or as my wife says; I'm wasting electricity.

Haha. :) Well, in the times of YouTube etc. I don't miss my TV at all. Also, in Germany we have a good number of public broadcasters that provide many of their transmissions in online "Mediatheken" (plural of Mediathek). And with a nifty tool called MediathekView, I can watch or even record all public station in one GUI.

Riverstorm

I have disabled EDID via a line hdmi_ignore_edid=0xa5000080 in my /boot/config.txt because I had issues with the HDMI splitter that I use to mirror my cabinet's picture on my video projector. So as I understand it, my Pi shouldn't even know what monitor it is connected to

@Clyde - The line above is why I was asking. I always thought the "handshake" between the Pi and display is how the Pi determines the display resolution and then calculates the Core Provided resolution for the display used. The thought being if the Pi has no idea what type of monitor is connected, whether be 1920 x 1080 or 1600 x 1200 how is the Pi calculating your Core Provided resolutions. Hopefully that makes better sense.

Ah, yes I know many folks that use strictly streaming for TV now but I do know a few that don't use any TV at al!. I guess they count on reading for current and world events. It's not totally a lost art I read every night. :)

@grant2258 - Your resolution is a perfect 1440 x 1080? I always seem to lose some pixels at different resolutions if a BD is loaded so I was curious what your actual Core Provided values are showing. Different BD's change the values also, like stars vs cockpit. I have some interesting values for each one and to help with troubleshooting I was hoping to get your actual values? If they actually show a perfect 1440 x 1080 my setup is really hosed.

UDb23

@grant2258 Just checked and actually I got the same resolution issues as @Riverstorm.
I never changed any of the default settings in my current config; 1080p tv, screen res is at 1080p (1440x1080 for omega race). Latest mame2003plus: omega race w white lines.
Used your settings but still no good image. As you can see from pictures below the issue is related to diagonals drawing. It seems lines are calculated at low res and then pixels are upscaled.

See letter R or M

This is advancemame's output (star castle):
letters

game

Same PI3b+ on same TV (game mode).

Tested also w BD disabled and has no impact on vector games quality (at least for me)

I'm quite clueless at this point.

UDb23

Also tested higher resolution multiplier, even with 6 still these ugly diagonals.