Jump to content


Popular Content

Showing content with the highest reputation on 04/20/2017 in all areas

  1. 1 point

    Street Fighter II

    You forgot to assign keyframes to the scenes you created. I uploaded a modified version. Which should export a fsq file also. Due to the crazy format Gottlieb is using to send the frames to the DMD there are limitations. You can only use frame replacement and palette switching which means you can´t add more colors to a scene with dynamic content like score etc. Is the display constantly alternating colors ? If yes you should try the other Gottlieb mode with pin2dmd.
  2. 1 point

    Making A Start - Safecracker :)

    Hi all, So - Whilst this sub-forum is primarilly about the Pin2DMD devices, I have one of the new DMD ST32's from PinballSp in Spain. Whilst this sounds like it's off topic, it still uses Lucky1's firmware, and still uses Steve's Pin2dmd editor, so no changes for those of you that are familiar with it Why Safecracker? Well it's something that colordmd arent going to touch with their range of LCD's since these are physically too big to fit. There is no spare room around the DMD above standard size, so until they come up with their rumored LED boards, and then code the thing, this IS the only solution Ok - so trying to get my head around this keyframe and pallette malarky (has anyone got a link to a decent youtube video that explains these and how they interact with pinball editor?? Steve's make sense to a point, however only seem to scratch the surface). I can grab the images using pinmame and the special file, so figured i would start with the standard attraction screens, and progress from there. The first question i have is - How do people cope with scrolling screens? SC scrolls a lot from right to left ( <-), and really i would like to have different pallets for different screens. Not sure on recommended techniques for when the screens scroll, and also capture of these from the Raw files. Any advice??? Thanks Paul
  3. 1 point

    SAMBuild2.9 beta thread

    PotC and Shrek cant´work with the dmddevice.dll from freezy, because the inframe colorization mechanism used by these tables is not public. No idea why tables don´t crash with freezys dll and crash with mine.on your machine. The tables work fine on my cab. The difference between patched and non patched ROMs is the self modifying code patch of sidechannel. This caused problems with the jit compiler in the past. So maybe setting at91_jit to zero helps. Use the search function to find more details about this option.
  4. 1 point

    Street Fighter II

    so, I dont know how to put the stuff on the SD card. I pick export project and its just a pal file, no dat file. The Capcom/SF animation isnt dont obviously.
  5. 1 point


    I uploaed a new version with some palette fixes
  6. 1 point

    StarTrek Pro

    I uploaded the colorization for ST Pro with the permission from Sharkky. LE Version is not finished. Happy Eastern
  7. 1 point

    Metallica 1.70 LE

    Version 1.0.0


    About This File ROM File patch for Stern Metallica LE by J_M To create the needed ROM file you can use bspatch (http://www.daemonology.net/bsdiff/) Place the .pal file in your ..\vpinmame\altcolor\mtl_170hc\ folder named pin2dmd.pal Patch needs vpinmame V2.9, latest dmddevice.dll and pin2dmd firmware >= V2.36. THIS PATCH DOES NOT WORK FOR REAL PINBALL MACHINES ! PLEASE CONTACT THE AUTHOR IF YOU NEED IT FOR A REAL PIN !
  8. -1 points

    Version 1.02


    VPU Patching System What is the VPU Patching System: The VPU Patching System is a way to provide modified tables without having to re-distribute the original creation. This method was created to allow our Direct Output admins to add DOF compliance to existing tables. Patches created using this system requires the original un-modified version of the table release. Each patch created should come with a "ReadMe.txt" file that shows the URL to download the original table that the patch is based on. Usage: 1. VPPatch comes in both a 32bit executable as well as a 64bit executable. Download the correct version of VPPatch for your processor. 2. Extract folder and files to your hard drive. You may place the extracted folder wherever you prefer. 3. Double click on the VPPatchXX.exe to start program. To Apply a patch: a. If you do not already have the table that the patch was created for; you will need to download that file. Read the "ReadMe.txt" file that comes with the patch download. The file should contain a link to the original file that the patch is based on. b. Make sure that you are on the "Apply Patch" tab located at the top of the window. c. Under "Original Table (Unmodified)". Click on "Choose" and then select the Original Unmodified Table that the patch was created for. d. Under "New Table Patch" click on "Choose" and select the patch file (.dif) that you want to apply to the table. e. Under "New Table File Name". Type in the name that you want to call your new table. Make sure that the file name ends in .vpt. f. Click "Apply Patch" - You will get a pop-up window indicating the location where your new file was created. This should be in the "mods" folder located in the same folder as the VPPatchXX.exe. To Create a patch - For table authors/modders: a. When updating or modding your table; Do not save over your original file. Save your file as a new file and use this new file for your updates or modifications. This application will compare the original file, with your update file, and it will output a new file (.dif) that includes ONLY your changes. Depending on the types of updates/mods; these files are normally smaller than the original file and will save bandwith. b. Click on the "Create Patch" tab located at the top of the window. c. Under "Original Source"; select the "Original un-modified table". d. Under "Modified Source"; select the file in which you did your updates/modifications to. e. Under "Dif Name"; type in what you want to call this patch and make sure that the file name ends with a .dif file extension. ex: Table_mod_v1.02.dif f. Click on "Create Patch". This will pop-up a command window; that may be blank. This is temporary for now, but this indicates that the patch creation is working. Depending on the changes it may take a minute or two for the patch (.dif) to be created. Once completed the new patch file will be located in the "difs" folder located in the same folder as the VPPatchXX.exe. g. When distributing a patch file. Please create a "ReadMe.txt" file along with your patch. Please make sure that the readme includes the name of the original file, as well as a URL where the user can download the original file that the patch is based on. 4. Hit the X on the window or the Esc button on your keyboard to close the application. Notes: If you use a patch on a table that it's not intended for, or a table that has already been modified, then applying the patch will have un-expected consequences. To Do: CRC validation against original source table. Add progress bar to show status when creating patch. Special Thanks: Thanks to Rascal for being an excellent member of the VPUniverse community. This application is a work based on his proof of concept for using dif files for patching VP tables. Thanks to Rascal for helping test this application and giving his valued input. Thanks to Members of VPUniverse.com for thinking outside of the box and advancing this hobby. Special Thanks goes out to each and every table author! If it wasn't for you; our hobby wouldn't be where it is today.