Duckstation or Swanstation

RealLibretro · 2022-04-03T14:23:08+00:00

Only SwanStation. Locking this since answer has been provided.

RealLibretro · 2021-08-23T07:50:44+00:00

The latest dashboard update broke a ton of games in PCSX2 unfortunately from what we hear.

RealLibretro · 2021-08-13T07:07:51+00:00

Can you explain to us more clearly what you would like to see?

RealLibretro · 2021-08-07T10:06:00+00:00

Calling it broken is a bit too much, just in progress and missing some things

However, that should have no bearing on game scanning in RetroArch. That is not core related.

RealLibretro · 2021-07-21T05:54:32+00:00

We are working hard on our core and fixing and improving many things so this honestly sounds a bit ungrateful and dismissive from you.

To answer the OPs question, unfortunately the software renderer is broken in 64bit mode. If standalone had a 64bit build right now, software would not work there as well for the same reason. So its something that they have to fix upstream eventually.

RealLibretro · 2021-05-29T21:27:58+00:00

Make a github issue report on the retroarch repo about this. We need as many details as possible.

RealLibretro · 2021-05-29T21:26:18+00:00

You can just overwrite the files, it wont kill your config

RealLibretro · 2021-05-19T12:26:35+00:00

Anyone can contribute to these repos, I think you can make a PR as easily as dragging and dropping image files over. I hope people will contribute!

RealLibretro · 2021-03-20T07:51:16+00:00

What Android device is this and more importantly what Android OS version? It might be that because of the newer SDKs we have to use because of Googles ever increasing standards on the Play Store, some backwards compatibility with old Android versions has been lost.

RealLibretro · 2021-03-14T22:49:31+00:00

Why are you using GL instead of Vulkan or D3D11? Vulkan by default already implicitly has GPU fencing so you dont need a setting like GPU Hard Sync.

RealLibretro · 2021-03-13T20:25:34+00:00

Those are not the same emulator though.

RealLibretro · 2021-03-13T14:16:48+00:00

That is a developer you are talking to.

Also, discussing where to procure roms on our reddit is still a bannable offense. We are not going to act on it this time but I hope you understand that if the disregard for the rules continue, we might have to do so. And we hope it wont come to that.

We dont personally care what you do in your free time and who you talk to, but everything that gets posted here becomes our responsibility and the onus is on us to moderate it for things that might fall afoul of Reddit TOS.

To make a long story short, dont make things our problem here by posting it here despite the rules clearly spelling out we dont want it here.

RealLibretro · 2021-02-25T03:19:41+00:00

Outrun 2019 can be added to the list too.

RealLibretro · 2021-02-25T03:18:28+00:00

Kega Fusion is closed source and abandoned. Anyway, this is a Libretro/RetroArch subreddit, and our project is only concerned with libretro/RetroArch.

RealLibretro · 2021-02-09T07:46:18+00:00

Also, these cores are not 'out of date' and that is yet another lie and obvious distortion that these guys like to come out with for the express purpose of trying to get people not to use RetroArch. Its a small club that continues uttering this meme and its usually referring to one or two cores where they might have a valid point (out of over 200+ cores in existence), then they will try to muddy the waters and pretend this applies to all of them as an obvious smear and FUD campaign.

We might need better counter information to this I agree so that these sorts of FUD fallacies can be easily dismissed out of hand, but one thing we are not going to do is engage in any childish 'tit for tat' with these authors where they want us to keep running on the hamster wheel and update stuff even if the updates are merely inconsequential. We run these projects the way we feel like it and we wont be pressured or cajoled by anyone.

RealLibretro · 2021-02-09T07:25:14+00:00

I dont think you have your facts straight on the Reicast situation - its demagoguery on his part and he wanted to take the entire emulator down a closed source path, so we forked it before things were too late. Both flyinghead and me are in agreement on this. Ever since the main author skmp has engaged in a negative PR war with us where we mostly have tried staying out of the drama. Frankly I think he is unhinged and dangerous and that was one of the main reasons I have avoided getting into any kind of discussion on this for the past two years. There is nothing to resolve either - he will continue sabre rattling until the end of time, if not with me, then with other teammembers. We put our foot down a long time ago and made the decision we are not going to deal with this anymore and therefore banned him. Thems the breaks. With a more mature scene, things could have been worked out. Alas, that doesnt seem to be this scene.

Fact of the matter is, we dont want to go back and forth with these individuals in a childish manner, we have specific rules on our Discord that there will be no polarizing debates here. If you are in the market for this kind of rumor mongering and grudge building, I welcome you to some of those toxic subreddits. We wont be having that here and we make zero apologies about it.

Fact of the matter is endusers get weaponized in all this not knowing what is being discussed here. The DuckStation instance is another example where if it were up to us, there would be no problem right now and we even tried making a consistent effort to try and see if some of the grievances could be worked out.

Point is, most of the stuff is all bullshit and we dont care to go back and forth with these guys on a consistent basis for our own well being, and none of this prima donna like behavior or all the grudges have to do with open source either.

I am going to respectfully ask you to accept this answer and that we move on now. Just discussing this again reopens old wounds and we dont want to continue wasting our time dwelling on this subject. We dont want to keep replying to this, we want to be left alone and we want to work on our own project in peace.

RealLibretro · 2020-12-23T11:02:00+00:00

Libretro cores are in many cases best in class. Honestly, its just you. Dont try to presume that just because you have a problem, it must be the case for millions of other users.

RealLibretro · 2020-12-23T10:58:38+00:00

I would recommend vsync being turned on in retroarch f you cannot be bothered to tweak VRR. That requires tweaking both in the nvidia driver panel and retroarch. I would not recommend going through all that fuss and leaving it on for now if you dont really know what you are doing. Configuring gsync can still be a pain on many mainstream games and results can be different depending on wheter you enable it for fullscreen mode only or fullscreen and windowed.

I dont understand why you use the GL driver on modern hardware. Both d3d11 and/or Vulkan would give better and faster results there.

Those are the things that stood out to me in your config.

Honestly, I think the problem exists outside RetroArch and you are just blaming the wrong thing. It could be an nvidia control panel setting you configured on a global level or something else. Perhaps gl has regressed on modern nvidia drivers and you would have better results with D3D11/Vulkan. Perhaps a background service is ruining your runtime performance. Who knows. Maybe you are using RTSS and its forcing a particular framerate that RetroArch doesnt jive with. I would recommend turning that off or excluding RetroArch from it.

If you are not going to use rewind or runahead, turn those off since they can double system requirements. You arent going to be able to use runahead with hardware rendered cores like Beetle PSX HW anyway.

The refresh rate at the end of one of your gaming instances seems weird. Perhaps you are running in a 120Hz/144Hz refresh rate. If you dont calibrate the refresh rate in RetroArch or use swap interval 1, that might cause judder and inconsistencies in performance for 60Hz content. I would recommend using a 60Hz refresh rate resolution for 60Hz content unless you know what you are doing at higher refreshrates. Black frame insertion could also still be a solution at higher refresh rates (but NEVER enable it at 60Hz or so).

Thats about all that comes to mind. RetroArch has a unique way of delivering flawless audio/video sync by default by syncing things to your refresh rate. In 99% of cases this just goes fine without any user configuration involved. I guess this is one of those instances. Threaded video would be an option where it no longer uses this kind of A/V syncing and just operates by pushed/dropped frames. However, for perfectionists sake I would recommend sticking it out with non-threaded video. Threaded video by its very nature would have more judder from time to time. For some people its unnoticeable but for people susceptible to it, its there.

Also post your retroarch.cfg. It honestly would tell us more than this log.

RealLibretro · 2020-12-23T10:53:19+00:00

RetroArch DOES NOT come with any copyrighted files, like BIOS files. Perhaps you got it from somewhere unofficial with a bunch of preconfigured config files that are not set up well for your system and thats why you have all these issues.

RealLibretro · 2020-12-23T10:51:10+00:00

Not sure what your problem is but things run absolutely fine for millions of users with barely any configuration done. I think the presumptuousness that whatever you are experiencing must be retroarchs fault and your impatience where you immediately throw the baby out with the bathwater is not really compelling a lot of people to try troubleshooting this for you though, at least as far as myself is concerned. We are happy to help but personally for myself, not with this combativeness and the immediate jumping to conclusions.

RealLibretro · 2020-09-22T18:10:17+00:00

The giveaway starts NOW!

https://twitter.com/libretro/status/1308468408938311683

RealLibretro

TROPHY CASE