Erzak

I just did, thanks for reminding me

Yep, I think that was the issue. I found that by default, PBX is being launched by a .bat file when Windows starts up. I changed that to a shortcut to the .exe itself, and made it run in Admin mode, and so far things are working better. Seems that if PBX is running as admin, anything it calls is as well?

Still seeing some intermittent issues. I've tried a couple of methods of launching dmdext from PBX. First, I created a .bat file that contains: "C:\Visual Pinball\VPinMAME\dmdext" mirror --source=pinballfx3 --no-virtual --quit-when-done That didn't seem to work, so I tried putting the path, command, and arguments into PBX like this: This sometimes works, but not always. It always seems to work for the couple of FX3-original tables, and sometimes works for FX3 Williams tables. Wondering if it has something to do with permissions? I thought I'd try the --fx3-legacy flag, but that didn't work at all, though I left all the other arguments in, perhaps that was incorrect?

The latest update did the trick! Thanks for pointing me to it. Now I just need to figure out how to get rid of the virtual DMD that FX3 puts on the playfield...

Should the information be shown in the command window, or in the virtual DMD window? I do not have a Teensy board. The latest Freezy release I see on github is from October 2018, v 1.7.3 (though the archive is labeled 1.7.2) Is there a newer release elsewhere?

When you say to check the dmdext screen, do you mean the virtual DMD that is on the playfield monitor? If so, I think, yes, there was stuff there. But nothing on the the real DMD. What do you mean by teensy board in my cab?

I'm having some issues getting my DMD to work with Pinball FX3 in my cabinet. I have a PinDMD3, I've got the latest Freezy DMDEXT (1.7.3) installed in my VpinMAME directory, and everything works fine for PinballX, VPX, and Future Pinball. I have tried the following: 1) Open a cmd window in c:\visual pinball\vpinmame and type 'dmdext test'. Gives me a test pattern both on the PinDMD3 and a virtual DMD on the playfield monitor. 2) Open a cmd window in c:\visual pinball\vpinmame and type dmdext mirror --source=pinballfx3 --no-virtual [enter]. Gives an error that need to run in administrative mode 3) Open a cmd window with admin privlidges in c:\visual pinball\vpinmame and type dmdext mirror --source=pinballfx3 --no-virtual [enter], then start Pinball FX3 and launch a game. Nothing appears on the PinDMD3, I see the virtual DMD that is coming from FX3, both one on the playfield and one that I've moved to the bottom of the backglass monitor. 4) Did some more reading and set the coordinates of the FX3 DMD screen back to 0,0, tried 3) again, still nothing on the PinDMD3 In FX3, I do have DMD repositioning turned on, and the dimensions are set to 780x204. I read somewhere, either here, or another site that the FX3 DMD should be somewhere off-screen, and maybe my dimensions are incorrect. Reading thru the command line options, I see the '-d' option, do I need to include '-d pindmdv3' in the commmand? I've tried it with both a Zen original table and a couple of the Williams tables, since I read that there were some issues with Williams tables, though I believe I read that those got fixed in the latest Freezy release. Any help or suggestions are appreciated. Thanks!

Yep! I compared my settings with what I read here last night and realized that my Stick Y axis wasn't inverted. That did the trick. Though something in the plunger settings must be off, as I can't launch a ball with much power using it (in FX3, okay in VPX). Will have to see if there are some adjustments in X360CE for that, or if I have to go into the VirtuaPin settings. So I have my start button mapped to 'A', flippers are mapped, launch button seems to be good (can't remember which VirtuaPin button it's mapped to) but it works for selecting things like initials when entering high scores. Guessing I should map the left stick to nudge/tilt? And then I have the credit button and the big button under the cabinet that is used to exit a game in PBX/VPX, so maybe that would be the equivalent of 'escape'? Seems like the other buttons that I see pop up on the screen are 'X' and then anything to do with the 'wizard' or changing views.

Does anyone have recommended settings/configuration for using a VirtuaPin controller with Pinball FX3? I am using X360CE to map the buttons to the Xbox controller in FX3, and have gotten flippers, start, and ball launch button to work okay, but can't get the plunger to do anything. I have tried mapping the plunger to the right stick, and then select RS in the FX3 options, but it doesn't work. Will try to attach image of my X360CE settings. Any suggestions are welcome. Thanks!

Thru some trial and error, I got it working. I used the batch file lines that Scutters posted. They didn't work when trying it from a command line, unless I right-clicked the .bat file and selected 'run as admin'. Once I got it working from a command line, tried using the 'launchafter' option and it didn't work, but then I tried right-clicking on pinballx.exe and setting it to run as admin, and then the batch file works from PBX. Right now I have it so that the .bat file runs after every VPX table exits, I suppose I could group the UltraDMD tables into an alternative .exe group, but probably no harm in that .bat file running everytime, I don't notice the couple of ms it takes. The only other nagging issue that I'm seeing (sometimes) is when launching Diablo form PBX, occasionally the table doesn't have focus, so I have to click the mouse on the playfield before I can start a game or anything. But it doesn't always do this. I know I read about this in a thread, either here or maybe on vpforums, will have to see if I can find that post again. Thanks again for the help!

Thanks all for the replies and suggestions. I will give these things a try this weekend, if not before. Really wish I'd stuck with Win7, since everything worked perfectly there. But when you're sold a system with a bogus product key and MS doesn't sell Win7 keys anymore, what other options are there?

I tried something like that and it didn't seem to do anything. Could you possibly post in here what is in your batch file?

I'm having trouble with PBX and VPX games that use UltraDMD. My cabinet OS was recently updated from Win7 to Win10, and the problems have started since the update. I have a two monitor + PinDMD3 cabinet. If I launch a UltraDMD table (Diablo, for example) from PinballX, the table launches and plays fine. When I push the button to go back to PBX, the backglass monitor stays on the Diablo backglass display, and the PinDMD continues to show whatever was last displayed when the table was active. If I then try to launch another table (non-ultraDMD) I get the "PinDMD3 not found error". The backglass display ususally resolves itself when starting another table, but it doesn't change if I cycle thru the tables in my collection in PBX. If I open Task Manager, I see that the UltraDMD process is still running. Killing it manually and re-starting PBX solves the problem, until I launch another UltraDMD table. If I start VPX by itself and launch the same table manually, then when I exit the table, it quits the backglass and DMD, and those processes are no longer running if I look in Task Manager. This makes me think that PBX is not cleanly quitting VPX when you exit a table. Is there anyway to change this? Thanks, Eric

I downloaded the latest version of PBX and installed the 32 bit version, but it won't run. Do I need to uninstall the 64 bit version first? If I do, do I need to back-up my .in or .XML files or will they be left alone during the uninstall process?

Hi folks, I have some questions about how to set-up things in PinballX. I have a 3 screen set-up: playfield and backglass are standard monitors, DMD is a PinDMD3. When I launch a game from VPX or VP9, the DMD works (after I configure VPinMame to use the external DMD). If I put a .db2s file in the tables directory, it shows up when I play the table. So that part I have figured out, and it makes sense. Now, when using PinballX, I am getting somewhat confused. I have 10 VP tables loaded into PinballX. When I aml scrolling thru the tables, two of them (Attack From Mars and Austin Powers) display the table-specific videos on the DMD, and if I look in C:\PinballX\Media\Visual Pinball\Real DMD Color Videos, I see those two .mp4 files. The other tables show the default PinballX color video. There are some videos and images for other tables in the C:\PinballX\Media\Visual Pinball\DMD Images and C:\PinballX\Media\Visual Pinball\DMD Videos directories, do those not show up because these files would only be used if the DMD was being displayed on an LCD monitor? For the two tables that have real DMD color videos, I have the 'Hide DMD' box unchecked in Game List Manager,is that correct? I know that if I don't check it for a game that doesn't have an associated video, I then get the "pindmd v3 not found" error message when I launch the game thru PBX. Or should I have that checked for all tables? But if so, then what is that option for? However, when PBX is in attract mode, I will sometimes see the DMD displaying stuff for Medieval Madness (which I have installed) but do not have a DMD video file for. And it doesn't necessarily play when Medieval Madness is the table being displayed. Where is that coming from? Is that PinMame doing something? I know there is an option to use Regarding backglasses, should the 'Hide backglass' box be checked in general? Doesn't seem like the 'Use B2S server' option is doing anything. I think that the backglass images/videos are being taken from the C:\PinballX\Media\Visual Pinball\Backglass Images and C:\PinballX\Media\Visual Pinball\Backglass Videos directories. What does the 'Import ROM' function do? I've tried that, but when I go check my .xml file, all tables still say <rom></rom>, as if I didn't make a selection, or it didn't save the information in the xml file. I thought I read somewhere that if you point to the ROM and have 'Use PinMame in frontend' on it will run the ROM image/video on the DMD, but I haven't gotten that to work. I did install the 64-bit version, haven't tried the 32-bit version to see if that fixes (or changes) things. Since I see there is a new version out (3.23), so perhaps I'll try that tonight and install the 32-bit version, assuming that won't mess things up to go from 64-bit to 32-bit. Sorry for all the quesions. I have read thru about ~1/3 of the posts in this forum, and while I did find some good information, I am still confused. I was hoping to find a newbie set-up guide, but did not. I did find 'PinballX_S2F_Documentation rev 1.3.pdf' but it's from an older version of PBX, and some of the newer features aren't covered at all, and others are just glossed over. Thanks, Eric