NES emulators in 16:9 black bars discussion

[backstander]

Thanks @meleu for the heads up! I actually like the RetroAchievements so I might stick with fceumm.

I was getting those " ugly scrolling artifacts" while using QuickNES to play Castlevania but the other 2 emulators didn't seam to have them but I only tested with that one game.

@UDb23

In any case the video_crop_overscansetting should work from config file and not only thru RGUI.

I was thinking the same thing but I wonder if maybe that variable might had changed name...like now it might be called "crop_overscan" instead of "video_crop_overscan" but then I thought it was odd that "video_crop_overscan" only works in QuickNES.

[edmaul69]

@backstander it doesnt work in fceumm because it became a core option. And core options override retroarch.cfg files. It has always been messed up using in quicknes. Nestopia doesnt crop so it has no need for the option.

[edmaul69]

@dankcushions can you explain the scrolling artifacts in smb 3? I was testing and i couldnt see any issuses other than the weird line that changes size, but that is something that i believe shows on a real system as well. It does show the blue down the whole left side, so maybe that is what you are talking about? I like to make a core-options.cfg in the systems config folder that has different options that i make individual game config files point to so i dont have to change the options back and forth. I need to get back to working on the psx games. I am pointing all the games that use analogs to the seperate core-options.cfg so i never have to swap back and forth for the analog settings.

[Capeman]

@edmaul69 The loading seam explained! (this is what some emulators try to cover up) - its normal part of NES games.

[edmaul69]

@Capeman gotcha. I edited my last file about creating seperate core-options file for games like this.

[dankcushions]

@edmaul69 said in NES emulators in 16:9 black bars discussion:

@backstander it doesnt work in fceumm because it became a core option. And core options override retroarch.cfg files.

in theory core options and retroarch.cfg options shouldn't really overlap. core options are those that are specific to the core you're using (enable_multitap or whatever), whereas retroarch options are potentially applicable to all libreto cores (enable_shader), although in retropie we have separate retroarch.cfg files for each core, as well as an /all/retroarch.cfg for generic options.

so in my opinion, overscan options should either be a retroarch, or a core option, not both, but i don't really know the intention/history of that option.