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: MAME eats up 50% cpu when it shouldn't  (Read 1074 times)

0 Members and 1 Guest are viewing this topic.

Brian Zellinger

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 27
  • Last login:July 08, 2008, 11:56:22 pm
MAME eats up 50% cpu when it shouldn't
« on: May 13, 2008, 08:29:42 pm »
3.2 ghz P4 Prescott
512 Mb ram
ArcadeVGA Ati 9200
Windows Home Server

I built a dedicated cab for trackball games. Centipede, Marble Madness, etc run 60fps no problem. However, Golden Tee '97 - Golden Tee Classic drop frames. They range from 45-60 fps and the cpu is constantly around 50%. These games run flawlessly on my 2.6ghz with XP. I've tried the latest MAME and also an old Pentium Pro build (105).

MAME ini (correct settings according to Ultimarc fro ArcadeVGA)

### mamepp.ini ###

### Frontend Related ###

### Windows path and directory options ###
rompath                 roms
samplepath              samples
# inipath               <NULL> (not set)
cfg_directory           cfg
nvram_directory         nvram
memcard_directory       memcard
input_directory         inp
hiscore_directory       hi
state_directory         sta
artwork_directory       artwork
snapshot_directory      snaps
diff_directory          diff
ctrlr_directory         ctrlr
cheat_file              cheat.dat

### Windows video options ###
autoframeskip           0
frameskip               0
waitvsync               0
triplebuffer            0
window                  0
ddraw                   1
direct3d                0
hwstretch               0
# screen                <NULL> (not set)
cleanstretch            auto
resolution              auto
refresh                 0
scanlines               0
switchres               1
switchbpp               1
maximize                1
keepaspect              1
matchrefresh            0
syncrefresh             0
throttle                1
full_screen_brightness   0.000000
frames_to_run           0
effect                  none
screen_aspect           4:3

### Windows Direct3D 2D video options ###
zoom                    2
d3dtexmanage            1
d3dfilter               1
d3dfeedback             0
d3dscan                 100
d3deffectrotate         1
d3dprescale             auto
d3deffect               none
# d3dcustom             <NULL> (not set)
# d3dexpert             <NULL> (not set)

### Windows misc options ###
sleep                   1
rdtsc                   0
high_priority           0

### Windows sound options ###
audio_latency           1
# wavwrite              <NULL> (not set)

### Input device options ###
mouse                   1
joystick                0
lightgun                1
dual_lightgun           1
offscreen_reload        1
steadykey               0
keyboard_leds           1
led_mode                ps/2
a2d_deadzone            0.300000
# ctrlr                 <NULL> (not set)
paddle_device           keyboard
adstick_device          keyboard
pedal_device            keyboard
dial_device             keyboard
trackball_device        mouse
lightgun_device         mouse
digital                 none

### Mame CORE video options ###
norotate                0
ror                     0
rol                     0
autoror                 0
autorol                 0
flipx                   0
flipy                   0
gamma                   1.200000
brightness              1.000000
pause_brightness        0.650000

### Mame CORE vector game options ###
antialias               1
translucency            1
beam                    1.000000
flicker                 0.000000
intensity               1.500000

### Mame CORE sound options ###
samplerate              44100
samples                 1
sound                   1
volume                  0

### Mame CORE misc options ###
artwork                 1
use_backdrops           1
use_overlays            1
use_bezels              0
artwork_crop            0
artwork_resolution      0
cheat                   1
debug                   0
# debugscript           <NULL> (not set)
# playback              <NULL> (not set)
# record                <NULL> (not set)
log                     0
oslog                   0
skip_gameinfo           0
skip_validitychecks     0
bios                    default
# state                 <NULL> (not set)

### Configuration options ###
readconfig              1
verbose                 0

I don't think there's an issue with the ini. I'm thinking is Windows Home Server. I would like some opinions. Thanks.


Brian Zellinger

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 27
  • Last login:July 08, 2008, 11:56:22 pm
Re: MAME eats up 50% cpu when it shouldn't
« Reply #1 on: May 13, 2008, 08:48:46 pm »
Update:

I just dragged the rom itself onto the mamepp.exe and I had no issues. I use MaLa if that makes a difference.

Update2:

I turned on hardware stretch and that fixed it. However, my monitor is rolling now.
« Last Edit: May 13, 2008, 08:53:05 pm by Brian Zellinger »