Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
CarnyPriest

SAMBuild3.3 beta thread

Recommended Posts

Latest SAMBuild for the version 3.3 cycle can be found in this post. 

The package includes the latest external DMD dlls if there has been a recent update. Or else find the external DMD dlls with the beta thread for the official VPinMAME build here:

http://www.vpforums.org/index.php?showtopic=27063&page=1

OR

at lucky1's GitHub repository for Pin2DMD here:

https://github.com/lucky01/PIN2DMD/tree/master/integration/pinmame 

OR

freezy's dmddevice.dll which provides full color DMD support for virtual DMD as well as hardware DMD (i.e., LED panels):

https://github.com/freezy/dmd-extensions/releases

 

Copy the files into your VPM directory, and run setup.exe again. There, press the install button (with each new build) and remember to setup the defaults again!

In case you have an external DMD connected that you want to use with VPM, please move the dlls from the respective subdirectory (Pin2DMD or PinDMD1 or PinDMD2 or PinDMD3) directly into your VPM directory!

Commits to official source:

https://sourceforge.net/p/pinmame/code/commit_browser

 

official rev r5150

 

 

 

 

 

 

 

 

 

 

SAMBuild_r5150.zip

  • Like 15
  • Upvote 1

Share this post


Link to post
Share on other sites

With the new VPMAlias feature, the full clones previously supported in the SAM branch can be assigned an alias that will enable VPM to load the romset using the official set name and still use alternate DOF configs, B2S, altcolor, PupPack, etc. All other differences have been incorporated into the official source, and I no longer maintain a separate code repository.

Commits to the official source can be found here:

https://sourceforge.net/p/pinmame/code/commit_browser

Just to avoid further confusion, I'll just keep calling it SAMBuild but note that it is identical to the official build except that I toggle on support for Stern color rom patches in the compile.

PinMAME64.exe is the 64bit version of the executable which I provide for romset audits. There has been a change in the source that prevents me from completing the 32bit compile.

Built with VS 2015

 

Official rev r4890

The package includes VPMAlias.txt from the source code with entries for the four clones from SAMBuild. 

The layout is simply alias name followed by comma followed by romset name for the set that you want to clone.

All other support files and documentation can be found in toxie's release at the VPForums link above.

SAMBuild_r4890.zip

  • Like 4

Share this post


Link to post
Share on other sites

Understand what you're saying. But, not being able to compile the 32bit version. Would that not become an issue fore at91jit ? I seem to remember that you mentioned that it didn't work as expected for 64bit ? Getting old, so maybe I've missed something down the line.

  • Like 1

Share this post


Link to post
Share on other sites

It’s only an issue if you need JIT for the executable version. I only use the executable version to audit rom sets with clrmamepro native PinMAME support. The dll version is still the 32bit version that you know and love.


Sent from my iPhone using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites

official rev r4895

Support 4-solenoid stepper motor mech used by High Roller Casino, Starship Troopers, and Playboy. [DJRobX]

update to BASS 2.4.15 [toxie]

new BASS libraries included in the package

SAMBuild_r4895.zip

  • Like 9

Share this post


Link to post
Share on other sites

I can't seem to get my colorized TAF_L7 Rom to display with latest PinMAME (VPX 10.6 win10x64).  I was able to get a different TAF rom to work, but not the latest L7 rom.  I'm using External DMD checked in the options.  I have tried on 2 different pincabs with same results.  After updating to latest PinMAME, DMD doesn't display.  I can get my other COlor and non color roms to work fine.  Please tell me others experience this.  Thanks

Share this post


Link to post
Share on other sites
Looks like it's working for me - TAF_L7

 

20200108_134032.jpg

Share this post


Link to post
Share on other sites
For the hell of it did you try to go back to 3.2 to see what happens

20200108_134032.jpg

Share this post


Link to post
Share on other sites

Thanks for the replys, Funny I just copied all my visual pinball, pinball x, over to my mini pin and its all working after updating the dmddevice.ini since I don't have a 4k on the minipin.  Seems to be working fine on that machine, which was not working 2 hours ago with older stuff, strange.  maybe something tied to running windows desktop at 125% scale on playfield (4k) as my eyes are getting bad.  I know that was always a no/no, but it seemed fine after a few changes to the dmddevice.ini file.  Still investigating but now know its me, phew I guess. :)

Share this post


Link to post
Share on other sites

Mystery continues, I figured out why my MiniPin worked, I forgot I changed the script in the Table to load up tafg_lx3 instead of taf_l7.  This does work for me in VpinMAME 3.3, but when I change the script back to load taf_l7 rom, no dmd is displayed.  I then tried to install VpinMAME 3.2, unblocked vpinmame.dll, reran setup and tried again.  DMD works, very strange.  Is everyone sure they are running 3.3 of vpinmame and ran setup.exe?

 

Share this post


Link to post
Share on other sites

Is everyone sure they are running 3.3 of vpinmame and ran setup.exe? --- Yes

Untitled.jpg

Share this post


Link to post
Share on other sites

Thanks, so strange.  I have gone back to 3.2 for now.  maybe I will look through the dmddevice.log and see something odd.

Share this post


Link to post
Share on other sites

Are you using PinSound? 

The BASS dll changed, and that's what is used for altsound.  If you were to try a different ROM, the altsound config will be different...

  • Like 2

Share this post


Link to post
Share on other sites

No PinSound, using the new bass.dll that came with 3.3, still works with 3.2.  I do see that I have a bass.dll in both my Visual pinball directory and also my PinMame directory.  Is that normal, should I delete the "older" one from my visual pinball directory?

 

Share this post


Link to post
Share on other sites

wooohoooo, Got it very close to working.  I have dmd working witthin the vpinmame setup testing option.  I deleted the bass.dll from my visualpinball directory, copied over the new 3.3 files into vpinmame directory.  But now when I run VPX editor, I get an error about missing bass.dll.  So I copied the bass.dll from the 3.3 vpinmame zip to visual pinball, now runs, but no DMD.  At least I'm getting somewhere.  Does everyone have 2 copies of bass.dll? seems wrong.

Thanks

 

 

Share this post


Link to post
Share on other sites
Yes I have bass.dll in both areas it comes with both pieces of software..

Do you have some unusual software running and//or hardware

  • Like 1

Share this post


Link to post
Share on other sites

I got it working fine on another computer, only real difference is this computer only has 1 display (1080p), but I' still using the external dll option in vpinmame and everything works fine.  I really hate computers sometimes.  So my next question is does anyone have this working on a pincab or a computer with multiple screens?  Only thing I can think of now.

Share this post


Link to post
Share on other sites

Up until now I've tested  the working status on my pincab that has 2 monitors.

  • Like 1

Share this post


Link to post
Share on other sites
On my cab I by have a 3 Screen setup plus a pin2DMD all Work fine.
Have you tried installing 3.3 but then replace the base.dll with the one from VP Or the one from 3.2

 

Share this post


Link to post
Share on other sites

good idea, trying that now.  Sadly no change.  I tried deleting freeway->vpinmame registry and rerunning setup, still same.

One strange thing is that if I run the Test inside the vpinMAME->setup.exe, the dmd is displayed.  When I run inside VPX nothing.  Might be something with my Pinup setup.  here is my log

 [7] 2020/01/09 13:09:04.471  INFO | Determined color path from assembly path: C:\Visual Pinball\VPinMAME\altcolor 
 [7] 2020/01/09 13:09:04.491  INFO | Starting VPinMAME API through VPinballX.exe. 
 [7] 2020/01/09 13:09:04.491  INFO | [vpm] Open() 
 [7] 2020/01/09 13:09:04.491  INFO | [vpm] Set_4_Colors_Palette() 
 [7] 2020/01/09 13:09:04.491  INFO | Setting palette to 4 colors... 
 [7] 2020/01/09 13:09:04.491  INFO | [vpm] PM_GameSettings(1) 
 [7] 2020/01/09 13:09:04.491  INFO | Enabling game colorization 
 [7] 2020/01/09 13:09:04.491  INFO | Setting game name: TAF_L7 
 [7] 2020/01/09 13:09:04.491  INFO | Setting color: #FFFF5820 
 [7] 2020/01/09 13:09:04.506  INFO | Loading palette file at C:\Visual Pinball\VPinMAME\altcolor\TAF_L7\pin2dmd.pal... 
 [7] 2020/01/09 13:09:04.506  INFO | Loading virtual animation file at C:\Visual Pinball\VPinMAME\altcolor\TAF_L7\pin2dmd.vni... 
 [7] 2020/01/09 13:09:04.580  INFO | Loaded animation set VPIN v4, 596 animation(s) 
 [7] 2020/01/09 13:09:04.580  WARN | Ignoring video renderer for non-existing path "PinUP" 
 [7] 2020/01/09 13:09:04.580 ERROR | No renderers found, exiting. 
 [7] 2020/01/09 13:09:11.398  INFO | [vpm] Close() 
 [7] 2020/01/09 13:09:11.398  INFO | Closing up. 
 

 

No renderers found, exiting -> seems wrong.

 

 

Share this post


Link to post
Share on other sites

here are my 2 log files, only difference is 3.2 installed vs 3.3 beta of vpinmame.

Good 3.2 one:

----------------------------------

 [1] 2020/01/09 13:46:54.837  INFO | Determined color path from assembly path: C:\Visual Pinball\VPinMAME\altcolor 
 [1] 2020/01/09 13:46:54.860  INFO | Starting VPinMAME API through VPinballX.exe. 
 [1] 2020/01/09 13:46:54.860  INFO | [vpm] Open() 
 [1] 2020/01/09 13:46:54.866  INFO | [vpm] Set_4_Colors_Palette() 
 [1] 2020/01/09 13:46:54.866  INFO | Setting palette to 4 colors... 
 [1] 2020/01/09 13:46:54.866  INFO | [vpm] PM_GameSettings(1) 
 [1] 2020/01/09 13:46:54.866  INFO | Enabling game colorization 
 [1] 2020/01/09 13:46:54.866  INFO | Setting game name: taf_l7 
 [1] 2020/01/09 13:46:54.881  INFO | Setting color: #FFFF5820 
 [1] 2020/01/09 13:46:54.881  INFO | Loading palette file at C:\Visual Pinball\VPinMAME\altcolor\taf_l7\pin2dmd.pal... 
 [1] 2020/01/09 13:46:54.897  INFO | Loading virtual animation file at C:\Visual Pinball\VPinMAME\altcolor\taf_l7\pin2dmd.vni... 
 [1] 2020/01/09 13:46:54.963  INFO | Loaded animation set VPIN v4, 596 animation(s) 
 [1] 2020/01/09 13:46:54.963  INFO | Opening virtual DMD... 
 [7] 2020/01/09 13:46:55.027  INFO | Added VirtualDMD renderer. 
 [7] 2020/01/09 13:46:55.027  INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False 
 [7] 2020/01/09 13:46:55.027  INFO | Just clearing palette, colorization is done by converter. 
 [7] 2020/01/09 13:46:55.041  INFO | Resizing virtual DMD to 128x32 
 [7] 2020/01/09 13:46:55.041  INFO | Setting up 2-bit Colored VPM Graph for 1 destination(s) 
 [7] 2020/01/09 13:46:55.077  INFO | Connecting 2-Bit Colorizer to Dmd (ColoredGray2 => Rgb24) 
 [7] 2020/01/09 13:46:55.085  INFO | Connecting 2-Bit Colorizer to Dmd (ColoredGray4 => Rgb24) 
 [7] 2020/01/09 13:46:55.085  INFO | Setting up 4-bit Colored VPM Graph for 1 destination(s) 
 [7] 2020/01/09 13:46:55.085  INFO | Connecting 4-Bit Colorizer to Dmd (ColoredGray2 => Rgb24) 
 [7] 2020/01/09 13:46:55.085  INFO | Connecting 4-Bit Colorizer to Dmd (ColoredGray4 => Rgb24) 
 [7] 2020/01/09 13:46:55.085  INFO | Setting up RGB24-bit VPM Graph for 1 destination(s) 
 [7] 2020/01/09 13:46:55.101  INFO | Connecting VPM RGB24 Source to Dmd (Rgb24 => Rgb24) 
 [1] 2020/01/09 13:46:59.661  INFO | [vpm] Close() 
 [1] 2020/01/09 13:46:59.665  INFO | Closing up. 
 [1] 2020/01/09 13:46:59.679  INFO | Source for 3 renderer(s) stopped. 
 [1] 2020/01/09 13:46:59.679  INFO | Source for 3 renderer(s) stopped. 
 [1] 2020/01/09 13:46:59.679  INFO | Source for 1 renderer(s) stopped. 

=================================================================

bad 3.3 one

----------

 [1] 2020/01/09 13:45:08.555  INFO | Determined color path from assembly path: C:\Visual Pinball\VPinMAME\altcolor 
 [1] 2020/01/09 13:45:08.579  INFO | Starting VPinMAME API through VPinballX.exe. 
 [1] 2020/01/09 13:45:08.579  INFO | [vpm] Open() 
 [1] 2020/01/09 13:45:08.586  INFO | [vpm] Set_4_Colors_Palette() 
 [1] 2020/01/09 13:45:08.586  INFO | Setting palette to 4 colors... 
 [1] 2020/01/09 13:45:08.586  INFO | [vpm] PM_GameSettings(1) 
 [1] 2020/01/09 13:45:08.586  INFO | Enabling game colorization 
 [1] 2020/01/09 13:45:08.600  INFO | Setting game name: TAF_L7 
 [1] 2020/01/09 13:45:08.600  INFO | Setting color: #FFFF5820 
 [1] 2020/01/09 13:45:08.600  INFO | Loading palette file at C:\Visual Pinball\VPinMAME\altcolor\TAF_L7\pin2dmd.pal... 
 [1] 2020/01/09 13:45:08.619  INFO | Loading virtual animation file at C:\Visual Pinball\VPinMAME\altcolor\TAF_L7\pin2dmd.vni... 
 [1] 2020/01/09 13:45:08.678  INFO | Loaded animation set VPIN v4, 596 animation(s) 
 [1] 2020/01/09 13:45:08.697 ERROR | No renderers found, exiting. 
 [1] 2020/01/09 13:45:13.036  INFO | [vpm] Close() 
 [1] 2020/01/09 13:45:13.040  INFO | Closing up. 
 

 

Does this help to give a clue whats going on?  I'm stumped :(

Share this post


Link to post
Share on other sites

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...