Daffy Duck
Member
Not making any promises but I'm trying to hook this up
Your image isn't working for me.
Not making any promises but I'm trying to hook this up
NoPardon my ignorance; is there a way to change the speed of the fast forward function?
FF in RetroArch is really just disabling vsync and letting the emulation run as fast as possible. If it's not going much faster, it's because your device is already running at close to top speed, as you suspected.
Pardon my ignorance; is there a way to change the speed of the fast forward function?
Just new to retroarch, set it up with the Beetle core HW for PSX. Set internal res to x2 and video driver to Vulkan but game crashes on any internal res other than native. Any possible solutions?
Just new to retroarch, set it up with the Beetle core HW for PSX. Set internal res to x2 and video driver to Vulkan but game crashes on any internal res other than native. Any possible solutions?
did you set the video driver to vulcan in the main driver menu (then exit retroarch to save the change) and in the psx hw core options as well.
I don't see the option in the PSX core?
Also which CRT shader is best suitable for PSX games?
Those options might not be available until you've loaded the game content. Try changing the "Driver" setting to vulkan first, then load the game -> F1 and go to options to check that vulkan is set there, too. Also would be a good idea to update video drivers if it's been a while for you.
Personally I'm a big fan of crt-royale.
Not seeing any option to change driver there?
You can only change driver in Beetle PSX HW core
I thought I had that selected so I deleted and redownloaded just that core and it worked! Thanks heaps. Crazy how much better it looks.
Have you managed to get Texture Filtering option to work? Change every setting and textures still looks unfiltered =(
PS - also PGXP (Parallel/Precision Geometry Transform Pipeline) is supposed to be look so glitchy?
Have you managed to get Texture Filtering option to work? Change every setting and textures still looks unfiltered =(
PS - also PGXP (Parallel/Precision Geometry Transform Pipeline) is supposed to be look so glitchy?
Can anyone help me with this aspect ratio issue when using borders on GB/GBC games? I've been wrestling with this problem for nearly a year. Any time I use one of the handheld borders with Gambatte the aspect ratio for the game itself appears to be set to 16:9. I tried using the Sameboy core instead and the aspect ratio was 4:3, but the audio was all messed up. I would prefer to use Gambatte but I can't figure out how to fix the aspect ratio of the game.
Edit: TGB Dual gives me the same issue.
Nestopia and probably FCEUX have options to disable the 8 sprites per scanline limit to help with flickering. BSNES-Mercury and SNES9x have a SuperFX overclock option to help with slowdown/general framerate in Starfox and the like. People have asked for an overclocking option in Genesis Plus GX, but it hasn't been added yet.Apologies if I asked this before (I searched my posts in this thread but seems I hadn't but still...), I'd like to know fi there are any emulators that can remove slowdown and/or sprite flickering, far as SNES, NES and Gen/MD games are concerned.
Nestopia and probably FCEUX have options to disable the 8 sprites per scanline limit to help with flickering. BSNES-Mercury and SNES9x have a SuperFX overclock option to help with slowdown/general framerate in Starfox and the like. People have asked for an overclocking option in Genesis Plus GX, but it hasn't been added yet.
I don't think I've ever seen one for just the regular SNES CPU. I never mess with those types of settings anymore though, preferring accuracy instead.What about an overclock for normal SNES games??.....Super Ghouls & Ghosts im looking at you!
Personally I'm a big fan of crt-royale.
what option?EDIT: NVM seems VGBA has that option.
what option?
It also obfuscates large chunks of the emulator being used from the end user, which I feel is a disservice to the people who worked on that emulator - you should know what it is that you're using so that you know who to give credit to for the hard work that went into it.
LOL. The principal devs are hardcore open source advocates. There is little chance of this happening.I also wouldn't put it past them to have an end goal of getting it into the Windows app store as a free download with paid in-app DLC.
*shrugs*A good thread with the MAME devs explaining why RetroArch is a clusterfuck of a program and shouldn't be supported.
http://www.mameworld.info/ubbthread...34&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1
A good thread with the MAME devs explaining why RetroArch is a clusterfuck of a program and shouldn't be supported.
http://www.mameworld.info/ubbthread...34&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1
A quirk I found is that you have to open the tray, go back to the emulator, then go back to the menu and change discs for it to work. Took me a while to figure that out while playing Lunar.I downloaded this not long ago because I was thinking of streaming a popular imported music game series for PS1. Turns out, disc swapping PS1 games is broken as of the 1.6.x tree. Whelp, gotta find another emulator then. :/
I'll care once any other emulator or front-end has the extensive shader and cropping/scaling support that RetroArch does, along with support for per-game overrides.A good thread with the MAME devs explaining why RetroArch is a clusterfuck of a program and shouldn't be supported.
Just a bunch of FUD.
We're not saints but we're not trying to harm any other projects either.
A good thread with the MAME devs explaining why RetroArch is a clusterfuck of a program and shouldn't be supported.
http://www.mameworld.info/ubbthread...34&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1
I love retroarch (and have contributed to it), but I don't particularly like the hard-fork development model for cores.
Twinaphex has been pushing for more upstreamed cores lately though. Redream and the new PPSSPP core he's been working on are examples. Nestopia, Genesis Plus GX and SNES9x have always been upstream friendly AFAIK too. It just doesn't happen for every core. Sometimes upstream isn't interested or doesn't want the extra burden of libretro specific support requests.I love retroarch (and have contributed to it), but I don't particularly like the hard-fork development model for cores.
There isn't a strong focus on pushing improvements/changes upstream, and really poor quality patches are often accepted only to break things and have to be reverted/cleaned up after. There seems to be a strong "hack it now, fix it later" attitude which results in continually degrading code quality on things that aren't core to the project.
Additionally, poor SCM practices make it tough to merge back from upstream. Merges are often done in such a way that history is rewritten or lost and subsequent merges become much more difficult.
I realize that getting functionality out is important, but I think it'd be much healthier to work with upstream to get patches accepted, even at the expense of near term functionality. It hurts, but is far better long term for the success of an open source project.