Mike_da_Spike

Odd, your log file shows a good start till end. Are you sure this is the logfile during the crash ?

can this be added/linked/merged to https://forums.gameex.com/forums/topic/14139-guide-how-to-ask-for-help/

Thanks @Draco1962! @DakotaPinball in your case : Create a custom filter in DBM, for example named "Horror". Enable the filter for all systems Enable the checkbox ‘Filter by Comment field’. In the advanced search, enter a keyword like HorrorCollection in the Comment field. Add this keyword HorrorCollection to the comment field of every table you’d like to include in the collection. For more details, check the chapter “Creating Custom Filters” in the Database Manager for PinballX User Manual.pdf

You know that DOF needs a special cabinet config for Visual Pinball? Those need to be assigned correctly in the DOF config tool. You can use the ports of the Pinscape to assign them in the DOF tool. If those are assigned correctly, it should run the correct toys during gameplay. PinballX has a special config as well. Not sure about pooper as I never installedthat one.

I I should definitly not go for . But just my opinion We've had a Steam Deck for the past couple of years, and it runs great without any issues. I don't have any experience with Bazzite, so I'm not sure if it will run smoothly. The reviews online seem pretty good. Doesn't have Tom GameEX OS yet ? 🤣

To check the Windows Event Viewer (often called eventvwr), you're essentially peeking into the system’s diary—it logs everything from software crashes to security warnings. Here's how you can open and use it: How to Open Event Viewer - Press Windows + R to open the Run dialog - Type eventvwr and hit Enter - Alternatively, you can search for "Event Viewer" in the Start menu What You Can Look For Once it's open, you'll see folders like: - Windows Logs - 🖥️ Application: App-level events (e.g. crashes, errors) - 🛡️ Security: Login attempts, account activity - ⚙️ System: System messages like driver failures, updates - Custom Views: Filtered logs based on conditions - Applications and Services Logs: More specific logs for services Tips for Navigation - Use the Date and Time column to spot recent events - Look for icons: ⚠️ means warning, ❌ is error, and ℹ️ is information - Double-click an event to see detailed info, like error codes and event

Added to the bug list

According to your log, you launched the table and allmost 1 minute late, Pbx finds the player and the rom. 3 seconds after that, the exit press is registered and pbx is within 8 sec to the wheel again. That's a total of minute and 40, from launch to end. I'm a really lousy player, but my games take longer than 1.20 minutes.🫣 Maybe lowering your 30 seconds of waits in settings would reduce the time, but I'm not sure.

In your example, it looks like that PinbalX starts creating your backglass, dmd and topper around 9 seconds after you pressed esc. 17:25:44.97 6/27/2025: C:\Visual Pinball\VPinballX.exe -play "C:\Visual Pinball\Tables\bad cats_vpw_v2.03.vpx" -minimized 17:26:49.11 6/27/2025: Visual Pinball Player Foreground 17:26:49.11 6/27/2025: Visual Pinball Player window foreground: 64 17:26:49.80 6/27/2025: Found PinMAME ROM: bcats_l5 17:26:52.34 6/27/2025: Exit System Control Pressed 17:26:52.91 6/27/2025: Found Visual Pinball editor window 17:26:53.51 6/27/2025: Process Closed 17:27:04.07 6/27/2025: Getting high score 17:27:04.27 6/27/2025: Writing high score 17:27:04.41 6/27/2025: Created DirectX BackGlass Window 17:27:04.43 6/27/2025: Created DirectX DMD Window 17:27:04.44 6/27/2025: Created DirectX Topper Window The log does not display when the playfield with the wheel is visible., is your experience that it takes 22 seconds? Did you changed any media ? Could be audio, media or (animated) images that is causing this. Just for testing, try to remove (or rename) the media files you are using for this table and try again.

Version 25.06.28 is just released Thanks to our bug hunter @robertms who identified a problem within an hour of the previous release, so we still couldn't enjoy from our summer break When using the "select File" button and double a file, it could result in an unhandled exception (odd, because we handle all the exceptions) But this is fixed in this release Another thing that our own CEO @scutters noticed was that MegaLinks gave an error : During to investigation Scutters found this is an issue that was introduced in the last couple of months with the API. Although the workarounds that people suggested on Internet didn't work with DBM. But we found another fix/workaround. in the Settings for Mega (click settings -> Mega folders tab), we added Email and password to provide access to MEGA Similar to GameEX FTP, you can enter your MEGA email address and password (a subscription is free at https://mega.nz/register), and MEGA should function properly again. Big thanks to @robertms to identify a bug within an hour ! Hereby we give you the Bug Hunter Trophy ! Also a big thanks to @scutters for noticing that MEGA was broke and found a quick solution ! And with great pride, I present this well-earned trophy to my good friend, trusted companion, and fellow developer of DBM!

This issues was already on the bullish https://forums.gameex.com/forums/topic/27935-bugs-tracking-thread/

One happy family!

Version 25.06.25 is just released This version tackles a handful of pesky bugs and introduces a few subtle improvements, but behind the scenes, it was a serious coding workout. To kick things off with something you won’t notice: @scutters and I spent a lot of time cleaning up the performance mess we lovingly called our “spaghetti release.” The codebase is over five years old, and it took quite a bit of unwiring, but the result? Smoother performance and a foundation that's easier for us to build on. There was still one beast of a function left. It touched a lot of buttons, which made it too risky to touch back in the March release… but we’ve finally tamed it. Ideally, you won’t notice a thing, which, in this case, is a good thing. Under the hood, though, it’s now way more readable and easier to maintain, especially if we want to make changes to the front page in the future. So what will you actually notice in this release? Let’s start with something that always bugged me: I never liked how, when using the keyboard to tab around, the buttons would get that default square highlight , and making the screen larger, the square lines didn't resize as well : When a window popped up with a question, it was difficult to determine which button was selected. In this version we made the square a bit smaller and 'dotted' Small is harder to see : but bigger, it is better to see : We also changed the color to a lighter shade, making it easier to see when the button is focused. Another small change on the surface, but a huge overhaul in the code, is how we handle the log file. Behind the scenes, we’ve completely restructured the logging system. While it might not be obvious to most users, this is a big win for us developers. We were logging a lot of information, but it was tough to pinpoint exactly where an error originated. So… we rolled up our sleeves and rewrote every single logging line, all 1,853 of them! That includes informational messages, warnings, debug messages, and errors. The Action Log output still looks the same, but now the full log file has been cleaned up and made Excel-friendly. It’s delimited by " : " (so 'space, colon, space' without the double quotes) and super easy to import for troubleshooting. The structure is simple: datetime : log type : function : message Messages that also appear in the Action Log are now clearly marked with an “ACTIONLOG -” prefix, and the “function” can refer to either the function name in DBBM or, occasionally, a log type. It might sound a bit confusing at first, but in practice, it's way easier for us to diagnose issues and improve things going forward. but in your favourite spreadsheet program it can look like this : To make the log file more accessible, the file path shown at the top of the Action Log is now clickable. If your system is set to open .txt files with a default text editor, clicking the link will open the log file directly in your favorite editor. We also fixed a handful of bug's. Special thanks to @scutters for his contribution and hard work to get this release to you again. I hope you enjoy it. for now, we take a long summer holiday break.

Apologies, that was my mistake. The section I posted was merely from the GitHub instructions on running from the command line and does not include the variables used in PinballLX. This is what I have: I use an INI file to configure different systems with slightly varying settings, such as for Kinect and VR. As I mentioned, it is not a fault and will not change anything, but perhaps in the near future, the parameters you use may become deprecated. Thank you. Please also capture a screenshot of your VPX video and graphic settings, as I am interested in knowing the configurations.

DBM uses the launch table option of pinballx. So is actually launches with pinbalkx. Can you launch the table from dbm and if successfully post your log ? Maybe that will help tom to identify the issue

I downloaded the table and added to my (test) system It launched without any issues the only difference is, I use PinMame 3.6.0.1227 Edit: updated to pinmame 3.7.0.46 (it's a pre-release with some fixes for roms) but still launching correctly Edit2: Also played Beat the clock and launches correctly fine and exiting) So not sure whats gogin on. Pretty curious if PBX is hung at the moment log.txt

Although it should be backwards compatible, the official commandline paramter to launch a game is : -Play [filename] you still use /play -[filename] Is PBX in a hang state at the moment ? Is the table loaded if you alt-tab to it ?

Just a fyi : Launch Uncheck the plugins you want to disable and click Exit.

Not sure where you downloaded the PinballX version, but it's running at least 400 (!) versions behind And the log is from a w7 version and thought you where talking about w10 and created on 25-05-2025

Sorry to also ask, but what firmware do you use for your ZeDMD? I see there are not of new firmware which uses newer drivers as well. And are you using zedmd via use or wifi ? Normal 128x32 or HD 256x64 ? Provide the info including the logs for Tomand he is able to help

If you have any questions, please let use know !

The documentation is enclosed in the PinbalLX installation as well : Adding tables easily to PinballX, can also be accomplished with the external tool Database Manager

Which realDMD do you have ? And about DOF. Is that happening when you launch the table again ? Looks like table is launched, but it cannot fi d the player to bring to front. What's the rest of your setup ? I mean, do you installed mjr latest 64 bit DOF and use his latest pinballx plugin as well ? I also see that you run. Doflinx at startup. Is that latest version as well ? I only launch doflinx when system is needing it, but that's just me.

No not a focus. But I also can confirm that KB5058499 is causing the issue. It is strange that when a startup video is added, the ESC key allows skipping the video, but once the playfield and wheel load, the ESC key ceases to function. I do not see any indication of running as an administrator or having a touchscreen in my log. Nothing in eventlog as well log.txt

Good catch @scutters! https://support.microsoft.com/en-us/topic/may-28-2025-kb5058499-os-build-26100-4202-preview-d4c2f1ee-8138-4038-b705-546945076f92 It's not a security patch, but just a "fix patch" And some fixes that should fix keyboard focus Maybe pbx is out of focus ? I say: blame MS ! (but maybe @Tom Speirs can think of something to fix it)