retrogamer01

Spot on, @Tom Speirs. I was able to isolate the issue to one of my Systems Logos that I added for Pinball Arcade. Without that file in there it works as expected. Thanks everyone for helping me resolve this. I suspect the next release will fix this also, but in the meantime I'm up and playing again!

Thanks @Tom Speirs, it's proving elusive but I'll keep looking for it. Thanks for addressing this in the code.

It works as expected when installed to a different directory with my config.ini file and the default media. When I move my media folder over to the new installation it exibhits the same behavior. I don't have any apng files on my system. I have ~700 tables worth of media though, so it's going to take a while to figure out what is corrupt. I'll start putting directories back one at a time until I find it.

Thanks for the quick reply. Redownloaded and installed with the same issue. log.txt and pinballx.ini attached. log.txt PinballX.ini

Running into this issue after upgrading from 4.7X. Crashes on launch with this in the logs. 19:29:01.42 1/29/2021: Error. Exiting 19:29:01.42 1/29/2021: 19:29:01.42 1/29/2021: File signature incorrect. 19:29:01.42 1/29/2021: at LibAPNG.APNG..ctor(Byte[] fileBytes, Boolean CreateFrameForSimplePng, Device Dev) 19:29:01.42 1/29/2021: at Direct2d.Surface.LoadSurfaceWIC(String Filename, Device Dev, MemoryStream ms) 19:29:01.42 1/29/2021: at Direct2d.Surface..ctor(String Filename, Device Device) 19:29:01.42 1/29/2021: at PinballX.FrmMain.RestoreSurfaces() 19:29:01.42 1/29/2021: at PinballX.FrmMain.InitDisplay(Boolean FullScreebWindowed, Boolean InitialLoad, Boolean IsIngame, Boolean WasLost, Boolean NoLog, Boolean CalledFromSelf, Boolean DontDisposeBlackForm) 19:29:01.42 1/29/2021: at PinballX.FrmMain..ctor()

[RESOLVED] In case anyone runs into this problem. I had VPMtoFront Hyperscript running from before when I was running Hyperpin. Once I migrated everything to PinballX, I forgot to remove this and I guess it has the opposite effect, sending the directB2S to the back.

Thank you for sharing your experience. I've standardized on static backglass images and table videos since I was unable to find backglass videos for all of my tables. I'd rather have a consistent flow rather than some tables with backglass videos and others with just images. So I'm not sure if it's the same. I've decided to uninstall pbX and start again this weekend. I don't remember this happening when i first moved from HP, so hopefully that's the answer.

I understand everyone's other responsibilities. The original post was about a month ago with no replies. I suspect that I might be the only one running into this hence trying to get it a little more visibility and if I'm still the only reply then I'll uninstall everything and try again. Just trying to save myself some cycles if this is a known issue.

Bump. Anyone else run into this? I upgraded to 1.87 and have the same behavior.

Not sure if it's a bug or just something I configured (or failed to configure). In the log BTTF displays the correct directtB2S and AFM's directB2S comes up and then is replaced by the static graphic or blank screen depending on the XML setting.

When a table is launched from PinballX, I'll get the initial load of the DirectB2S server and then a second later the static image defined in the Visual Pinball/Media/Backglass Images will be placed over the top. I've tried using the hidebackglass feature in the database XML, however instead of the static image, I'll get just a black screen over the top of the DirectB2S. I can alt-tab and find it and then return focus back to the table if I so desire. I've also found that there are some tables, namely the ones where the backglass provides for scoring or other features that seem to work and are not covered up by the image, however I can't find any consistency between those that work and those that do not. Currently running 1.85 if that makes a difference. Thanks!