bushav

That fixed it. Thanks @Mike_da_Spikeand @scutters. My csv file was in place but it was empty of any data for some reason.

9/2/2025 11:26:27 AM : ERROR INFO : ConvertCSVtoDataTable : ACTIONLOG - Object reference not set to an instance of an object. Any help as to why I am getting this error message? I'm suspecting it has to do with the new feature to export to a excel file. I am thinking I need to create a file for it to export to? DBManagerLog.txt

It’s fine with me if you mark this topic as resolved. I think it’s a rare occurrence if you are getting out of a table immediately after launching. You are probably right about PinballX just having to sequence through my self imposed videos and settings. I really was mostly interested if anyone else had experienced a slightly different lag lately. Not wanting to beat this horse to death and tie up your time.

I'll do some more experimenting. In my experience, the game becomes active and playable, I hit the button to return to the wheel and I get no response. I continue this about every ten seconds and approximately on the third try the table disappears and PinballX wheel appears shortly therafter. I did try disabling DOF and there was no change. I did remove the loading video and there was no change. I did not remove topper and backglass videos but I can try with them removed.

done

I tried disabling my only plugin (DOF) and it did not resolve the issue. So I launch a game from PinballX, loads great but lets say I want another table instead. If I try to return to the wheel the button isn't recognized for about 30 seconds. So usually this characteristic is not noticed in normal operation. Log attached. Thanks to you guys the log is much cleaner than it was last week. I don't see any failed processes. log.txt [SETTINGS].log PinballX.ini

A recent release, sorry I don't know which, changed the "close table" command on my cab. I now have to wait about thirty seconds after launching a table before my "return to wheel" button is active. This is only noticed if you accidentally launch a table and want to quickly return to the wheel. Cound you guys see if you can replicate this on your systems please. I thought maybe it was related to the launch audio issues I was experiencing but after testing it seems unrelated. My logs are useless for this characteristic as they show no errors. But, I can submit them if you guys think this issue is isolated to my system and not affecting others.

Guys thanks for all the help. I changed my loading parameters, no change in performance. I let PinballX sit unattended for three minuites while loading Led Zeppelin and voila it loaded finally after a long pause on the black screen. I deleted the loading audio and voila it loads after about five seconds. So consider this thread solved, closed, resolved. Is there any chance we could get PinballX to close the loading audio after a short play and therefore eliminate this issue in the future? On my trip I had noticed @scutters helped another user with the same problem so I suspected for the last few days that the loading audio was my issue. I am certain that some of my other tables have a loading audio long enough to be slowing down the load. In fact Led Zeppelin loads so fast now that I may consider just removing all my loading audios until a solution is found. I have another quirk that I have noticed on the newest release but will start a new thread for that issue. Many thanks to @Mike_da_Spike, @scutters and @Tom Speirs. You guys are very much appreciated.

I can launch from DBM. When doing that I see PinballX initialize and then the table successfully launches. I’ll post the log when I get back from my work trip.

I have confirmed. If I launch directly from VPX they work. Also if I launch from Database Manager they work. I am eager to get back home and set a 30 second delay for buggy tables option. Maybe my PinballX just isn’t waiting long enough on slow loading tables.

I'll fix this. Could you take a screenshot of your visual pinball paths in the PinballX setup manager? I am not sure exactly how to format the executable to match your suggestion. When I click on the help menu to the right it doesn't show [filename] as a readable option. It only shows [tablename] and some others. It is interesting to see your log attached above and see how you are managing your setup. I've got to check out the statistics plugin and I see you are loading the ini files with the table. If I don't have that command is PinballX preventing the ini files from being loaded when the table is loaded? I think VPX 10.7 introduced those files to control the POV and I have saved some but not set PinballX up any differently. Also, while sleeping I remembered seeing in the documentation that the example setup had an additional 30 second wait for table opening. I don't have an additional wait set in my system. Maybe PinballX isn't giving the table enough time to load in my system. I'll change when I get home.

Very cool! Thanks for the tip. I placed them all back in the plugin folder and disabled as per your instruction. It looks like the DOF plugin is the only one I really need active. PinballX funcions like I expect with only that one plugin active and sure loads a few seconds faster. I did not solve my root problem however. Leaving for a five day work trip in a few hours so I'll be AWOL for a while. I'll implement any suggestons on my return. log.txt

I wasn't sure how to disable all plugins so I removed the following dll's from the plugin folder. DirectOutput PinballX PBX LoadingImage Pinballx Direct Output PlugInLED PlugInSpeech QuickLaunch(PinballX Edition) No change to the fact that some tables hang up while loading. But PinballX itself is sure loading faster! I need to research which of these PlugIns are outdated and not needed anymore. I'll include the new log file. log.txt

Long time user of PinballX and really love it. I have an isolated problem. One table (that I know of) is not loading properly when selected. It goes into the loading screen and after about sixty seconds my main playfield just goes dark. B2S and Topper keep playing, I have to restart computer to continue. All other tables seem to be loading properly (I haven't tried all 256). I just downloaded the new version of Led Zeppelin Original and no change in performance. The log just stops with the loading command. I can not find any logs showing a crash or fault. I will attach my logs. When I open Database Manager and open from there the table launches fine. If I launch PinballX and try to open from the wheel it gives me the loading screen but then the main monitor just goes black. If I use "control+alt+tab I do not see the table running. So somehow it is dumping the load of VPX at some point. I tried using an alternate exe (VPX86) but still no good. Any help is appreciated. Here is link to table https://vpuniverse.com/files/file/5940-led-zeppelin-pinball/ I am running VPX 10.8.0, PinMame 3.7.0.46 all in 64 bit but have tried the 32 bit exes also. Going through my wheel I found another table with same issue-"Beat The Clock". I am attaching that PinballX log because it shows me loading several tables and then getting to the bad load. It is more obvious where the load is hanging up. It does seem that if I hit control+alt+tab I can see VPX editor running. I tabed to it and if I hit the play button the table will load. So could the process be getting interruped before the table finishes loading? log.txt [SETTINGS].log PinballX.ini log.txt

Hey guys, I'm an avid arcade dude from the 80's! I've built a virtual pinball cabinet running PinballX front end. I have also built two stand up Galaga themed cabinets running the cheap jamma based emulators available. I hate the crummy user interface in these cabinets. Has anyone designed a jamma board that runs GameEx? Ideally one that would plug and play in my cabinets that are running above mentioned hardware. Thanks

I have a feature request I would like to propose. The request is in regards to how "hide backglass" affects the recording of table videos for the media folders. Myself and I suspect others, use the backglass videos in the front end wheel and continue to let them play while the selected table is loading. The result is that the user sees a seamless transition from the wheel to the actual loaded table. The alternative to this experience is a loss of the selected backglass while the selected table is loading, ruining the illusion of a seamless transition from browsing to playing. The way this illusion is achieved is by deselecting "hide backglass" for the individual table in Game Manager or Database Manager. With this method the backglass video from your PinballX media folder plays and then is covered up by the B2S when the table loads. Be cautious with Pinup Player tables as those videos will conflict with the backglass video and therefore the traditional method of "hiding backglass" must be used in this instance. The issue arises that when recording table media in Game Manager or Database Manager the "hide backglass" option MUST be checked in Game Manager. As far as I can tell this is a requirement for me to get a fresh backglass recording. I have tried several combinations and this is the option that works. If "hide backglass" is not selected in Game Manager then PinballX will skip the backglass when recording media. I realize that using the bulk video recording has worked for some but I would rather not use bulk video recording as a habit. EDIT AS REQUESTED IN BELOW COMMENT: Mike_da_Spik points out that Database Manager does work when using Bulk Video Recording method. My request is to divorce this backglass selection from the recording code. It seems that if the user has selected to record the backglass in the general settings then there should not be a secondary consideration. I realize that I have found a work around but I would like the community and Tom to give consideration to this request in the pursuit of avoiding the work around. Thank you for your great work here, Lane

Thank you for the explanation. Humor me for a moment as I describe why I don't hide the backglass expcept on Pup pack tables. If you "hide backglass during game" 1) You browse tables in the front end and see the table, backglass, topper, DMD etc. change with the table. 2) When you select a table the backglass goes "blank" and only the table loading media is shown. In my case a table video. 3) Upon completion of table loading the B2S and the table are active. If you Don't "hide backglass during game" On step 2 above the backglass video remains while the table is loading and you do not get the glitch of losing the backglass while loading On step 3 above the B2S is on top of the backglass video so you actually see the B2S and the scoring and forget the backglass video is there To me it is a more prototypical experience to not have the backglass go "blank" while waiting for the table to load. Now with pup packs I must hide the backglass video because it doesn't play nice with the pup player and they fight each other for screen priority. But in summary you guys are the ones putting the effort into this product so I only offer an opinion. Manipulating the settings for recording is no big deal now that I realize what I must do. Thank you for all you guys do and just consider the above if it is a worthwhile consideration.

I don't think it has always been this way but for the last six months I have had trouble recording backglasses. My log would show "Not Hide Backglass!" and then in the recording area of the log it would show "playfield video exists" " DMD video exists" and would not even show that it checked for a Backglass. I started really noticing this when I started using Database Manager and was cleaning up my media files and tidying up my front end. Today I tried multiple combinations of PinballX settings and Game Manager and Database Manager. I have discovered that "hide backglass" must be checked (selected) in Game Manager for PinballX to look for a backglass video and if one is missing make a recording. I prefer leave the backglass visable so there is a seamless transition between loading and game playing. Of course, now I know to make sure it is "hidden" when recording videos for front end and then uncheck that selection. My question is "why". Why must "hide backglass" be selected in Game Manager to get a backglass recording using the single table "record video" button? Could a change be implemented so that the "hide" features don't effect the recordings? Thanks guys! log.txt DBManagerLog.txt PinballXDatabaseManager.ini PinballX.ini

EDIT: Don't spend any time with this issue. I am not recording new backglasses no matter how I configure or what EXE is use. My recording issue is local to me and a real head scratcher. You are correct with the above description. Regarding bulk videos. I am just hesitant to start a bulk process. I have my frontend neatly arranged and beautiful. I'd rather not let any executable start rearranging on my behalf. Just me.

Using Database Manager - Back in July I reported I was not able to get my backglass to record a video and place it in the media file for the frontend use. Playfield and DMD were recording but no backglass recording attempted. You reported that I should "uncheck" "hide backglass during gameplay" in the default setting and in the individual game setting while recording videos. I never do bulk recordings. I record as I add tables, one at a time. I was still unable to get this feature to work, irregardless of how I treated the hide backglass in database manager. This moring I worked on it again. I discovered that I must use the legacy PinballX Game Manager and uncheck "hide backglass" for Goldeneye table. Once I did that I was able to record backglass as expected. It leads me to believe that at least on my system Database Manager is not playing well with PinballX when it comes to "hide backglass" options. It could be just a local problem with my system. I am sure others would be mentioning it if there was a coding issue.

I continued to struggle with this. I could not get my backglass to record a video irregardless of the settings on "hide or not hide". However, I discovered my problem this morning. I had to uncheck "hide backglass during game" in the settings for PinballX using the legacy settings exe. Evidently Database Manager was not overwriting this particular setting in PinballX on my system. I have not tested on additional tables but I was able to record a backglass for "Goldeneye" this morning after unchecking "hide backglass" in the PinballX "Settings EXE".

Here is my PinballX Future Pinball xml if that helps. Future Pinball.xml

Guys, Thanks for the update! I am getting an error message while loading Database Manager this morning. It was not present before the update. I believe from the log it has to do with my Future Pinball Database. Could you comment on what the issue might be please. I seem to have all the Future Pinball tables that are listed in my database and have not altered my Future Pinball tables in months. The message does not seem to be a fatal error but my OCD side hates to see "red"! DBManagerLog.txt

Thanks for figuring out what is going on! I have unselected the "hide backglass during game" because I want a seamless loading experience. It is my thought that the backglass goes blank during the game loading pause if this is checked. I will check this box while recording videos going forward. I am glad to see that the problem is just an error on my part. Thanks again!

@Mike_da_SpikeThanks for taking a look. PinballXDatabaseManager.ini