Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Mamewah runs slow - see Oct 22 post  (Read 10831 times)

0 Members and 1 Guest are viewing this topic.

Minwah

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7662
  • Last login:January 18, 2019, 05:03:20 am
    • MAMEWAH
Re: Mamewah runs slow - see Oct 22 post
« Reply #80 on: October 24, 2005, 11:55:35 am »
Not sure I completely understand. Specifically, if I run a rom from command line, isn't using the mame.ini? If so, wouldn't I have the same problem?

It is using the same mame.ini, but 'resolution auto' might not behave the same.

Quote
Not trying to doubt the solution - just trying to figure out the "why".

Is it because mame.ini is set to auto and I have mamewah set to 640x480?

Lets say your desktop res. is 800x600, and Mamewah runs at 640x480.  Run a game from a command prompt (your pc will be at 800x600 - desktop res.) and mame's 'resolution auto' will pick mode X.  Now run the same game from Mamewah (res 640x480) and mame will pick mode Y.  Mode X & Y might well be totally different resolutions (or they might be the same) - I'm not sure exactly why this happens, but it does.

Edit: as anyone who has an ArcadeVGA knows, 'resolution auto' doesn't always pick the best mode so I presume it is just a flaw.

DemonBrew

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 51
  • Last login:December 10, 2014, 06:05:50 am
Re: Mamewah runs slow - see Oct 22 post
« Reply #81 on: October 24, 2005, 12:52:54 pm »
Extremely helpful, thanks again. I'll try it and let you know how it worked.
this space intentionally left blank

DemonBrew

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 51
  • Last login:December 10, 2014, 06:05:50 am
Re: Mamewah runs slow - see Oct 22 post
« Reply #82 on: October 25, 2005, 05:17:41 am »
I went into mame.ini and changed resolution from auto to 640x480. Which is what my desktop is currently set to. It didn't make any difference, unfortunately. Same thing  - some games run fine, some games just give me a black screen.

When I go into Task Manager, I see "mamewah not responding". Closing mamewah and mame either has no effect, or takes too long and I end up rebooting.
« Last Edit: October 25, 2005, 06:58:32 am by DemonBrew »
this space intentionally left blank

Minwah

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7662
  • Last login:January 18, 2019, 05:03:20 am
    • MAMEWAH
Re: Mamewah runs slow - see Oct 22 post
« Reply #83 on: October 25, 2005, 08:37:29 am »
When I go into Task Manager, I see "mamewah not responding". Closing mamewah and mame either has no effect, or takes too long and I end up rebooting.

The problem is Mamewah is waiting for MAME to quit, it is not actually not-responding.

Two other things you can try:

1) Make sure you don't have frames_to_run 1 set in mame.ini (some people were using this to skip warning screens)

2) Set {safelaunch} in your commandline_format instead of {nosafelaunch}

Leave the resolution set to 640x480 just until you have it working.  BTW you can set this to anything (doesn't have to be your desktop res) - it's just important to change from 'auto' as this can have unexpected results.

DemonBrew

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 51
  • Last login:December 10, 2014, 06:05:50 am
Re: Mamewah runs slow - see Oct 22 post
« Reply #84 on: October 25, 2005, 09:30:01 am »
I'll give that a shot. Thanks again.
this space intentionally left blank