erkrystof

DOS76 said OP needs the client server model because he is using a tablet and a PC in tandem because his PC only has one display adapter. If he has any free USB ports he could always get a USB display adapter and if it is an arcade machine with a marquee just run the USB up to a secondary screen I use five USB display adapters on my six screen desktop and they work very well they even have newer USB 3.0 versions but my 2.0 versions work great as long as they are plugged directly into the PC they suffer if using a hub. Actually that is what the OP's friend needs the OP would be fine without the server/client model. Good idea, I'll have to keep that in mind.

SentaiBrad said Great Idea and I don't mean this insultingly but that's still over complicated. There really wouldn't need to be another application installed. A Plugin system could work in the future, given a lot of work and security scrutiny, but why not just create an attract mode? No offense taken whatsoever. I think it would be cool if it was built into Launchbox. The complication I'm still prototyping, though, is meant to be semi-front-end agnostic. Not to say Launchbox isn't my front end of choice, but I'm a tinkerer by nature and would like to practice a design and this most flexible for integration with numerous front ends if desired. I could easily see me halting the prototype work if this makes it into Launchbox someday, I'll be too busy ooohing and ahhhhing :)

Exactly. As a super rough 2 minute diagram, I was prototyping this: This was the initial thought. I'm not so much looking for launchbox to handle the marquee art myself (though if you guys did it I wouldn't necessarily write my stuff :) ), just the hooks to identify it are enough for me. That being said if I preload the marquee server database with a Launchbox import (yeah, have to handle refreshes as well), I feel the rom name being passed to the emulator batch file would probably be enough, but that's why I posted to see if any hooks like this already exist to begin with. (It really smells of a plugin framework integration point, doesn't it?) If I ever get anything up and running I'll post back here. Thanks!

DOS76 said I understood it that LaunchBox would still be local the client server thing was just to launch the artwork on the secondary monitor now I may have misunderstood it somewhere though. As to launching the game you would need a variable setup that would represent the game in CADScoot's Daphne tutorial he is using %Games% or something similar and that is launching the different games in LaunchBox using that. I'm interested in seeing if he can run anywhere with this idea as I have a secondary monitor and would be willing to help test it out. Yup, that's more in line with what I was horribly representing in my ramble. I can probably rig up a simple diagram that better explains it going forward (and if this thing worked well enough to actually release somewhere I'd have to anyway). I did some more searching and it looks like I've unknowingly started prototyping something very similar to GameEx Extender, but I'm not sure since I've never used it.

Hi Brad, I apologize if I wasn't make it clear, let me give it a shot. :) The plan is to have a mini PC inside a game cabinet. The PC will have one display for the main game and one display for a dynamic marquee as my PC supports multiple outputs (the networking only came into play as a means for my friend who would only have one display card output but could easily get a tablet mounted). All the roms and image media will be on the same machine in this example. Use Launchbox to launch a game. Secondary display displays various media, such as the marquee or control panel layout / instructions piece. Once the game is exited, the marquee goes back to blank or some default layout. That's why i was thinking I needed some hooks to know when a game is launched and when it exits, as well as what exact game is being played so I can lookup the appropriate media to display. So i see where you're saying 'have a piece of software read the images folder and display flowing images", but I'm still wondering how I could best map the game currently being played to the marquee/steam banner/whatever image to display. Given that my only 'hook' is the rom being launched, I was wondering if any other command line parameters or something else could be provided, as I fear the rom name alone may not be sufficient, but perhaps it is if I preloaded my display software with a database import of the launchbox config (so it would know that launching the Commodore 64 version of pacman means the marquee is in 'systems/images/commodore64/marquees/pacman_2.jpg' as an example) Does that make sense? Thanks for your time.

Greetings, all. I tried Marquee Magician and CpWizBiz and the former kept breaking down on me while the latter seemed more than I wanted to bargain for. I'm a fan of Launchbox and decided to prototype my own secondary display launcher since I'm having a difficult time finding something that suits my needs. (I don't know if there's something else that does this or not, I'm a bit new on the retro side of things and have only really tried EmulationStation and Launchbox) My high level idea was to have a client/server solution that could be hooked into with simple targets for launching marquee artwork and other media samples on a secondary display while playing on the primary display. An example launch hook could be Arcade:PacMan, or Commoodore-64:Pacman, DOS:Scored Earth, etc. Something simple along the lines of Platform/Game name. The idea is that I might want platform based layouts and have the defined game name drive the determination of the actual media to load (with platform designation defaulting some pieces possibly, like a intro movie, logo, etc). The server, then, must have a database of sorts that it can use to provide media and layout instructions for the client process to render. I think that piece is straight forward enough, and I was even thinking of taking my launchbox configuration and importing pieces into the server component datastore, like artwork location, and marry those together when launching. However, I was wondering how I could best integrate this in launchbox. So far I think the easiest would be to wrap each emulator configuration with a batch file to wrap the marquee client/server handshake/media display, launch emulator, then teardown secondary display on emulator exit. Barring any flaws in my logic there, I'm trying to figure out a decent way to 'identify' the game being launched. I could use the batch file, for example, a mame batch file knows it's mame, a commodore 64 emulator wrapping batch file knows it's commodore 64, etc, but I was wondering if it's only the ROM name that's ever passed or if we could get any other information as well, as an argument or environment variable? Like platform, maybe even the GUID from the launchbox XML, etc. Maybe I'm barking up the wrong tree here, just kind of musing while I prototype. I just love the idea of a second monitor mounted above what eventually becomes a full cabinet display showing control panel photo, marquee, etc. I have not done any tablet/phone development but I guess I could see using one of those as well for s***s and giggles someday since it's all client/server. On a side note, great job, Jason. I really like how Launchbox has developed, especially BigBox.