Mike_da_Spike

@Tom Speirs are plugins always running in a 32 bit environment? The dof plugin uses the com object of DOF, but 64 bit com object errors to initialize.

To be honest, I'm not certain. For any issues with Pinup Player, you should contact Nailbuster. He's active on Discord, so perhaps sending him a direct message would be helpful. Sorry I cannot help you

Again, you didn't attached this one . But I did register the 64 bit on my machine and got the same results. I made the following steps, let me know if this works. To fix DOF in PinballX after upgrading to DOF64 : If your DOF plugin shows that it is pointing to a 64 bit folder, DOF will not work on PinballX Your PinballX logfile will show : 06:51:34.19 17-5-2024: Loaded Plugin:"DirectOutput PinballX Plugin" Version 1.5 By Swisslizard (modified by Mike da Spike) 06:51:34.39 17-5-2024: PlugIn Did not initialize. Disabling PlugIn Go to your 32 bit DOF folder and run RegisterDirectOutputComObject.exe (DO NOT RUN THE INSTALLER FROM THE 64BIT FOLDER !) (confirm if you have UAC enabled) Check if your DOF plugin is now showing the path to the 32 bit folder Additional steps if plugin still shows it is using the 64 bit path If your plugin still shows that the DOF plugin is pointing to the wrong location, open your registry editor as admin navigate to : \HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{A23BFDBC-9A8A-46C0-8672-60F23D54FFB6}\InprocServer32 First check if the codebase is the correct location (this should do the RegisterDirectOutputComObject.exe) if you got 2 hives under the InprocServer32 remove the hive with has the codebase pointing to the 64 bit The DOF plugin should point now to 32 bit Launching PinballX, the DOF should work and you should see that the PinballX log.txt will shows : 07:17:35.03 17-5-2024: Loaded Plugin:"DirectOutput PinballX Plugin" Version 1.5 By Swisslizard (modified by Mike da Spike) 07:17:38.99 17-5-2024: PlugIn: "DirectOutput PinballX Plugin" Initialized OK

No, you are on the wrong way. Don't delete anything from registry or re install pinballx. You will get into more troubles Just follow my long post which I posted my moning

Pinballx plugin is using the com+ object. Vpx uses a redirection from b2sserver to the dof folder without using the registrated object. Although the pinballx plugin says it is fine, during launch of Pinballx it cannot load the plugin. My assumption is that you didnt put the config files for pinballx in the config folder

The DOF plugin shows in the pinballX .log that it canot be initialized : 13:48:26.09 5/15/2024: Loaded Plugin:"DirectOutput PinballX Plugin" Version 1 By Swisslizard 13:48:26.43 5/15/2024: PlugIn Did not initialize. Disabling PlugIn You didn't attached the "PinballX DirectOutput Plugin.log" from the plugin folder. It could give 1 of the following errors : Could not find the DirectOutput.ComObject. Please check if the DirectOutputComObject is registered. Could not create a instance of the DirectOutput framework. So not sure which error you get, but maybe one of your dof registartions (32 or 64 bit) is not fine. Running RegisterDirectOutputComObject.exe as admin should fix it in your directoutput log I see the following : 2024.05.14 21:29:25.987 No cabinet config file loaded. Will use AutoConfig. Just to be sure : in your DOF64\config (but also in your dof\config) you must have xml called GlobalConfig_PinballX.xml This config should have valid paths and settings. Here's my example : <?xml version="1.0" encoding="utf-8"?> <!--Global configuration for the DirectOutput framework.--> <!--Saved by DirectOutput Version 3.1.6863.36690: 2018-12-15 15-17-15--> <GlobalConfig> <LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs> <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs> <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs> <IniFilesPath>C:\Pinball\DirectOutput</IniFilesPath> <CabinetConfigFilePattern>C:\Pinball\DirectOutput\config\cabinetPBX.xml</CabinetConfigFilePattern> <TableConfigFilePatterns /> <EnableLogging>true</EnableLogging> <ClearLogOnSessionStart>true</ClearLogOnSessionStart> <LogFilePattern>.\DirectOutputPBX.log</LogFilePattern> </GlobalConfig> The logFilePattern can be changed, so it will only create a DOF log for PBX. I hope this info will help you to get it to work again

Set in pinballx to hide the startup command. That should avoid it

If you have a kl25z controller, you can configure a button as a 'shift' button and configure it as combo buttons (create new buttons or keyboard presses). I can now handle a lot of extra buttons (including buy-in ball, vr up and down and recenter, 1 coin and 2 coins etc)

Yes please. Log.txt from pinballx, pinballx.ini, your dof log file from the plugins directory and check dor dof.log from the dof directory

You have set UseB2S=True in your setup, which means it will display the B2S file from VPX. Videos and image creations (and their display) will be ignored. You can use DBM to check if the media is fine, and it will give a message when using B2S. Set this to NO

Wow. Nais !

I have a question for you. Are you having two front ends for your system, or is it a coincidence that someone else is using your name? https://vpuniverse.com/forums/topic/10299-vpx-gameplay-keys-not-working-when-launching-from-pinup-popper/

You can still use The Pinball Arcade, but I don't like the physics and graphics. I think most tables are now in Visual Pinball and it plays much better (and looks good). And VPX launches pretty quick (an average game in 12 seconds). But that's just my opinion. You can still have a system with TPA and use the Pinball Arcade launcher.

Yes, I use it in my arcade cabinet as well, or do you have an arcade/pinball combined cabinet ? A long time ago, I used TPA. I remember having issues with the freecammod because it required the correct version of TPA (and I always updated that one). I use the original Steam version since I purchased all the tables years ago. These are my TPA settings with the TPA loader (although I have disabled it): The parameters are: -arcooda -table [TABLEFILE] (it's possible that -arcooda can be omitted, but I'm not certain). A newer and better method is to use PinballArcadeLoader. The parameters are simply the executable file in the correct TPA Steam folder and the table name. Refer to my example for guidance: Are you referring to the window that displays the table information? The cursor should be focused on the button, and you can press launch (or start) to close it. Once you have played the table, this window will not appear again. I have never been able to locate where this setting is stored. I hope this helps

No, no,no. Please read one of my first posts , answer all my questions and check all your dmddevice.log's That would be a better Idea than reinstalling (older) stuff

The batch file is utilized by PinballX when accessing the settings.exe to launch PinballX during the Windows setup process. Its function is to copy the batch file to the user's 'run' explorer. I have personally developed a custom batch file that executes upon Windows logon, without employing or substituting the shell. There is no necessity to execute PinballX with administrative privileges. All operations can be performed as a standard user. Furthermore, I find the usage of JoyToKey undesirable, particularly considering that all the features I require can be accessed using a joystick.

You confuse me with your question. Not really sure what you try to accomplish. Did you check pinballx documentation "table loading media mode"? I thought it was on page 4-5 Edit: ah I got it. Yes, loading.gif should be an overlay to your pf images . Check the folder if your playfield images are not black. If you use playfield videos, it will cteate 1 time a pf image from it, but thought it should not haave a black frame on frame 0. Does that make sense ?

I do not utilize the instant sheller, but is it not possible to direct it to pinballx.exe? I still desire to employ the explorer as a shell, thereby enabling me to automatically log in and utilize my batch file to configure the screens, initiate doflinx and pinvol, and solely ascertain the execution of a single instance of pinballx.exe. It's not as nice as running instant sheller, but it's good enough for me. Perhaps a more experienced person can provide you with additional information on the topic of instant sheller.

@Benoit33 Whats the status of your issue ? Still having issues ?

Installing pinballx from old to newer version would not break database files and media. Just follow the instructions from yhe manual and you are good. If I have time, I will test your issues on my cabinet as well. Did you upgrade FP as well ? As Terry did a lot of changes on fp as well.

As a Dutch person I am often seen as stubborn (don't reply to this @scutters 😋,) but I suspect that your problem lies in dmdext(dmddevice.dll). As I asked before, is this a new problem? Or have you recently put the zedmd in your system?

Yes it has native support, and freezy updated the driver 2 weeks ago

Did this ever worked ? Do you have a dmddevice.log from pinballx folder as well? My assumption: Pinballx starts and uses dmddevice.dll. from pinballx log I see it uses the dmddevice.dll, but as you didn't provide this log, I assume it worked. Pinballx starts a game. It give the command to shutdown the dmd l, but the serumdll didn't do that (should be in the dmddevice.log from pinballx if it shutsdown). Visual Pinball starts but the Dmd will be initialized from a 2nd instant of dmddevice.dll (from the visual pinball folder). This logs shows it doesn't find de ZeDMD When visual pinball closes, it returns to pinballx , but crashes the mainform as it cannot access the dmd corre tly. Just an assumption, but almost the same as I had in previous version of dmddevice.dll for my pindmdv3 The only difference was that it showed in the dmddevice.log from visual pinball that the dmd gave an access denied. That's why I asked : did this worked before as freezy updated recently his dmddevice.dll (or dmdext) from 2.2.1 to 2.2.2 and the big upfldate was As pinballx works fine for me with dmdext for my real dmdpinv3, my assumption is that dmddevice.dll doesn't handle correctly the close command (or whatever it sends to stop the dmd) and during the 2nd instance it doesn't access your zedmd

I believe I understand the nature of your issue, and I may have experienced a similar problem with my pindmdv3 in the past. Could you please provide all of the files I have requested and answer the questions I have asked?

Please provide logs as described in is dll 2.2.2 freezy's latest dll ? If so, provide dmddevice.log from pinballx and from your visual pinballx directory. A wild guess would say, that it won't release the dmd corre tly. Did this work before ?