Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

bkenobi

Elite Member
  • Posts

    4581
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by bkenobi

  1. Sorry, I'm not familiar with modes so I really don't know.
  2. Tempest is referring to the filters associated with MAME. Anytime you change something that has to do with what roms will be displayed for MAME, you need to update your list to see the changes. This does not apply for other emulators as those changes appear automatically.
  3. Aren't some of those games clones that would be filtered out even with "no clones unless better" turned on? I remember a while back there was a thread where it was mentioned that some of the more popular games are filtered out because of this. Unfortunately, I don't know which ones, so I'm probably filtering them myself
  4. Someone in the 9.71 update thread mentioned that the system tray icon shows up after about 5 seconds. Is it possible that the codec isn't being initialized immediately? I don't have a lot of experience with codecs (they are one of my arch rivals). In my experience, a video either works or it doesn't. If it does, I leave things as they are. If it doesn't, I try to get a better codec pack. I am currently using the Vista Codec Pack on my main PC and it seems ok. I really just go by other people's recommendations for the most part.
  5. Just because you install the FFDSHOW codec doesn't mean that's what Windows is using. If you have previously installed other codecs, they might still be the ones that are being used. Like others have said, the only way to be positive that the FFDSHOW pack is being used is to have it as the only set installed. It's possible to use certain utilities to change it, but codecs are a challenging beast! If you've previously tried a number of packs, you might just be better off reinstalling Windows (like Toms suggested).
  6. Note that mouse mapping in GameEx is a registered version feature.
  7. Make sure you disable the system tray icon. If you don't, it could steal focus from GameEx and cause other problems.
  8. In the emulator setup on one of the pages there is a field called "Map file". Delete whatever is in that text box and it will be disabled.
  9. Okay, how about WILLIE Wiz?
  10. FYI - the vista codec pack will work with both Vista and XP.
  11. Did you try any of the AHK scripts that have been posted on their forum? I know there are at least a couple that already do key -> mouse. I assumed you were doing this because you wanted to get the experience or something. If you just want it to work, that's where I would go. http://www.autohotkey.com/docs/scripts/NumpadMouse.htm
  12. Yes, this is an update Tom incorporated around 9.69 or so (at least 2 versions ago anyway).
  13. That's what I thought was going on too. I think I'm lost...what else is new
  14. Don't forget the GameEx Setup Wizard!
  15. Some things are turned on automatically, some require you to enable them. I don't know how Tom decides...
  16. I don't see how that would help in this situation. If you want to start from scratch, it will effectively result in the same thing. The problem is that the emulator is being called with the wrong command line somehow. This is likely a simple fix if you take a couple minutes to check your paths.
  17. The runit.bat file contains the command that GameEx used to run the last game you played in GameEx. If that doesn't work outside of GameEx, it's certainly not going to work in it. Check your paths and such. If you want more detailed help, post the contents of the file.
  18. Tempest, did you make a lookup for the rom name in your script? I didn't review it line-for-line, but if it's sending the rom name, it won't work. I saw you mentioned that, so I'm assuming that isn't an issue... If it's only a couple games that aren't loading correctly, why not just trap those specific games with MAME_Loader and have it send the specific game number it needs with the zinc command line? For instance, check for "ehrgeiza" and if present, use "40" for the rom name instead of the game.
  19. Does it still work outside GameEx? Launch the "Run Last Game.bat" file found in the GameEx Start folder to make sure it's working.
  20. This is a shot in the dark, but my guess is that you are using the shift or some other system type key for your buttons. When you hold down the key, it brings up the sticky keys thing for you which tries to steal focus. The only thing I can really suggest to be sure is to check to see if there are any error messages in the MAME cmd window. Run Asteroids and then exit GameEx. Launch "Run Last Game.bat" from the GameEx Start folder. Before you do that, add 'PAUSE' to the end of that file so the window doesn't disappear after finishing. What does that window say when you exit MAME?
  21. Please note that by accepting the updates, you don't necessarily get the new features by default. Sometimes they are optional in which case Tom doesn't necessarily turn them on. For example, force shutdown and HiToText both require you to turn them on in the settings.
  22. My uninformed guess would be that Tom will keep the program side of things up to date, but the hi-score files would likely be your responsibility. These are basically DAT files and Tom doesn't typically keep those up to date (controls.ini, catver.ini, history.ini, etc.)
  23. 'C:\Program Files\GameEx' by default. If you opted to install it elsewhere, you would have to go to that location.
  24. The origitnal MAME_Loader script will launch any time GameEx tries to launch a game through MAME. In the case of Model2, GameEx will use the other emulator and won't call MAME. As a result, those games should be unaffected.
  25. There is a key -> mouse feature built right into Windows that you might consider checking out also. I believe it's part of the Accessibility Options, but it will allow you to use the number pad as a mouse. IMO though, it's probably better/easier to use a script since it's more customizable. I just wanted to mention it in case you weren't aware. Here's a link to the MS page detailing it: http://www.microsoft.com/enable/training/w.../mousekeys.aspx
×
×
  • Create New...