Jump to content

Recommended Posts

Posted

I've got an issue with Last Action Hero from VPW, when playing that table at some point my DOF dies usually once starting a multiball. I've had another person online have to same issue but we have still not figured out a solution. Is anyone else having this issue? I've got solenoids, shaker, fan, beacon, strobes and RGB lights setup. I put a comment on the table thread at vpinuniverse but never heard anything back. Can someone else with full dof setup test this table? I cleared my dof log and played the game till DOF died and the errors i saw were the following. On Killer Instinct there was a "Cant parse the trigger part SE114" issue that i changed to E114. And on Men in black there was an error  "Cant parse the part 117" so i changed that to an E117. Last Action Hero fired up and played longer than normal but the DOF still died around the 10 minute mark. I've attached my most recent DOF log from this game. I don't see anymore errors but it still died with "WriteUSB failed". This is the only game I've seen this on however it used to die on Medieval Madness until the script change came around to fix the drawbridge. Im on the most recent VPX, Vpinmame, B2Sserver but have tried rolling back and still same issue. I really love this table but would like to figure this out. Thanks for any help

DirectOutput.log

  • 4 weeks later...
Posted

The Killer Instinct DOF has errors and will crash DOF.  I don't have this table so it doesn't affect me, but if you want to use DOF with that table then you'll need to edit the DOF to remove the errors.  You can test your DOF config ini files using the LedControlFileTester application in your DirectOutput folder.  It will list any errors found, so you can either delete that table completely, or fix the errors.  

 

Note that over at the VP Custom LED effects group (on Facebook) we have a custom, HD set of DOF LED effects for Killer Instinct that should work absolutely fine.

 

To solve your LAH problem, and assuming that the FileTester does not find an error, I'd start by progressively removing DOF config files - you may have multiple files depending on your setup.  I only have addressable LEDS set up via directoutputconfig30 and non-addressable LEDS and strobes via directoutputconfig.  You may have others too.  Rename them, one at a time (e.g. directoutputconfig30BAK.ini) and try playing LAH to see if the crash happens.  Once you figure out which part of your DOF setup is causing the crash, you may have more clues about how to fix it.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...