Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

If neither of those of work for you, you can donate any amount by clicking here.

Recommended Posts

Posted

Is there an installation and configuration FAQ somewhere for PinballX?  Game Manager?  I found a large pdf covering older versions, but I am trying to setup current v2.31 with Windows 10.

 

I have Visual Pinball working perfectly outside of Pinball X including PinDMD3, cab mode with 2 monitors (pf and bg).

When I first launch PinballX, the first table I try to load loads fine.  When I try to launch a subsequent  game in PinballX, the B2S backglasses get messed up, the game won't load, no DMD activity, no error boxes.  LOG files don't reveal anything funny, no differences between successful launch of first table and failed launch of second table.  The B2S backglass will display briefly, then it becomes blank but looks like DMD dots on the BG monitor.  It might flicker back to display the correct backglass image, then go back to dots.

I set Compatibility of VP9.9.3 to XP SP3, Run as Administrator.  Also have PinballX set to Run as Administrator.

 

I'm hoping an FAQ can help me, or someone in the forums.  If there are log files to post please advise.  I don't have the computer online so I'll have to copy over and post if needed.

 

Thanks in advance for the consideration.

 

Posted

The guide zeenon put together is the most current to my knowledge.  While perhaps not 100% relevant to Windows 10 and the current version, it should prove to still be a good source of information.

 

Posted

@tthurman and @outhere:  are you running on Windows 10 Home?

 

Thanks. I followed Zeenons guide except for:

   have not created killbackglass.exe because Windows 10 does not recognize tskill.exe

   have not created the .ahk file for the mouse click startup program

I have ensured all .exe files are Run As Administrator

did not use "Compatibility" settings for anything PinballX

I am still having issues.

I will try the create the killbackglass.exe and other compiled .ahk file as mentioned in Zeenons guide and try again.

Lastly, are there any .direct2bs settings I should use or not use?  I am doing defaults, which I believe are Launch as EXE.  I did try "Standard" by clicking on backglass and changing, but that did not change anything.

Thank you!

 

 

Posted

I think your case is unusual or you have gone overkill. Its pretty much plug n play as far as I have ever been aware. There should be no need to kill the backglass.

Your log and settings would help a lot. look at the signature above.

Posted

Thanks everyone.  I hate being "that guy" who asks for help but can't seem to figure it out.  I really appreciate the help.

 

Attached are log, ini and xml files.  Sequence is this:

Windows 10 Home 64

powered on computer

immediately launch PinballX

1st game run = Al's Garage Band.  It loaded successfully.  Exited game back to menu

2nd game run  = 24.  It loaded successfully.  Exited game back to menu. 

3rd game run = Al's Garage Band, again.  It loaded successfully.  I'm excited and thinking things are working.  Exit game back to menu

4th game run = 24.  This time it fails to load properly.  Backglass is messed up and game does nothing, vpinmame not running.  Exit game back to menu

5th game run = Al's Garage Band.  This time it fails to load properly.  Same symptoms as "24".  Backglass flashes briefly, then entire BG screen is filled with what I can best describe as "DMD Dots".  Playfield monitor shows table, but no activity / vpinmame not running.  Exit game.  Exit PinballX.  Copy log, ini, xml below.

Log.txt File:

  Reveal hidden contents

 

PinballX.ini file:

  Reveal hidden contents

 

Visual Pinball.xml file

  Reveal hidden contents

Thank you all so very much for looking at this.

Posted

Some additional info:

When the launched table is messed up, if I press CTRL-ALT-DEL and bring up the blue screen to choose Task Manager, when the blue selection screen is up, the PINDMD3 starts running.  When I choose Task Manager, which shows on the playfield monitor, the backglass monitor indeed displays the DMD data.  It takes up the entire screen - backglass is hidden but occasionally parts of it flash through briefly.

Also, in this state, Task Manager shows an ERROR box from Visual Pinball:

   Fatal Error:  HRESULT 88760868

   at RenderDevice.cpp:420

 

That box only appears when Task Manager is running.  BEFORE launching TAsk Manager, if I Alt-Tab around when the table is messed up, that dialog box is not there.  After launching Task Manager, the error box appears.

 

Hope that helps - Thank you!

Posted

Solved - Sort of...

I tried several things including:

- updating NVidia drivers and removing nVidea experience

- verifying .NET was current at 4.6.2

- unblocking all DLLs / files / directories

- disabling Windows Defender

- updating to latest VPINMAME

None of the above helped.

 

I did find a PinballX 2.29 setup program in another directory so I installed that.

v2.29 seems to work perfectly!

 

So, I -solved- the problem by reverting from 2.31 back to 2.29.

 

Tom - what is different between 2.29 and 2.31?  Is there anything I am missing by running 2.29?

 

Thank you so much!

Posted
  On 2/3/2017 at 9:24 AM, Tom Speirs said:

Pretty much nothing at all as far as I am aware. Just the expiry removal. Its odd,

Expand  

I think the real issue lay elsewhere.  I still am having some issues launching tables with directB2S backglasses and the score display showing properly, even with PinballX v2.29.  I got to thinking that the score display is really vpinmame display, so I went looking there.  I ran Setup for vpinmame and noticed under "Setup Paths..." the "Display" option was set to "DISPLAY2 on Nvidia GTX960".  I must have set that at some time but I don't recall.

 

Changing that to "[Default]" seems to have made all the difference.  The tables which consistently were problematic to load through PinballX are launching fine now.

 

I am guessing that when PinballX calls VPinball.exe and subsequently when vpinmame gets called. parameters are set, or registry settings are changed, stuff goes on behind the scenes that I have no idea about.  Perhaps not having "[Default]" for the vpinmame display was causing conflicts with whatever settings or parameters are sent from PinballX to Vpinball.exe to Vpinmame.exe...

 

Anyway, posting this observation in case it might help someone else in the future.

Guest
This topic is now closed to further replies.
×
×
  • Create New...