![]() DLIBRETRO=ON -DENABLE_GNUTLS=ON, although note that this 'tls' is 'thread local storage' not 'transport layer security'. It's called on getting a color for the console. #1 0x00007fffa82179c4 in IConsoleWriter::GetColor() const (this=0x7fffa853fba0 ) at /home/i3/Downloads/pcsx2-git/common/Console.cpp:327 ![]() sysdeps/x86_64/tls_get_addr.S: No such file or directory. Thread 1 "retroarch" received signal SIGSEGV, Segmentation fault. ![]() Don't bother trying to stay up to date with master until you're ready to PR. In general, I would recommend that if you plan to make big changes to anything, that you make a fork from the start. Same goes for the plugin to core merge, if you're working on a JIT you shouldn't have to touch any of the things touched by those merges, and can just ignore them. That was the plan from the beginning, so if you were worried about it, you could have asked on the PR thread and we would have said so. If it's a clean slate rewrite, why would it be affected by changes to the current one? And while there was all sorts of changes happening on the 圆4 work branch, the final merge was fairly clean and changed little. Because that's how and why forks are made - to have a comfortable codebase that doesn't turn to a fucking warzone overnight. Well, I've lost any shred of hope for those guys, so I'm starting my own fork. Now it's more of the same: the same week I revisited the issue, spending some 16 hours to untangle the core's dependency graph, some other nutcase has just decided that it'd be nice to open the road for even more nutcases to break the plugins encapsulation and smear them all over the core, as if it isn't a fucking nightmare already. Now pcsx2 has 64-bit EE and IOP recs that are roughly twice slower than that they have any right to be. It's not that I hated being one-upped, it's just that for the entire summer the codebase was as volatile as Nitroglycerin, precluding any meaningful work on my part. Half a year ago I've spent a week working on a clean-slate rewrite of the jit, targeting amd64 and aarch64, and have had to scrap the work due to some nutcase embarking on a months-long crusade of hacking the existing jit to do amd64. in the case of Play! license is MIT, and since there is no CLA in place, relicensing isn't a choice I even have (nor will I be able to obtain since I'm not the project owner XD).and no CLA is in place at the moment (while I don't foresee a CLA in the future, (1) its does not apply retroactive, (2) so my work regarding the core remains true, (3) should Jean (emu owner) does purse it, its his choice, but I don't see it having a bearing on this bounty as per point (1) and taking that into account, this could apply to ALL current cores, so not really my issue in the future) ().I read about logging to try and pinpoint the problem but I don't think I have the tools to produce retroarch logs on android.Thanks for the reply, but it didn't really address my question, the issue was original opened for PCSX2, but then Play! was added as an acceptable alternative, though the wording for that is somewhat discouraging, so I want to confirm if a core for Play! will indeed be accepted for the bounty? (as I believe the issue has to be closed for the bounty to be processed?) I also read that it shouldn't matter whether the files are iso or bin/cue they should work equally fine. cue file separately (as this is what worked for my Sega Saturn emulator) but this doesn't work either. I done a bit of research online and I discovered that the video drivers should be set to Vulkan instead of GL so I've toggled these settings back and forth to no avail. For one of the games (tekken tag) I just get a black screen with mumbled audio periodically. cue images but I can't seem to get any to work at the moment. I've downloaded the "Play!" Core as I want to test out the PS2 compatibility, I've gone on to the github page which lists the games compatible with the emulator as it's not many at the moment, I have a few of the games as. I'm using the retroarch 64-bit app on my android device (S20 Ultra).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |