User Tools

Site Tools


puppack_troubleshoot

Trouble Shooting Pup-Packs

PuP-Packs are a combination of videos/media and config files to work with tables so that the media will play during gameplay.

There are actually 3 different methods Pup-Pack authors can choose to get it working.

1> table script (example: stranger things SE edition). this is where total control of the PinUP Player system is controlled by vpx table script. You DO NOT use pinuppackeditor.exe to customize these tables, in fact if you try and create a b2spup file with these tables you will be screwing up the puppack config.

2>b2splugin. This is where the puppack grabs events from table like 'switch 13' is triggered. You can then have video/sound play when that switch is triggered. This is great as it involves no table script changes and can be distributed without any care about which table version or table script is running. It works solely on the romevents. Limitation is that it is difficult to make a really 'top-quality' puppack using just romevents. Table script interface give you more 'fine-tuning' than just rom events.

3>PuPCapture: this is a great way and usually the best to use now if you don't know table script PuP interface. Using Freezy DMD DLL interface v1.7.1 or newer PinUP will 'scan/match' frames and trigger events that way. This allows a lot of great flexibility like knowing when multi-ball starts/ends, jackpots… all without knowing rom events/switch #s. etc.

ok. regardless of the method. to install a puppack you need to unzip/copy the rom_folder_name to your PuPVideos subfolder of PinUPSystem.

it will look something like this for trn_174h puppack

c:\PinUpSystem\PuPVideos\trn_174h

in this folder is where the media is (you should NOT have it like this: c:\PinUpSystem\PuPVideos\trn_174h\trn_174h… that would be WRONG)

Ok, so assuming you followed the PinUP System install videos on this site and placed the puppacks. Starting/Launching the tables should work automatically.

Most important: Make sure you have Freezy Setup to latest v.1.7.1 or newer. See Here:

BUT here are some things you need to check if things don't work.

PinUPPlayerB2SDriver:

Make sure your B2S is set to allow plugins: right-click on a backglass and make sure these settings are set like this:

You should also press the plugin settings and make sure is says PinUP Player 'active' with no errors. (you will need to restart vpx editor/table after you change settings)

Other items:

Make sure you have dmddevice.ini setup correctly and is located in your vpinmame root folder!. see: http://www.nailbuster.com/wikipinup/doku.php?id=upgrade_freezy

For PuPCapture tables you need to make sure 'Use External' is set when you press F1 (vpinmame) setup within game.

If your videos looks scaled or shifted, then make sure ALL your monitors in windows are set to 100%dpi (no scaling).

Also, you may think you have a PuP-Pack working but could be missing 80% of the videos. A PuP-Pack can use a combination of rom_events and PuPCapture frames. so you may only be seeing the rom_events videos.

Start the table you may be having a problem with. then exit the table.

go to you vpinmame folder and examine the PUPLOG.TXT file. (this file is created each time a table is launched).

Here a good sample of what Avatar will look like:

20180712 13:16:18 Open called
20180712 13:16:18 Set Game Name thread avr_200
20180712 13:16:18 Start Thread Matching
20180712 13:16:18 create PuPCap
20180712 13:16:18 Init Game name:avr_200
20180712 13:16:18 Create Object Display
20180712 13:16:18 imagedir:C:\VISUAL~1\Tables\PINUPP~1\PuPVideos\avr_200\PuPCapture
20180712 13:16:18 num images 49
20180712 13:16:22 Free Object Display

if you don't have a puplog.txt file then you are not configured correctly.

Make sure there are no blocked dlls in your vpinmame folder like the 'dmddevicepup.dll'.

also, if you are NOT using freezy dmddevice.dll, like perhaps you are using luckys' pin2dmd dmddevice.dll then you will not be able to use any puppacks that use PuPCapture (most will in the future).

Performance:

If you have video stuttering or artifacts with PuP-Packs with VPX… you most likely don't have VSYNC properly setup in VPX. Set “FPS Limiter/VSYNC” to 1, and “Maximum Pre-Rendered Frames” to 1 in VPX Video Options. This can also be set per-table in the Table's “User Customization” options, so check that as well.

Also, other VPX Videos settings can cause issues in VPX if your system is not able to handle running VPX and a some of the more demanding PuP-Packs. Things like brute force AA, Ambient Occlusion, and the Reflection options can severely affect performance, and its a good idea to disable those options, unless you have a high end system. The following is a good reference for how you should have your VPX video setting for good performance, using exclusive fullscreen (change the resolution for your screen):

Having certain programs running in the background can also cause issues as they may interfere with VLC or prevent Overlays from displaying. Try closing out other programs / processes to see if that helps resolve any issues.

Now that you know the basics of getting PuPPacks up and runnings… watch the videos here to get to know all the customized features you can use with PinUpPlayer.

http://www.nailbuster.com/wikipinup/doku.php?id=pup_capture

When I close a table with a PuP-Pack the media continues playing (won't close) when I return to frontend.

Some things to try:

  • pinupmenu.exe needs to be run as admin (and nothing else in PinupSystem folder)
  • UltraDMD tables. Some of these tables don’t have a proper closing or exit part added to the table’s script
  • you may have something else causing an error in the background that you may not notice.
  • SAM (Stern) tables and at91jit can cause issues for some people and cause crashing
  • the PuP-Pack may be too much for your system to handle, so it didn’t exit out properly after having some kind of crash.
  • FX3 tables using dmdext and pup / doflinx can’t have dmdext run as admin, or the pup-pack won’t close out when exiting the table.

With Popper make sure your VPX exit key is not the same as Popper Exit Emulator Key.

If it happens only on some tables, it could be a problem with the VPX Table script not closing out B2S properly.

Open up VPX Table Script and look for a sub like this. You want to make sure it has Controller.Stop line in there somewhere. If Sub doesn't exists you may have to add it.

Sub table1_Exit
    if B2SOn Then Controller.stop
End Sub
puppack_troubleshoot.txt · Last modified: 2018/11/11 22:44 by 174.114.169.127