Jump to content
LaunchBox Community Forums

Torquemurder

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Torquemurder

  1. Thanks for the reply. I am debating whether or not to create a wrapper or a standalone tool to manage the library itself by editing the XML. The main issue with the wrapper is that LB won't even attempt to launch it if the ROM doesn't exist in the first place. I feel that the best way to handle this is for the LB team to add an option that will allow for an application to be launched (with the four available variables) when a rom file does not exist.
  2. I'm a developer and I've been trying to find a way to add the ability to check if a ROM is installed, and, if not, download the file/directory from a server. The issue that I'm running into is getting LB to pass along necessary info to my app. If I use the 'Additional Apps' functionality, the %romfile%, etc variables do not appear to be supported. I suppose I could work around this by creating a new emulator which acts as a proxy/wrapper for the actual emulator, but then it won't launch at all if the romfile doesn't exist. At the moment, it appears that I have a case of you-can't-get-there-from-here. Assuming that I'm not missing anything, I think that adding the framework to allow an application to be called that provides the romfile and launchbox installation path would be useful. I'd love to be able to copy my LB installation, minus roms to a latop and not have to worry about needing 8tb+ of HD space. I'm aware that ExoDOS implemented his own solution to this, but I don't think that is a workable solution for those of us with already-curated libraries.
  3. This is a very old problem with the original GS hardware. It has to do with whether or not you were using the internal or external joyport and the speed that the GS runs at. Essentially, the problem is that some software polls the joyport too quickly and reports half the values. The fix in the old days was to calibrate the pots on your analog joystick to center at around 66, and then everything would work normally. I added a hack to KEGS years ago to allow users to change the offset via configuration, since no one has joysticks with potentiometers, anymore. Anyway, MAME is doing the correct thing, here; the bugs are in the original software. You can work around it with KEGS/GSplus by changing the Trim X/Y settings in the joystick setting to -66. Not sure if there is an equivalent fix in MAME, but you'd only want to do it for certain titles.
×
×
  • Create New...