This member have not add any projects yet.

See all projects

This member have not add any works in progress yet.

See all wips

You need to log in or to post to this user's Wall.

  • Check that in-game Ambient Occlusion is off (and verify that the table setting in Backdrop Properties is also off).

    If your ball is not smooth with vsync on, you’re not maintaining 60fps consistently, regardless of what the F12 display says.

     

  • The all in one installer referenced in this thread is old, you should start with the newer one with VP 10.2 that can be found on VPForums.

    To play some of the Stern games you’ll need to replace VPinMame after that, but it’s still a good idea to install the all-in-one installer first as it installs a number of…[Read more]

  • Let’s back up a minute.  Why are you wanting to disable the backglasses?

    If it’s for performance reasons, then deleting the directb2s file is the easiest way to go.   Under HyperPin it will leave a static (non-moving) image up, which doesn’t hurt performance at all but still gives you the benefit of having an image up there.   PinballX can do t…[Read more]

  • Let’s back up a minute.  Why are you wanting to disable the backglasses?

    If it’s for performance reasons, then deleting the directb2s file is the easiest way to go.   Under HyperPin it will leave a static (non-moving) image up, which doesn’t hurt performance at all but still gives you the benefit of having an image up there.   PinballX can do t…[Read more]

  • It looks like you are trying to run the old PRO table with the LE rom, and it’s choking on the additional lighting information it’s not expecting.   Make sure the cGameName is twd_156 not twd_156h.

     

  • Ooh!   Early Christmas presents!   :good:

    Man does this ever look great!  And it plays just as good at is looks.   Great job!

  • Ooh!   Early Christmas presents!   :good:

  • If PWM flashers are used in DOF, there will be “NoBool” hints in the config that tell it that it is looking for a 0-255 value, instead of 0-1.   But the “classic” boolean method sends 1, and DOF responds by lighting the light very dim.  DOF config tool only has one table config per ROM, there’s no way to support both in one profile.

    The s…[Read more]

  • If PWM flashers are used in DOF, there will be “NoBool” hints in the config that tell it that it is looking for a 0-255 value, instead of 0-1.   But the “classic” boolean method sends 1, and DOF responds by lighting the light very dim.  DOF config tool only has one table config per ROM, there’s no way to support both in one profile.

    The s…[Read more]

  • If PWM flashers are used in DOF, there will be “NoBool” hints in the config that tell it that it is looking for a 0-255 value, instead of 0-1.   DOF config tool only has one table config per ROM, there’s no way to support both in one profile.

    The simplest fix is to add Const UseVPMModSol=1 in the old table’s script.   You also have to ensure “…[Read more]

  • If PWM flashers are used in DOF, there will be “NoBool” hints in the config that tell it that it is looking for a 0-255 value, instead of 0-1.   DOF config tool only has one table config per ROM, there’s no way to support both in one profile.

    The simplest fix is to add Const UseVPMModSol=1 in the old table’s script.   You also have to ensure “…[Read more]

  • If PWM flashers are used in DOF, there will be “NoBool” hints in the config that tell it that it is looking for a 0-255 value, instead of 0-1.   DOF config tool only has one table config per ROM, there’s no way to support both in one profile.

    The simplest fix is to add Const UseVPMModSol=1 in the old table’s script.   You don’t have to further m…[Read more]

  • Load More
  • Facebook Auto Publish Powered By : XYZScripts.com

    DJRobX

    Profile picture of DJRobX

    @djrobx

    active 2 days, 6 hours ago
    Member