Tom Speirs

New and improved table loading image support. Animated GIFs are supported again and there are now two modes for loading images (configured under general settings). You can use the existing loading image/video mode or the new playfield image mode. With the new mode it will either use a playfield image or take a snapshot of your playfield video. Then either use a default or one of your own animated gifs which is then overlayed and animated with a fade in. The result looks pretty slick in my opinion and this is a highly requested feature. Note that animated GIFs are now auto rotated if required and regular images at 0 degrees should be used. Note, if you have an unusually long animated GIF the number of frames may be clipped. The fade in of loading images is now done on a thread and games may load a little quicker too. There are also some blitting optimizations to avoid slow done on a UHD 4k display. Enjoy! View the full article

Also it could be that exceptions are going on and causing slow down which is what draco was saying. That could be down to a bug or the system not being able to handle your GameEx config. A fresh or separate install may determine that.

hmm. Does seem odd. GameEx should have no problems with your system specs and easily run at 60fps. Like I said I have also used the CRT driver but had no problems. Again, try not running fullscreen exclusive in GameEx (AKA Fullscreen windowed)

It should run fine in that setup. Not really sure right now. Maybe something to do with the GroovyMAME driver. Do you have LAV Codecs installed? Please be a bit more description about what is slow or a video perhaps? It does look like something is up I see the display initializing a lot in the log file. I have used GameEx with the CRT driver but on Windows 10 and had no issues. So maybe not that exactly. You could try runming GameEx fullscreen but windowed see if that help.

I refer to my first reply to this topic basically. and we will see if anyone else reports anything. Only other thing would be is if fx 3 is set to run as admin and pbx is not.

Also, do me a favour and download the older version and confirm its working. If that's the case then only I can resolve this.

Hi, sorry, you didn't make it clear an older version of PinballX worked. Which version exactly?

Your version of Pinball FX 3 looks a bit "iffy" but everything in the config looks normal.

Hi, In this scenario no, not right now, not without reencoding the videos and adding a border, although not sure how your managing to play 16:9 games on a 4:3 CRT unless it adds a border in 16:9 res.

No worries. Anyway, Im guessing steam needs the normal explorer shell to work or perhaps needs a 64 bit shell. Its never been discussed here as far as I know and like I said I don't know.

I really don't know the answer to that but have some respect buddy, we have a competing product here.

I feel the nostalgia too obviously but your really just buying a dream here and people get upset with broken dreams. Id love it if it was but this isn't Atari unfortunately and a console is just a PC.

Try setting the backglass to hide in the game manager. Also turn off the rotate for fx3. Assuming your using cabinet mode you shouldn't have that.

No worries but that's MAME for you rather than GameEx, as far as I know!

Sorry to state the obvious and not come up with a complex solution but doesn't the information screen show this? Maybe the op has it disabled?

Hey @marcocaps You reported the post for moderation rather than reply. Not a problem though. Are you all set now then?

Got to thank you for pointing me to it buddy but as for overkill, that's me in a nutshell, lol! Had you not noticed that!?

Just to let you know I updated the MAME release download to the latest a couple of days ago as it seemed to be causing a lot of confusion like this. Cheers. Tom.

Im still not sure of the exact cause and like I said I only had the issue once. Maybe MS updates helped later but 1903 certainly caused the issue. As for why its working now its because I added timeouts of 30 seconds * 5. Ive got a feeling MS added some of the enterprise shelling features to the pro edition which really is a good thing, right? Ill have a look ina VM later.

Im still trying to ascertain what the issue is but it could take over 2 minutes (with 0.91). I tested on win 10 enterprise (1903) and I got the issue you described. I then worked on the app and made 0.91 and I could no longer duplicate the problem.

Really, for three million US, I myself could get past a porotype pretty easily. Production though and how cheap you get it for sale is a different matter. I also wonder how much they paid for the name alone. Unless its a total scam, or there really dumb its probably an android device wit some over priced software development.

Thanks for hanging in there. Yeah, still a few kinds to work out. That one will need Ben. I will look at the default down button though and also the exit game escape key issue and get another release out. Cheers. Tom.

No worries. I just updated the MAME version to the latest on the site here as that seems to cause a lot of confusion. As for the controller what exactly is it? Did you try remapping the controls? It could be that the defaults are off. PS: I did get the same last run output with some other games.

If I turn off wait for exit I can get a freeze but this is expected behaviour. Do you have that turned off. It should be on for MAME. PS: Is the other version really that crappy!? lol

I cant duplicate this unfortunately. Working fine for me with latest MAME. Which video card are you using? Please run winver.exe and tell me windows version. Your last run output looks really off too. Plase just use a rehular version of MAME with default settings. Here is mine: 00:00:18.5801141: FileName: 'G:\Dropbox\Mame32\mame64.exe' 00:00:18.5801150: Arguments: 'gtmr -rompath "H:\- RESILIO -\-ROMS-\ARCADE\-MAME ROMS 0.213 -" -joystick -nowindow -skip_gameinfo -output windows' 00:00:23.5892031: System Process Has Exited. 00:00:23.8261193: Total Time Played: 0 Hours 0 Minutes 5 Seconds. Here is yours: 00:00:00.0001871: FileName: 'D:\MAME_LARGE\MAMEAutoDownload\MAME\mame64.exe' 00:00:00.0001906: Arguments: 'pc_1942 -rompath "D:\MAME_LARGE\ExceedinglyMAME\Roms" -joystick -nowindow -skip_gameinfo -output windows' 00:00:05.0162067: === Start 'mame64' Window Info === 00:00:05.0189666: Index: 1 Handle: 0x333618 Title: 'MAME: 1942 (PlayChoice-10) [pc_1942]' Class: 'MAME' IsChildWindow: False IsMainWindow: True IsWindowOwner: True IsWindowVisible: True IsForegroundWindow: True 00:00:05.0189774: Index: 2 Handle: 0x1185724 Title: 'MAMEOutput' Class: 'MAMEOutput' IsChildWindow: False IsMainWindow: False IsWindowOwner: True IsWindowVisible: False IsForegroundWindow: False 00:00:05.0189897: Index: 0 Handle: 0x202632 Title: 'D3DProxyWindow' Class: 'D3DProxyWindow' IsChildWindow: False IsMainWindow: False IsWindowOwner: False IsWindowVisible: True IsForegroundWindow: False 00:00:05.0189965: Index: 3 Handle: 0x399190 Title: 'Default IME' Class: 'IME' IsChildWindow: False IsMainWindow: False IsWindowOwner: False IsWindowVisible: False IsForegroundWindow: False 00:00:05.0190024: Index: 4 Handle: 0x6821704 Title: 'MSCTFIME UI' Class: 'MSCTFIME UI' IsChildWindow: False IsMainWindow: False IsWindowOwner: False IsWindowVisible: False IsForegroundWindow: False 00:00:05.0190085: Index: 5 Handle: 0x530352 Title: 'Default IME' Class: 'IME' IsChildWindow: False IsMainWindow: False IsWindowOwner: False IsWindowVisible: False IsForegroundWindow: False 00:00:05.0190100: === End 'mame64' Window Info === 00:00:11.0123113: Average speed: 100.00% (8 seconds) 00:00:11.1735953: System Process Has Exited. 00:00:11.3503564: Total Time Played: 0 Hours 0 Minutes 11 Seconds.