Wizard

Strange as MFME v19 doesn't use that runtime anymore

UK Fruit machines don't have Marquees in the traditional sense.

I have now added the output to the diag window in v20. On a real machine it sends this to a IR led so the data could be collected by a handheld device.

I have no idea why it does that, it's not my program so there is nothing I can do about it. v20 has an updater that I wrote myself, so hopefully these issues will be gone in future.

That issue has been reported before by a few people, unfortunately no solution has been found so far.

That's what I said isn't it?

Yes it can't magic them up out of thin air, nor would you be able to visit the forums to get them, so it's a moot point.

As there are no RAM files provided, it won't be able to set up the ccTalk devices It only looks on the internet if the required file is not found in the local folder.

Erm buy a license? Not every program on the internet is free. This one is time limited although it will still work after 40 days, it just has a nag screen.

Lamp test always starts in Flash Mode, you can press other buttons and it will change to a sequential test. You have made the layout too large for your monitor, hence you now get scroll bars. You can change the size by right clicking on the background and entering the Window Size option and selecting something that will fit your monitor, then the scroll bars will disappear,

Make sure you have Showtime set to enabled in config

Normally you tell the programmer exactly what the chip is.

You use the PAC Drive section in the MFME config screen.

It should be creating a file called "gamesV19.0.db" in your Main Game Folder, it uses that to populate the game manager list on startup. I don't recommend having the games folder in the same directory as MFME itself. It might be that MFME doesn't have permission to create the DB file in the program files folder?

The original idea was to be able to issue an update every time a bug was fixed and rather than creating a new download package and submitting it etc just provide an update. But due to the limitations of the original Updater, this proved impossible. WIth the new updater I can issue an update anytime without affecting the release number ( unless I have to ),, and MFME can be set to check for updates on Start Up. I don't want to clog up the Download section with dozens of updates. It's also just easier for me tbh and has proved useful when updating the beta version virtually every day.

If he can access DIF, he can access the updates. It's only happening on two peoples PCs, so it must be an issue with their setup somehow.

That is the plan. The EM editor/Simulator is used for development and creation of electromechanical machines like Pool Play/Super Number Gambler/Hot Dog/Ten Up etc There aren't that many releases of those due to the amount of work needed to create them as the whole schematic has be entered into MFME component by component and wire by wire.

I have no idea then, it's not code that I wrote so I can'r debug it. You'll have to wait for v20 which has a new Updater that I wrote myself.

Someone else had this issue and we never got to the bottom of it. Have you tried running it as Administrator? ( Update.exe that is )

If the stop sound plays while the reel is still spinning then it's probably because your PC is too slow.

Don't need to open the door, just click refill and it should enter the refill menu and then you can enter coins to refill it, the refill is a manual process. Not to be confused with Top Up

It could but you don't necessarily know it's a coin mech switch unless the Coin Note or Effect are set correctly

7, 8 or 9 or click on the note values above the Note Acceptor, if it does nothing you probably need to do a refill ( No Notes lamp lit ) Also seems like you have coin/note effects disabled otherwise you would hear the note going in and then being rejected

Actually the error is caused by not having Lockout checked on the bezel to disable the coin mech when the light goes out:

I can get it to work, but all these boards ( apart from the PACdrive ) aren't quick enough to keep up with the flashing lamps in MFME so aren't suitable tbh The main issue is that you can't write to all output ports at the same time, so there is always lag. The PACdrive allows you to write to all 16 outputs in one message whereas the others only allow 8 outputs, so need 12 seperate messages to update all 96 outputs ( UltimateIO ) It's a shame they behave this way as they are very good hardware wise.