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

fRequEnCy

Elite Member
  • Posts

    3889
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by fRequEnCy

  1. Good deal! Enjoy!
  2. LOL. I spend more time with you guys than I do with the girlfriend!
  3. This can be different as we have different versions of these games. Best to try the method found in the tutorial section found here. If that doesn't help then post again and we'll try to help as much as we can.
  4. According to the help file: ProSystem Emulator Documentation Command Line switches The following list the command line switches allowed in ProSytem. If loading a rom file on the command line, it must be the last parameter in the list. -Fullscreen value Use value = 1 for fullscreen Use value = 0 for windowed -MenuEnabled value Use value = 1 to enable the menu bar Use value = 0 for no menu bar -Palette filename filename is the palette to use. If the name contains spaces, be sure to surround it with quotes -Zoom value Value can be 1 to 4 to increase the window size -Mute value Use value = 1 to mute the sound Use value = 0 to enable sound -Latency value Set to desired Sound Latency -SampleRate value Set to desired Sound Sample Rate -Region value Use value = PAL for PAL Use value = NTSC for NTSC Use value = AUTO for Auto-Detect Example ProSystem -Fullscreen 0 -MenuEnabled 1 C:\centipede.a78 This will start ProSystem in windowed mode, with the menu bar enabled, and with C:\centipede.a78 as the rom to load. So I would personally use the suggested command-line in GameEx. This will set the emulator fullscreen as well as hide the menubar. ProSystem.exe -Fullscreen 1 -MenuEnabled 0 "[ROMPATH]\[ROMFILE]"
  5. Try here, here, and here. There are other sources but until we know your naming convention it's hard to where to direct you to.
  6. This has to do with the fullscreen settings of these emulators. If you set Show Desktop to true then you will see that they are running. Currently it is set to false which is why you're seeing a blank screen but can hear them in the background. Either set it to true or fix your fullscreen settings for these emulators.
  7. Done on my end!
  8. Yeah! Most of these if not all are in preliminary status according to MAWS.
  9. Yeah! The list is much bigger now than it was before. I'm showing 50 out of the 53. I'm sure has to do with my filtering but much improved and Tom was quick about it. Thanks Tom for the new release. And Thanks Visitor Q for the heads up.
  10. He doesn't have a clue!
  11. I'd say it's probably a little of both!
  12. I always say if it doesn't work, script it!
  13. Maybe has to do with the resolution you're setting from command-line? Try removing that option just to test.
  14. It does write to the emulator.ini file. If you check the command-line then where does it tell where your MAME roms are? For testing to prove me wrong....LOL....put a semi-colon in front of the rom directory Dir1 which should point to your MAME directory. Then run from GameEx and look at emulator.ini again and you'll notice that GameEx writes a new value for Dir1 and will point to your MAME directory.
  15. According to rlswick's config, that's exactly it. Nice call bkenobi!
  16. Well for Model 2, you can setup your rom directory to also include your Model 2 romset. If you don't want to use the MAME directory at all then the only thing you can do is set the emulator.ini file to read-only so that GameEx doesn't write to it. As far as ZiNc, I'll take a look at get back to you.
  17. I would change the filters. Sometimes game saves can be saved in the same directory as your roms so if you filter includes everything then maybe GameEx is running those. Filter your roms with either zip if they're zipped, or the extension of your snes roms. Your command-line looks fine so not sure what else it could be other than what I suggested.
  18. Why would there be a need to set the path in GameEx if it can be defined in the emulator.ini file? That's where it's gathering where the roms are to load anyways. GameEx adds the location of your MAME roms to the emulator.ini file and then GameEx simply runs the the command-line as follows: emulator_multicpu.exe [ROM] I have this pointing to my Model 2 romset as well and it works fine.
  19. Thanks for all your hard work Circo! It's great to see that you're getting so big that you have to change servers. Sorry that it's such a pain for the transition. Hope all goes well and keep up the good work!
  20. Trust me when I say it works! LOL. Give us more status on what's going on so we can further help you.
  21. Congratulations Tom! Glad to see you release this.
  22. Hey LucasBarton! After toying with this some more I came to a conclusion that it's the video plugin that causes this. I tried some different ones and they didn't have it show. So it's a matter if other plugins work for you or if you wanna just deal with seeing it for a few while game is loading.
  23. Thanks Tom!
  24. That would be what you're lookin for. UI Cancel is what's used to exit MAME.
  25. fRequEnCy

    Iso's

    Using GameEx Advanced Configuration: Choose an emulator slot and select the config you want using the dropdown box. Then click on import. Using GameEx Setup Wizard: Select Custom mode. Then Emulator Selection. Choose one of the configs and click on the Left arrow to import. These configs have the suggested command-lines. Once imported, please change paths to match your needs and you're good to go.
×
×
  • Create New...