Core broken on linux and windows (and others?) [Retroarch 1.7.8]

[paradadf]

Hi! After installing Retroarch 1.7.8 the core stopped working. I've tested it on Windows and Linux. Bios are inside the keropi folder, right checksum and tested roms worked before.

[gingerbeardman]

Stop working how? How did behaviour change for you?

I do not have much time to test but I see this on macOS:

1.7.8, pressing F12 after starting core with content.

[paradadf]

I can only show you the log I get before the core crashes... I don't know why it doesn't work https://pastebin.com/yX1wcMfS

[negativeExponent]

how does it not work? what is actually happening? does the core launch at all? does the core stops at black screen? can you open the menu (F12)? do you have any other fdd/hdd images to test? i just tested on Linux and its working as well, dim, d88, hdf

[paradadf]

The core doesn't launch at all. I've tested dim and hdf files. But If you @negativeExponent are using 1.7.8 and it works, then I might just make a complete reinstall.

[negativeExponent]

im on latest commit everythin on linux. try running px68k without content (using Load Core > Start Core only) see if menu at least appears.

[paradadf]

Hi! This is what I get:

The core isn't properly starting, regardless of loading content or not.

[gingerbeardman]

I would try a new install.

[negativeExponent]

i dont think that is even related to the core. loading it might have triggered that error but it sure is not the core itself since it does not have cdrom core in it

[paradadf]

That‘s why I think it might be Retroarch 1.7.8 conflicting somehow. The thing is, I get that CDROM stuff on my Raspberry Pi too. Anyway, I‘ll make a clean reinstall and hope for the best. Many thanks for the help!

[paradadf]

I can finally tell what's going on! px68k crashes/doesn't boot if video_threaded = true in retroarch.cfg. That didn't happen before.

[negativeExponent]

ok this can be closed then...