Jump to content
LaunchBox Community Forums


  • Content count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About wasili

  • Rank
    8-Bit Processor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've been waiting for years for the Launchbox devs to include gog.com support as it already exists for Steam and when the plugin API came about I hoped somebody would make a plugin for it. Since this didn't happen I started doing it myself. It will be another two weeks or so until it's in a state fit for a first release, but until that I thought I show you my progress and maybe somebody can answer some of my questions along the way or want to give some input. While in theory - with the introduction of the gog Galaxy client and user profiles - everything we are used from steam integration could be implementet in a similar fashion for gog.com, the documentation for this isn't quite complete and also I wanted to start out with the assumption that you don't need to have Galaxy installed for the plugin to work. So my first challenge was user authentification. Since this is only possible with a browser supporting JavaScipt I shopped for libraries and ended up with CefSharp, a wrapper for the Chrome Embedded Framework for Visula Studio/.Net. After loging in for the first time we receive an acces token for further API calls. To make life (and debugging) easier the token is refreshed before every API call of the plugin and stored in a file in the plugin folder so the session can be kept alive when restarting Launchbox. After that we can get all the game data from gog.com including download paths not only for the game but also for manuals and all the extra stuff! The next step will be adding the games to the Launchbox collection and implementing a hook to ask for the download of a game when attempting to play it and set the proper application path after that. A lot of other stuff is imaginable, like downloading and adding extras like manuals and wallpapers from the context menu, proper integration with Galaxy client if installed, implementing gog.com Achievments in the Retro Achievments API and so on... At the moment I still have a problem with plugin loading: CefSharp comes with it's own binary and a lot of additional class libraries. It seems Launchbox tries to load them as plugins (even after moving them to a subfolder of the plugin folder). While it doesn't break anything it causes a ton of pop ups like the one below. Is there a way to prevent this?
  2. wasili

    Your List of Small Things

    Being able to add multiple PDF (manuals and stuff) to a game would be great. EDIT: Btw there's already an entry in the issue tracker for it: https://bitbucket.org/jasondavidcarr/launchbox/issues/855/manuals-right-click-sub-menu-more-manual
  3. wasili

    Adding FS-uae supoort for LB

    I guess you've seen this page: https://fs-uae.net/command-line ? You just set fs-uae as emulator in Launchbox and give the necessary command line arguments. For whdload games you don't need any other arguments, you start them with: fs-uae.exe game.zip or fs-uae.exe game.lha So no reason to unzip them! For multiple disk games you could try to mount all of them by emulating multiple drives: fs-uae.exe --floppy-drive-0=Disk1.adf --floppy-drive-1=Disk2.adf --floppy-drive-2=Disk3.adf FrodeSolheim on 2016-04-16 at 18:25 said: With recent development versions, you can add arguments like this: Launcher.exe --config:key=value, for example Launcher.exe --config:amiga-model=CD32. See https://fs-uae.net/2016/02/25/fs-uae-2-7-8dev-released for more information.
  4. wasili

    New Fields

    Cool thing! "Alternate Title" (and maybe also "Subtitle"?) would be useful... About the "Medium" field: I would like it. But it would mean to have more entries for different versions of a game, which wasn't the plan so far as I understood. It would make sense tough, since a lot of DOS games were reissued on CD and often with better music and stuff like that... It would also make sense then to merge platforms like Jaguar and Jaguar CD, Genesis and Sega CD and so on.... But I think other stuff, like the ability to add new games you are going to implement or having more genres to choose from would be more important. Also changing the platform of a game. For the genres we would need a whole new discussion thread though ^^ robbforce said "Also on xxx system", with a comment field to describe notable differences, like "Dreamcast: Enhanced graphics and audio. There's an easter egg when you enter this room and hit the left wall to make Sonic appear momentarily on screen." I think stuff like that could just be written into the "Overview" field (which translates to "Notes" in Launchbox I guess?).
  5. wasili

    Policy for shareware/episodic titles?

    Maybe just one more word on the kind of shareware I'm talking about: You got the first episode for free (you were allowed to "share" them with your friends) and than you could pay to get the other episodes. Even after owning all episodes you had to start them seperately (they also came on seperate disks, especially in the time of 5.25'' floppy disks). This first episodes were a final product though. If you owned all episodes you owned the whole product, so the distinction between full release and shareware seems wrong to me. After all it's just a form of distribution And as I said, many full version re-releases of famous shareware titles like Commander Keen are still just launchers for the individual episodes running in DOSBOX.
  6. wasili

    Policy for shareware/episodic titles?

    Haha ^^ I was mostly thinking about old shareware titles. My reasons why I would keep Episode entries: Some titles might not exist as complete editions, you already own them as episodes or they are available as freeware in this form. In this case I would never buy a new version from gog or steam just for a launcher file that lets me select the episode.....
  7. wasili

    Policy for shareware/episodic titles?

    I am currently adding data for some DOS shareware titles. They often come in episodes and re-releses as complete editions as well. For some, there are db entries for episodes AND the whole game, for others only of one kind. Are there any specific plans how to handle this in the future? I think having entries for both individual episodes and complete editions totally makes sense...
  8. wasili

    Scraping Amiga Games

    since people keep asking about the whdload scraping thing I created a bitbucket issue and linked to it in this thread: https://www.launchbox-app.com/forum/contributions/missing-database-amiga-whdload
  9. wasili

    Images & Database Matching

    since people keep asking about the whdload scraping thing I created a bitbucket issue and linked to it in this thread: https://www.launchbox-app.com/forum/contributions/missing-database-amiga-whdload
  10. wasili

    Missing database, Amiga WHDLoad

    Since this was a recurring question and I couldn't find one I created a new bit bucket issue for it: https://bitbucket.org/jasondavidcarr/gamesdb.launchbox-app.com/issues/85/
  11. wasili

    A perfect Commodore Amiga WinUAELoader.exe aviable!

    Hey dudechester, i'm pretty sure fs-uae creates some kind of hardrive image for every game which allows using the built-in save functions of the games. I played Eye of the Beholder on it so I'm sure it works. Did you try fs-uae? If it doesn't work like that out of the box just read a bit at their website.... PS: Technically whdload games ares something like packaged hard drive installs of amiga games. It shouldn't make any difference for using the save function of a game. Generally amiga emulations have options to write stuff on a hard disk image or on a virtual disk, you might have to go through some options menus and stuff. In any case using disk images won't make your life easier. For multi disk games you could do the following: fs-uae allows configuration and starting from the command line. For x disks you must add x virtual disk drives to your virtual amiga machine and than start up the game with a batch script.
  12. The entries for Crystal Caves Volume 1 through 3 are filed under a wrong platform as well. It should be MS-DOS but it's Windows. http://gamesdb.launchbox-app.com/games/details/13633 http://gamesdb.launchbox-app.com/games/details/13634 http://gamesdb.launchbox-app.com/games/details/13635 The same is true for the Episodes of Paganitzu: http://gamesdb.launchbox-app.com/games/images/20395 http://gamesdb.launchbox-app.com/games/details/20397 http://gamesdb.launchbox-app.com/games/details/20399
  13. I also really miss this feature... There are some people talking about the GOG API over at gog.com: https://www.gog.com/forum/general/gogcom_api/page1 One of them even wrote a little documentation for it: https://sites.google.com/site/gogdownloader/GOG%20API%20Documentation.pdf So I guess this is doable Also I couldn't find the corresponding issue at bickbucket to vote it up? Anybody has an ID for it?
  14. wasili

    Images & Database Matching

    dudechester said MASSIVE problem however, is that WHDLoad doesn't support savestates whdload is not an emulator. emulators like fs-uae which are perfect for running whdload-installs do support save states as far as I know... SentaiBrad said Yea we thought of doing something like that, but unfortunetly that would require one for each game, and most games don't exist. I'm not sure I get you here... You mean there are no whdload images for most amiga games? I would say the opposite is true. And isn't ist possible to have null values for games that are not concerned by this? Or do you mean, if you made it a db attribute, games of every platform would have it which would cause issues of some kind? Anyway including name conversion for theese games somehow would be great!
  15. wasili

    Images & Database Matching

    A comment on this subject from an amiga/whdload perspective: I don't know how ROM names are mached to game titles for other platforms, but couldn't you add a db attribute "rom name", possibly with multiple entries, that db entries are matched against when you import games? This way amiga enthusiasts could fill in theese fields and problem solved.