RetroFE forums

Been there... wishing you the best!

Thanks! I'd never sort that out by myself. Although, having now compiled the latest version, it still crashes the same way ): Here's the latest crash log: https://pastebin.com/mLi0GzW1

I would test a pre-compiled macOS release, if any of you are able able to provide it, perhaps I'm doing something wrong at that stage. The furthest I've managed was the aforementioned version where I got past the intro video crash into the main collection menu, until it then crashes upon entering any collection. I don't remember how that version was compiled. Here is the crash log of it: https://pastebin.com/nw6y8MQQ

Thanks for your response. I didn't post it because I'm fairly sure it isn't much help. Compared to a Windows install, it's just not working properly out of the box, and RetroFE doesn't log this type of thing on the file. Here is the log with the compiled version that gets me the furthest, using my settings from my old Windows build: https://pastebin.com/Eb8m8FEy

I'm hopeful it's something about the gcc c+11 compatibility that you've mentioned. There's some clue to it here https://bitbucket.org/phulshof/retrofe/issues/27/compilation-c-11-missing-error-on-ubuntu but the fix given fails on macOS at just about the last step when compiling:

[ 98%] Building C object CMakeFiles/retrofe.dir/Users/firewater/retrofe/RetroFE/ThirdParty/sqlite3/sqlite3.c.o
error: invalid argument '-std=c++0x' not allowed with 'C'
I'd like to compile it again without relying on these forceful fixes. I'm not a programmer, so when I look "gcc macos c+11 enable" up I get confused with all the terminology. brew tells me I'm running gcc 9.3.0_1, but obviously that's not enough to default since the syntax error mentioned above keeps happening. How do I properly enable c+11 for gcc?

Thanks for your work Pieter. I'm looking forward to mp3 support!

Made some progress. Digging an old post I was linked to a page with better instructions for macOS https://bitbucket.org/RetroPrime/retrofe/src/default/ This led me to successfully install the required libraries via brew.

I'm now at an error when compiling

cmake --build RetroFE/Build
Scanning dependencies of target retrofe
[  2%] Building CXX object CMakeFiles/retrofe.dir/Collection/CollectionInfo.cpp.o
[  4%] Building CXX object CMakeFiles/retrofe.dir/Collection/CollectionInfoBuilder.cpp.o
[  6%] Building CXX object CMakeFiles/retrofe.dir/Collection/Item.cpp.o
[  8%] Building CXX object CMakeFiles/retrofe.dir/Collection/MenuParser.cpp.o
/Users/firewater/retrofe/RetroFE/Source/Collection/MenuParser.cpp:100:55: error: expected expression
        std::sort(menuItems.begin(), menuItems.end(), [](Item *a, Item *b) {return Utils::toLower(a->fullTitle) <= Utils::toLower(b->fullTitle);});
                                                      ^
1 error generated.
make[2]: *** [CMakeFiles/retrofe.dir/Collection/MenuParser.cpp.o] Error 1
make[1]: *** [CMakeFiles/retrofe.dir/all] Error 2
make: *** [all] Error 2

I'm loading screenshot_1, screenshot_2, and fanart placed in "metadata/<collection>/medium_artwork/" with this:
<reloadableImage type="screenshot_1" x="370" y="780" xOrigin="center" yOrigin="center" height="200" layer="4">It works for all collections beacuse the collection name always matches a folder in "metadata", but this one doesn't. So I want to load "metadata/Super Nintendo/medium_artwork/fanart" images for a collection called"Super Nintendo Alternative".

edit: aaaand like you say, I have to do it per type, so "M:/Media/Games/Metadata/Super Nintendo/medium_artwork/screenshot_2" is the complete path, thanks !

Thanks a lot for your time keeping RetroFE alive Pieter! Hopefully this can get sorted out eventually. In the meantime, here's one I came up with so one can get around the issue. It's all based on using the per-game launcher feature (explained here: http://retrofe.nl/SMF/index.php?topic=51.0). There are 3 ways to go about it, and I'm gonna list them from most cumbersome to least.

1. You set up a game launcher that uses the complete address of the folder.
arguments = "M:/Media/Games/System/PlayStation/Tekken/Tekken.chd" -L "cores/mednafen_psx_libretro.dll"This will work for both the PlayStation collection, and the game. The cons is that you will end up having to create dozens of launchers (one for each game), which can get messy.
2. You set up a game launcher that uses the command the merged collection accepts as valid:
arguments = "%ITEM_DIRECTORY%\%ITEM_NAME%\%ITEM_NAME%.chd" -L "cores\mednafen_psx_libretro.dll"This will work for only the merged collection. If you were to open the game from the collections it's from, it won't.
3. You set up a new collection made exclusively for use in merged collections. So you create "PlayStation for Merged" with a command that merged collection accepts as valid:
arguments = "%ITEM_DIRECTORY%\%ITEM_NAME%\%ITEM_NAME%.chd" -L "cores\mednafen_psx_libretro.dll"This way you have a separate command for your normal PlayStation collection and the merged one (so the game will work on both), without having to create per-game launchers.

Do note that this launcher exception has to be created on the collection the merged one is retrieveing the games from (so on "PlayStation", not on "Fighting Games").