forums.marpirc.net

bm, can you tell if it's a mame63 vs. tgmame63 thing, to at least get barry off the hook :)

I have 9.0a on both 98 and xp now and it didn't change anything, (err at least i think) i installed the wxwebsetup but it said 9.0.

My NBA Jam tests were all with the standard versions so it has nothing to do with AlphaMAME.

Did you check the version number with DXDiag? Start -> Run -> dxdiag

If you want the full setup go to http://www.microsoft.com/downloads/deta ... layLang=en

One thing that I can think of that appeared in 0.63 was the change in timing system. Console version defaults to QueryPerformanceCounter(), MAME32 defaults to RDTSC. RDTSC can be forced with the -rdtsc switch. You can see which is being used by using the -log switch ("Use developers' log" in MAME32), run MAME, and opening error.log.

-rtdsc or -nortdsc had no effect on bbh's (working for me) or luja's (not working for me) other than in the error RTDSC was reported when i used -rtdsc.

Same here. Stuff either works or doesn't.

bbh + Luja, can you make quick recordings (that at least get 10k or so) with http://mahlemiut.marpirc.net/alphamame-062-3.zip and post. Luja's goes out of sync at 200 but i don't know how fast bbh's goes out of synch for others since it works for me) so maybe a quick record would do.

throwing up an idea: should we put a special rule in for these games (that have this peculiar quality) to only be recored with tg/mame62 untill we figure out what's going on? I'd hate to allow recordings where the said OS, processor and options were used for the recording that can't be played back with the same set and options.

Comparison using performance counter for timing:

should we put a special rule in for these games (that have this peculiar quality) to only be recored with tg/mame62 untill we figure out what's going on?

If the current recordings will not be zeroed, yes. How do we find out which games have these problems though?

and my performance?

if the 62 plays back correctly with both of your configs, and rule is setup, all recordings after 62 should be removed just for the reason of them never being able to playback if the person doesn't have this unknown (as of yet) setting on their computer to get it to playback. You have the most at stake with all the basketball recordings :) Maybe we'll figure it out, though. So we can leave them in, and then add the setting to the description to allow everyone to play them back...

These could only be determined if they are posted here and we see the same sort of patterns, certain people play them back and certain dont.

I don´t agree with the removing of the confirmed inps. It's not an easy thing to make these records!

I hope to figure what´s the problem!

I've download the alphamame62.3 file, but I don´t use the command line version earlier. What exactly have to put to make an inp of the game Zwackery?

Thx

Luja wrote:and my performance?

You need to enable the logfile (see mahlemiut's post) and check for yourself. Please post the result here.

Chad: We have a few games now with this problem so setting up rules for those wouldn't be much of a problem. But what about other games? Do I have to check all new submissions on both of my setups from now on?

SJK can play back my bball inps, hehe.

I've download the alphamame62.3 file, but I don´t use the command line version earlier. What exactly have to put to make an inp of the game Zwackery?

You get this batch file: http://marp.retrogames.com/bat/record.bat

and put it in your MAME dir. Start a recording with "record zwackery".

This what appears in the error log:

using RDTSC for timing ... cycles/second = 1540080120
width 512, height 480 depth 16
set visible area 0-0 0-0
set visible area 0-511 0-479
Physical width 1024, height 768
Machine reset
watchdog armed

In MAME32 under Misc. (where you enabled the error log) can you please uncheck "user pre-0.63 timing" and check the log again. It should say "using performance counter..." instead of "using RDTSC..." then.

Error log:

using performance counter for timing ... cycles/second = 1540080000
width 256, height 224 depth 16
set visible area 223-223 0-0
set visible area -16-207 0-255
Physical width 800, height 600
Machine reset

and the zwackery inp with those horrible default controls!!!