Mike_da_Spike

Your not the only one, but we need to check what's going on. Can you reproduce your issue and post the log file of databasemanage ? What OS are you using ? As we just move to a complete new dotnet version, can you try the previous version ? The part for ftp access is the same, but just wanted to know if that is working , as all works from scutters and me. In the program we connect with TLS to make it more secure. Is TLS enabled or disabled within your OS ? Sorry for all the questions, but just want to figure out why this isn't working for you, but works for others

I thought that game manager uses http to connect. We connect directly to the ftp server.

@Topspliff discovered the first "bug" without realizing it. He's having trouble accessing the FTP server, and I've observed that the icons for revealing the password (the eye symbol) in the settings dialog are not displayed. Hovering over the area reveals the password, but the icons (for visibility/invisibility in both dark and light themes) are missing. We will wait here for his issue to be addressed. EDIT: You mentioned receiving a 504 error. Typically, a 504 error indicates a timeout when connecting to the remote server (for instance, see 'What is a 504 Gateway Timeout error, and how to fix it? - SiteGround KB). In our program, we have set the timeout limit to 15 seconds. Could you try connecting to the FTP server using a program like FileZilla? If that works, does it take longer to log in to the server?

Version 24.06.07.0 has been released. This major update has kept @scutters and myself occupied for an extended period. Last year, we upgraded DBM from the .NET Framework 4.0 to 4.8, which only caused us minor headaches. I had been suggesting to @scutters that we should upgrade to .NET, but the migration path seemed too extensive. However, last month we began some tests and migrated our 'legacy' .NET Framework code to .NET Core code. Even though Microsoft offers a helpful migration assistant, it wasn't sufficient for our needs. We had to change a significant amount of code and forms, and acquire new NuGet packages to get everything working again. But now, the final result is here! We have successfully built a version based on .NET 8! What does this mean for you as a user? The application launches faster, and overall performance should be improved. Moreover, .NET 8 includes security enhancements, such as improved memory safety and mitigations against common vulnerabilities. With .NET 8's cross-platform compatibility, we may be able to support new platforms if PinballX does as well. We have also restructured the installation folder: - The INI file has been moved to the config folder. - Additional files have been placed into the resources folder. - PDFs are now located in the documentation folder. - The number of DLLs in the parent directory has been reduced. As always, a big thanks to @scutters. Without his help, we would never have been at this point (even though he was hesitant to take this path and upgrade to .NET 8). Thanks, mate, buddy, friend, for everything!

You version is 200 updates behind. Probably your gpu isnt powerful enough to run the full version.

As you didn't provide any settings or log file (and yiu still have an old bersion) it is hard to. Say. My assumption is that you use visual pinball as you want to add credits. Check the visual pinball keymappings and assign your credits button in there. Depend on the table (rom or not rom based : If you are afraid to update, make a backup of your harddrive (or make a backup/copy of your complete pinballx folder) before upgrading it. You can check the PinbalLX documentation as wel. Upgrade is described (and also to fall back to a previous version):

I apologize, but I cannot think of anything at the moment. The plugin utilizes the COM object, and the PinballX plugin manager is employing the plugin which is currently using the COM object. However, starting it through PinballX is failing for some unknown reason. There seems to be a persistent issue with the 64-bit and 32-bit versions of DOF on your system. Yet, a search of the registry reveals no references, which is peculiar. I would like to assist you, but I am unable to do so right now. I am not certain if starting from scratch will be beneficial.

Yes. Thanks. Pinballx log shows that it cannot initilaize. And the pluging log showsit cannot find the comobject. This is odd as you register the 32 bit and the p,ugin shows a version. But still looks like the 32 bit isnt reregistered

Can you post the log.txt from the log folder and from the plugin folder the "PinballX DirectOutput Plugin.log " ?

If it doesn't work, we start all over with posting the new leggings. So the pinballx log.txt and the plugin log from the plugin folder. This is the point we wanted to start woth (did yiu reboot as well ?)

Hello there! The statistics plugin gathers data from PinballX and Database Manager. If you wish to view this data outside of PinballX, you will need to combine the sources. I'm not entirely sure where or how you would like to see this data, but it may be necessary to create a new program for this purpose. Alternatively, most of the information is displayed in Database Manager, with the exception of a few values. If you are using Database Manager and would like to see the missing values, please let us know and we maybe add them.

If you now run the 32 bit installer as admin, will it say successfully? And what will the registry keys shows?

Joyrider created a script yhat activates the cabinet mode each time and jump to table https://github.com/joyrider3774/PinballFXLauncher But highly preferable to use the steam

Áre the keys you send after the registartion of the 32bit application ? and are these only found ? Because this looks like only the object is there only not associated with any DLL (so ready to go for 32 bit)

The -applaunch parameter is the parameters of Steam not of EPIC. As Stated in the pinballx documentation, pinballx will not magicly fix an issue or launch a table. You need to have it working on the command prompt (as I mentioned in previous post) I searched on the Zen site, and the parameters for -table and -gamemode should work, bit the parameter for epic you need to find from epic See https://www.pinballfx.com/?page_id=7754 I think you are with pic 1 on the correct way, but need replace -applaunch (and number) for something that epic will do. I thought that the shortcut on the desktop that is created by epic contains the correct parameters to launch the game from the epiclauncher

@nicofab18 Are you playing games with me? You altered the image again (the colon is removed and you put more behind), but it still appears to be photoshopped. Instead of modifying the image, could you please answer my question? @joyrider3774 yiu have epic pinball fx. Is the direct launch working and same parameters as for steam ? I can't believe that the parameters like -appid is the same as steam

This forum is focused off the front-end programs of GameEx (GameEx/PinballX & Touch-Play) , not gaming tables. The front end doesn't demand extensive CPU/GPU resources, but it won't run on very outdated hardware. If the front-end performance is lagging, you might consider using the Lite versions. When installing on Windows XP or Vista, you will encounter an option to select the Lite version. Tables : The frontend supports a variety of systems, depending on the hardware capabilities. Zen Pinball FX2 and FX3 may be playable with reduced settings. However, Zen Pinball FX should not be attempted on older hardware as it requires a newer GPU. The Pinball Arcade is also playable, and the resolution can be lowered if the gameplay is not smooth. Visual Pinball 9 is compatible as well. Most tables created for Visual Pinball 10 (up to version 10.7.4) should run smoothly. Tables created in version 10.8 or newer generally demand a more powerful CPU and GPU. I hope this helps (and that you can translate it)

It appears that the previous images may have been altered, as certain fonts seem to be different. In the path, there is a colon (:) before "epic games". That's definitely not correct As stated in the documentation, please open a command prompt, paste the '<path>\<executable> <parameters>', and if that launches successfully, then everything is in order. If it does not work, kindly provide your log.txt and pinballx.ini files (after reproducing the issue). You mentioned that the issue occurred after the update. This is unusual, as the update should not have affected the launch process from PinballX or altered the start parameters.

I do not use the Epic version of the software, but use the Steam version. Could you please provide more details about the issue you are encountering? The description "encounter problems" is too vague to provide any meaningful assistance. Was Epic able to launch the table directly, or are you still using the launcher ? Please provide the pinballx log.txt file that is created when the issue occurs, as well as your settings file. This information would be greatly appreciated in order to better understand and resolve the problem.

@Benoit33 did you ever figured out why your ZeDMD issue ? if so, it would be nice to add the solution jere

Indeed, I have a folder named "c:\pinball" which serves as a junction point to my "d:\" partition. All software related to pinball, including Steam, is stored within this folder. I regularly perform a system state backup of my "c:\" partition and a separate file backup of my "d:\" drive. From a DOF perspective, the location of the folder should not impact its functionality.

Strange part is, You have 2 versions in your registry pointing to C:\DirectOutput\ 3.1.7776.42174 and 3.1.8440.34790 My 64 bit is 3.1.8440.34790 and 32 bit is 3.1.7776.42174 Anyway, lets try this. 1) Run the following reg file (and confirm to install) VPA35BKSOR_fix.reg 2) Go to your 32bit directory (C:\\DirectOutput) and run RegisterDirectOutputComObject.exe DO NOT RUN THE 64BIT INSTALLER ! 3) Check your plugin, if it got a version number and pointing to the correct 32 bit path Still not correct ? 1) Run the regfile again 2) open registry editor 3) Search for : {A23BFDBC-9A8A-46C0-8672-60F23D54FFB6} The value should only be twice in the following keys : HKEY_CLASSES_ROOT\DirectOutput.ComObject\CLSID HKEY_LOCAL_MACHINE\SOFTWARE\Classes\DirectOutput.ComObject\CLSID 4) If found in any other key, please export the key, and serach furhter until you reach end of the file. Please report all the Reg Files that you found I hope we will get closer to your working DOF

Please export the 2 following keys as a reg file (2 reg files is fine as well) HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{A23BFDBC-9A8A-46C0-8672-60F23D54FFB6} HKEY_CURRENT_USER\SOFTWARE\Classes\WOW6432Node\CLSID\{A23BFDBC-9A8A-46C0-8672-60F23D54FFB6}\ I will check tomorrow and hope to give you a file that will fix it