In my personal experience, this creates a race condition on the client-side software if you try to add more than about 50 games at once - at which point adding more will cause significant delays in processing or leave your local client in a condition like Milldorĭescribes where some games won't show as "owned" (see step 4 above). Unfortunately, it's not a well optimized process when you want to add hundreds or thousands of games to your client while simultaneously needing to do synchronous server-side tasks. There are several problems with this process but I suppose GOG considers it to be "good enough" since the overwhelming majority of users will have libraries of less than 100 or even 1,000 digital games. Plugin runs in the background when GOG Galaxy is running, refreshing this data every "tick" which I believe is 15 seconds.GOG then goes through a seemingly complex server-side process that permanently ties that game to your GOG account.Plugin informs GOG that the new game is "owned" by the user (RetroGOG should do this automatically for any ROM file it finds in the configured path).If a match is made, Galaxy will attempt to download artwork and associated metadata for that title.Galaxy attempts to match the name / platform of that game to their online database.Plugin (RetroGOG in this case) tells GOG Galaxy that a new game has been added to the connected platform.User connects Plugin to GOG Galaxy and authenticates.This isn't specific to RetroGOG or retro roms, which is why I always ask how many ROMs are being processed at once.Īs best I can tell, the program works thusly: server side processing that happens when you add games to GOG Galaxy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |