> mame pacman -nothrottle -str 30 -video d3d ->141.85% ->90.00%
> mame pacman -nothrottle -str 30 -video opengl ->1131.77% ->1170.22%
> mame pacman -nothrottle -str 30 -video bgfx ->99.00% -98.99
> 2 runs each on my new (lowest end... 1050 video card) "gaming" laptop. Curious on the
> speed drop on the second d3d and bgfx runs, but a speed bump on the 2nd opengl.
> And... the HUGE difference. Why would the latest video technology throw-up at d3d,
> and excel at opengl? my settings must be whacked...
> While I'm at it... how do I fix the fact that after every run, I get:
> plugins/data_story.lua attempt to call a null value (method 'get_char_width')
> Edit: disabled plugins for now. Got rid of the above warning. 99% d3d on pacman is
> still curious though
RE: Lua problem - are you positive you've updated all files when updating MAME binary? If you use mismatched plugin files with current MAME, you do have a larger chance of issues/error showing.
The -nothrottle doesn't cancel any your forced vsync commands for MAME, so it sounds like MAME is already syncing and not allowing unthrottle. You could try the same thing but making sure you have all syncing commands OFF.